Pro plan from £5 per endpoint per month · see pricing
Secronyx
In the next releaseLinuxWindowsmacOS

InfluxDB

See whether InfluxDB 2 is up and which version runs, which buckets exist with what retention, and which tasks failed on their last run and why, with a token that only reads buckets and tasks. This plugin is in the next Secronyx release; the current download does not include it yet.

What it answers

Questions an on-call engineer asks, which an AI client can answer with this plugin.

  • Is InfluxDB up and ready for queries and writes, and which version is running?
  • Which buckets exist, and what is each one's retention period?
  • Which tasks failed on their last run, and with what error?
  • When did the failing downsampling task last finish?

What it returns

Each of the plugin's read-only tools, described in words.

  • InfluxDB server health in one row - status (pass or fail), the health message, version and build commit
  • InfluxDB buckets the token can see - name, ID, organization, type (user or system), retention and shard group duration in seconds (0 keeps data forever) and when created and last changed
  • InfluxDB tasks whose last run failed - name, ID, organization, status (active or inactive), schedule, when the last run finished and its normalised error; never the Flux script

At a glance

Plugin
influxdb 1.0.0
Publisher
levantar
Platforms
Linux, Windows, macOS

Tested on

  • InfluxDB 2.7.12 on Linux (Ubuntu 24.04, Docker), test lab
  • InfluxDB 2.7.11 on macOS 15 (Intel, official release), test lab
  • InfluxDB 2.7.11 on Windows Server 2022 (official release), test lab

How it logs in

Without an explicit choice, install tries the methods that need no secret first, in this order.

  • A bearer token

The least-privilege login

The setup file in the pack. secronyx plugin setup influxdb prints it; an administrator applies it by hand.

#!/bin/sh # The least-privilege login for the influxdb plugin: an API token that can # read the buckets and tasks of one organization and nothing else. Run it # once, with curl, as someone who may create tokens (an operator or # all-access token in INFLUX_TOKEN): # INFLUX_TOKEN=... INFLUX_ORG=my-org sh grants.sh # INFLUX_URL=https://influx.example:8086 (default http://127.0.0.1:8086) # The same with the influx CLI: # influx auth create --org my-org --read-buckets --read-tasks \ # --description "secronyx influxdb plugin" # InfluxDB has no permission that lists buckets without also reading the # data in them, so whoever holds this token can query the organization's # buckets with other tools. The plugin itself cannot: the agent refuses # every request but GET /health, /api/v2/buckets and /api/v2/tasks. set -eu : "${INFLUX_TOKEN:?set INFLUX_TOKEN to a token that may create tokens}" : "${INFLUX_ORG:?set INFLUX_ORG to the organization name}" url=${INFLUX_URL:-http://127.0.0.1:8086} # The token goes to curl on stdin, not on the command line. api() { printf 'header = "Authorization: Token %s"\n' "$INFLUX_TOKEN" | curl -fsS --max-time 30 -K - "$@"; } org=$(api -G --data-urlencode "org=$INFLUX_ORG" "$url/api/v2/orgs" | tr -d '\n\t ' | sed -n 's/.*"orgs":\[{[^[]*"id":"\([0-9a-f]*\)".*/\1/p') [ -n "$org" ] || { echo "organization $INFLUX_ORG not found" >&2; exit 1; } # Prints the new authorization; its "token" is what to install: # secronyx plugin install ./influxdb-1.0.0.scxp --auth token --password-stdin < token api -X POST -H 'Content-Type: application/json' "$url/api/v2/authorizations" -d '{ "orgID": "'"$org"'", "description": "secronyx influxdb plugin", "permissions": [ { "action": "read", "resource": { "type": "buckets", "orgID": "'"$org"'" } }, { "action": "read", "resource": { "type": "tasks", "orgID": "'"$org"'" } } ] }'

See it run

Terminal recording from the test lab: influxdb-linux-harness
A real run on the shared test lab.
Terminal recording from the test lab: influxdb-macos-harness
A real run on the shared test lab.
Terminal recording from the test lab: influxdb-windows-harness
A real run on the shared test lab.

Read-only, in layers

Every request is a GET or HEAD to the endpoint the operator configured, on a path fixed in the signed pack. Redirects are not followed, and requests known to change state are refused.

These controls narrow what the plugin can do; none of them is a guarantee on its own. An administrator can still accept a more powerful login on purpose (audited and shown in status), root or Administrator on the host can replace the agent, and the plugin can read whatever its login can see.