> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/bmc-user-guide/advanced-management/automating-diagnostics-and-tasks.md).

# Automating Diagnostics & Tasks

In addition to manual operations, the BMC provides tools to automate the collection of diagnostic data and to monitor the status of all background tasks running on the system. These features help you automatically capture critical information when a problem occurs and give you clear visibility into everything the BMC is doing.

This chapter covers how to configure automatic video recording and how to monitor system tasks.

## **Configuring automatic video recording**

This feature allows the BMC to automatically record a short video clip of the KVM console when specific system events are detected. This is invaluable for post-mortem analysis of a server crash or an unexpected reboot, as it shows you exactly what was on the screen at the moment of failure.

1. In the sidebar menu, navigate to **Settings** > **Auto Video Settings**.
2. In the **Video Trigger Settings** tab, enable the toggles for the events you want to trigger a recording. Common triggers include:
   * **Critical Events (Temperature/Voltage)**: When temperature or voltage goes out of a critical range.
   * **Chassis Power Off/Reset Events**: When the server is unexpectedly powered off or reset.
   * **Watchdog Timer Events**: When the operating system freezes.
3. (Optional) You can enable **Pre-Event Video Recordings** to capture the few seconds leading up to the event for more context.
4. (Optional) In the **Video Remote Storage** tab, you can configure the recorded videos to be automatically saved to a remote network share (NFS or CIFS) to protect them from being lost on local storage.
5. Click **Save**.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfvwTCJVGMF72n6RMOUxL4OS1sK-vfP2TE2uLF3EEUT9WJZ65yuzwiqCq-taVbpyhW7qSzXA7_pBtCyDQzGvuKEhttkHXzum-_Dlli8D58idqhz2KXF4-xdcdRnAA704cBcuxdgQg?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdVuqazwat_5ZJCHRw4mY8YSMRB58rRH7YfOY2shxeEwXu1ZD4B4O9STATibzkpLz951uu9Kz2FB3QZuFFQQOtw2WDAZB-CIpkw-zX9OCIJe7jaMeieqV2SdffIY_Md0cKKXW6fwA?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

## **Monitoring background system tasks**

The **Tasks** page provides a central dashboard to see the status of all asynchronous background tasks initiated by the BMC, such as generating a system dump, uploading firmware, or applying a configuration update.

To view task status:

1. In the sidebar menu, navigate to **Operations** > **Tasks**.
2. The page will display a table listing all running or completed tasks.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdOF6lxCiI3Rfn6WvXdRuBEa7LkUMH0tlt-jR_ekUc1nlywTJ9i8oQQpihxgf-5aKXmk3e_MFJ8O8mtycpYIVUi4jkKZLH7ZBDoaa4oNAsWqui5uH16fmzVHgBhsBFYX-keFcloJQ?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

This table gives you the following information:

* **Task Description**: A brief summary of the task type (e.g., "Initiate Dump", "Firmware Upload").
* **Percent Complete**: The progress of the task, shown as a percentage.
* **Http Operation**: The RESTful operation that triggered the task (if applicable).
* **Target Uri**: The endpoint or resource that the task is acting upon.
* **Start Time / End Time**: The timestamps marking the beginning and end of the task.
* **Action**: The current status or result of the operation (e.g., a green checkmark for `Completed`, an `In Progress`status, or a `Failed` indicator). For tasks that are still running, a **Cancel** button may be available.

{% hint style="info" %}
**Pro Tip: Verify long-running operations**

For operations that take a long time, like a firmware update, the **Tasks** page is the best place to confirm that the operation has completed successfully or is still in progress. If you encounter issues after an update, check here first to see the final status of the task.
{% endhint %}


---

# 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://doc.engenius.ai/bmc-user-guide/advanced-management/automating-diagnostics-and-tasks.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.