When an issue diagnosed by Pastures AI matches problems on other clusters in your fleet, a fleet correlation banner appears in the response.
What it looks like
The banner is styled with an amber background and appears directly in the AI response:
⚡ This issue is also active on 3 other clusters: prod-east, prod-west, staging-01
How it works
Fleet correlation is powered by the Oracle backend’s cross-cluster matching:
- When a diagnosis is generated, Oracle checks the query and root cause against data from all registered clusters
- If the same issue signature is detected on other clusters, the response includes a
fleetCorrelation object
- The AI drawer renders this as a warning banner with the count and names of affected clusters
interface FleetCorrelation {
count: number; // Number of other clusters affected
clusters: string[]; // Names of the affected clusters
}
Mode availability
| Mode | Fleet correlation |
|---|
| Oracle | Fully supported — cross-cluster matching from Engine data |
| Demo | Simulated on select responses (etcd, Longhorn queries) |
| BYO Model | Not available — requires fleet-wide data from the Engine |
Fleet correlation requires the Oracle backend to have visibility into multiple clusters. It is not available when using a BYO model, since your own endpoint has no access to fleet-wide cluster data.
Why it matters
Without fleet correlation, operators troubleshoot clusters in isolation. A Longhorn degradation on one cluster might be treated as a local issue, when in reality the same problem is hitting three other clusters due to a shared storage driver version.
Fleet correlation surfaces these patterns automatically, enabling:
- Faster triage — understand blast radius immediately
- Coordinated remediation — fix all affected clusters, not just the one you noticed
- Pattern detection — identify systemic issues before they escalate
