-
Notifications
You must be signed in to change notification settings - Fork 248
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
Metrics: Implement Advisory Parameters #1686
Comments
Right now, just working on the explicit bucket boundaries advisory parameter. Attributes is marked as experimental. Checking in on open-telemetry/opentelemetry-specification#3785 to see if it's stable enough to implement. |
👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the |
👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the |
To help update bucket boundaries for instruments in instrumentation, implement advisory parameters (AKA advice)
API: https://opentelemetry.io/docs/specs/otel/metrics/api/#instrument-advisory-parameters
SDK: https://opentelemetry.io/docs/specs/otel/metrics/sdk/#instrument-advisory-parameters
JS implementation example: open-telemetry/opentelemetry-js#3876
JS instrumentation example: https://github.com/open-telemetry/opentelemetry-js-contrib/blob/770130a7a41125dbf8a8c18b3384e5fcc370deef/plugins/node/instrumentation-undici/src/undici.ts#L127-L141
The text was updated successfully, but these errors were encountered: