TLDR Nishant faced issues separating metrics data for visualization based on IP/job_name. Srikanth suggested using `instance` or `service_instance.id`.
hey team, I am using for exposing redis metrics and collecting them with signoz with the below config defined in `signoz/deploy/docker/clickhouse-setup/otel-collector-metrics-config.yaml`
```# Redis server metrics
- job_name: redis_exporter
# - 10.0.1.170:9121```
Using Signoz with docker on AWS t3a.2xlarge and I am able to collect all the metrics and have a visualisation dashboard for metrics data from instance on ip `10.0.0.105` however when I uncomment the ip below it (`10.0.1.170`) then the perf metrics of both the redis instance mixing in the clickhouse (im assuming this is happening because both uses same exporter) and there’s no distinction tag which I can use to separate the metrics stored in clickhouse to create a separate visualisation or pass the ip as parameter in existing dashboard.
dashboard was made using query builder and where clause only giving `__name__` as the tag to create distinction which doesn’t provide an appropriate value at all.
Expected behaviour : I should be able to separate the metrics data for visualisation based on ip/ job_name defined in config
It will be available as either `instance` or `service_instance.id` with `host:port` .
Indexed 1060 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI