Caution
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.
remotecfg block (beta)
remotecfg
is an optional configuration block that enables Grafana Agent Flow to fetch and load the configuration from a remote endpoint.
remotecfg
is specified without a label and can only be provided once per configuration file.
The API definition for managing and fetching configuration that the remotecfg
block uses is available under the Apache 2.0 license.
BETA: The
remotecfg
enables beta functionality. Beta features are subject to breaking changes, and may be replaced with equivalent functionality that cover the same use case.
Example
remotecfg {
url = "SERVICE_URL"
basic_auth {
username = "USERNAME"
password_file = "PASSWORD_FILE"
}
id = constants.hostname
metadata = {"cluster" = "dev", "namespace" = "otlp-dev"}
poll_frequency = "5m"
}
Arguments
The following arguments are supported:
If the url
is not set, then the service block is a no-op.
If not set, the self-reported id
that the Agent uses is a randomly generated,
anonymous unique ID (UUID) that is stored as an agent_seed.json
file in the
Agent’s storage path so that it can persist across restarts.
The id
and metadata
fields are used in the periodic request sent to the
remote endpoint so that the API can decide what configuration to serve.
Blocks
The following blocks are supported inside the definition of remotecfg
:
The >
symbol indicates deeper levels of nesting.
For example, oauth2 > tls_config
refers to a tls_config
block defined inside an oauth2
block.
basic_auth block
password
and password_file
are mutually exclusive, and only one can be provided inside a basic_auth
block.
authorization block
credential
and credentials_file
are mutually exclusive, and only one can be provided inside an authorization
block.
oauth2 block
client_secret
and client_secret_file
are mutually exclusive, and only one can be provided inside an oauth2
block.
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.
tls_config block
The following pairs of arguments are mutually exclusive and can’t both be set simultaneously:
ca_pem
andca_file
cert_pem
andcert_file
key_pem
andkey_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
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)