Open patrijua opened 1 year ago
And for extra information, we are using Opentelemetry Operator to autoinstrument our applications to send logs, traces and metrics. Here's an example of container OTEL_RESOURCE_ATTRIBUTES env:
OTEL_RESOURCE_ATTRIBUTES : k8s.container.name=xxxx-service,k8s.deployment.name=xxxx-service-deployment,k8s.namespace.name=staging,k8s.node.name=$(OTEL_RESOURCE_ATTRIBUTES_NODE_NAME),k8s.pod.name=$(OTEL_RESOURCE_ATTRIBUTES_POD_NAME),k8s.replicaset.name=xxxx-service-deployment-54785c498c
I defined new resource attributes for our data (service.namespace + deployment.environment) and now I can use them to filter Service Map and Services. However, I would expect, that there would not be need to define any new resource attributes than those which are set by the Opentelemetry Operator already.
Bug description
It's not possible to filter data on Service Map view. The UI does not allow me to type anything to text box and displays information: "No resource attributes available to filter. Please refer docs to send attributes."
However, logs and traces data are enriched since I can filter data in them without problem. For example In Logs query:
k8s_namespace_name IN (‘staging’)
And in Traces view I can filter traces for example with:
k8s.namespace.name.(string) In ("staging")
Expected behavior
I expect that I can filter data in Service Map view in similar ways so I could see service map based on namespace I want.
Version information
Thank you for your bug report – we love squashing them!