Obsy Copilot¶
Obsy Copilot is provided with the workspace and requires no additional configuration. Users can ask questions directly in natural language, or on specific pages, let Obsy Copilot complete analysis or content generation based on the current object, accessible workspace data, and enabled capabilities.
Obsy Copilot handles immediate tasks initiated by users, helping them query, analyze, and create content within the workspace more efficiently and accurately.
Getting Started¶
Click the Obsy AI icon in the top navigation bar of the platform, and the Obsy Copilot drawer will expand on the right side of the page. You can open Obsy Copilot on any page and switch pages or continue operating the platform during the conversation. Click the icon again to collapse the drawer.
The top of the drawer provides an entry to Obsy Agent Teams, which you can click to access the corresponding workspace.
The Obsy Copilot drawer supports the following general operations:
- New Conversation: Click
+to create a new conversation that does not inherit the current session context. - History Conversations: View, continue, or manage previous conversations.
- Maximize or Restore: Expand to full screen to view complex content; click again to restore the default width.
- Close: Collapse the drawer, and the current conversation content will be retained.
History Conversations¶
Obsy Copilot saves history conversations so you can continue previous analyses. Click the history conversations icon at the top of the drawer to view the conversation list sorted by last update time.
In the history conversations list, you can:
- Click a conversation to restore the existing context and continue asking questions.
- Rename a conversation for easier identification later.
- Delete conversations that are no longer needed.
Note
- History conversations are isolated by workspace and user, visible only to the current user.
- History conversations are retained for up to 30 days and will be automatically cleaned up after the retention period.
Quick Actions¶
When you first open Obsy Copilot or start a new conversation, the window displays quick actions, for example:
- What can you do?
- Introduce the core features of the platform.
- Summarize the latest alert for me.
Quick actions are designed to help users start a conversation. When performing specific tasks, it is recommended to supplement the analysis object, time range, and expected results. For example, instead of just saying "Help me look," you can say "Analyze the current error links, identify the most likely failure node, the scope of impact, and the next troubleshooting steps."
Capability Overview¶
Obsy Copilot capabilities are categorized into four types based on usage goals:
| Capability Category | Included Capabilities | Primary Value |
|---|---|---|
| Observability Analysis | Page Analysis & Root Cause Location, List & Asset Analysis, Database Query Optimization, Alert Aggregation & Compression, Incident Preliminary Analysis. | Combines current objects, page scope, and observability data to extract anomaly clues, reducing time for fault diagnosis and root cause investigation. |
| Data Retrieval | DQL / PromQL Assistant, Explorer Natural Language Search. | Converts natural language into query statements or filter conditions, lowering the barrier to using DQL, PromQL, and Explorer syntax, and improving data retrieval efficiency. |
| Resource Generation | Create & Modify Dashboards, Generate Pipeline Parsing Rules. | Generates dashboard drafts and Pipeline parsing rules based on business goals and workspace metadata, reducing repetitive configuration and coding from scratch. |
| Knowledge Services | Create Notes & Runbooks, Product Documentation Q&A. | Organizes analysis results into reusable notes or operational procedures, and provides usage guidance based on product documentation, reducing the cost of knowledge organization, querying, and sharing. |
The completeness and accuracy of Obsy Copilot analysis results and generated content are affected by factors such as site version, deployment configuration, user permissions, current page context, and the completeness of observability data collection. When using the results, it is recommended to cross-check key conclusions with the original data and actual environment, and perform necessary validation before proceeding with subsequent operations.
Usage Tips¶
- When analyzing a specific object, first navigate to the corresponding detail or list page, then open Obsy Copilot. This reduces repetitive descriptions and keeps results within the current filter scope.
- Specify the target, time range, and expected output in your questions. When generating queries or configurations, also provide the data domain, samples, and key constraints.
- Obsy Copilot only uses data and features that the current user has access to. If data, permissions, or necessary context are missing, the results will explain the limitations, and you should not assume the issue has been fully verified.
- Confirm queries, configurations, and disposal suggestions generated by Obsy Copilot before using them in production environments. Processes involving resource creation are still subject to the corresponding module's permissions and save operations.