-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support OpenTelemetry collectors #14
Comments
This is done by using OpenTelemetry collectors, which I'm fairly certain Jaeger is being written to support natively. |
Any changes to flags need to be backwards compatible, so any PR that fixes this would have to mark the existing jaeger flags as hidden and introduce new ones. |
@jzelinskie: was this done in jzelinskie/cobrautil@21e5e5d? |
The changes to cobrautil have been made, but the SpiceDB still needs to add a new flag for it (because it's not backcompat) and then mark the existing jaeger flag as hidden. |
@cjs @christroger are either of ya'll still interested in taking this on? |
Yes we will take care of it. I think we also need to do another PR against cobrautil to fix an issue with getting some OTel parameters from the environment. |
As an update here, I opened a PR for the fix of the |
This also updates to a version that supports generic OpenTelemetry collectors. Fixes #14.
This also updates to a version that supports generic OpenTelemetry collectors. Fixes #14.
Issue authzed/spicedb#14 was closed in March - so updated docs to reflect that any OpenTelemetry Collector can be used.
Everything is instrumented using OpenTelemetry, but Jaeger is the only format exposed by command-line flags.
If it can be made generic enough, this could be upstreamed into cobrautil.
The text was updated successfully, but these errors were encountered: