Table: nomad_agent_member - Query Nomad Agent Members using SQL
Nomad is a simple and flexible workload orchestrator to deploy and manage containers and non-containerized applications across on-prem and clouds at scale. Nomad is widely adopted and used in production by PagerDuty, Trivago, Deluxe Entertainment, and more. An agent member in Nomad represents a single instance of the Nomad agent.
Table Usage Guide
The nomad_agent_member
table provides insights into the members of a Nomad agent. As a DevOps engineer or system administrator, explore member-specific details through this table, including their role, status, and protocol versions. Utilize it to uncover information about members, such as their status, roles, and the protocol versions they are using.
Examples
Basic info
Explore the status and details of various agents within the Nomad system. This can be useful in monitoring network health and identifying potential issues with specific agents.
select name, address, port, status, protocol_curfrom nomad_agent_member;
select name, address, port, status, protocol_curfrom nomad_agent_member;
List global agents
Explore which global agents are currently active in your network. This can help you manage your resources more efficiently and identify potential issues with network connectivity or performance.
select name, address, port, status, protocol_curfrom nomad_agent_memberwhere tags ->> 'region' = 'global';
select name, address, port, status, protocol_curfrom nomad_agent_memberwhere json_extract(tags, '$.region') = 'global';
List agents which are not alive
Discover the details of agents that are not currently active. This query can be used to identify potential issues or disruptions in your network by pinpointing inactive agents.
select name, address, port, status, protocol_curfrom nomad_agent_memberwhere status <> 'alive';
select name, address, port, status, protocol_curfrom nomad_agent_memberwhere status <> 'alive';
Schema for nomad_agent_member
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form, e.g. connection_name. | |
address | text | The IP address or hostname of the agent member. | |
delegate_cur | bigint | The current number of delegations held by the agent member. | |
delegate_max | bigint | The maximum number of delegations allowed by the agent member. | |
delegate_min | bigint | The minimum number of delegations allowed by the agent member. | |
name | text | The name of the agent member. | |
port | bigint | The network port number used by the agent member. | |
protocol_cur | bigint | The current version of the protocol used by the agent member. | |
protocol_max | bigint | The maximum version of the protocol supported by the agent member. | |
protocol_min | bigint | The minimum version of the protocol supported by the agent member. | |
status | text | The current operational status of the agent member. | |
tags | jsonb | A set of key-value pairs that describe the agent member. | |
title | text | The title of the agent member. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- nomad
You can pass the configuration to the command with the --config
argument:
steampipe_export_nomad --config '<your_config>' nomad_agent_member