Skip to content

Knowledge Services


Obsy AI Copilot can organize analysis results from the current conversation into a platform note. It can also search official documentation and answer product usage questions. The first capability preserves conclusions that have already been developed; the second provides guidance aligned with product documentation.

Create Platform Notes

After troubleshooting an incident, analyzing logs, explaining a query, or discussing a solution, turn useful conversation content into a platform note instead of copying and reorganizing it manually.

Start Note Creation

You can enter the note flow in either of these ways:

  • Request it directly: Ask Copilot to turn the analysis above into a note, save the latest trace analysis as a note, or organize the current session into a note.
  • Accept a Copilot suggestion: When the conversation contains a sufficiently complete analysis, Copilot may suggest organizing it into a note.

When only part of the conversation should be included, state the scope explicitly. Asking for a note from the latest analysis includes only the most recent substantive result, while asking to organize the current session can include multiple useful items from that session.

Creation Flow

  1. Copilot checks whether the current account can create notes.
  2. It prepares a draft for the requested scope and displays a confirmation card with the title, content scope, sections, tags, and other summary information.
  3. Review the card and approve creation when the scope is correct.
  4. After creation, Copilot returns a result card. Select the note name to open it without closing the conversation.

The draft can reference query and chart summaries that already exist in the conversation, but it does not copy complete raw logs, oversized query results, or unrelated history into the note.

Note
  • The current account must have permission to create notes. Contact an administrator when permission is unavailable.
  • Copilot only prepares a draft before approval; no note is created until the user confirms.
  • When the conversation lacks enough content, Copilot identifies what is missing or organizes only the conclusions already available.
  • After creation, verify important conclusions, query references, and object scope before sharing the note or using it for remediation.

Product Documentation Q&A

Product documentation Q&A searches the platform's official help documentation for feature descriptions, navigation paths, configuration rules, operating steps, and common troubleshooting guidance. It provides links to the relevant documentation when useful.

Use it for product questions such as:

  • You do not know what a feature does or where to find it;
  • You need installation, integration, creation, or configuration steps;
  • You need to confirm a field, default value, version requirement, or limitation;
  • A configuration has no data or has not taken effect and you need a troubleshooting sequence;
  • You want the corresponding official help page.

Submit a Product Question

Describe the task and include the relevant product, module, and current stage. For example:

How do I install DataKit for a Kubernetes cluster and verify that metrics are being reported?

For a complex question, state the final goal and what has already been completed. Copilot organizes the answer around prerequisites, steps, and verification. You can also ask explicitly for the relevant documentation link.

Copilot organizes an answer from the retrieved documentation and provides accessible site links when needed. Configuration and troubleshooting answers prioritize execution order, constraints, and verification methods.

Product documentation Q&A provides guidance only. It does not create, update, delete, install, or deploy resources on your behalf. If the retrieved documentation does not provide enough evidence to confirm a rule, Copilot identifies the limitation instead of filling the gap with general knowledge.

Feedback

Is this page helpful? ×