All Classes and Interfaces

Class
Description
Feeds application-level operational signals (retries, retry exhaustion, circuit trips) into a Cockroach Aegis AegisClient as AppEvents.
Client for the CockroachDB Cloud control-plane API (part of Cockroach Continuum): list clusters and configure metric export.
A CockroachDB Cloud cluster (control-plane view).
Configuration for the Cloud client.
Metric-export configuration; settings holds target-specific fields.
A Cloud metric-export sink.
A Cockroach virtual cluster.
Health probe for the Cockroach Continuum Cloud control plane.
AegisFactory provider registered via META-INF/services.
Factory for CloudClient: returns a SimulatedCloudClient when the client is disabled or has no API key, otherwise an HttpCloudClient.
Factory for McpClient: returns a SimulatedMcpClient when the client is disabled or has no endpoint, otherwise an HttpMcpClient.
HTTP-backed Cockroach Aegis client.
HTTP-backed CloudClient using a service-account Bearer token.
An HTTP response: status code and (text) body.
A pluggable HTTP transport: (method, url, headers, body) -> response.
HTTP-backed McpClient speaking the MCP Streamable HTTP transport (spec 2025-06-18).
An HTTP response: status code, headers, and (text) body.
A pluggable HTTP transport: (method, url, headers, body) -> response.
Adapts an McpClient to the AegisClient SPI.
Maps Aegis operations to the tool names an MCP server advertises.
Minimal client for the Model Context Protocol (MCP).
The result of a tools/call.
Configuration for an MCP client.
One content block of a tool-call result.
A tool advertised by an MCP server.
Typed builders for the three metric-export sinks.
StorageInsightsFactory provider registered via META-INF/services so Crdb.storage(ds) resolves to StorageInsightsImpl.
In-memory Cockroach Aegis backend for development and tests.
In-memory CloudClient for development and tests.
In-memory McpClient for development and tests.
A recorded tools/call.
Cockroach Plenum storage insights over customer-safe SQL surfaces.
Manages Cockroach virtual-cluster lifecycle over a SQL connection using the CREATE / SHOW / DROP VIRTUAL CLUSTER statements (these require a Continuum-enabled cluster).
The minimal SQL surface the manager needs.