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

Add support to enrich OTLP data with kubernetes metadata #21239

Closed
Sh4d1 opened this issue Sep 9, 2024 · 2 comments
Closed

Add support to enrich OTLP data with kubernetes metadata #21239

Sh4d1 opened this issue Sep 9, 2024 · 2 comments
Labels
type: feature A value-adding code addition that introduce new functionality.

Comments

@Sh4d1
Copy link
Contributor

Sh4d1 commented Sep 9, 2024

A note for the community

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Use Cases

Some applications in kubernetes, might send out logs & traces to an otlp endpoint. Usually it's done with a "proxy" like otelcollector, or grafana alloy (which uses otelcollector IIRC). They both allow to add kubernetes metadata on the incoming traces or logs, based on source IP, or others.

Attempted Solutions

Currently, Vector can only attach kubernetes metadata to logs taken directly from the pods (which is a valid, and I guess the majority's case), but leave no other options to do what I describe above.

Proposal

I haven't looked that much at the kubernetes' logs source, but I think some code could be re-used to create a kubernetes_pod transform or something like that.

References

No response

Version

0.40.1

@Sh4d1 Sh4d1 added the type: feature A value-adding code addition that introduce new functionality. label Sep 9, 2024
@jszwedko
Copy link
Member

jszwedko commented Sep 9, 2024

Hi @Sh4d1 !

Thanks for opening this. I think it is a special case of the more general feature request to have a transform for k8s metadata enrichment: #5077. I'll close this one in-lieu of that one, but let me know if you disagree.

@jszwedko jszwedko closed this as not planned Won't fix, can't repro, duplicate, stale Sep 9, 2024
@Sh4d1
Copy link
Contributor Author

Sh4d1 commented Sep 9, 2024

Perfect thanks I missed it, my bad!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature A value-adding code addition that introduce new functionality.
Projects
None yet
Development

No branches or pull requests

2 participants