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

Generate logs from trace pipeline #30459

Closed
ewoolsey opened this issue Jan 12, 2024 · 4 comments
Closed

Generate logs from trace pipeline #30459

ewoolsey opened this issue Jan 12, 2024 · 4 comments
Labels

Comments

@ewoolsey
Copy link

ewoolsey commented Jan 12, 2024

Is your feature request related to a problem? Please describe.

opentelemetry-rust is still very immature and the logging pipeline isn't well supported. I would like the collector to generate logs purely from events that occur within the tracing pipeline. I think this is a pretty common use case and it would make instrumenting programs with otel much easier!

Describe the solution you'd like

The collector should be able to generate logs directly from trace events.

Describe alternatives you've considered

In rust using the tracing ecosystem it us currently very cumbersome to implement logging. There isn't really any great alternative for those already using tracing.

@crobert-1
Copy link
Member

Hello @ewoolsey, sorry for the delayed response. Can you share some more context for your request? Are you suggesting adding logging to the collector's telemetry in trace pipelines? Are you proposing a new component that generates logs from a traces pipeline, and sends the generated logs to a log pipeline?

What kind of logs are you looking for that would be helpful?

Is this feature request specific to opentelemetry-rust, or do you mention it just as the source your proposal? Would it be used for any possible sources of traces?

Copy link
Contributor

github-actions bot commented Apr 8, 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.

Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label Jun 10, 2024
Copy link
Contributor

github-actions bot commented Aug 9, 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 Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants