# Monitoring

**This documentation is for the CARTO Self-Hosted Legacy Version**. Use only if you've installed this specific version. Explore our latest documentation for updated features.

Ensuring the health and status of your CARTO Self-Hosted deployment is crucial for a seamless user experience. Follow the instructions below to verify the status in both the Docker Compose and Kubernetes versions.

## Single VM deployments (Docker Compose)

To check the status of your CARTO deployment in the Docker Compose version, follow these steps:

1. Open a terminal.
2. Navigate to your CARTO Self-Hosted installation directory.
3. Check the logs of each container using the following command:

   ```bash
   docker-compose logs -f <service_name>
   ```
4. Review the logs for each container and ensure there are no error messages. A healthy deployment will have no critical errors reported in the logs.

## **Enable debug mode in CARTO Self-Hosted deployment**

Debug mode in CARTO allows you to gather additional information for troubleshooting and diagnosing issues. Follow the steps below to enable the debug mode in a CARTO Self-Hosted installation.\\

Add the following line into your <mark style="color:orange;">customer.env</mark> file and apply the changes:

```bash
CARTO_TRACING_MODE=local
```

By regularly checking the status of your CARTO deployment, you can proactively address any potential issues and ensure a reliable and robust CARTO environment.


---

# Agent Instructions: 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:

```
GET https://docs.carto.com/carto-self-hosted/carto-self-hosted-legacy/maintenance/monitoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
