Trace Search & Analytics is used to filter APM data by user-defined tags such as
app_name to help troubleshoot and filter your requests. To enable it, either:
Note: To enable trace search and analytics with the Agent, services must be already flowing into Datadog.
servicesfrom which to extract APM events.
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:
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