To enable trace search, services must be flowing into Datadog. Once services are set up, navigate to the Trace Search & Analytics docs page to find a list of each of the services running within your infrastructure.
In Datadog, every automatically instrumented service has an operation name, which is used to set the type of request being traced. For example, if you’re tracing a Python Flask application, you might have a
flask.request as your operation name. In a Node application using Express, you would have
express.request ask your operation name.
Replace both the
<OPERATION_NAME> in your configuration with the service name and operation name of the traces you want to add to Trace Search.
For example, if you have a Python service named
python-api, and it’s running Flask (operation name
<SERVICE_NAME> would be
python-api, and your
<OPERATION_NAME> would be
The Trace Search & Analytics docs page populates with a list of your services and resource names available for usage in Trace Search:
servicesto extract APM events from.
apm_config. For example:
apm_config: analyzed_spans: <SERVICE_NAME_1>|<OPERATION_NAME_1>: 1 <SERVICE_NAME_2>|<OPERATION_NAME_2>: 1
[trace.analyzed_spans]. For example:
[trace.analyzed_spans] <SERVICE_NAME_1>|<OPERATION_NAME_1>: 1 <SERVICE_NAME_2>|<OPERATION_NAME_2>: 1
DD_APM_ANALYZED_SPANS to the Agent container environment (compatible with version 12.6.5250+). Format should be a comma-separated regular expressions without spaces. For example: