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

discovery.marathon

discovery.marathon allows you to retrieve scrape targets from Marathon’s Service API.

Usage

Alloy Copy

discovery.marathon "LABEL" {
  servers = [MARATHON_SERVER1, MARATHON_SERVER2...]
}

Arguments

The following arguments are supported:

At most, one of the following can be provided:

• auth_token argument.
• auth_token_file argument.
• bearer_token_file argument.
• bearer_token argument.
• basic_auth block.
• authorization block.
• oauth2 block.

Blocks

The following blocks are supported inside the definition of discovery.marathon:

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

authorization block

oauth2 block

tls_config block

Exported fields

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

Each target includes the following labels:

• __meta_marathon_app: the name of the app (with slashes replaced by dashes).
• __meta_marathon_image: the name of the Docker image used (if available).
• __meta_marathon_task: the ID of the Mesos task.
• __meta_marathon_app_label_<labelname>: any Marathon labels attached to the app.
• __meta_marathon_port_definition_label_<labelname>: the port definition labels.
• __meta_marathon_port_mapping_label_<labelname>: the port mapping labels.
• __meta_marathon_port_index: the port index number (e.g. 1 for PORT1).

Component health

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

Debug information

discovery.marathon does not expose any component-specific debug information.

Debug metrics

discovery.marathon does not expose any component-specific debug metrics.

Example

This example discovers targets from a Marathon server:

Alloy Copy

discovery.marathon "example" {
  servers = ["localhost:8500"]
}

prometheus.scrape "demo" {
  targets    = discovery.marathon.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.marathon has exports that can be consumed by the following components:

• Components that consume Targets