Hi everyone, With signoz 0.18.3, should I be able to filter exceptions by any resource attribute? e.g. k8s_namespace_name ? Currently, there is only one available field available

signoz.collector.id

nothing else.

Yes you can filter exceptions by any resource. You have to send

k8s_namespace_name

as resource attribute to be able use it as filter

@Vishal Sharma here is an entry that does indeed contain

k8s_namespace_name

select * FROM signoz_traces.distributed_signoz_error_index_v2 limit 1


┌─────────────────────timestamp─┬─errorID──────────────────────────┬─groupID──────────────────────────┬─traceID──────────────────────────┬─spanID───────────┬─serviceName─┬─exceptionType────────────────────────────────────────┬─exceptionMessage───┬─exceptionStacktrace────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┬─exceptionEscaped─┬─resourceTagsMap────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ 2023-05-02 00:00:12.326284860 │ a78affb938ab4d85ba7364c0351fa656 │ f767290ce9682bc52f8b23267e352bc5 │ e7eca14967f924759b77d39fa062494a │ 63351f06a0bbc171 │ acme-server  │ com.biztech.acme.exceptions.NotFound │ Pin Not Recognized │ com.biztech.acme.central.api.exceptions.NotFound: Pin Not Recognized
│ false            │ {'os.description':'Linux 5.15.0-1035-azure','os.type':'linux','process.pid':'1','process.runtime.name':'OpenJDK Runtime Environment','service.name':'acme-server','telemetry.sdk.language':'java','k8s.deployment.name':'acme','k8s.pod.name':'acme-7c96459d5-mrg5f','k8s.pod.uid':'ebab11df-2a4a-4e27-af67-4af8432b5dc9','container.id':'6eea1b662df0e810d789a792a81677161663817e109c1a30a4dd878b86cf5e71','host.arch':'amd64','telemetry.sdk.version':'1.23.1','k8s.node.name':'agentpool-000013','telemetry.auto.version':'1.23.0','k8s.pod.ip':'10.240.0.41','k8s.pod.start_time':'2023-04-14 06:30:34 +0000 UTC','signoz.collector.id':'89eb1714-a562-4c0f-82f0-9fea2a673757','host.name':'acme-7c96459d5-mrg5f','telemetry.sdk.name':'opentelemetry','k8s.namespace.name':'lecreuset'} │
└───────────────────────────────┴──────────────────────────────────┴──────────────────────────────────┴──────────────────────────────────┴──────────────────┴─────────────┴──────────────────────────────────────────────────────┴────────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┴──────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

This key is being fetched from metrics db. @Srikanth Chekuri Is it a possible bug in signoz otel collector?

I recently recently resolved K8s Attribute Filtering Issue in Logs Is there a similar K8s attribute filtering issue in Exceptions?

No, since the services tab relies on the span metrics, it only shows the labels from span metrics. Although the same doesn’t make sense for exceptions but the implementation hasn’t been changed since the first support of resource attributes.

Is there any additional diagnostic information I can share that would help diagnose this issue? When I click into the Search and filter field, Loading activity spinner appears for 1 - 2 seconds, then

signoz.collector.id

(the only filter field option) appears.