> For the complete documentation index, see [llms.txt](https://docs.trilio.io/rhv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trilio.io/rhv/troubleshooting/important-tvm-logs.md).

# Important TVM Logs

## TrilioVault Appliance logs used during configuration

The following logs contain all information gathered during the configuration of the TrilioVault Appliance

**`/var/log/workloadmgr/tvault-config.log`**

This log contains all information of pre-checks done, when filling out the configurator form.

**`/var/log/workloadmgr/ansible-playbook.log`**

This log contains the complete Ansible output from the playbooks that run when the configurator is started.

{% hint style="info" %}
With each configuration attempt a new ansible-playbook.log gets created. Old ansible-playbook.logs are renamed according to their creation time.
{% endhint %}

### TrilioVault Appliance logs during any task after configuration

**`/var/log/workloadmgr/workloadmgr-api.log`**

This log tracks all API requests that have been received on the wlm-api service.

This log is helpful to verify that the TrilioVault VM is reachable from the RHV-M and authentication is working as expected.

**`/var/log/workloadmgr/workloadmgr-scheduler.log`**

This log tracks all jobs the wlm-scheduler is receiving from the wlm-api and sends them to the chosen wlm-workloads service.

This log is helpful, when the wlm-api doesn't throw any error, but no task like backup or restore is getting started.

**`/var/log/workloadmgr/workloadmgr-workloads.log`**

This log contains the complete output from the wlm-workloads service, which is controlling the actual backup and restore tasks.

This log is helpful to identify any errors that are happening on the TVM itself including RESTful api responses from the RHV-M.


---

# 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.trilio.io/rhv/troubleshooting/important-tvm-logs.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.