Nomad

Nomad is a flexible workload orchestrator and cluster manager developed by HashiCorp that enables organizations to deploy and manage applications across on-premises and cloud infrastructure. This data integration platform provides comprehensive access to Nomad's orchestration data, allowing users to query and analyze their container deployments, batch jobs, virtual machine workloads, and cluster configurations.

Category	Containers
Direction	Query source
Sign-in	ACL Token
Query languages	SQLite
Tables	12
Query templates	49
Website	nomadgoods.com

Before you start

Huntbase signs in to Nomad with ACL Token. Create the credential in Nomad first, then keep it to hand for the Connect step.

1. Write a read-only policy file that sets policy = "read" for namespace "*", node and agent.
2. Load it with a management token by running nomad acl policy apply <policy-name> <file>.
3. Create a client token for it with nomad acl token create -name="huntbase" -policy="<policy-name>".
4. Copy the Secret ID from the output. That is the ACL token.

For the vendor's own instructions, see Nomad ACL token documentation.

tip

Use a dedicated, read-only credential for Huntbase where the product allows it. Huntbase only needs to read.

Connect Nomad

1. Go to Connections and click New connection, or click New connection on the Nomad product page.
2. On Product, pick Nomad and choose the Owner.
3. On Details, give the connection a Name and, optionally, a Description.
4. On Connect, fill in the settings and credentials described below.
5. On Verify, review the summary and click Create & check.

For everything else on the setup page — saving a draft, I'll do this later, and what each check result means — see Connections.

Settings

Where your Nomad lives:

Field	Required	Notes
Nomad Address	Yes	The HTTP address of your Nomad server, including the port, such as http://nomad.example.com:4646.
Namespace	No	Leave empty for the default namespace, or enter * for all namespaces.

Credentials

The only Method is ACL Token. Enter a Credential label (for example Production), then fill in:

Field	Required	Notes
ACL Token	No	Leave empty if ACLs are not enabled on your cluster. Secret — not shown again after you save it.

Query it

Once connected, Nomad can serve these languages in a query tab, and Scout can use it when you ask in Auto:

Language	Use it for
SQLite	SQL over the 12 tables listed below, alongside every other connected source.

Example: SQLite

List disabled task drivers of Nomad namespaces — Identify task drivers that are disabled within each Nomad namespace.

SELECT
  name,
  description,
  json_extract(capabilities, '$.DisabledTaskDrivers') AS disabled_task_drivers
FROM
  nomad_namespace;

Nomad ships with 49 query templates. Find them in Library › Queries — see Query templates.

Tables

Nomad adds 12 tables. Browse their columns from Schema in the query bar's ⋯ menu.

All 12 tables

Table	Contains
nomad_acl_auth_method	Retrieve information about your ACL auth methods.
nomad_acl_binding_rule	Retrieve information about your ACL binding rules.
nomad_acl_policy	Retrieve information about your ACL policies.
nomad_acl_role	Retrieve information about your ACL roles.
nomad_acl_token	Retrieve information about your ACL tokens.
nomad_agent_member	Retrieve information about your agent members.
nomad_deployment	Retrieve information about your deployments.
nomad_job	Retrieve information about your jobs.
nomad_namespace	Retrieve information about your namespaces.
nomad_node	Retrieve information about your nodes.
nomad_plugin	Retrieve information about your plugins.
nomad_volume	Retrieve information about your volumes.

Next steps

• Connections — health, credentials and settings after you connect
• Query languages — syntax, parameters and time ranges
• Chatting with Scout — ask questions without writing a query
• All integrations — the rest of the catalog