You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bvader
changed the title
logs processor is not emitting event.dataset some UI do not work properly
logs processor is not emitting event.dataset some UIs do not work properly
Oct 18, 2024
@rogercoll Just pinging on this I am getting more interest and this bug is creeping in causing issues, do you want me to create a PR etc?
Sorry for my late response, a PR would be great, but I think this attribute decoration is not needed anymore with the otel native data model. I am about to merge this PR that changes the Otel demo deployment within Elastic completely to be Otel native: #120 (so this decoration won't be needed)
Bug Report
Which version of the demo you are using? (please provide either a specific
https://github.com/elastic/opentelemetry-demo/tree/1.11.5
Symptom
logs processor is not emitting event.dataset some UI do not work properly
What is the expected behavior?
logs processor should emit event.dataset
What is the actual behavior?
event.dataset is missing
Reproduce
Run the otel demo add the metrics and logs daemonset.
Fix
This line should have
attributes/dataset
as part of the list of processorsopentelemetry-demo/kubernetes/elastic-helm/daemonset.yaml
Line 314 in 27b4923
Is
processors: [batch, k8sattributes, resourcedetection/system, resourcedetection/eks, resourcedetection/gcp, resource/demo, resource/k8s, resource/cloud, attributes/k8s_logs_dataset]
Should be
processors: [batch, k8sattributes, resourcedetection/system, resourcedetection/eks, resourcedetection/gcp, resource/demo, resource/k8s, resource/cloud, attributes/k8s_logs_dataset, attributes/dataset]
The text was updated successfully, but these errors were encountered: