Overrides in APM

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Overview

Both integration overrides and service overrides change the service name of spans. The initial service name is referred to as the base service.

This page explains integration overrides and service overrides in APM.

Integration overrides

Datadog tracing libraries automatically set different service names on client spans to represent databases, queues, or third-party dependencies in integrations. These types of overrides are referred to as integration overrides. With inferred entities, integration overrides are not necessary to represent dependencies, and may pollute service lists and maps. For instructions on how to remove integration overrides, see Integration Override Removal.

Service overrides

You can manually set the service name on spans. This gives you visibility into specific components of the service, such as shared libraries and middleware layers. These types of overrides are referred to as service overrides.

How overrides are represented

Integration overrides and service overrides are represented similarly in APM.

In service and resource pages

Services that are overrides are flagged in the service page header. Hover over the flag to see the list of base services where the service name is overridden.

Service page overrides

In service maps

In service maps, overrides are represented as part of the edge going from the base service and the inferred service.

Service map overrides

In traces

In the trace side panel, the client span header represents the call going from the base service to the inferred service. The top of the overview section also shows information about the base service name, the overridden service name, and the inferred entity name.

Trace side panel service overrides

Removing integration overrides

You can remove integration overrides directly in the Datadog UI or with a configuration change. For more details, see Integration Override Removal.

Glossary

Integration override

A service name set for a span which differs from the default DD_SERVICE name, set automatically by some Datadog integrations.

Service override

A service name set for a span which differs from the default DD_SERVICE name, set manually by users.

Base service

The default DD_SERVICE name.

Further reading

Documentation, liens et articles supplémentaires utiles: