---
title: "Nomad integration | Grafana Cloud documentation"
description: "Learn about Nomad Grafana Cloud integration."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Nomad integration for Grafana Cloud

Nomad is a simple and flexible workload orchestrator to deploy and manage containers and non-containerized applications across on-prem and clouds at scale.

This integration includes 2 pre-built dashboards to help monitor and visualize Nomad metrics.

## Before you begin

Add the [telemetry](https://developer.hashicorp.com/nomad/docs/configuration/telemetry#prometheus) stanza below in your Nomad client and server configuration files, by default it would be /etc/nomad.d/nomad.hcl:

![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```none
telemetry {
  disable_hostname = true
  prometheus_metrics = true
  publish_allocation_metrics = true
  publish_node_metrics = true
}
```

## Install Nomad integration for Grafana Cloud

1. In your Grafana Cloud stack, click **Connections** in the left-hand menu.
2. Find **Nomad** and click its tile to open the integration.
3. Review the prerequisites in the **Configuration Details** tab and set up Grafana Alloy to send Nomad metrics to your Grafana Cloud instance.
4. Click **Install** to add this integration’s pre-built dashboards to your Grafana Cloud instance, and you can start monitoring your Nomad setup.

## Configuration snippets for Grafana Alloy

### Simple mode

These snippets are configured to scrape a single Nomad instance running locally with default ports.

First, **manually** copy and append the following snippets into your alloy configuration file.

### Metrics snippets

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
discovery.relabel "metrics_integrations_integrations_nomad" {
	targets = concat(
		[{
			__address__ = "nomad1:4646",
		}],
		[{
			__address__ = "nomad2:4646",
		}],
		[{
			__address__ = "nomad3:4646",
		}],
		[{
			__address__ = "nomad-client1:4646",
		}],
	)

	rule {
		target_label = "instance"
		replacement  = constants.hostname
	}
}

prometheus.scrape "metrics_integrations_integrations_nomad" {
	targets    = discovery.relabel.metrics_integrations_integrations_nomad.output
	forward_to = [prometheus.remote_write.metrics_service.receiver]
	job_name   = "integrations/nomad"
	params     = {
		format = ["prometheus"],
	}
	metrics_path = "/v1/metrics"
}
```

### Advanced mode

The following snippets provide examples to guide you through the configuration process.

To instruct Grafana Alloy to scrape your Nomad instances, **manually** copy and append the snippets to your alloy configuration file, then follow subsequent instructions.

### Advanced metrics snippets

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
discovery.relabel "metrics_integrations_integrations_nomad" {
	targets = concat(
		[{
			__address__ = "nomad1:4646",
		}],
		[{
			__address__ = "nomad2:4646",
		}],
		[{
			__address__ = "nomad3:4646",
		}],
		[{
			__address__ = "nomad-client1:4646",
		}],
	)

	rule {
		target_label = "instance"
		replacement  = constants.hostname
	}
}

prometheus.scrape "metrics_integrations_integrations_nomad" {
	targets    = discovery.relabel.metrics_integrations_integrations_nomad.output
	forward_to = [prometheus.remote_write.metrics_service.receiver]
	job_name   = "integrations/nomad"
	params     = {
		format = ["prometheus"],
	}
	metrics_path = "/v1/metrics"
}
```

To monitor your Nomad instance, you must use a [discovery.relabel](/docs/alloy/latest/reference/components/discovery.relabel/) component to discover your Nomad Prometheus endpoint and apply appropriate labels, followed by a [prometheus.scrape](/docs/alloy/latest/reference/components/prometheus.scrape) component to scrape it.

Configure the following properties within each `discovery.relabel` component:

- `__address__`: The address to your Nomad Prometheus metrics endpoint.
- `instance` label: `constants.hostname` sets the `instance` label to your Grafana Alloy server hostname. If that is not suitable, change it to a value uniquely identifies this Nomad instance.

If you have multiple Nomad servers to scrape, configure one `discovery.relabel` for each and scrape them by including each under `targets` within the `prometheus.scrape` component.

## Dashboards

The Nomad integration installs the following dashboards in your Grafana Cloud instance to help monitor your system.

- Nomad cluster
- Nomad jobs

**Nomad overview**

**Nomad jobs**

## Metrics

The most important metrics provided by the Nomad integration, which are used on the pre-built dashboards, are as follows:

- nomad\_client\_allocated\_cpu
- nomad\_client\_allocated\_disk
- nomad\_client\_allocated\_memory
- nomad\_client\_allocations\_blocked
- nomad\_client\_allocations\_migrating
- nomad\_client\_allocations\_pending
- nomad\_client\_allocations\_running
- nomad\_client\_allocations\_terminal
- nomad\_client\_allocs\_cpu\_total\_percent
- nomad\_client\_allocs\_cpu\_total\_ticks
- nomad\_client\_allocs\_memory\_cache
- nomad\_client\_allocs\_memory\_rss
- nomad\_client\_host\_cpu\_idle
- nomad\_client\_host\_disk\_available
- nomad\_client\_host\_disk\_inodes\_percent
- nomad\_client\_host\_disk\_size
- nomad\_client\_host\_memory\_available
- nomad\_client\_host\_memory\_free
- nomad\_client\_host\_memory\_total
- nomad\_client\_host\_memory\_used
- nomad\_client\_unallocated\_cpu
- nomad\_client\_unallocated\_disk
- nomad\_client\_unallocated\_memory
- nomad\_client\_uptime
- up

## Changelog

md ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```md
# 1.0.0 - December 2025

* Chore: Fix incorrect semver to 1.0.0. No further changes

# 0.0.6 - November 2023

* Replaced Angular dashboard panels with React panels

# 0.0.5 - September 2023

* Update Grafana Agent configuration snippets to include filtered metrics used in gauge panels

# 0.0.4 - September 2023

* New Filter Metrics option for configuring the Grafana Agent, which saves on metrics cost by dropping any metric not used by this integration. Beware that anything custom built using metrics that are not on the snippet will stop working.
* New hostname relabel option, which applies the instance name you write on the text box to the Grafana Agent configuration snippets, making it easier and less error prone to configure this mandatory label.

# 0.0.3 - May 2022

* Update nomad-cluster dashboard:
  - Fix allocated gauges
* Update nomad-jobs dashboard:
  - Set decimal from fixed '3' to auto
  - Add tooltip sort: desc for tasks
  - Transform memory cache panel to timeseries graph
  - Fix units for CPU percentage

# 0.0.2 - April 2022

* Add Nomad setup prerequisites
* Add Nomad screenshot
* Add Nomad summary panels
* Fix panels repeat by $instance
* Fix queries: Remove not common service label from nomad selector
* Fix allocations and nomad clients gauge thresholds
* Flip CPU idle to CPU usage
* Fix instructions: Include format=prometheus in agent.jsonnet
* Update titles to Title case
* Rename $instance label from host to 'Nomad client'
* Remove vendor/ prefix from integration tag
* Transform nomad dashboards to jsonnet as is.

# 0.0.1 - July 2021

* Initial release
```

## Cost

By connecting your Nomad instance to Grafana Cloud, you might incur charges. To view information on the number of active series that your Grafana Cloud account uses for metrics included in each Cloud tier, see [Active series and dpm usage](/docs/grafana-cloud/fundamentals/active-series-and-dpm/) and [Cloud tier pricing](/products/cloud/pricing/).