Skip to content

Preferred aggregation temporality is under-specified #2403

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

Closed
jmacd opened this issue Mar 5, 2022 · 0 comments · Fixed by #2404
Closed

Preferred aggregation temporality is under-specified #2403

jmacd opened this issue Mar 5, 2022 · 0 comments · Fixed by #2404
Assignees
Labels
area:sdk Related to the SDK release:required-for-ga Must be resolved before GA release, or nice to have before GA spec:metrics Related to the specification/metrics directory

Comments

@jmacd
Copy link
Contributor

jmacd commented Mar 5, 2022

What are you trying to achieve?

Whether through Views or another mechanism, the MetricReader needs a way to dictate the aggregation temporality that is used by default. For some exporters (OTLP, Console, In-Memory), the choice is something the user might care about, particularly for OTLP where there are memory costs associated with this decision.

What did you expect to see?

Some way that a user can control temporality, if they care. The current specification does not give strict requirements for "preferred aggregation temporality". One solution was outlined in #2314, where the View allowed to specify a strategy which was either "preferred", "cumulative" or "delta" (hypothetically). Another solution that was discussed in that PR would to let the temporality decision be defaulted on a per-instrument basis.

This applies to most of the exporters, makes the decision a "5-way function" for the five instruments that define the concept of aggregation temporality (i.e., the six instruments except Gauge).

This PR defines the requirements, but does not go as far as defining environment variable syntax for configuring the temporality on a per-instrument basis.

@jmacd jmacd added the spec:metrics Related to the specification/metrics directory label Mar 5, 2022
@reyang reyang added area:sdk Related to the SDK release:required-for-ga Must be resolved before GA release, or nice to have before GA labels Mar 11, 2022
@reyang reyang added this to the Metrics API/SDK Stable Release milestone Mar 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:sdk Related to the SDK release:required-for-ga Must be resolved before GA release, or nice to have before GA spec:metrics Related to the specification/metrics directory
Projects
None yet
3 participants