-
Notifications
You must be signed in to change notification settings - Fork 28
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
Tracing enhancements #384
Tracing enhancements #384
Conversation
…n (string) becomes '-tags' (key-value pairs)
docs/user-guides/observability.md
Outdated
|
||
Integration with an OpenTelemetry collector can be enabled by supplying the `--tracing-service-endpoint` command-line flag (e.g. `authorino server --observability-service-endpoint=http://jaeger:14268/api/traces`). | ||
|
||
The additional `--tracing-service-tags` command-line flag allow to specify fixed agent-level key-value tags for the trace signals emitted by Authorino (`key1=value1[,keyN=valueN]*`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
have you considered supporting multiple flags? That would leave the parsing logic to the CLI lib.
authorino server --tracing-service-tags a=1 --tracing-service-tags b=2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not, but it's a good idea. It feels more Golang flags.
Done.
e71c1a9
to
eead461
Compare
…f comma-separated
observability-*
cmd-line flags renamed astracing-*
– so it's clear this is the only kind of signal being pushed, other types would require their own separate endpoints anywayseed
flag turned into a string array flag that accepts key=value pairs, renamedtag
Related to #163