Monitoring & incidents · wired today
What can agents actually do with Loki?
Incidents move faster than humans can tab-switch. The Loki connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
The Loki tool list, exactly as agents see it
labels— List every log label name known to this Loki instancelabel_values— List the values a given log label takes across streams (e.g. job, namespace)query_range— Run a LogQL query over a time range and return the matching log streams and entriesseries— List the log streams (label sets) matching one or more stream selectors
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Loki connector needs
You provide base URL from your Loki account; Quox sends it as a credential embedded in the endpoint path. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Loki's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Loki instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.
Loki integration FAQ
What can Quox agents do with Loki?
Agents can run 4 read-only tools against Loki: labels, label values, query range, series. Every call is receipted in the evidence trail.
What does the Loki integration need?
You provide base URL from your Loki account; Quox sends it as a credential embedded in the endpoint path. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Loki credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Loki connector?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Loki instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.