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

Which processors should be used by default? #2152

Closed
pavolloffay opened this issue Apr 3, 2020 · 4 comments
Closed

Which processors should be used by default? #2152

pavolloffay opened this issue Apr 3, 2020 · 4 comments

Comments

@pavolloffay
Copy link
Member

Created from #2148 (comment)

List of OTEL processors https:/open-telemetry/opentelemetry-collector/tree/master/processor

@pavolloffay pavolloffay transferred this issue from jaegertracing/jaeger-opentelemetry-collector Apr 6, 2020
@ghost ghost added the needs-triage label Apr 6, 2020
@pavolloffay
Copy link
Member Author

Based on #2148 (comment). OTEL collector might run without any processor.

@objectiser
Copy link
Contributor

Use of the queued_retry processor may be required if we want a certain set of metrics - I will re-review the metrics again this week following some changes upstream, so we can list which metrics would be dependent upon which particular processors.

@pavolloffay
Copy link
Member Author

Once our storage exporters will accept batches we could enable batch and queued retry processors.

For now, I wanted to enable memory limiter, however, it accepts absolute settings. I have submitted a proposal to accept percentage configuration open-telemetry/opentelemetry-collector#1078 that would enable us to enable it by default for any deployment.

@pavolloffay
Copy link
Member Author

Closing as it is a "low level" issue related to V2 which might take a different approach.

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