OpenTelemetry.Instrumentation.Process

Process Instrumentation for OpenTelemetry .NET

This is an Instrumentation Library, which instruments .NET and collects telemetry about process behavior.

The process metric instruments being implemented are following OpenTelemetry metrics semantic conventions.

Steps to enable OpenTelemetry.Instrumentation.Process

Step 1: Install package

Add a reference to OpenTelemetry.Instrumentation.Process package.

dotnet add package --prerelease OpenTelemetry.Instrumentation.Process

Add a reference to OpenTelemetry.Exporter.Prometheus.HttpListener package.

dotnet add package --prerelease OpenTelemetry.Exporter.Prometheus.HttpListener

Step 2: Enable Process instrumentation

Process instrumentation should be enabled at application startup using the AddProcessInstrumentation extension on MeterProviderBuilder:

using var meterProvider = Sdk.CreateMeterProviderBuilder()
    .AddProcessInstrumentation()
    .AddPrometheusHttpListener()
    .Build();

Refer to Program.cs for a complete demo. This examples sets up the OpenTelemetry Prometheus exporter, which requires adding the package OpenTelemetry.Exporter.Prometheus.HttpListener to the application.

Additionally, this document shows how to use Prometheus and Grafana to build a dashboard for your application. This is the Grafana dashboard template which has all the metrics currently supported by this package; plus an additional aggregated metric CPU utilization calculated with the raw metrics, CPU time and CPU count.

Please follow the instructions in this document to import a Grafana dashboard by uploading the JSON template file.

Metrics

process.memory.usage

The amount of physical memory allocated for this process.

The API used to retrieve the value is:

• Process.WorkingSet64: Gets the amount of physical memory, in bytes, allocated for the associated process.

process.memory.virtual

The amount of committed virtual memory for this process. One way to think of this is all the address space this process can read from without triggering an access violation; this includes memory backed solely by RAM, by a swapfile/pagefile and by other mapped files on disk.

The API used to retrieve the value is:

• Process.VirtualMemorySize64: Gets the amount of the virtual memory, in bytes, allocated for the associated process.

process.cpu.time

Total CPU seconds broken down by CPU modes.

The APIs used to retrieve the values are:

• Process.UserProcessorTime: Gets the user processor time for this process.

• Process.PrivilegedProcessorTime: Gets the privileged processor time for this process.

process.thread.count

Process threads count.

The API used to retrieve the value is:

• Process.Threads: Gets the set of threads that are running in the associated process.

process.uptime

The time the process has been running.

The API used to retrieve the value is:

• Process.StartTime: Gets the time that the associated process was started.

process.windows.handle.count

Number of handles held by the process. Only emitted on Windows.

The API used to retrieve the value is:

• Process.HandleCount: Gets the number of handles opened by the process.

process.unix.file_descriptor.count

Number of unix file descriptors in use by the process. Only emitted on Linux.

The API used to retrieve the value is:

• Process.HandleCount: Gets the number of file descriptors opened by the process.

References

• OpenTelemetry Project