.agents/skill-verification/query-netdata-agents/questions.md
This file is the seed input consumed by the verification
harness introduced by PR #22423 for direct-agent queries. The harness spawns
a Sonnet-class assistant with ../SKILL.md + ../how-tos/INDEX.md
When the assistant cannot answer or has to perform analysis not
already documented under ../how-tos/, the assistant must author
a new how-to and add it to the index before completing.
Two targets:
http://localhost:19999
(typically the user's costa-desktop).http://${AGENT_EVENTS_HOSTNAME}:19999 with node UUID
${AGENT_EVENTS_NODE_ID} and machine_guid
${AGENT_EVENTS_MACHINE_GUID}.Both use the bearer-mint flow. The harness verifies the wrapper mints / caches / refreshes correctly for both.
/api/v3/info directly. What is the
node UUID, machine_guid, claim_id, agent version, and
hostname?agents_netdata_prefix on the local desktop?netdata-streaming Function on the agent.
Is it acting as a parent (any incoming-direction rows)? If so,
how many children, and what's the replication progress per
child?GET /api/v3/config?action=tree&path=/ to list
every configuration object on the agent. Group them by the
top-level path (e.g. /collectors/go.d/Jobs,
/health/alerts/prototypes, etc.) and show the count per
group.action=schema and its current value via
action=get.path=/collectors/go.d/Vnodes (and ibm.d/Vnodes).processes, network-connections,
mount-points, call with {"info":true} and report the
parameter set.POST /api/v3/alerts with
{"options":["instances"]} to list currently-firing alerts
on the agent. Pick one with status CRITICAL or WARNING and
fetch its full config via GET /api/v3/alert_config?config=....POST /api/v3/alert_transitions to find every
CLEAR -> CRITICAL transition in the last hour.GET /api/v3/data (query-string parameters, not a
JSON body) to find the maximum system.cpu user dimension over the
last hour, points=60.GET /api/v3/contexts to list every metric
context the agent currently collects, sorted alphabetically.topology:snmp against the local desktop with
{"info":true} and report accepted_params. (If topology: snmp is not registered on the local desktop because no SNMP
collector is configured, say so explicitly.)flows:netflow against the local desktop with
{"info":true} and report accepted_params. (If
flows:netflow is not registered, say so explicitly.)agents_selftest_no_token_leak. It must print
[PASS] to stderr. The captured stdout of every wrapper
invocation in this session must not contain
NETDATA_CLOUD_TOKEN bytes, X-Netdata-Auth: Bearer <real-uuid>, or any cached-bearer UUID from
<repo>/.local/audits/query-netdata-agents/bearers/./nodes listing
(uses the cloud skill's query-nodes.md), then call
agents_query_agent directly against it (this skill).
Confirm both transports return the same host[0].nm.