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.

Documentation Grafana Agent Flow mode Concepts Configuration language

Configuration language

Grafana Agent Flow dynamically configures and connects components with a custom configuration language called River.

River aims to reduce errors in configuration files by making configurations easier to read and write. River configurations use blocks that can be easily copied and pasted from the documentation to help you get started as quickly as possible.

A River configuration file tells Grafana Agent Flow which components to launch and how to bind them together into a pipeline.

The River syntax uses blocks, attributes, and expressions.

river Copy

// Create a local.file component labeled my_file.
// This can be referenced by other components as local.file.my_file.
local.file "my_file" {
  filename = "/tmp/my-file.txt"
}

// Pattern for creating a labeled block, which the above block follows:
BLOCK_NAME "BLOCK_LABEL" {
  // Block body
  IDENTIFIER = EXPRESSION // Attribute
}

// Pattern for creating an unlabeled block:
BLOCK_NAME {
  // Block body
  IDENTIFIER = EXPRESSION // Attribute
}

River is designed with the following requirements in mind:

• Fast: The configuration language must be fast so the component controller can quickly evaluate changes.
• Simple: The configuration language must be easy to read and write to minimize the learning curve.
• Debuggable: The configuration language must give detailed information when there’s a mistake in the configuration file.

River is similar to HCL, the language Terraform and other Hashicorp projects use. It’s a distinct language with custom syntax and features, such as first-class functions.

• Blocks are a group of related settings and usually represent creating a component. Blocks have a name that consists of zero or more identifiers separated by ., an optional user label, and a body containing attributes and nested blocks.
• Attributes appear within blocks and assign a value to a name.
• Expressions represent a value, either literally or by referencing and combining other values. You use expressions to compute a value for an attribute.

River is declarative, so ordering components, blocks, and attributes within a block isn’t significant. The relationship between components determines the order of operations.

Attributes

You use Attributes to configure individual settings. Attributes always take the form of ATTRIBUTE_NAME = ATTRIBUTE_VALUE.

The following example shows how to set the log_level attribute to "debug".

river Copy

log_level = "debug"

Expressions

You use expressions to compute the value of an attribute. The simplest expressions are constant values like "debug", 32, or [1, 2, 3, 4]. River supports complex expressions, for example:

• Referencing the exports of components: local.file.password_file.content
• Mathematical operations: 1 + 2, 3 * 4, (5 * 6) + (7 + 8)
• Equality checks: local.file.file_a.content == local.file.file_b.content
• Calling functions from River’s standard library: env("HOME") retrieves the value of the HOME environment variable.

You can use expressions for any attribute inside a component definition.

Referencing component exports

The most common expression is to reference the exports of a component, for example, local.file.password_file.content. You form a reference to a component’s exports by merging the component’s name (for example, local.file), label (for example, password_file), and export name (for example, content), delimited by a period.

Blocks

You use Blocks to configure components and groups of attributes. Each block can contain any number of attributes or nested blocks.

river Copy

prometheus.remote_write "default" {
  endpoint {
    url = "http://localhost:9009/api/prom/push"
  }
}

The preceding example has two blocks:

• prometheus.remote_write "default": A labeled block which instantiates a prometheus.remote_write component. The label is the string "default".
• endpoint: An unlabeled block inside the component that configures an endpoint to send metrics to. This block sets the url attribute to specify the endpoint.

Tooling

You can use one or all of the following tools to help you write configuration files in River.

• Experimental editor support for
  • vim
  • VSCode
  • river-mode for Emacs
• Code formatting using the agent fmt command

You can also start developing your own tooling using the Grafana Agent repository as a go package or use the tree-sitter grammar with other programming languages.