> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/insights/audit/audit-event-types.md).

# Audit Event Types

The following audit events are generated by AppControl:

| Control Domain          | Event Code                | Event Name              | Description                                                                                                               |
| ----------------------- | ------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Change Management       | DEPLOY\_STARTED           | Deployment started      | A deployment process has been initiated for an app or environment, marking the start of a controlled change execution.    |
| Change Management       | DEPLOY\_COMPLETED         | Deployment completed    | A deployment has successfully completed, confirming that the change was applied to the target environment.                |
| Change Management       | DEPLOY\_FAILED            | Deployment failed       | A deployment attempt failed, indicating that the intended change was not successfully applied.                            |
| Change Management       | ROLLBACK\_EXECUTED        | Rollback executed       | A rollback has been executed, reverting the environment to a previous known revision after an issue or failed deployment. |
| Change Management       | CONFIG\_CHANGED           | Configuration changed   | A configuration setting was modified in the environment, impacting runtime behavior or operational setup.                 |
| Change Management       | REVISION\_CHANGED         | Revision changed        | The active application revision was updated, reflecting a new version or build deployed to the environment.               |
| Change & Release        | CHANGE\_APPROVED          | Change approved         | A change request has been formally approved in accordance with defined change management controls.                        |
| Change & Release        | CHANGE\_REVIEW\_COMPLETED | Change review completed | A change review process has been completed, documenting assessment prior to approval or deployment.                       |
| Logging & Observability | POLICY\_CHANGED           | Policy changed          | A policy (app, data, compliance) setting has been changed.                                                                |


---

# 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.bluestorm.io/dashboards/insights/audit/audit-event-types.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.