You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The community made the following suggestions to BentoML observability.
Add a configuration option to return the trace id in the response as a header.
Consider adding a traceparent header that includes the trace id in the response. I only found mentioning of such protocol by vendors, such as https://uptrace.dev/opentelemetry/opentelemetry-traceparent.html, but not any official OpenTelemetry documentation.
Add service.name=%(otelServiceName)s in logs generated.
The community made the following suggestions to BentoML observability.
Consider adding a
traceparent
header that includes the trace id in the response. I only found mentioning of such protocol by vendors, such as https://uptrace.dev/opentelemetry/opentelemetry-traceparent.html, but not any official OpenTelemetry documentation.service.name=%(otelServiceName)s
in logs generated.otelServiceName
should be configurable through an environment variable. Possibly through the OTEL_SERVICE_NAME environment name, open-telemetry/opentelemetry-specification#1677, and default to the bento name. Evaluate addingOTEL_RESOURCE_ATTRIBUTES
to include any arbitrary KVPs to be logged. https://opentelemetry.io/docs/reference/specification/sdk-environment-variables/The text was updated successfully, but these errors were encountered: