Hello SigNoz Support Team, I have a question about the Service Map: Many of our instrumented services communicate with Redis, but they actually connect to different Redis instances. In the current Service Map, all Redis spans appear under a single “redis” node because

db.system

is always set to “redis.” Is there a way to have the Service Map show each Redis host by name instead of lumping them together? For example, could we overwrite

db.system

with the value of

net.peer.name

so that each Redis instance shows up separately? If that isn’t the recommended approach, could you please advise on how to configure SigNoz (e.g., via Helm or the Collector) so that each Redis endpoint or any other external endpoint appears distinctly in the Service Map? Thanks in advance for your help.

Hey @Prajith P! I needed to identified differents services that where hosted on the same VM on a multi VM architecture. I could do that by adding a processors for each services like :

processors:
  resource/passport:
    attributes:
      - key: service.name
        value: "PASSPORT"
        action: upsert

Then add it in the pipeline

pipelines:
    metrics/passport:
      receivers: [httpcheck/passport]
      processors: [resourcedetection, resource/env, resource/passport, transform/http_code, batch]
      exporters: [clickhousemetricswrite, metadataexporter]

Maybe you can adapt something like that.

Hey @Gil Thanks for sugesstion here, @Prajith P Let us know if the suggestions works for you

That's not configurable @Prajith P. Here is the view that is responsible for the inferred db https://github.com/SigNoz/signoz-otel-collector/blob/2b30bd6c77d7ab16f82d8a4382e14[…]2/cmd/signozschemamigrator/schema_migrator/traces_migrations.go.