Grafana Alloy is the new name for our distribution of the OTel collector. Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to Grafana Alloy.

This is documentation for the next version of Agent. For the latest stable release, go to the latest version.

Open source


The prometheus.exporter.process component embeds process_exporter for collecting process stats from /proc.


prometheus.exporter.process "LABEL" {


The following arguments can be used to configure the exporter’s behavior. All arguments are optional. Omitted fields take their default values.

procfs_pathstringprocfs mountpoint./procno
track_childrenboolWhether to track a process’ children.trueno
track_threadsboolReport metrics for a process’ individual threads.trueno
gather_smapsboolGather metrics from the smaps file for a process.trueno
recheck_on_scrapeboolRecheck process names on each scrape.trueno


The following blocks are supported inside the definition of prometheus.exporter.process:

matchermatcherA collection of matching rules to use for deciding which processes to

matcher block

Each matcher block config can match multiple processes, which will be tracked as a single process “group.”

namestringThe name to use for identifying the process group name in the metric."{{.ExeBase}}"no
commlist(string)A list of strings that match the base executable name for a process, truncated to 15
exelist(string)A list of strings that match argv[0] for a
cmdlinelist(string)A list of regular expressions applied to the argv of the

The name argument can use the following template variables. By default it uses the base path of the executable:

  • {{.Comm}}: Basename of the original executable from /proc/<pid>/stat.
  • {{.ExeBase}}: Basename of the executable from argv[0].
  • {{.ExeFull}}: Fully qualified path of the executable.
  • {{.Username}}: Username of the effective user.
  • {{.Matches}}: Map containing all regex capture groups resulting from matching a process with the cmdline rule group.
  • {{.PID}}: PID of the process. Note that the PID is copied from the first executable found.
  • {{.StartTime}}: The start time of the process. This is useful when combined with PID as PIDS get reused over time.
  • {{.Cgroups}}: The cgroups, if supported, of the process (/proc/self/cgroup). This is particularly useful for identifying to which container a process belongs.

NOTE: Using PID or StartTime is discouraged, as it is almost never what you want, and is likely to result in high cardinality metrics.

The value that is used for matching comm list elements is derived from reading the second field of /proc/<pid>/stat, stripped of parens.

For values in exe, if there are no slashes, only the basename of argv[0] needs to match. Otherwise, the name must be an exact match. For example, “postgres” may match any postgres binary, but /usr/local/bin/postgres will only match a postgres process with that exact path. If any of the strings match, the process will be tracked.

Each regex in cmdline must match the corresponding argv for the process to be tracked. The first element that is matched is argv[1]. Regex captures are added to the .Matches map for use in the name.

Exported fields

The following fields are exported and can be referenced by other components.

targetslist(map(string))The targets that can be used to collect exporter metrics.

For example, the targets can either be passed to a discovery.relabel component to rewrite the targets’ label sets or to a prometheus.scrape component that collects the exposed metrics.

The exported targets use the configured in-memory traffic address specified by the run command.

Component health

prometheus.exporter.process is only reported as unhealthy if given an invalid configuration. In those cases, exported fields retain their last healthy values.

Debug information

prometheus.exporter.process does not expose any component-specific debug information.

Debug metrics

prometheus.exporter.process does not expose any component-specific debug metrics.


This example uses a prometheus.scrape component to collect metrics from prometheus.exporter.process:

prometheus.exporter.process "example" {
  track_children = false

  matcher {
    comm = ["grafana-agent"]

// Configure a prometheus.scrape component to collect process_exporter metrics.
prometheus.scrape "demo" {
  targets    = prometheus.exporter.process.example.targets
  forward_to = [prometheus.remote_write.demo.receiver]

prometheus.remote_write "demo" {
  endpoint {

    basic_auth {
      username = USERNAME
      password = PASSWORD

Replace the following:

  • PROMETHEUS_REMOTE_WRITE_URL: The URL of the Prometheus remote_write-compatible server to send metrics to.
  • USERNAME: The username to use for authentication to the remote_write API.
  • PASSWORD: The password to use for authentication to the remote_write API.

Compatible components

prometheus.exporter.process has exports that can be consumed by the following components:


Connecting some components may not be sensible or components may require further configuration to make the connection work correctly. Refer to the linked documentation for more details.