-
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
Collector giving the 404 response while exporting the traces #36137
Comments
Please let me know if any additional details are required |
This issue appears specific to the |
Pinging code owners for exporter/azuremonitor: @pcwiese. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
The error vanished after setting the following in the Instrumentation. apiVersion: opentelemetry.io/v1alpha1 |
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
The text was updated successfully, but these errors were encountered: