It reads. It never touches.
A read-only collector on your login node or inside your cluster reads scheduler and health data. Zero changes to your cluster; it writes nothing to your nodes.
Your side of the line. Nothing runs where the provider can see it.
Your sideThe statement
- It only reads. Nothing on your cluster changes.
- It runs on your side, not the provider’s.
- It drafts. You decide what gets sent.
What it reads, how it ships, what it never does.
- Reads
- Signed
- Never sends
Illustrative.
Where the data lives. On your side, in your network.
- The data stays on your side. The provider sees the statement only if you send it.
- It does not guarantee that a provider will pay a credit, and it is not legal advice. Every figure in a statement points at an event in your own logs.
Questions
It runs on your login node or inside your cluster, never on the provider’s control plane.
Built for clusters whose logs cannot leave the building.
It runs on your login node or inside your cluster, and the provider sees the statement only if you send it.
Get the free statement