> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/operations/about-operations.md).

# About Operations

Overview of Vectra AI operations guides for analysts and administrators, from investigations to backups and updates.

Operations guides cover day-to-day use and care of your Vectra AI deployment. Choose a topic below to get started.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Analyst Guidance</strong></td><td>Analyst workflow guidance and quick links for investigations, testing, and reporting.</td><td><a href="https://docs.vectra.ai/operations/analyst-guidance.md">Analyst Guidance</a></td></tr><tr><td><strong>Backup / Restore / DR</strong></td><td>Backup, restore, disaster recovery, and migration guidance for Vectra Brain appliances.</td><td><a href="https://docs.vectra.ai/operations/backup-restore-dr.md">Backup / Restore / DR</a></td></tr><tr><td><strong>Dashboards and Reports</strong></td><td>Dashboard and report guidance for operational, executive, Recall, and custom reporting views.</td><td><a href="https://docs.vectra.ai/operations/dashboards-and-reports.md">Dashboards and Reports</a></td></tr><tr><td><strong>Detection specific guidance</strong></td><td>Detection-specific guidance for interpreting selected Vectra detections, behaviors, and investigation context.</td><td><a href="https://docs.vectra.ai/operations/detection-specific-guidance.md">Detection specific guidance</a></td></tr><tr><td><strong>Exposure</strong></td><td>Landing page for Exposure related content that includes Findings and Asset Inventory content.</td><td><a href="https://docs.vectra.ai/operations/exposure.md">Exposure</a></td></tr><tr><td><strong>General</strong></td><td>General operations guidance for attack graphs, AI Triage, suspect protocol activity, and RUX portal links.</td><td><a href="https://docs.vectra.ai/operations/general.md">General</a></td></tr><tr><td><strong>Event Search</strong></td><td>Guides for AI-assisted search, SQL search, API usage, metadata, and Event Search workflows.</td><td><a href="https://docs.vectra.ai/operations/event-search.md">Event Search (Investigate)</a></td></tr><tr><td><strong>Licensing</strong></td><td>Licensing guidance for Vectra products, including metrics and license-related reference information.</td><td><a href="https://docs.vectra.ai/operations/licensing.md">Licensing</a></td></tr><tr><td><strong>Updates</strong></td><td>Update guidance for Vectra appliances, including offline updates and troubleshooting upgrade status.</td><td><a href="https://docs.vectra.ai/operations/readme-1.md">Updates</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vectra.ai/operations/about-operations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
