Fix ServerMonitor thread name

[raipc]

Current thread name is verbose and breaks integration with monitoring tools which prohibit = in label values.

Old name example: cluster-ClusterId{value='67664b095dd867448cefc455', description='null'}-db.example.com:27017
New name: cluster-67664b095dd867448cefc455-db.example.com:27017

[stIncMale]

breaks integration with monitoring tools which prohibit = in label values

@raipc, could you please provide more detains about the above, and clarify what you mean by "label values"?

[raipc]

could you please provide more detains about the above, and clarify what you mean by "label values"?

When this thread name is collected via JMX and fed into monitoring systems as a label or tag value (e.g. in metrics like {name=jvm.thread.cpu_time.ns, thread=...}), the characters {, }, ', =, , cause issues:

Graphite — uses . as hierarchy separator and does not allow {}; the metric path gets corrupted
InfluxDB — , and = are reserved in line protocol; they require escaping and even then the result is barely readable
Datadog Agent — aggressively normalizes tag values by replacing all special characters with _, so the original structure is lost silently
Micrometer → Graphite/StatsD registry — mangles the value beyond recognition