Learn how Software Catalog discovers services from Datadog APM, USM, RUM, infrastructure metrics, and logs.

APM, USM, RUM Users

Datadog Software Catalog is pre-populated with entries detected through APM, eBPF-based autodiscovery with Universal Service Monitoring, and RUM applications.

Note: Datadog APM automatically discovers dependencies–such as databases, queues, and third-party dependencies–for instrumented services, even if the dependencies haven’t been instrumented yet. These un-instrumented dependencies are each categorized as services, and Datadog applies their names to service tags on client spans (span.kind:client). For example, a client span representing a client call from a service auth-dotnet to a PostgreSQL database would be tagged with service:auth-dotnet-postgres.

If you are using APM and would like to remove the automatically named services from your Software Catalog and Service Map, you can opt in to inferred entities to filter Software Catalog entries by entity type, such as database, queue, or third-party dependencies. You can optionally remove service overrides like service:my-service-http-client from your catalog or map.

For information about discovering endpoints, see Discovering Endpoints from APM.

Infrastructure and Logs Users

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:

Setting Up Software CatalogDOCUMENTATION