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

Mezmo OTEL exporter does not accept Kubernetes Enrichment #27238

Closed
88nafees77 opened this issue Sep 27, 2023 · 5 comments
Closed

Mezmo OTEL exporter does not accept Kubernetes Enrichment #27238

88nafees77 opened this issue Sep 27, 2023 · 5 comments
Labels
enhancement New feature or request exporter/mezmo needs triage New item requiring triage processor/resourcedetection Resource detection processor Stale waiting for author

Comments

@88nafees77
Copy link

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.

Screenshot 2023-09-06 at 11 08 21 AM

Describe the solution you'd like

I just want the support of Kubernetes enrichment with otel.

below is the configuration file of otel collector.

otel-collector-config: |
    receivers:
      otlp:
        protocols:
          grpc: 
          http:
    processors:
      batch:
      k8sattributes:
    exporters:
      mezmo:
        ingest_url: "https://logs.mezmo.com/otel/ingest/rest"
        ingest_key: "<ingest_key>"
    service:
      pipelines:
        logs:
          receivers: [otlp]
          processors: [k8sattributes, batch]
          exporters: [mezmo]
      telemetry:
        logs:
          level: "debug"`

Describe alternatives you've considered

No response

Additional context

No response

@88nafees77 88nafees77 added enhancement New feature or request needs triage New item requiring triage labels Sep 27, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1
Copy link
Member

Hello @88nafees77, have you tried to use the resourcedetection processor to get the information you're missing? From the image you shared and the docs I found, it looks like that might be a good option to try to get the information you're looking for.

@crobert-1 crobert-1 added the processor/resourcedetection Resource detection processor label Sep 27, 2023
@github-actions
Copy link
Contributor

Pinging code owners for processor/resourcedetection: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself.

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.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request exporter/mezmo needs triage New item requiring triage processor/resourcedetection Resource detection processor Stale waiting for author
Projects
None yet
Development

No branches or pull requests

2 participants