diff --git a/content/en/profiler/enabling/full_host.md b/content/en/profiler/enabling/full_host.md index f849334b5beef..5dd860a88f7c2 100644 --- a/content/en/profiler/enabling/full_host.md +++ b/content/en/profiler/enabling/full_host.md @@ -40,6 +40,8 @@ Debugging information ## Installation +
Always set DD_SERVICE for each service you want to profile and identify separately. This ensures accurate attribution and more actionable profiling data. To learn more, see Service naming + The Full-Host Profiler is distributed as a standalone executable. ### Container environments @@ -72,6 +74,16 @@ To build the Full-Host Profiler directly on your machine, run: make ``` +## Service naming +When using full-host profiling, Datadog captures profiles from all processes running on the host. The service name for each process depends on the `DD_SERVICE` environment variable. + +If `DD_SERVICE` is set, the profiler uses the value of `DD_SERVICE` as the service name. This is the recommended and most reliable approach. + +If `DD_SERVICE` is not set, Datadog infers a service name from the binary name. For interpreted languages, this is the name of the interpreter. For example, for a service written in Java, the full-host profiler sets the service name to `service:java`. +{{< img src="profiler/inferred_service_example.png" alt="Example of an inferred services within Profiling" style="width:50%;">}} + +If multiple services are running under the same interpreter (for example, two separate Java applications on the same host), and neither sets `DD_SERVICE`, Datadog groups them together under the same service name. Datadog cannot distinguish between them unless you provide a unique service name. + ## What's next? diff --git a/static/images/profiler/inferred_service_example.png b/static/images/profiler/inferred_service_example.png new file mode 100644 index 0000000000000..6c370a3342de6 Binary files /dev/null and b/static/images/profiler/inferred_service_example.png differ