SKILL.md
APM Service Remapping
Before acting: Surface an impact preview (monitors/dashboards referencing the old service name) before presenting the planned rule. For inferred-entity remaps, also confirm
peer.serviceis set on outbound spans. Variables from## Context to resolve before actingcan be gathered alongside that preview rather than blocking it.
How Service Remapping Works — Domain Knowledge
Read this before building any rule. It gives you the mental model to construct the right filter and catch edge cases.
What remapping does: A rule intercepts telemetry at ingestion time and rewrites the service name before indexing. A rule says: "for any entity matching this filter, replace its service name with this new value."
Two entity types — pick the right one:
| Entity type | rule_type integer |
What it targets |
|---|---|---|
| SERVICE | 0 |
Instrumented services — have spans with an explicit service tag set by a tracer |
| INFERRED_ENTITY | 1 |
Auto-detected from outbound calls — named from peer.service. Requires peer.service to be set on outbound spans (see prerequisite below). |