#support

Issue with Filtering Data by Namespaces in Services Map View

TLDR Juha faced issues filtering data by namespaces in Services Map view. Srikanth suggested using deployment.environment, but a bug may exist, and an issue was created on GitHub.

8mo

Join the chat

Apr 17, 2023 (8 months ago)

Photo of md5-f6bbff9abeea1c8430cb80b160f25d8a

Juha

02:55 PM

Hello! I want to user Services Map view to filter data by namespaces. I’m using Opentelemetry operator to autoinstrument my applications (using Instrumentation CRD). But it seems that after autoinstrumentation, there are not compatible attributes added to instrumented pods OTEL_RESOURCE_ATTRIBUTES so I can not filter per namespace. OTEL_RESOURCE_ATTRIBUTES has k8s.namespace.name attribute but according to SigNoz documentation, that is not supported. Suitable attribute should be resource_k8s_cluster_namespace. How to add that to autoinstrumentation?

Apr 18, 2023 (8 months ago)

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

03:29 AM

> OTEL_RESOURCE_ATTRIBUTES has k8s.namespace.name attribute but according to SigNoz documentation, that is not supported
Where is it this mentioned? The k8s.namespace.name is converted to k8s_cluster_namespace for the compatibility reasons and it should be available if you are sending the data.

Apr 20, 2023 (8 months ago)

Juha

08:15 AM

Hi Srikanth for example in Logs view I can filter logs using k8s_namespace_name, for example k8s_namespace_name IN (‘staging’)

Same can not be used in Service Map view.

08:16

Juha

08:16 AM

In service map view, UI complains that I do not have any resource attributes to filter.

Srikanth

09:37 AM

The service map data is coming from the traces. It could be possible that for logs you are using automatic collection, which enriches the data but may be missing for traces. Can you confirm if your traces are also enriched with k8s metadata?

Juha

10:53 AM

Srikanth Yes, traces are enriched because I can filter traces using for example using query k8s.namespace.name.(string) Equals ("staging")

Srikanth

11:16 AM

Ok, thanks for the confirmation; this is probably a bug.

11:16

Srikanth

11:16 AM

I believe at least deployment.environment should work, but I am not sure if that helps.

Juha

12:02 PM

Ok. I will create an issue about this to GH.

12:04

Juha

12:04 PM

deployment.environment does not help because UI does not allow me to type anything to text field.

12:17

Juha

12:17 PM

Issue created: https://github.com/SigNoz/signoz/issues/2604

Srikanth

01:31 PM

> deployment.environment does not help because UI does not allow me to type anything to text field.
If you send this as a part of the resource attributes it will show up in the dropdown https://signoz.io/docs/userguide/metrics/#steps-to-add-resource-attributes

Juha

01:42 PM

Hmmh. No idea how I can control what attributes Opentelemetry Operator adds to OTEL_RESOURCE_ATTRIBUTES 🙁

03:16

Juha

03:16 PM

Ahaa, now I know how I could add that deployment.environment to OTEL_RESOURCE_ATTRIBUTES. So I can try that, but still this should work with default resource attributes that Opentelemetry Operator sets (k8s.namespace.name, k8s.container.name, k8s.pod.name, k8s.pod.uid, k8s.node.name …) so the issue is valid.

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Filtering Applications in Services and Service Map Sections

Ayan asked how to filter applications in Services and Service Map sections. Srikanth and Vishnu provided guidance on supported filters and adding custom dimensions in otel-collector-config.yaml, which they successfully implemented.

5mo

Log Queries Not Working After Updating to 0.18.1

Al reports log queries not working after updating to `0.18.1`, specifically filtering by `k8s_namespace_name`. Srikanth suggests Nityananda might have an answer, but no response yet.

7mo

Troubleshooting Namespace Issues In Alerts with Otel+Signoz

Ayushman had a query about retrieving their kubectl pod's namespace in alerts using otel+signoz. Prashant and Srikanth gave steps, but found that Ayushman's applications might not be sending the necessary attributes.

3mo

SigNoz Production Feedback and Improvement Suggestions

Users shared their SigNoz experiences and feedback. Issues mentioned include memory consumption, UI/UX improvements, connection difficulties, and automation limitations.

9mo

Extracting Custom Fields as Attributes from Log in SigNoz

Harald wants to have custom fields from their body parsed as attributes in the SigNoz logger. They have tried implementing suggestions from nitya-signoz and Prashant, but the issue remains unsolved due to a potential race condition encountered while executing the code. They have provided a full example using Kind for further assistance.

209

5mo