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 Alloy Reference Components discovery discovery.nomad

discovery.nomad

discovery.nomad allows you to retrieve scrape targets from Nomad’s Service API.

Usage

alloy Copy

discovery.nomad "<LABEL>" {
}

Arguments

You can use the following arguments with discovery.nomad:

At most, one of the following can be provided:

• authorization block
• basic_auth block
• bearer_token_file argument
• bearer_token argument
• oauth2 block

Blocks

You can use the following blocks with discovery.nomad:

The > symbol indicates deeper levels of nesting. For example, oauth2 > tls_config refers to a tls_config block defined inside an oauth2 block.

authorization

The authorization block configures generic authorization to the endpoint.

basic_auth

The basic_auth block configures basic authentication to the endpoint.

oauth2

The oauth block configures OAuth 2.0 authentication to the endpoint.

tls_config

The tls_config block configures TLS settings for connecting to the endpoint.

Exported fields

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

Each target includes the following labels:

• __meta_nomad_address: The service address of the target.
• __meta_nomad_dc: The data center name for the target.
• __meta_nomad_namespace: The namespace of the target.
• __meta_nomad_node_id: The node name defined for the target.
• __meta_nomad_service_address: The service address of the target.
• __meta_nomad_service_id: The service ID of the target.
• __meta_nomad_service_port: The service port of the target.
• __meta_nomad_service: The name of the service the target belongs to.
• __meta_nomad_tags: The list of tags of the target joined by the tag separator.

Component health

discovery.nomad is only reported as unhealthy when given an invalid configuration. In those cases, exported fields retain their last healthy values.

Debug information

discovery.nomad doesn’t expose any component-specific debug information.

Debug metrics

discovery.nomad doesn’t expose any component-specific debug metrics.

Example

This example discovers targets from a Nomad server:

alloy Copy

discovery.nomad "example" {
}

prometheus.scrape "demo" {
  targets    = discovery.nomad.example.targets
  forward_to = [prometheus.remote_write.demo.receiver]
}

prometheus.remote_write "demo" {
  endpoint {
    url = "<PROMETHEUS_REMOTE_WRITE_URL>"

    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

discovery.nomad has exports that can be consumed by the following components:

• Components that consume Targets