service-remapping

Rename and consolidate APM service names at ingestion time.

150|23|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/datadog-labs/agent-skills --skill service-remapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-remapping
Source: https://github.com/datadog-labs/agent-skills/tree/main/dd-apm/service-remapping
Command: npx skills add https://github.com/datadog-labs/agent-skills --skill service-remapping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill assists in renaming, consolidating, or normalizing APM service names, ensuring consistent service mapping and accurate telemetry without the need for re-instrumentation.

Core Features & Use Cases

  • Service Renaming: Rename services to align with internal conventions or to resolve service mapping issues.
  • Service Consolidation: Merges multiple inferred service names into a single, unified service entry.
  • Name Normalization: Strip unnecessary prefixes or suffixes from service names to standardize their format.
  • Use Case: Imagine a situation where multiple services with similar names are generating too much noise in your APM dashboards. Use this Skill to consolidate these services into a single name, improving the readability of your metrics and traces.

Quick Start

Remap the 'payments' service to 'financing' with this command: pup apm service-remapping create --name financing --filter 'service:payments' --rule-type 0 --value 'financing'

Frequently Asked Questions about service-remapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rename APM service names at ingestion time without re-instrumenting my application?

You can rename APM services at ingestion time by applying remapping rules that rewrite incoming telemetry data dynamically, ensuring consistent service mapping without modifying application code.

What is inferred service remapping and when do I need it for APM data normalization?

Inferred service remapping consolidates multiple auto-generated service entries into a unified name. You need it when similar inferred services create excessive dashboard noise and obscure your application performance monitoring visibility.

Do I need to set peer.service tags before consolidating inferred APM services?

Yes, setting the peer.service tag is required for inferred entity remapping. This tag provides the necessary context to accurately identify, merge, and rewrite target APM service names.

How do I consolidate multiple noisy APM service entries into a single unified service?

You consolidate noisy APM services by creating a remapping rule that filters by the target service name and rewrites the value to a single unified entry, simplifying service mapping and metrics readability.

Can I strip unnecessary prefixes or suffixes from APM service names to standardize telemetry format?

Yes, you can normalize APM service names by applying remapping rules that strip unnecessary prefixes or suffixes during ingestion, standardizing the format of your application performance monitoring telemetry.