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
Having a highest bucket boundary of only 10 seconds for request duration is absurd for HTTP requests.
I have not quite grokked the dense manner of speaking in the OTEL spec docs yet, but what I think I understand so far is:
It is within spec to allow use of other bucket boundaries..
It is allowable for either the library author or the user to specify their own bucket boundaries, as long as they are "valid" (I assume non-overlapping, etc.).
It is the duty of author of the library providing the Meter to do the validation
i. I have not found any code yet where the OTEL libraries validate the bucket boundaries - possibly because the status of the spec is still "mixed"?
ii. This is the point I am least sure on
I will poke at some people that know OTEL on the Grafana side to see if I am interpreting this correctly.
advisory parameters are an optional set of recommendations provided by the author of the Instrument, aimed at assisting implementations in providing useful output with minimal configuration. They differ from other parameters in that Implementations MAY ignore advisory parameters.
OpenTelemetry SDKs MUST handle advisory parameters as described here.
advisory parameters may be general, or may be accepted only for specific instrument kinds.
Instrument advisory parameter: ExplicitBucketBoundaries
When a Meter creates an instrument, it SHOULD validate the instrument advisory parameters. If an advisory parameter is not valid, the Meter SHOULD emit an error notifying the user and proceed as if the parameter was not provided.
If multiple identical Instruments are created with different advisory parameters, the Meter MUST return an instrument using the first-seen advisory parameters and log an appropriate error as described in duplicate instrument registrations.
The text was updated successfully, but these errors were encountered:
Having a highest bucket boundary of only 10 seconds for request duration is absurd for HTTP requests.
I have not quite grokked the dense manner of speaking in the OTEL spec docs yet, but what I think I understand so far is:
Meter
to do the validationi. I have not found any code yet where the OTEL libraries validate the bucket boundaries - possibly because the status of the spec is still "mixed"?
ii. This is the point I am least sure on
I will poke at some people that know OTEL on the Grafana side to see if I am interpreting this correctly.
Links to reference start here: open-telemetry/opentelemetry-specification#3525 (comment)
Instrument advisory parameters
Status: Mixed
advisory parameters are an optional set of recommendations provided by the author of the Instrument, aimed at assisting implementations in providing useful output with minimal configuration. They differ from other parameters in that Implementations MAY ignore advisory parameters.
OpenTelemetry SDKs MUST handle advisory parameters as described here.
advisory parameters may be general, or may be accepted only for specific instrument kinds.
Instrument advisory parameter: ExplicitBucketBoundaries
Instrument advisory parameters
Status: Development
When a Meter creates an instrument, it SHOULD validate the instrument advisory parameters. If an advisory parameter is not valid, the Meter SHOULD emit an error notifying the user and proceed as if the parameter was not provided.
If multiple identical Instruments are created with different advisory parameters, the Meter MUST return an instrument using the first-seen advisory parameters and log an appropriate error as described in duplicate instrument registrations.
The text was updated successfully, but these errors were encountered: