> For the complete documentation index, see [llms.txt](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/event-log.md).
# Event Log
## Event Log
The Event Log provides a chronological view of all system and user activities related to assessments, deployments, and rollbacks. It is the primary place to track progress, diagnose failures, and understand what happened and why.
### System vs User events
**System** will show you a log activities and messages that are initiated by the set of backend systems and engines that execute processes
User will show your all events that were initiated by user request
All will show you all events traced by the system
***
## Event List Table
Clicking on an event will allow you to see the full details of the message. The JSON text area with the details of the event can be copied by selecting the copy icon on the text field below.
You can filter and search the events for specific keywords using the search bar on the top right of the page.
#### Event Table Columns
* **Type**\
Indicates the category of activity, such as:
* *Assessment Progress*
* *Deployment Progress*
* *Rollback Progress*
* **Time**\
Timestamp of when the event occurred. Sorting by time helps reconstruct the execution flow.
* **Status**\
Visual indicator of the event outcome:
* 🟢 **Completed** – step finished successfully
* 🔵 **In progress** – step currently executing
* 🔴 **Failed** – error occurred, action did not complete
* **Message**\
Human-readable description of the action, including:
* What is being executed
* IDs of deployments/actions
* Error details when failures occur
***
## How to Read the Log
### Follow the Flow
Events are logged **step by step**. Read **top to bottom** (or reverse by time) to understand:
1. What started
2. What executed
3. Where it failed or completed
4. Whether rollback was triggered automatically
Example:
* *Assessment started* → *Assessment completed*
* *Deployment executing* → *Deployment failed*
* *Rollback initiated automatically* → *Rollback completed*
### Identifying Failures
* Look for **red “Failed”** entries.
* Read the **error message carefully** — it often includes:
* Configuration issues
* Validation errors
* Missing cloud resources (e.g. Log Analytics workspace)
* Failures are typically followed by **automatic rollback events**, which are clearly logged.
### Understanding Rollbacks
When a deployment fails:
* The platform **automatically triggers a rollback**
* Rollback steps are logged individually
* A final **“rolled back successfully”** message confirms the environment was restored to its previous state
This ensures deployments are **safe and reversible**.
---
# 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.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/event-log.md?ask=&goal=
```
`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.
**System** will show you a log activities and messages that are initiated by the set of backend systems and engines that execute processes
User will show your all events that were initiated by user request
All will show you all events traced by the system
***
## Event List Table
Clicking on an event will allow you to see the full details of the message. The JSON text area with the details of the event can be copied by selecting the copy icon 
on the text field below.