-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
telemetrygen subcommand to generate OTLP log events #12927
Comments
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I'll help with this issue. @mx-psi |
Thanks @fatsheep9146 🚀 let me know if I can help |
Sure, sorry, this fell of my bucket list. I can cut a smaller PR to take care of refactoring. |
@fatsheep9146 #17898 is merged, so this is now unblocked :) |
Is your feature request related to a problem? Please describe.
Easily running integration tests for Vector's OTLP logs.
Describe the solution you'd like
The WIP
telemetrygen
currently has documented (WIP) support for traces and metrics, we should track in the implementation of logs as well.Describe alternatives you've considered
Today I've just run the opentelemetry-collector to push logs with otlpexporter and otlphttpexporter.
The text was updated successfully, but these errors were encountered: