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

[processor/deltatocumulative]: determine default stream limit #31603

Closed
Tracked by #30705
sh0rez opened this issue Mar 5, 2024 · 4 comments
Closed
Tracked by #30705

[processor/deltatocumulative]: determine default stream limit #31603

sh0rez opened this issue Mar 5, 2024 · 4 comments

Comments

@sh0rez
Copy link
Member

sh0rez commented Mar 5, 2024

Component(s)

processor/deltatocumulative

Describe the issue you're reporting

The deltatocumulativeprocessor is about to support setting an upper limit for the number of tracked streams.
It should have a good default value for that.

However having zero production experience with this component, we cannot confidently do so just yet.

@sh0rez sh0rez added the needs triage New item requiring triage label Mar 5, 2024
@sh0rez
Copy link
Member Author

sh0rez commented Mar 5, 2024

/label discussion-needed -needs-triage

Copy link
Contributor

github-actions bot commented Mar 6, 2024

Pinging code owners for processor/deltatocumulative: @sh0rez @RichieSams. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

github-actions bot commented May 6, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label May 6, 2024
Copy link
Contributor

github-actions bot commented Jul 5, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants