Hi there ! Got into SigNoz after looking for an open source complete stack o11y platform... and really glad to see it... After playing around a bit (tried running the flask demo app), I was wondering if there is any intent to add some more (pretty basic in my opinion) OTEL_RESOURCES_ATTRIBUTES into account in the UI... I imagine how good would it be to be able to filter interesting services by their namespace for example (service.namespace in otel's semantic conventions), or maybe the version of a service - in order to be able to correlate bad deployments to some monitored signal... (service.version) Does anyone know about a reason not to add / intent to add a usage of these attributes ?

@User very interesting use case. Could you create a github issue for this? I was wondering whether otel-collector can automatically get these attributes but anyhow I think adding from

OTEL_RESOURCES_ATTRIBUTES

won't harm to get started.

@User I will create a new feature request on GitHub - sure !

thanks @User for the detailed issue. Will check it out 🙂