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 stanza below in your Nomad client and server configuration files, by default it would be /etc/nomad.d/nomad.hcl:

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

Install Nomad integration for Grafana Cloud

In your Grafana Cloud stack, click Connections in the left-hand menu.
Find Nomad and click its tile to open the integration.
Review the prerequisites in the Configuration Details tab and set up Grafana Alloy to send Nomad metrics to your Grafana Cloud instance.
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

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

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 component to discover your Nomad Prometheus endpoint and apply appropriate labels, followed by a 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