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

Collector giving the 404 response while exporting the traces #36137

Open
sonuverma1505 opened this issue Oct 17, 2024 · 4 comments
Open

Collector giving the 404 response while exporting the traces #36137

sonuverma1505 opened this issue Oct 17, 2024 · 4 comments
Labels
bug Something isn't working exporter/azuremonitor needs triage New item requiring triage

Comments

@sonuverma1505
Copy link

Describe your environment

collector version v0.109.0
K8s version v1.28.9

What happened?

Using the collector in AKS cluster and when its doing the export its giving the error
collector version which we are using v0.109.0

2024-10-09T05:01:24.230Z debug azuremonitorexporter@v0.109.0/factory.go:139 Response: 404 {"kind": "exporter", "data_type": "logs", "name": "azuremonitor"}

Steps to Reproduce

Install the OpenTelemetry operator (version 0.109.0) and the collector using the Helm chart. Enable auto-instrumentation for your pod, and you will see errors related to this in the collector logs.

Expected Result

No 404 should be present in the logs

Actual Result

2024-10-09T05:01:24.230Z debug azuremonitorexporter@v0.109.0/factory.go:139 Response: 404 {"kind": "exporter", "data_type": "logs", "name": "azuremonitor"}

Additional context

No response

Would you like to implement a fix?

None

@sonuverma1505 sonuverma1505 added the bug Something isn't working label Oct 17, 2024
@sonuverma1505
Copy link
Author

Please let me know if any additional details are required

@codeboten
Copy link
Contributor

This issue appears specific to the azuremonitorexporter, transferring to the contrib repo where that component lives

@codeboten codeboten transferred this issue from open-telemetry/opentelemetry-collector Nov 1, 2024
@codeboten codeboten added exporter/azuremonitor needs triage New item requiring triage labels Nov 1, 2024
Copy link
Contributor

github-actions bot commented Nov 1, 2024

Pinging code owners for exporter/azuremonitor: @pcwiese. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@researcherarjun
Copy link

The error vanished after setting the following in the Instrumentation.

apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
name: python-demo-instrumentation
spec:
env:
- name: OTEL_METRICS_EXPORTER
value: none
- name: OTEL_EXPORTER_OTLP_PROTOCOL
value: grpc
exporter:
endpoint: http://otel-collector.azure-arc.svc.cluster.local:4317
propagators:
- tracecontext
- baggage
sampler:
type: parentbased_traceidratio
argument: "1"
python:
env:
# Required if endpoint is set to 4317.
# Python autoinstrumentation uses http/proto by default
# so data must be sent to 4318 instead of 4317.
- name: OTEL_METRICS_EXPORTER
value: none
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: http://otel-collector.azure-arc.svc.cluster.local:4318

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working exporter/azuremonitor needs triage New item requiring triage
Projects
None yet
Development

No branches or pull requests

3 participants