Caution
Grafana Agent has reached End-of-Life (EOL) on November 1, 2025. Agent is no longer receiving vendor support and will no longer receive security or bug fixes. Current users of Agent Static mode, Agent Flow mode, and Agent Operator should proceed with migrating to Grafana Alloy. If you have already migrated to Alloy, no further action is required. Read more about why we recommend migrating to Grafana Alloy.
Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
phlare.write
phlare.write receives performance profiles from other components and forwards them
to a series of user-supplied endpoints using Phlare’ Push API.
Multiple phlare.write components can be specified by giving them
different labels.
Usage
phlare.write "LABEL" {
endpoint {
url = PHLARE_URL
...
}
...
}Arguments
The following arguments are supported:
Blocks
The following blocks are supported inside the definition of
phlare.write:
The > symbol indicates deeper levels of nesting. For example, endpoint > http_client_config refers to an http_client_config block defined inside an
endpoint block.
endpoint block
The endpoint block describes a single location to send profiles to. Multiple
endpoint blocks can be provided to send profiles to multiple locations.
The following arguments are supported:
When multiple endpoint blocks are provided, profiles are concurrently forwarded to all
configured locations.
http_client_config block
The http_client_config configures settings used to connect to the
remote_write server.
bearer_token, bearer_token_file, basic_auth, authorization, and
oauth2 are mutually exclusive and only one can be provided inside of a
http_client_config block.
basic_auth block
password and password_file are mututally exclusive and only one can be
provided inside of a basic_auth block.
authorization block
credential and credentials_file are mutually exclusive and only one can be
provided inside of an authorization block.
oauth2 block
client_secret and client_secret_file are mututally exclusive and only one
can be provided inside of an oauth2 block.
The oauth2 block may also contain its own separate tls_config sub-block.
tls_config block
When min_version is not 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)
Exported fields
The following fields are exported and can be referenced by other components:
Component health
phlare.write is only reported as unhealthy if given an invalid
configuration. In those cases, exported fields are kept at their last healthy
values.
Debug information
phlare.write does not expose any component-specific debug
information.
Example
phlare.write "staging" {
// Send metrics to a locally running Phlare instance.
endpoint {
url = "http://phlare:4100"
headers = {
"X-Scope-Org-ID" = "squad-1",
}
}
external_labels = {
"env" = "staging",
}
}
phlare.scrape "default" {
targets = [
{"__address__" = "phlare:4100", "app"="phlare"},
{"__address__" = "agent:12345", "app"="agent"},
]
forward_to = [phlare.write.staging.receiver]
}


