> ## Documentation Index > Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt > Use this file to discover all available pages before exploring further. # Assistant capabilities reference > Reference for the data the Chronosphere Assistant reads, the skills it uses, and the changes it can make. export const AddToDashboardIcon = props => { return ; }; export const CollectionIcon = props => { const drawPath = "M21 6.5c-1.66 0-3 1.34-3 3 0 .07 0 .14.01.21l-2.03.68c-.64-1.21-1.82-2.09-3.22-2.32V5.91C14.04 5.57 15 4.4 15 3c0-1.66-1.34-3-3-3S9 1.34 9 3c0 1.4.96 2.57 2.25 2.91v2.16c-1.4.23-2.58 1.11-3.22 2.32l-2.04-.68C6 9.64 6 9.57 6 9.5c0-1.66-1.34-3-3-3s-3 1.34-3 3 1.34 3 3 3c1.06 0 1.98-.55 2.52-1.37l2.03.68c-.2 1.29.17 2.66 1.09 3.69l-1.41 1.77C6.85 17.09 6.44 17 6 17c-1.66 0-3 1.34-3 3s1.34 3 3 3 3-1.34 3-3c0-.68-.22-1.3-.6-1.8l1.41-1.77c1.36.76 3.02.75 4.37 0l1.41 1.77c-.37.5-.59 1.12-.59 1.8 0 1.66 1.34 3 3 3s3-1.34 3-3-1.34-3-3-3c-.44 0-.85.09-1.23.26l-1.41-1.77c.93-1.04 1.29-2.4 1.09-3.69l2.03-.68c.53.82 1.46 1.37 2.52 1.37 1.66 0 3-1.34 3-3S22.66 6.5 21 6.5zm-18 4c-.55 0-1-.45-1-1s.45-1 1-1 1 .45 1 1-.45 1-1 1zM6 21c-.55 0-1-.45-1-1s.45-1 1-1 1 .45 1 1-.45 1-1 1zm5-18c0-.55.45-1 1-1s1 .45 1 1-.45 1-1 1-1-.45-1-1zm1 12c-1.38 0-2.5-1.12-2.5-2.5S10.62 10 12 10s2.5 1.12 2.5 2.5S13.38 15 12 15zm6 4c.55 0 1 .45 1 1s-.45 1-1 1-1-.45-1-1 .45-1 1-1zm3-8.5c-.55 0-1-.45-1-1s.45-1 1-1 1 .45 1 1-.45 1-1 1z"; return ; }; export const CollectionNavIcon = props => { const drawPath = "M8.4 18.2C8.8 18.7 9 19.3 9 20C9 21.7 7.7 23 6 23S3 21.7 3 20 4.3 17 6 17C6.4 17 6.8 17.1 7.2 17.3L8.6 15.5C7.7 14.5 7.3 13.1 7.5 11.8L5.5 11.1C5 11.9 4.1 12.5 3 12.5C1.3 12.5 0 11.2 0 9.5S1.3 6.5 3 6.5 6 7.8 6 9.5V9.7L8 10.4C8.6 9.2 9.8 8.3 11.2 8.1V5.9C10 5.6 9 4.4 9 3C9 1.3 10.3 0 12 0S15 1.3 15 3C15 4.4 14 5.6 12.8 5.9V8.1C14.2 8.3 15.4 9.2 16 10.4L18 9.7V9.5C18 7.8 19.3 6.5 21 6.5S24 7.8 24 9.5 22.7 12.5 21 12.5C19.9 12.5 19 11.9 18.5 11.1L16.5 11.8C16.7 13.1 16.3 14.5 15.4 15.5L16.8 17.3C17.2 17.1 17.6 17 18 17C19.7 17 21 18.3 21 20S19.7 23 18 23 15 21.7 15 20C15 19.3 15.2 18.7 15.6 18.2L14.2 16.4C12.8 17.2 11.2 17.2 9.8 16.4L8.4 18.2Z"; return ; }; export const ServiceIcon = props => { return ; }; export const ServiceNavIcon = props => { return ; }; export const CSharpIcon = props => ; export const PipeIcon = props => ; export const AiMessageIcon = props => ; 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](/early-access) page. The [Assistant](/navigate/assistant) in Chronosphere Observability Platform reads your telemetry and configuration to answer questions, and acts on the resource you're viewing when you ask it to. Use this reference to determine what it can read, the skills it applies to specialized tasks, and the changes it can make. 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. ## Data the Assistant reads The Assistant queries your telemetry with the permissions of your account's [role](/administer/accounts-teams/teams). It can't read data that your account can't already access. The following table lists the data the Assistant reads and examples of how you can prompt each source: | Source | What the Assistant reads | Example prompt | | ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | | [Metrics](/overview/types/metrics) | Metric names, labels, label values, and the results of PromQL instant and range queries | Chart the error rate of a service over the last hour | | [Logs](/overview/types/logs) | Log field names, field values, and the results of logging queries | Find the most common error messages for a service | | [Traces](/overview/types/traces) | Traces by service and operation, or by trace ID, including full span trees | Retrieve the slowest traces for an endpoint | | [Change events](/overview/types/change-events) | Change events and their categories, types, sources, and labels | Correlate a latency increase with a deploy | | [Alerts](/investigate/alerts/alert-details) | Triggered and resolved alerts, filtered by status, severity, monitor, SLO, team, or muting state | Summarize which alerts triggered overnight | | Configuration resources | Definitions of dashboards, monitors, SLOs, shaping rules, notification policies, muting rules, notifiers, collections, teams, services, derived telemetry, datasets, trace behaviors, and notebooks | Explain what conditions trigger a monitor | | Entity search | Names, slugs, types, and ownership of dashboards, monitors, SLOs, collections, services, and teams | Find the dashboard that covers a service | | Documentation | The contents of this documentation | Explain how rollup rules work | | Your account | Your account and the other accounts in your tenant | Identify who owns a resource | The Assistant reads these sources in a sandboxed environment that allows it to filter and combine results before responding. When you expand a tool call in the conversation, you see the commands it ran and their output. For more information, see [Tool calls](/navigate/assistant/interface#tool-calls). ## Skills A *skill* is a set of instructions the Assistant loads for a specialized task, such as writing a query in a specific language or investigating a signal. The Assistant selects skills on its own based on your prompt. To direct it to a specific skill, type `/` in the message field and select the skill. **Table 2: Assistant skills** The following table lists the skills available from the slash command menu: | Command | Purpose | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `/investigate` | Explains what changed in a signal and identifies likely causes. Use it for a triggered alert, a monitor, a dashboard panel, an anomalous metric, or any question about why something is happening. | | `/promql` | Writes and modifies [PromQL](/investigate/querying/promql) queries. It discovers real metric and label names in your tenant rather than guessing them, and applies the correct function for each metric type. | | `/logs` | Explores your log data and writes [logging queries](/investigate/querying/query-logs/query-syntax). It discovers log fields and values, and samples raw logs to confirm spelling and casing before building a query. | | `/events` | Writes queries for [change events](/overview/concepts/change-events). It discovers the categories, types, sources, and labels present in your tenant before filtering. | | `/dashboarding` | Writes, reviews, and repairs [dashboard](/observe/dashboards) JSON against the Chronosphere dashboard schema, including panels, variables, layouts, and queries. | | `/joke` | Tells a random observability joke. | ## Changes the Assistant can make The Assistant can change the dashboard or notebook you have open, and can navigate you to another page. It validates each change before applying it and tells you what it changed. For dashboards, it stages the changes so you can review and modify them before saving the updated dashboard. ### Edit the open dashboard When you're viewing a [dashboard](/observe/dashboards), the Assistant can read its current state, including unsaved edits, and apply changes such as adding a panel or adjusting a query. The Assistant validates its change against the dashboard schema before applying it. When validation fails, it reports the problem and leaves the dashboard unchanged. After a successful change: * The dashboard switches to edit mode. * The change is recorded in the dashboard's edit history as **Edited dashboard with assistant**, so you can undo it like any manual edit. * The change isn't saved until you review it and click **Save**. To start, open a dashboard in edit mode and ask the Assistant what you want to change. For example: Add a panel to this dashboard showing request rate by status code. ### Edit the open notebook When you have a [notebook](/navigate/notebooks) open, the Assistant can read its contents as Markdown and edit its text, visualization panels, and tables. Notebook edits are saved automatically, so review them after the Assistant reports a change. Notebooks retain their [version history](/navigate/notebooks#view-version-history), and you can restore an edited notebook to a previous state. The Assistant edits a notebook by matching exact text. When the text it's looking for appears more than once or doesn't appear at all, rather than editing the wrong section, it rejects the change and reports why. ### Navigate to a page The Assistant can open another page in Observability Platform for you, such as a dashboard or an explorer. It navigates only to valid Observability Platform routes and documentation pages, and reports an error rather than following a link elsewhere. ## Start an investigation This feature isn't available to all Chronosphere Observability Platform users and might not be visible in your app. For information about enabling this feature in your environment, contact [Chronosphere Support](/support). The Assistant can start a deep investigation and monitor its progress while you work elsewhere. Investigations are available on tenants that have them enabled. To start an investigation from the Assistant, ask it to investigate an alert, dashboard panel, or symptom. Before starting one, the Assistant confirms with you unless your prompt clearly requested it. After starting, it links to the investigation and offers to monitor it. To start an investigation from a dashboard panel: 1. Hold the pointer over the panel, and then click the three vertical dots icon. 2. Click **Add to investigation**. When an investigation already exists for that panel and time range, click **Show investigation** instead. Observability Platform opens the Assistant and starts the investigation. Progress appears as an [investigation card](/navigate/assistant/interface#investigation-cards) in the conversation. To continue a completed investigation, open its report and click **Continue investigation**, describe the direction you want to pursue in the **Look deeper into** field, and then click **Submit**. Observability Platform forks a follow-up investigation and hands it to the Assistant to monitor. ## Escalate from query generation [Natural language query generation](/investigate/querying/natural-language) produces a single query in the field you're editing. When it can't fulfill a request, its error message includes an **Ask Assistant** link. Click the link to send the same prompt to the Assistant, which opens in the side panel and retries the request with its full set of capabilities, including metric discovery and the `/promql` skill. ## Tenant-specific guidance Chronosphere can configure instructions that the Assistant applies to every conversation in your tenant, such as your naming conventions, the services your teams own, or the dashboards to prefer for a given question. The Assistant follows these instructions alongside its built-in behavior. These instructions don't change your account's permissions or grant access to data your tenant can't otherwise read. To request them, contact [Chronosphere Support](/support).