Skip to main content
This feature is in Early Access (EA), and might not be visible in your app. To learn more about this program and the features it contains, see the Early access page.
Operator is a conversational generative artificial intelligence (AI) feature in Chronosphere Observability Platform. Ask it a question in plain language, and it searches and runs queries against your telemetry. It responds with an explanation, a query you can open in an explorer, or a change to the resource you’re viewing. Operator is available from every page in Observability Platform, in both standard and Admin modes. It knows which page you’re on when you send a message, so you can ask about the dashboard, alert, notebook, or explorer in front of you without restating the context.
Generative AI features can produce incorrect results, hallucinate data, and deliver inaccurate analysis. Use generative AI features with care, and independently verify all information produced by generative AI tools before applying it.Certain prompts, data, or other inputs might produce irrelevant content. Don’t rely on generative AI features or responses for any uses that exceed their designed scope.

​
What Operator does

Operator combines the following capabilities that are otherwise separate in Observability Platform:
  • Answers questions about your telemetry and your Chronosphere configuration, including the contents of the Chronosphere documentation.
  • Queries your data by generating and running PromQL, logging queries, change event queries, and trace searches, then summarizing the results.
  • Acts on the page you’re viewing by editing the open dashboard or notebook, and by navigating you to another page.
For the full list of data Operator can read and the actions it can take, see Operator capabilities. Operator differs from other generative AI features in Observability Platform in two ways. It’s conversational, so it retains the context of earlier messages in the same chat. It’s also agentic: rather than producing a single response, it runs a sequence of searches, queries, and shell commands until it can answer, and shows you each step. Compared to related features:
  • Natural language query generation produces one query in the field you’re editing. Use it when you know which query you want and only need help writing it.
  • The Chronosphere MCP server exposes your tenant to an external large language model (LLM) client. Use it when you want to work in an editor or terminal instead of Observability Platform.

​
Open Operator

Open Operator in a side panel or as a full page. Both surfaces share the same conversations, so you can start a chat in the panel and continue it on the page. To open Operator in a side panel, use one of these methods:
  • Click Ask Operator in the page header.
  • Press A as a keyboard shortcut.
To open Operator as a full page, in the navigation menu, select Operator. The Ask Operator button displays its label only when the panel is closed and your browser window is wide enough. Otherwise, it displays as an icon with a tooltip. The button and A shortcut are disabled while you’re on the Operator page. For more details about every Operator control, see Operator interface.

​
Send your first prompt

To prompt Operator:
  1. Open Operator from the page you want to ask about.
  2. Enter a prompt in the message field. To direct Operator to a specific skill, type / and select the skill from the menu.
  3. Press Enter (Return on macOS) to send the prompt.
Operator streams its response as it works. It displays each search, query, and command it runs, and you can expand any of these steps to review its inputs and outputs. To stop a response that’s in progress, click Stop generating. For guidance on phrasing prompts, see Write effective prompts. You can also ask Operator for advice or example prompts relevant to your current context.

​
Page context

Each message you send includes the URL of the page you were viewing when you sent it. Operator uses that URL to identify the dashboard, alert, monitor, SLO, notebook, investigation, or explorer that you’re asking about. When the page changes between messages, Observability Platform displays a chip preceding your message that names the context, such as Dashboard or Logs explorer. Hold the pointer over the chip to view the full URL, and click the URL to open that page in a new tab. Only the URL is attached.

​
Availability and permissions

Operator reads the underlying resource by querying your telemetry as you, which means it respects the same data access as your account. Your role determines what you can do with Operator, and its actions are subject to the same restrictions as you are when you edit those resources.
  • Accounts with a role that grants edit permissions, such as Editor or SysAdmin, have full access. Operator also saves your 20 most recent conversations to its chat history, and you can share chats.
  • Accounts with the None role, which grants read-only Viewer permissions, chat in temporary mode. Conversations aren’t saved, don’t appear in chat history, and can’t be shared. The message field displays an incognito icon with the message Chats aren't saved for users with Viewer permissions.

​
Limitations

  • Operator answers questions about Observability Platform and your telemetry. It declines prompts outside that scope.
  • When Operator changes a dashboard, the changes aren’t saved until you review and save them yourself.
  • Each conversation has a context window. As you approach its limit, Observability Platform warns you in the context gauge. Start a new chat to reset it.
  • Conversations can’t be renamed, deleted, or exported.