Pro plan from £5 per endpoint per month · see pricing
Secronyx

Plugins

Look inside the services you run

Signed, read-only packs that let Secronyx answer questions about the databases, brokers and web servers on your hosts.

Available plugins

Pick the services you run

Each plugin is a signed pack for one service. Install it on the hosts that run that service, give it a least-privilege login, and its read-only queries appear next to the built-in ones.

Databases

9 plugins

Relational databases.

Apache Cassandra See which Cassandra nodes are down or joining, which thread pool is backed up, whether compaction keeps up and which table has too many SSTables or tombstones, from five fixed read commands on the node. In the next releaseLinux ClickHouse See what is running, merging and stuck inside ClickHouse, which tables have too many parts and how full the disks are, with a login the server keeps read-only. In the next releaseLinux Elasticsearch and OpenSearch See why a cluster is yellow or red, which shards are unassigned and what blocks them, how the nodes' heap, CPU and disk compare with the watermarks, and what the master is busy with, through read-only monitor requests. In the next releaseLinuxmacOS 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. In the next releaseLinuxWindowsmacOS Microsoft SQL Server See who is blocking whom, what the server waits on, and whether backups, jobs and availability groups are healthy, with a read-only monitoring login. AvailableLinuxWindows MySQL and MariaDB See what is running, waiting and lagging inside MySQL and MariaDB, with a read-only monitoring login. AvailableLinuxWindowsmacOS Patroni See which member leads the PostgreSQL cluster, which replicas stream, lag or are stopped, whether it is paused, and when the primary last changed, through the REST API's reads with no login. In the next releaseLinux PgBouncer See which PgBouncer pools are full, how many clients are queueing for a connection and for how long, with a read-only stats login. In the next releaseLinuxmacOS PostgreSQL See what is running, waiting and lagging inside PostgreSQL, with a read-only monitoring login. AvailableLinuxWindowsmacOS

Web, proxy & app servers

9 plugins

Web servers and reverse proxies.

Apache HTTP Server See whether every Apache worker is busy, how much traffic it is taking and what each worker is doing, from the read-only server status report. AvailableLinuxWindowsmacOS Apache Tomcat See whether Tomcat has run out of request threads, which requests hold them and for how long, and how full each JVM memory pool is, with a status-only manager login. In the next releaseLinuxWindowsmacOS Caddy See which hosts and ports Caddy serves, where each site proxies, and which reverse proxy upstreams Caddy has marked unhealthy, from its admin API on this host with read-only requests. In the next releaseLinuxWindowsmacOS Envoy See which Envoy upstream clusters have no healthy hosts and why, where its listeners accept connections, which certificates expire soon and what its counters say, from its admin interface on this host with read-only requests. In the next releaseLinux NGINX See how many connections NGINX holds, whether they are reading, writing or idle in keep-alive, and whether it is dropping any, from its stub_status page on this host. AvailableLinuxWindowsmacOS PHP-FPM See whether every PHP-FPM worker is busy, how many requests are queuing for one, and which script each worker is running and for how long, from the pool's status page on this host with read-only requests. In the next releaseLinux Squid See how busy a Squid proxy is, how well its cache is hitting, whether it is running out of file descriptors and how much traffic it has carried since it started, from its cache manager on this host with read-only requests. In the next releaseLinux Traefik See whether Traefik has routers or services in error, why a router is disabled, which router serves a host, and which backend servers its health checks mark down, from its API on this host with read-only requests. In the next releaseLinuxWindowsmacOS Varnish Cache See the Varnish hit ratio, whether the cache is full and evicting, which backend fails its health probes and whether the cache process restarted, read from its shared memory counters without the admin secret. In the next releaseLinux

How plugins work

A declaration, not code

A plugin names a service, how to log in to it, and a fixed set of read-only queries or requests. It contains no code that runs on the host.

One compiled, signed pack

The pack is a single file. The agent checks that it and every folder above it are owned by root, SYSTEM or Administrators, then verifies the signature against a signer you trust, before it parses anything.

Read-only engines

Queries and requests are fixed in the pack. Each engine has a deny-by-default allowlist that lives in the agent, and it is checked when the pack is built, every time it loads, and before every SQL call.

Least-privilege logins

Each plugin ships the grant for a read-only login. For SQL databases the agent asks the server how powerful the login is, and refuses to register the tools when it has more rights than the plugin needs.

Install, verify, load

Four commands on the host

Run them as root (Linux, macOS) or Administrator (Windows) on the host that runs the service.

  1. Trust the signer once per host

    secronyx plugin trust add <key-id>.json
  2. Install the pack

    It verifies the pack and tries the logins that need no secret. A login with too many rights is refused, and the command prints the grant script for a least-privilege one.

    secronyx plugin install ./<plugin>-<version>.scxp
  3. Create the least-privilege login

    The admin password is read once from stdin and is not stored. Only the new login is kept.

    secronyx plugin setup <plugin> --apply --admin-user <admin> < admin-password
  4. Check it is ready

    secronyx plugin status

Recordings of these steps from the test lab will appear here and on each plugin's page.

Security model, in short

Layers, and what they do not cover

What limits a plugin

  • The login: read-only grants, checked by the agent for SQL databases.
  • The engine: fixed queries, an allowlist in the agent, read-only transactions that are always rolled back.
  • The result: only the columns a tool declares leave the agent, and every call is recorded in the agent's audit log.

What remains

  • An administrator can accept a more powerful login on purpose. That choice is audited and shown in status, not prevented.
  • Root or Administrator on a host can replace the agent or its trusted signer keys.
  • A pack can read anything its login can see, so the least-privilege login matters.

Write your own plugin

Your services, your signing key

Describe your own service in a plugin.yaml, check it, and sign it with a key you create. Hosts load it once they trust your key.

secronyx plugin keygen --publisher <you> --names <plugin> --out ./keys secronyx plugin lint ./<plugin> secronyx plugin build ./<plugin> --sign-key keys/<key-id>.key