This message was deleted.

@User Looks like resources is just for passing attributes related to service you are instrumenting: https://github.com/SigNoz/sample-golang-app/blob/ae3e200c890e17574ff4b66e1fb3bc1cd8ed5ccc/main.go#L53 Official example:https://github.com/open-telemetry/opentelemetry-go/blob/main/sdk/trace/benchmark_test.go So you need not pass them.

Yes, that is the idea.. If I am passing attributes for my service using semconv they should appear on dashboard

Looks like we are not storing these keys on the backend

Got it, We can pass custom keys as well with otel sdk and it would be helpful if we can start storing and surfacing this info.

This looks somewhat related to this issue as we are not storing namespace, schemaURL, etc. @User Please create a new issue for this

@User this seems interesting. How would you like to use those extra attributes? In the application list page or trace filtering page? Would like to pick this up in upcoming sprint. Please add a github issue for this to track it publicly and that others need this feature too

Use case : 1. We have 4 non prod environments and one common cluster of otel collector and signoz backend to receive data from all these 4 enviornments. We should be able to view traces from one env at a time. 2. We may want to pass service names from application code which is more business specific. The issue pointed out by vishal is exactly our requirements. https://github.com/SigNoz/signoz/issues/881