-
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
k8sattributes processor attributes not appearing in Azure Monitor Logs #24210
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@bastbu Can you take a look here? I know you made a change a few months ago to include resource attributes in the log exporter... |
I tried to reproduce it, but for me all resource attributes originating from the From the original description I can see that the The Elastic |
/label waiting-for-author |
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. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/azuremonitor
What happened?
Description
When I use the
logging
exporter I can see thek8sattributes
values added in the collector logs. But when I add theazuremonitor
exporter, there are nok8sattributes
in the log lines. I expect to see them in thecustomDimensions
but they are nowhere.Steps to Reproduce
Expected Result
To have the K8s pod name and other attributes present in the
customDimensions
sectionActual Result
(There are no k8sattributes to be found anywhere)
Collector version
v0.80.0
Environment information
Environment
OpenTelemetryOperator deployed collector
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: