I can use that resource attribute to filter in the Traces area of Signoz, but the Services area will not show it as a filter option - only the signoz collector id shows up as filterable.
Any ideas on why it wouldn't be allowing the Service filter on another but the collector id even thought the data is there and filterable in the traces area?
p
Prashant Shahi
03/18/2024, 5:51 AM
Only
signoz.collector.id
and
deployment.environment
are supported in services page at the moment.
Try adding the
deployment.environment
resource attribute.
In case of multiple environments, we recommend adding that in application instrumentation env itself.
e
Eric Thompson
03/18/2024, 4:52 PM
Thank you! We eventually found that through deep inspection of the signoz charts and OTEL docs. How do I request an update to the signoz docs? Is there a ticket I could create somewhere?
p
Prashant Shahi
03/20/2024, 5:58 AM
cc @Chitransh Gupta
c
Chitransh Gupta
03/20/2024, 6:03 AM
@Eric Thompson you can create an issue for this here - https://github.com/SigNoz/signoz.io/issues.
Please add some description about the problem and we will work on improving the documentation.
SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.