Skip to content

OWL

OWL is a unified capability entry point provided by TrueWatch for tooling and intelligent scenarios, supporting two access forms: OWL CLI and OWL MCP Server.

Through OWL, users can invoke capabilities such as metrics, logs, events, monitors, dashboards, APM, RUM, and infrastructure in TrueWatch in a unified way.

OWL does not replace the TrueWatch console or the Open API. Instead, it provides a wrapper entry point built on top of existing capabilities that is better suited for tool invocation, automation orchestration, and AI Agent integration.

How It Works

flowchart LR
  user["Users / Scripts"] --> cli["OWL CLI"]
  agent["AI Agent / MCP Clients"] --> mcp["OWL MCP Server"]
  cli --> owl["OWL Tool Catalog and Execution Service"]
  mcp --> owl
  owl --> platform["TrueWatch Platform Capabilities"]

OWL CLI and OWL MCP Server access the same set of platform capabilities, but they target different access methods and use cases.

Access Type Use Cases Core Capabilities
OWL CLI Local command line, scripts, and automated workflows Sync the tool catalog, view tool descriptions, execute tools, and export the Agent Schema
OWL MCP Server AI Agent and MCP client integration Provide standardized tool service interfaces based on the Model Context Protocol

Use Cases

  • Query metrics, logs, events, monitors, dashboards, and other information from the terminal
  • Query data from multiple authorized workspaces on the same target site through Authorized Workspace Discovery and Cross-Workspace Query
  • Quickly verify observability capabilities in customer workspaces during implementation and delivery
  • Use separate Profiles to store multiple accounts or environments, and explicitly select an access identity for terminals, scripts, or Agents
  • Integrate TrueWatch capabilities into AI clients that support MCP
  • Let Agents invoke TrueWatch query, analysis, and management tools using natural language
  • Leverage capabilities such as the same-organization workspace list (same-org), the dedicated cross-workspace Trace query tool (owl.data.same_org.trace.query), the SLO list (owl.slo.list), and documentation search (mdsearch) for cross-workspace troubleshooting and queries

Usage Limitations

  • OWL's access permissions follow the API Key in use. Resources that the API Key is not authorized to access are also inaccessible to OWL;
  • Write-type tools modify resources in TrueWatch, such as creating dashboards, updating monitors, and appending comments;
  • When integrating with an AI Agent or MCP client, it is recommended to configure a manual confirmation or approval mechanism for write-type operations to avoid unintended changes.

In addition, when AI APIs are invoked through OWL, usage is metered by Triggers and counted separately from model credit consumption.

Quick Entry

Scenario 1: Command Line Operations

Suitable for developers, operations and maintenance personnel, and implementation and delivery staff to manually execute query and management tasks.

Scenario 2: AI Agent Integration

Suitable for integrating platform capabilities into large language model applications to enable natural language interaction.