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

[metricstarttimeprocessor] Factor start time cache out into generic cache #38382

Closed
dashpole opened this issue Mar 5, 2025 · 1 comment · Fixed by #38579
Closed

[metricstarttimeprocessor] Factor start time cache out into generic cache #38382

dashpole opened this issue Mar 5, 2025 · 1 comment · Fixed by #38579
Assignees
Labels

Comments

@dashpole
Copy link
Contributor

dashpole commented Mar 5, 2025

Component(s)

processor/metricstarttime

Is your feature request related to a problem? Please describe.

The metric start time processor will need to cache start timestamps and values for timeseries it processes for a variety of strategies.

The current cache is part of the true_reset_point strategy: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/metricstarttimeprocessor/internal/truereset/start_time_cache.go

Describe the solution you'd like

We should move that to its own internal directory, and the type it stores generic so that it can be re-used by other strategies.

Describe alternatives you've considered

No response

Additional context

No response

Copy link
Contributor

github-actions bot commented Mar 5, 2025

Pinging code owners for processor/metricstarttime: @dashpole @ridwanmsharif. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment