Nomad is an orchestrator for heterogeneous workloads maintained by Hashicorp.

This issue keeps track of efforts to support Nomad in Beats.

Nomad support could follow a similar approach to the available support for Kubernetes, for that the following components should be implemented:

• nomad autodiscover provider.
• add_nomad_metadata processor.
• Try to use the events API for watching https://www.nomadproject.io/api-docs/events (it is polling now).
• nomad metricbeat module.
• nomad filebeat module for nomad agents.
• Filebeat input if current ones are not enough.
• Documentation and reference job files to deploy beats in nomad.

The code for these features should be placed under x-pack (licensed as Basic).

At the moment of creating this issue there are some open community PRs that provide some of the required components, we have to review and continue with them:

• Add nomad processor #14500 - Adds an add_nomad_metadata processor.
• Autodiscover provider for Nomad #14954 - Adds an add_nomad_metadata processor too, and a nomad autodiscover provider.

There are also some known issues regarding Nomad support (though they can be general issues):

• Stops sending logs after harvester error #12988 - Filebeat fails to collect logs from containers started by nomad
• [Heartbeat] Docker autodiscovery generates monitors for non-published ports #12178 - Problems reaching non-published ports with Docker autodiscover

// cc: @jorgelbg and @jorgemarey as authors of current open PRs