---
title: "pyroscope.scrape | Grafana Alloy documentation"
description: "Learn about pyroscope.scrape"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# `pyroscope.scrape`

`pyroscope.scrape` collects [pprof](https://github.com/google/pprof/blob/main/doc/README.md) performance profiles for a given set of HTTP `targets`.

`pyroscope.scrape` mimics the scraping behavior of `prometheus.scrape`. Similarly to how Prometheus scrapes metrics via HTTP, `pyroscope.scrape` collects profiles via HTTP requests.

Unlike Prometheus, which usually only scrapes one `/metrics` endpoint per target, `pyroscope.scrape` may need to scrape multiple endpoints for the same target. This is because the component scrapes different profile types from different endpoints. For example, the component may scrape mutex profiles from a `/debug/pprof/delta_mutex` HTTP endpoint, and memory consumption from a `/debug/pprof/allocs` HTTP endpoint.

You can configure the profile paths, protocol scheme, scrape interval, scrape timeout, query parameters, and any other settings within `pyroscope.scrape`.

The `pyroscope.scrape` component regards a scrape as successful if it responded with an HTTP `200 OK` status code and returned the body of a valid [pprof](https://github.com/google/pprof/blob/main/doc/README.md) profile.

If a scrape request fails, the [debug UI](../../../../troubleshoot/debug/) for `pyroscope.scrape` shows:

- Detailed information about the failure.
- The time of the last successful scrape.
- The labels last used for scraping.

The component can forward the scraped performance profiles to components such as `pyroscope.write` through the `forward_to` argument.

You can specify multiple `pyroscope.scrape` components by giving them different labels.

## Usage

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
pyroscope.scrape "<LABEL>" {
  targets    = <TARGET_LIST>
  forward_to = <RECEIVER_LIST>
}
```

## Arguments

`pyroscope.scrape` starts a scrape job to scrape all of the input targets. The component can start multiple scrape jobs for a single input target when it scrapes multiple profile types.

You can use the following arguments with `pyroscope.scrape`:

Expand table

| Name                       | Type                     | Description                                                                                      | Default        | Required |
|----------------------------|--------------------------|--------------------------------------------------------------------------------------------------|----------------|----------|
| `forward_to`               | `list(ProfilesReceiver)` | List of receivers to send scraped profiles to.                                                   |                | yes      |
| `targets`                  | `list(map(string))`      | List of targets to scrape.                                                                       |                | yes      |
| `bearer_token`             | `secret`                 | Bearer token to authenticate with.                                                               |                | no       |
| `bearer_token_file`        | `string`                 | File containing a bearer token to authenticate with.                                             |                | no       |
| `delta_profiling_duration` | `duration`               | How long to scrape a delta profile. Must be larger than 1 second.                                | `"14s"`        | no       |
| `enable_http2`             | `bool`                   | Whether to support HTTP2 for requests.                                                           | `true`         | no       |
| `follow_redirects`         | `bool`                   | Whether to follow redirects from the server.                                                     | `true`         | no       |
| `http_headers`             | `map(list(secret))`      | Custom HTTP headers to send with each request. The map key is the header name.                   |                | no       |
| `job_name`                 | `string`                 | The job name to override the job label with.                                                     | component name | no       |
| `no_proxy`                 | `string`                 | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |                | no       |
| `params`                   | `map(list(string))`      | A set of query parameters to send when scraping the target.                                      |                | no       |
| `proxy_connect_header`     | `map(list(secret))`      | Specifies headers to send to proxies during CONNECT requests.                                    |                | no       |
| `proxy_from_environment`   | `bool`                   | Use the proxy URL indicated by environment variables.                                            | `false`        | no       |
| `proxy_url`                | `string`                 | HTTP proxy to send requests through.                                                             |                | no       |
| `scheme`                   | `string`                 | The URL scheme with which to fetch profiles from targets.                                        | `"http"`       | no       |
| `scrape_interval`          | `duration`               | How frequently to scrape the targets of this scrape configuration.                               | `"15s"`        | no       |
| `scrape_timeout`           | `duration`               | The timeout for scraping targets of this configuration.                                          | `"10s"`        | no       |

You can provide at most one of the following:

- [`authorization`](#authorization) block
- [`basic_auth`](#basic_auth) block
- [`bearer_token_file`](#arguments) argument
- [`bearer_token`](#arguments) argument
- [`oauth2`](#oauth2) block

Any omitted arguments take on their default values. If you pass conflicting arguments, for example, configuring both `bearer_token` and `bearer_token_file`, then `pyroscope.scrape` fails to start and reports an error.

`no_proxy` can contain IPs, CIDR notations, and domain names. IP and domain names can contain port numbers. `proxy_url` must be configured if `no_proxy` is configured.

`proxy_from_environment` uses the environment variables HTTP\_PROXY, HTTPS\_PROXY, and NO\_PROXY (or the lowercase versions thereof). Requests use the proxy from the environment variable matching their scheme, unless excluded by NO\_PROXY. `proxy_url` and `no_proxy` must not be configured if `proxy_from_environment` is configured.

`proxy_connect_header` should only be configured if `proxy_url` or `proxy_from_environment` are configured.

### `job_name`

The `job_name` argument defaults to the component’s unique identifier.

For example, the `job_name` of `pyroscope.scrape "local" { ... }` is `"pyroscope.scrape.local"`.

### `targets`

You can define the list of `targets` [statically](#default-endpoints-of-static-targets), [dynamically](#default-endpoints-of-dynamic-targets), or as a [combination of both](#default-endpoints-of-static-and-dynamic-targets).

The following special labels can change the behavior of `pyroscope.scrape`:

- `__address__` is the special label that *must always* be present and corresponds to the `<host>:<port>` that’s used for the scrape request.
- `__name__` is the special label that indicates which profile type the component collects.
- `__profile_path__` is the special label that holds the path to the profile endpoint on the target (for example, “/debug/pprof/allocs”).
- `__profile_path_prefix__` is the special label that holds an optional prefix to prepend to the profile path (for example, `"/mimir-prometheus"`).
- `service_name` is a required label that identifies the service you profile.

The component treats labels that start with a double underscore as *internal* and removes them before scraping.

Every profile carries a `service_name` label. You can set it on the target yourself. If you don’t, `pyroscope.scrape` adds the label and infers a value from the following sources, in this order:

1. `__meta_kubernetes_pod_annotation_pyroscope_io_service_name` which is a `pyroscope.io/service_name` Pod annotation.
2. `__meta_kubernetes_namespace` and `__meta_kubernetes_pod_container_name`
3. `__meta_docker_container_name`
4. `__meta_dockerswarm_container_label_service_name` or `__meta_dockerswarm_service_name`

When you don’t set `service_name` and the component can’t infer a value, it uses `unspecified`.

The component injects the following labels into the scraped profiles so that you can link them to a scrape target:

Expand table

| Label                  | Description                                                                  |
|------------------------|------------------------------------------------------------------------------|
| `"job"`                | The `job_name` that the target belongs to.                                   |
| `"instance"`           | The `__address__` or `<host>:<port>` of the scrape target’s URL.             |
| `"service_name"`       | The inferred Pyroscope service name.                                         |
| `"otel.scope.name"`    | The instrumentation scope name, set to `com.grafana.alloy/pyroscope.scrape`. |
| `"otel.scope.version"` | The Alloy version that produced the profile.                                 |

Alloy only sets `otel.scope.name` and `otel.scope.version` if they aren’t already present on the scraped profile. `otel.scope.version` is only set when `otel.scope.name` matches the default value.

#### `scrape_interval`

The `scrape_interval` typically refers to the frequency with which Alloy collects performance profiles from the monitored targets. It represents the time interval between consecutive scrapes or data collection events. This parameter is important for controlling the trade-off between resource usage and the freshness of the collected data.

If `scrape_interval` is short:

- Advantages:
  
  - The component loses fewer profiles if the scraped application crashes.
- Disadvantages:
  
  - Greater consumption of CPU, memory, and network resources during scrapes and remote writes.
  - The backend database (Pyroscope) consumes more storage space.

If `scrape_interval` is long:

- Advantages:
  
  - Lower resource consumption.
- Disadvantages:
  
  - The component loses more profiles if the scraped application crashes.
  - If you set the [delta argument](#delta-argument) to `true`, the batch size of each remote write to Pyroscope may be bigger. You may need to tune the Pyroscope database with higher limits.
  - If you set the [delta argument](#delta-argument) to `true`, you run a larger risk of reaching the HTTP server timeouts of the scraped application.

For example, consider this situation:

- You configure `pyroscope.scrape` with a `scrape_interval` of `"60s"`.
- The scraped application runs an HTTP server with a timeout of 30 seconds.
- Any scrape HTTP requests where you set the [delta argument](#delta-argument) to `true` fail, because they attempt to run for 59 seconds.

## Blocks

You can use the following blocks with `pyroscope.scrape`:

No valid configuration blocks found.

Any omitted blocks take on their default values. For example, if you don’t specify `profile.mutex` in the configuration, the component uses the defaults documented in [profile.mutex](#profilemutex).

### `authorization`

Expand table

| Name               | Type     | Description                                | Default | Required |
|--------------------|----------|--------------------------------------------|---------|----------|
| `credentials_file` | `string` | File containing the secret value.          |         | no       |
| `credentials`      | `secret` | Secret value.                              |         | no       |
| `type`             | `string` | Authorization type, for example, “Bearer”. |         | no       |

`credential` and `credentials_file` are mutually exclusive, and only one can be provided inside an `authorization` block.

> Warning
> 
> Using `credentials_file` causes the file to be read on every outgoing request. Use the `local.file` component with the `credentials` attribute instead to avoid unnecessary reads.

### `basic_auth`

Expand table

| Name            | Type     | Description                                           | Default | Required |
|-----------------|----------|-------------------------------------------------------|---------|----------|
| `password_file` | `string` | Path to a file that contains the basic auth password. |         | no       |
| `password`      | `secret` | Basic auth password.                                  |         | no       |
| `username`      | `string` | Basic auth username.                                  |         | no       |

When you use `password_file`, the file is read on every outgoing request that uses basic authentication.

`password` and `password_file` are mutually exclusive, and only one can be provided inside a `basic_auth` block.

> Note
> 
> High scrape or write rates create repeated file reads when you use `password_file`. You can use the [`local.file`](/docs/alloy/v1.20/reference/components/local/local.file/) component to read the password file and provide the content to the `password` attribute. This avoids repeated file reads because `local.file` monitors the file and reads when it changes.

### `clustering`

Expand table

| Name      | Type   | Description                                       | Default | Required |
|-----------|--------|---------------------------------------------------|---------|----------|
| `enabled` | `bool` | Enables sharing targets with other cluster nodes. | `false` | yes      |

When Alloy is [using clustering](../../../../get-started/clustering/), and you set `enabled` to true, this `pyroscope.scrape` component instance opts in to participating in the cluster to distribute scrape load between all cluster nodes.

Clustering causes the set of targets to be locally filtered down to a unique subset per node, where each node is roughly assigned the same number of targets. If the state of the cluster changes, such as when a node joins, the cluster recalculates the subset of targets to scrape per node.

When you enable clustering mode, all Alloy instances participating in the cluster must use the same configuration file and have access to the same service discovery APIs.

If Alloy is *not* running in clustered mode, this block is a no-op.

### `oauth2`

Expand table

| Name                     | Type                | Description                                                                                      | Default | Required |
|--------------------------|---------------------|--------------------------------------------------------------------------------------------------|---------|----------|
| `client_id`              | `string`            | OAuth2 client ID.                                                                                |         | no       |
| `client_secret_file`     | `string`            | File containing the OAuth2 client secret.                                                        |         | no       |
| `client_secret`          | `secret`            | OAuth2 client secret.                                                                            |         | no       |
| `endpoint_params`        | `map(string)`       | Optional parameters to append to the token URL.                                                  |         | no       |
| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |         | no       |
| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |         | no       |
| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
| `scopes`                 | `list(string)`      | List of scopes to authenticate with.                                                             |         | no       |
| `token_url`              | `string`            | URL to fetch the token from.                                                                     |         | no       |

`client_secret` and `client_secret_file` are mutually exclusive, and only one can be provided inside an `oauth2` block.

> Warning
> 
> Using `client_secret_file` causes the file to be read on every outgoing request. Use the `local.file` component with the `client_secret` attribute instead to avoid unnecessary reads.

The `oauth2` block may also contain a separate `tls_config` sub-block.

`no_proxy` can contain IPs, CIDR notations, and domain names. IP and domain names can contain port numbers. `proxy_url` must be configured if `no_proxy` is configured.

`proxy_from_environment` uses the environment variables HTTP\_PROXY, HTTPS\_PROXY, and NO\_PROXY (or the lowercase versions thereof). Requests use the proxy from the environment variable matching their scheme, unless excluded by NO\_PROXY. `proxy_url` and `no_proxy` must not be configured if `proxy_from_environment` is configured.

`proxy_connect_header` should only be configured if `proxy_url` or `proxy_from_environment` are configured.

### `profiling_config`

The `profiling_config` block configures the profiling settings when scraping targets.

You can use the following arguments with the `profiling_config` block:

Expand table

| Name          | Type     | Description                                   | Default | Required |
|---------------|----------|-----------------------------------------------|---------|----------|
| `path_prefix` | `string` | The path prefix to use when scraping targets. |         | no       |

### `profile.block`

The `profile.block` block collects profiles on process blocking.

You can use the following arguments with the `profile.block` block:

Expand table

| Name      | Type      | Description                                 | Default                | Required |
|-----------|-----------|---------------------------------------------|------------------------|----------|
| `delta`   | `boolean` | Whether to scrape the profile as a delta.   | `false`                | no       |
| `enabled` | `boolean` | Enable scraping for this profile type.      | `true`                 | no       |
| `path`    | `string`  | The path to the profile type on the target. | `"/debug/pprof/block"` | no       |

For more information about the `delta` argument, see the [delta argument](#delta-argument) section.

### `profile.custom`

The `profile.custom` block collects profiles from custom endpoints. You must give each block a label:

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
profile.custom "<PROFILE_TYPE>" {
  enabled = true
  path    = "<PROFILE_PATH>"
}
```

You can specify multiple `profile.custom` blocks. Labels assigned to `profile.custom` blocks must be unique across the component.

You can use the following arguments with the `profile.custom` block:

Expand table

| Name      | Type      | Description                                 | Default | Required |
|-----------|-----------|---------------------------------------------|---------|----------|
| `delta`   | `boolean` | Whether to scrape the profile as a delta.   | `false` | no       |
| `enabled` | `boolean` | Enable scraping for this profile type.      |         | yes      |
| `path`    | `string`  | The path to the profile type on the target. |         | yes      |

When the `delta` argument is `true`, a `seconds` query parameter is automatically added to requests. The `seconds` used is equal to `scrape_interval - 1`.

### `profile.fgprof`

The `profile.fgprof` block collects profiles from an [fgprof](https://github.com/felixge/fgprof) endpoint.

You can use the following arguments with the `profile.fgprof` block:

Expand table

| Name      | Type      | Description                                 | Default           | Required |
|-----------|-----------|---------------------------------------------|-------------------|----------|
| `delta`   | `boolean` | Whether to scrape the profile as a delta.   | `true`            | no       |
| `enabled` | `boolean` | Enable scraping for this profile type.      | `false`           | no       |
| `path`    | `string`  | The path to the profile type on the target. | `"/debug/fgprof"` | no       |

For more information about the `delta` argument, see the [delta argument](#delta-argument) section.

### `profile.godeltaprof_block`

The `profile.godeltaprof_block` block collects profiles from the [godeltaprof](https://github.com/grafana/pyroscope-go/tree/main/godeltaprof) block endpoint. The target computes the delta.

You can use the following arguments with the `profile.godeltaprof_block` block:

Expand table

| Name      | Type      | Description                                 | Default                      | Required |
|-----------|-----------|---------------------------------------------|------------------------------|----------|
| `enabled` | `boolean` | Enable scraping for this profile type.      | `false`                      | no       |
| `path`    | `string`  | The path to the profile type on the target. | `"/debug/pprof/delta_block"` | no       |

### `profile.godeltaprof_memory`

The `profile.godeltaprof_memory` block collects profiles from the [godeltaprof](https://github.com/grafana/pyroscope-go/tree/main/godeltaprof) memory endpoint. The target computes the delta.

You can use the following arguments with the `profile.godeltaprof_memory` block:

Expand table

| Name      | Type      | Description                                 | Default                     | Required |
|-----------|-----------|---------------------------------------------|-----------------------------|----------|
| `enabled` | `boolean` | Enable scraping for this profile type.      | `false`                     | no       |
| `path`    | `string`  | The path to the profile type on the target. | `"/debug/pprof/delta_heap"` | no       |

### `profile.godeltaprof_mutex`

The `profile.godeltaprof_mutex` block collects profiles from the [godeltaprof](https://github.com/grafana/pyroscope-go/tree/main/godeltaprof) mutex endpoint. The target computes the delta.

You can use the following arguments with the `profile.godeltaprof_mutex` block:

Expand table

| Name      | Type      | Description                                 | Default                      | Required |
|-----------|-----------|---------------------------------------------|------------------------------|----------|
| `enabled` | `boolean` | Enable scraping for this profile type.      | `false`                      | no       |
| `path`    | `string`  | The path to the profile type on the target. | `"/debug/pprof/delta_mutex"` | no       |

### `profile.goroutine`

The `profile.goroutine` block collects profiles on the number of goroutines.

You can use the following arguments with the `profile.goroutine` block:

Expand table

| Name      | Type      | Description                                 | Default                    | Required |
|-----------|-----------|---------------------------------------------|----------------------------|----------|
| `delta`   | `boolean` | Whether to scrape the profile as a delta.   | `false`                    | no       |
| `enabled` | `boolean` | Enable scraping for this profile type.      | `true`                     | no       |
| `path`    | `string`  | The path to the profile type on the target. | `"/debug/pprof/goroutine"` | no       |

Refer to [delta argument](#delta-argument) for more information about the `delta` argument.

### `profile.memory`

The `profile.memory` block collects profiles on memory consumption.

You can use the following arguments with the `profile.memory` block:

Expand table

| Name      | Type      | Description                                 | Default                 | Required |
|-----------|-----------|---------------------------------------------|-------------------------|----------|
| `delta`   | `boolean` | Whether to scrape the profile as a delta.   | `false`                 | no       |
| `enabled` | `boolean` | Enable scraping for this profile type.      | `true`                  | no       |
| `path`    | `string`  | The path to the profile type on the target. | `"/debug/pprof/allocs"` | no       |

Refer to [delta argument](#delta-argument) for more information about the `delta` argument.

### `profile.mutex`

The `profile.mutex` block collects profiles on mutexes.

You can use the following arguments with the `profile.mutex` block:

Expand table

| Name      | Type      | Description                                 | Default                | Required |
|-----------|-----------|---------------------------------------------|------------------------|----------|
| `delta`   | `boolean` | Whether to scrape the profile as a delta.   | `false`                | no       |
| `enabled` | `boolean` | Enable scraping for this profile type.      | `true`                 | no       |
| `path`    | `string`  | The path to the profile type on the target. | `"/debug/pprof/mutex"` | no       |

Refer to [delta argument](#delta-argument) for more information about the `delta` argument.

### `profile.process_cpu`

The `profile.process_cpu` block collects profiles on CPU consumption for the process.

You can use the following arguments with the `profile.process_cpu` block:

Expand table

| Name      | Type      | Description                                 | Default                  | Required |
|-----------|-----------|---------------------------------------------|--------------------------|----------|
| `delta`   | `boolean` | Whether to scrape the profile as a delta.   | `true`                   | no       |
| `enabled` | `boolean` | Enable scraping for this profile type.      | `true`                   | no       |
| `path`    | `string`  | The path to the profile type on the target. | `"/debug/pprof/profile"` | no       |

For more information about the `delta` argument, see the [delta argument](#delta-argument) section.

### `tls_config`

Expand table

| Name                   | Type     | Description                                              | Default | Required |
|------------------------|----------|----------------------------------------------------------|---------|----------|
| `ca_pem`               | `string` | CA PEM-encoded text to validate the server with.         |         | no       |
| `ca_file`              | `string` | CA certificate to validate the server with.              |         | no       |
| `cert_pem`             | `string` | Certificate PEM-encoded text for client authentication.  |         | no       |
| `cert_file`            | `string` | Certificate file for client authentication.              |         | no       |
| `insecure_skip_verify` | `bool`   | Disables validation of the server certificate.           |         | no       |
| `key_file`             | `string` | Key file for client authentication.                      |         | no       |
| `key_pem`              | `secret` | Key PEM-encoded text for client authentication.          |         | no       |
| `min_version`          | `string` | Minimum acceptable TLS version.                          |         | no       |
| `server_name`          | `string` | ServerName extension to indicate the name of the server. |         | no       |

The following pairs of arguments are mutually exclusive and can’t both be set simultaneously:

- `ca_pem` and `ca_file`
- `cert_pem` and `cert_file`
- `key_pem` and `key_file`

When configuring client authentication, both the client certificate (using `cert_pem` or `cert_file`) and the client key (using `key_pem` or `key_file`) must be provided.

When `min_version` isn’t provided, the minimum acceptable TLS version is inherited from Go’s default minimum version, TLS 1.2. If `min_version` is provided, it must be set to one of the following strings:

- `"TLS10"` (TLS 1.0)
- `"TLS11"` (TLS 1.1)
- `"TLS12"` (TLS 1.2)
- `"TLS13"` (TLS 1.3)

> Caution
> 
> If you set `insecure_skip_verify` to `true`, you disable verification of the server’s certificate chain and hostname. Alloy accepts any certificate the server presents, including expired, self-signed, or invalid certificates.
> 
> You can use `insecure_skip_verify` for local development, self-signed certificates, or endpoints that use a private CA outside the system trust store. If the hostname doesn’t match the certificate, set `server_name` instead of `insecure_skip_verify`. In production, use `ca_file` or `ca_pem` to trust a private CA instead of `insecure_skip_verify`.
> 
> Set `insecure_skip_verify` to `true` only in isolated development or testing environments where you don’t transmit sensitive data. Remove the setting before you deploy to production.

## Common configuration

The following configuration applies across the profile types described in [Blocks](#blocks).

### `delta` argument

When the `delta` argument is `false`, the [pprof](https://github.com/google/pprof/blob/main/doc/README.md) HTTP query is instantaneous.

When the `delta` argument is `true`:

- The [pprof](https://github.com/google/pprof/blob/main/doc/README.md) HTTP query runs for a certain amount of time.
- A `seconds` parameter is automatically added to the HTTP request.
- The default value for the `seconds` query parameter is `scrape_interval - 1`. If you set `delta_profiling_duration`, then `seconds` takes the same value as `delta_profiling_duration`. However, the `delta_profiling_duration` can’t be larger than `scrape_interval`. For example, if you set `scrape_interval` to `"15s"`, then `seconds` defaults to `14s` If you set `delta_profiling_duration` to `16s`, then you must set `scrape_interval` to at least `17s`. If the HTTP endpoint is `/debug/pprof/profile`, then the HTTP query becomes `/debug/pprof/profile?seconds=14`

## Exported fields

`pyroscope.scrape` doesn’t export any fields.

## Component health

`pyroscope.scrape` is only reported as unhealthy if given an invalid configuration. In those cases, exported fields retain their last healthy values.

## Debug information

`pyroscope.scrape` reports the status of the last scrape for each configured scrape job on the component’s debug endpoint.

## Debug metrics

The following Prometheus metrics are exposed:

Expand table

| Name                                | Type        | Description                                                  |
|-------------------------------------|-------------|--------------------------------------------------------------|
| `pyroscope_fanout_latency`          | `histogram` | Write latency for sending to direct and indirect components. |
| `pyroscope_forwarded_entries_total` | `counter`   | Total number of samples sent to downstream components.       |

## Examples

The following examples show how to scrape profiles from static and dynamically discovered targets, and how to enable and disable specific profile types.

### Default endpoints of static targets

The following example sets up a scrape job of a statically configured list of targets - Alloy itself and Pyroscope. The component sends the scraped profiles to `pyroscope.write`, which remote writes them to a Pyroscope database.

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
pyroscope.scrape "local" {
  targets = [
    {"__address__" = "localhost:4040", "service_name"="pyroscope"},
    {"__address__" = "localhost:12345", "service_name"="alloy"},
  ]

  forward_to = [pyroscope.write.local.receiver]
}

pyroscope.write "local" {
  endpoint {
    url = "http://pyroscope:4040"
  }
}
```

The component scrapes these endpoints every 15 seconds:

text ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```text
http://localhost:4040/debug/pprof/allocs
http://localhost:4040/debug/pprof/block
http://localhost:4040/debug/pprof/goroutine
http://localhost:4040/debug/pprof/mutex
http://localhost:4040/debug/pprof/profile?seconds=14

http://localhost:12345/debug/pprof/allocs
http://localhost:12345/debug/pprof/block
http://localhost:12345/debug/pprof/goroutine
http://localhost:12345/debug/pprof/mutex
http://localhost:12345/debug/pprof/profile?seconds=14
```

The component adds `seconds=14` to the `/debug/pprof/profile` endpoint, because:

- The `delta` argument of the `profile.process_cpu` block is `true` by default.
- `scrape_interval` is `"15s"` by default.

The component doesn’t scrape the `/debug/fgprof` endpoint, because the `enabled` argument of the `profile.fgprof` block is `false` by default.

### Default endpoints of dynamic targets

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
discovery.http "dynamic_targets" {
  url = "https://example.com/scrape_targets"
  refresh_interval = "15s"
}

pyroscope.scrape "local" {
  targets = [discovery.http.dynamic_targets.targets]

  forward_to = [pyroscope.write.local.receiver]
}

pyroscope.write "local" {
  endpoint {
    url = "http://pyroscope:4040"
  }
}
```

### Default endpoints of static and dynamic targets

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
discovery.http "dynamic_targets" {
  url = "https://example.com/scrape_targets"
  refresh_interval = "15s"
}

pyroscope.scrape "local" {
  targets = array.concat([
    {"__address__" = "localhost:4040", "service_name"="pyroscope"},
    {"__address__" = "localhost:12345", "service_name"="alloy"},
  ], discovery.http.dynamic_targets.targets)

  forward_to = [pyroscope.write.local.receiver]
}

pyroscope.write "local" {
  endpoint {
    url = "http://pyroscope:4040"
  }
}
```

### Enable and disable profiles

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
pyroscope.scrape "local" {
  targets = [
    {"__address__" = "localhost:12345", "service_name"="alloy"},
  ]

  profiling_config {
    profile.fgprof {
      enabled = true
    }
    profile.block {
      enabled = false
    }
    profile.mutex {
      enabled = false
    }
  }

  forward_to = [pyroscope.write.local.receiver]
}
```

The component scrapes these endpoints every 15 seconds:

text ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```text
http://localhost:12345/debug/pprof/allocs
http://localhost:12345/debug/pprof/goroutine
http://localhost:12345/debug/pprof/profile?seconds=14
http://localhost:12345/debug/fgprof?seconds=14
```

These endpoints are **NOT** scraped because they’re explicitly disabled:

text ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```text
http://localhost:12345/debug/pprof/block
http://localhost:12345/debug/pprof/mutex
```

## Compatible components

`pyroscope.scrape` can accept arguments from the following components:

- Components that export [Targets](../../../compatibility/#targets-exporters)
- Components that export [Pyroscope `ProfilesReceiver`](../../../compatibility/#pyroscope-profilesreceiver-exporters)

> Note
> 
> 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.