Skip to content
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

fix: allow otel tracing provider in config #1039

Merged
merged 2 commits into from
Dec 1, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec/config.schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -1851,8 +1851,8 @@
"properties": {
"provider": {
"type": "string",
"description": "Set this to the tracing backend you wish to use. Supports Jaeger, Zipkin, DataDog and elastic-apm. If omitted or empty, tracing will be disabled. Use environment variables to configure DataDog (see https://docs.datadoghq.com/tracing/setup/go/#configuration).",
"enum": ["zipkin", "jaeger", "datadog", "elastic-apm"],
"description": "Set this to the tracing backend you wish to use. Supports Jaeger, Zipkin, DataDog, Elastic APM and OpenTelemetry. If omitted or empty, tracing will be disabled. Use environment variables to configure DataDog (see https://docs.datadoghq.com/tracing/setup/go/#configuration).",
"enum": ["zipkin", "jaeger", "datadog", "elastic-apm", "otel"],
"examples": ["zipkin"]
},
"service_name": {
Expand Down