From fa5814111fdf2e0e421e35778e7481eaa37e9981 Mon Sep 17 00:00:00 2001 From: Mariana Frangos <67069168+marianafrangos@users.noreply.github.com> Date: Thu, 21 May 2026 06:36:00 -0700 Subject: [PATCH 1/2] Update service_remapping_rules.md update to change the behavior of overrides --- content/en/tracing/services/service_remapping_rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/tracing/services/service_remapping_rules.md b/content/en/tracing/services/service_remapping_rules.md index 439ac6f33d3..d1a0da8d4d0 100644 --- a/content/en/tracing/services/service_remapping_rules.md +++ b/content/en/tracing/services/service_remapping_rules.md @@ -72,7 +72,7 @@ Remapping rules are applied across APM, Logs, Metrics, USM, DSM, DJM, DBM, Profi - **Historical data:** Changes made by remapping rules affect only telemetry ingested while a rule is active, and past data is not updated retroactively. Deleting or modifying a rule stops it from applying to new data, but does not revert names on previously ingested data. - **Logs service remapper:** Service remapping rules occur before logs pipelines. If the logs service remapper and remapping rules are both applied to a service, the remapping rules take precedence. - **Dashboards and monitors:** Existing queries that reference old service names are not automatically updated. Review and update these manually. -- **Integration overrides:** Remapping rules apply to base services; integration overrides are not remapped. [Remove integration overrides][15] for the best APM experience. +**Integration and custom overrides:** If integration overrides or custom overrides fall within the scope of a remapping rule, they will also be remapped. [Remove integration overrides][15] for the best APM experience. - **Service naming hierarchy:** Service names are determined by the following hierarchy, from highest to lowest priority: 1. Service remapping rules 2. Service defined in code (`tracer.Start(WithService(xx))`) From 78ef5a7679ac5a5ca24a4620cd415b1f4466e4d2 Mon Sep 17 00:00:00 2001 From: Mariana Frangos <67069168+marianafrangos@users.noreply.github.com> Date: Thu, 21 May 2026 12:09:32 -0700 Subject: [PATCH 2/2] Update content/en/tracing/services/service_remapping_rules.md Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com> --- content/en/tracing/services/service_remapping_rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/tracing/services/service_remapping_rules.md b/content/en/tracing/services/service_remapping_rules.md index d1a0da8d4d0..81aad8793b0 100644 --- a/content/en/tracing/services/service_remapping_rules.md +++ b/content/en/tracing/services/service_remapping_rules.md @@ -72,7 +72,7 @@ Remapping rules are applied across APM, Logs, Metrics, USM, DSM, DJM, DBM, Profi - **Historical data:** Changes made by remapping rules affect only telemetry ingested while a rule is active, and past data is not updated retroactively. Deleting or modifying a rule stops it from applying to new data, but does not revert names on previously ingested data. - **Logs service remapper:** Service remapping rules occur before logs pipelines. If the logs service remapper and remapping rules are both applied to a service, the remapping rules take precedence. - **Dashboards and monitors:** Existing queries that reference old service names are not automatically updated. Review and update these manually. -**Integration and custom overrides:** If integration overrides or custom overrides fall within the scope of a remapping rule, they will also be remapped. [Remove integration overrides][15] for the best APM experience. +**Integration and custom overrides:** If integration overrides or custom overrides fall within the scope of a remapping rule, they are also remapped. [Remove integration overrides][15] for the best APM experience. - **Service naming hierarchy:** Service names are determined by the following hierarchy, from highest to lowest priority: 1. Service remapping rules 2. Service defined in code (`tracer.Start(WithService(xx))`)