-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[cmd/telemetrygen] migrate log to use go sdk #18902
Comments
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. |
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 updates telemetrygen to use the otel go SDK for logs instead of pdata for the logging signal. This aligns with the tracing and metrics signal. Fixes #18902 --------- Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com> Co-authored-by: Matthew Wear <matthew.wear@gmail.com>
Component(s)
cmd/telemetrygen
Is your feature request related to a problem? Please describe.
For now, since the log of go sdk is now frozen. So the telemetrygen can only use
pdata
and other package to create log data.When go log sdk is ready, we could check whether it is sufficient for telemetrygen to generate log data.
Describe the solution you'd like
None
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: