-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Stability Level #34632
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
Comments
Please join a SIG meeting to discuss this. The collector is going through a stabilization effort starting with core libraries and OTLP. See Collector: v1 |
Hi, I have the same question, but for exporters. I like the idea of an OTEL collector, but all exporters are in the beta/alpha state. It's not acceptable for big companies to use it in production. Any insight on when we can expect a stable version? |
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 |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
No response
Describe the issue you're reporting
Most of the receiver in contrib github is in alpha & beta phase. Are they table enough to be used in production. Planning to use OpenTelemetry in Production setup.
I am bit confused here.
The text was updated successfully, but these errors were encountered: