Discover Existing Services in Software Catalog
Learn how Software Catalog discovers services from Datadog Application Performance Monitoring (APM), Universal Service Monitoring (USM), Real User Monitoring (RUM), infrastructure metrics, and logs.
Automatic discovery with APM, USM, and RUM
Datadog Software Catalog is pre-populated with entries detected through APM, eBPF-based autodiscovery with Universal Service Monitoring, and RUM applications.
APM service detection and dependencies
Datadog APM automatically discovers dependencies from instrumented services, even when the dependencies aren’t instrumented. These include:
- Databases
- Message queues
- Other third-party dependencies
These dependencies appear as services, and Datadog automatically applies their names to service tags on client spans (span.kind:client). For example, a client call from auth-dotnet to PostgreSQL would create a service tagged as service:auth-dotnet-postgres.
Managing automatically-named services:
- You can opt-in to inferred entities to filter out entities by type (database, queue, third-party).
- You can optionally remove service overrides such as
service:my-service-http-client from your catalog or map.
For information about discovering endpoints, see Discovering Endpoints from APM.
Discover Infrastructure and Logs services
To discover services through Datadog infrastructure metrics or logs, navigate to the Software Catalog Import Entries tab. You can import services from Datadog telemetry containing the DD_SERVICE tag.
After importing, entries appear in the Explore tab. Entries may expire unless you add metadata, such as the owner or contacts, by using the API or the GitHub integration.
To remove imported services from the default Explore view, click Clear Previously Imported Services on the Import Entries tab. This removes all services that do not have metadata or do not have APM, Universal Service Monitoring (USM), or Real User Monitoring (RUM) telemetry.
Further reading
Additional helpful documentation, links, and articles:
