Hello team, i am trying to configure My EKS cluster to set logs on SigNoz when I try to filter with namespace I see below error, can someone guide me ?

The error indicates that the metric key

k8s.namespace.name

is present in both the resource data and attribute data. Somewhere in your setup, it is setting the metric key twice. And Signoz doesn't know which one you are wanting to query with. @Srikanth Chekuri The old query builder used to have blue/yellow colors when you selected a different metric source. Did the ability to do this get lost in the new query builder? Is there way to do this now?

resource(k8s.namespace.name) in ['mongodb']

attribute(k8s.namespace.name) in ['mongodb']

The linked docs in the error have links for the syntax to use. It would be

resource.k8s.namespace.name

or

attribute.k8s.namespace.name

depending on the context.

I dnt understand what I have to do, why I am not able to select deployment = "xyz" and namespace = "pqr" why it so complicated ? above is my values.ymal for debugging

I can understand the frustration. Please take some time to go thorough the linked docs. It will help you understand the concepts. And wanted to point out that what you are seeing it warning not an error.

But I am not able to filter logs, this is happening in matrics also, also can you share me doc links again

Can you please what is the search expression where you are not able to filter logs?

@Ganesh Wankhede Version 0.92.1 and earlier had a bunch that prevented some sorts of metric/log filtering. Please make sure you're on the latest release, 0.92.2 at the time of writing. The docs for the query builder can be found at the following pages. Its a lot of reading, but it'l get you up to speed on everything the query builder can support. • https://signoz.io/docs/userguide/query-builder-v5/ • https://signoz.io/docs/userguide/search-syntax/ • https://signoz.io/docs/userguide/operators-reference/ • https://signoz.io/docs/userguide/field-context-data-types/ That last link in particular points out the issue you're having with k8s.namespace.name and how to fix it. As mentioned above, if you query for

resource.k8s.namespace.name

, then things should work.