-
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
Mezmo OTEL exporter does not accept Kubernetes Enrichment #27238
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hello @88nafees77, have you tried to use the |
Pinging code owners for processor/resourcedetection: @Aneurysm9 @dashpole. 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'm going to close for now as I believe the resource detection processor can get the information you're looking for. Please let us know if it doesn't have something you're looking for though, I'd be happy to discuss further. |
Component(s)
exporter/mezmo
Is your feature request related to a problem? Please describe.
I would like to request the addition of support for Mezmo Kubernetes enrichment in OpenTelemetry (OTel).
I can see the all the kubernetes related logs in the otel agents and otel collector, but those data are not showing in mezmo UI.
As you can see in the below image, we are able to get all the logs in Mezmo but the Kubernetes info are not showing.
Describe the solution you'd like
I just want the support of Kubernetes enrichment with otel.
below is the configuration file of otel collector.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: