> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/changelog/explore-by-month/april-2026/vision-events.md).

# Vision Events

Vision Events allows you to record, search, and analyze what your deployed computer vision models observe in production. You can browse and query events to review the output image, model predictions, hardware source, and customizable metadata. This provides a centralized, filterable history of activity related to your computer vision pipeline, making it easier to understand what is happening across your deployments.

You can integrate Vision Events into a pipeline using the native Workflow block, the REST API, or automated edge device backups. From there, data can be queried and filtered directly in the dashboard or via the API. This enables you to track specific detection classes, investigate edge cases, and monitor overall system performance across large fleets by grouping events into structured use cases.

[Learn more about Vision Events](https://docs.roboflow.com/deploy/vision-events)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.roboflow.com/changelog/explore-by-month/april-2026/vision-events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.