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

Specifying Histogram Buckets - without views #3826

Open
coxley opened this issue Mar 1, 2023 · 1 comment
Open

Specifying Histogram Buckets - without views #3826

coxley opened this issue Mar 1, 2023 · 1 comment
Labels
blocked:specification Waiting on clarification of the OpenTelemetry specification before progress can be made enhancement New feature or request

Comments

@coxley
Copy link

coxley commented Mar 1, 2023

Problem Statement

Example referenced: https://github.com/open-telemetry/opentelemetry-go/blob/main/example/view/main.go#L49-L60

I've been referencing the Go API docs, source code, and example usages for the last day and from what I can tell "Views" are the only way to specify buckets per histogram.

  1. Is this true?
  2. If this is true, can someone clarify why?

I know the project has been against providing default histogram boundaries because the meaning changes based on what's being measured. But if views are the only way to do it — and they are attached to your main MeterProvider — then I'm not sure how to define boundaries alongside creating a single histogram.

The reason this matters for me is our setup for exporting metrics and defining metrics are very far apart.

Thanks for your time.

@coxley coxley added the enhancement New feature or request label Mar 1, 2023
@Aneurysm9
Copy link
Member

This is a common request and something we would love to support. Unfortunately, the OTel metrics specification does not have allowances for configuration of this type. There has been discussion of a "hints" API that would allow for specifying a suggested default view for an instrument when it is created, but so far no specification language that we could use to create an implementation. See open-telemetry/opentelemetry-specification#2229 for one such discussion.

@Aneurysm9 Aneurysm9 added the blocked:specification Waiting on clarification of the OpenTelemetry specification before progress can be made label Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked:specification Waiting on clarification of the OpenTelemetry specification before progress can be made enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants