Incident Management
Platform
AI
Dedicated compute
Dedicated compute keeps concurrent queries stable and complex analysis fast.
Learn moreDedicated compute
Dedicated compute keeps concurrent queries stable and complex analysis fast.
Learn moreWhat OWL CLI does
OWL CLI does not replace the Guance console or OpenAPI. It provides a tool-oriented entry point for catalog sync, schema inspection, queries, and supported actions. Tool visibility and results follow the API Key permissions; write tools change workspace resources and should remain behind an explicit review or approval step.
Client capabilities and installation flows differ. Verify the current setup guide for the environment in which OWL will run.
Claude Code
Codex
Cursor
Trae
GitHub Copilot
WindsurfThe catalog is synchronised from Guance and evolves with platform capabilities. Use `owl list` and `owl show` to confirm the tools, parameters, and permissions available in the current workspace.
Discover and query supported metrics, logs, RUM, APM, network, profiling, billing, and related data.
Search DQL guidance, validate a complete query, and then run it against the intended data scope.
Read event, incident, comment, operation, and on-call context exposed by authorised tools.
Query catalog entities, infrastructure records, entity details, and available relationships.
List or manage supported monitor resources and inspect available SLO context according to permission.
Read or perform documented dashboard actions when the credential grants the required access.
Start from a concrete operational question, keep the tool call and parameters visible, and separate returned evidence from the final engineering judgement.
Use authorised discovery and query tools to identify the relevant data source, validate the query, and compare log or trace evidence by service, endpoint, environment, and version.
Use workspace discovery and the dedicated trace query path where it is available, then review the returned workspace, service, and span context before drawing a conclusion.
A script or Agent can invoke read-only tools on a schedule and produce a draft summary. Keep query windows and tool results attached so an engineer can verify changes before acting.
OWL CLI is Guance’s command-line entry point for synchronising a tool catalog, viewing tool descriptions and schemas, and executing supported Guance tools from a terminal, script, or AI Agent workflow.
The available categories and tools are returned by the current Guance service and depend on the configured workspace and API Key permissions. Use `owl sync`, `owl list`, and `owl show` to verify the current catalog rather than relying on a fixed marketing list.
Some documented tools create or update resources. A write tool changes the Guance workspace and requires the relevant permission. Use manual confirmation or another approval control before an AI Agent performs write actions.
Both expose Guance’s tool-oriented capabilities. OWL CLI is designed for local command-line, script, and Agent workflows; OWL MCP Server presents tools to clients through the Model Context Protocol.
Connect model requests, latency, errors, token use, and workflow spans for investigation.
Capture Agent sessions, traces, tool calls, and execution context without treating model output as evidence by itself.
Synchronise the available tool catalog, inspect schemas, and execute authorised Guance tools from a terminal.
Configure an MCP connection, verify authentication, and review the tools exposed to the client.
