Integrations
Look inside the services you run
Built-in, read-only integrations that let Secronyx answer questions about the databases, brokers and web servers on your hosts.
Available integrations
Pick the services you run
Each integration covers one service and is built into the agent: there is nothing to download or install. Configure 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.
No integration matches these filters.
Databases
9 integrationsRelational databases.
Messaging & streaming
5 integrationsMessage brokers and queues.
Web, proxy & app servers
9 integrationsWeb servers and reverse proxies.
Platform & orchestration
6 integrationsService discovery, secrets, schedulers and Kubernetes nodes.
Observability & CI
2 integrationsMetrics and alerting.
How integrations work
A declaration, not code
An integration 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.
Built into the agent
The integrations on this page are compiled into the agent binary, so they are trusted because the agent is. One does nothing until you configure it: it registers no tools and opens no connection.
Read-only engines
Queries and requests are fixed in the integration. Each engine has a deny-by-default allowlist that lives in the agent, and it is checked when the integration is built, every time it loads, and before every SQL call.
Least-privilege logins
Each integration 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 integration needs.
Configure, check, use
Three commands on the host
Run them as root (Linux, macOS) or Administrator (Windows) on the host that runs the service.
Configure the integration
It 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 integration configure <name>Create the least-privilege login
The admin password is read once from stdin and is not stored. Only the new login is kept.
secronyx integration setup <name> --apply --admin-user <admin> < admin-passwordCheck it is ready
secronyx integration status
Or run no command at all: put the same settings in the agent's config file, or in environment variables for a container, and the integration is active when the agent starts.
Recordings of these steps from the test lab are on each integration's page as they are made.
Security model, in short
Layers, and what they do not cover
What limits an integration
- 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.
- An integration can read anything its login can see, so the least-privilege login matters.
Custom integrations
Your services, your signing key
For a service this page does not cover, describe it in the same declarative form, check it, and sign it with a key you create. The result is one signed pack file, and it is the only kind of integration you install: hosts load it once they trust your key.