Monitoring

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

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. Run the following command to start a shell with permissions to check the logs of the containers:

   ./carto shell

4. Execute the following command to view the status of all pods:

   kubectl get pods -n kotsadm

5. Check the status column for each pod. A healthy deployment will show Running in the status column.

6. Check the logs of each container using the following command:

   kubectl logs -f <service_name> -n kotsadm

7. Additionally, be aware that CARTO Self-Hosted is designed to internally monitor the health of each container. If any container reaches an unhealthy state, the system will automatically deploy a new container to maintain system stability.

Orchestrated container deployment

For the Kubernetes version, you can check the status and health of your CARTO deployment with the following steps:

1. Open a terminal or use your preferred Kubernetes management tool.

2. Execute the following command to view the status of all pods:

   kubectl get pods -n <namespace>

3. Check the status column for each pod. A healthy deployment will show Running in the status column.

4. Check the logs of each container using the following command:

   kubectl logs -f <service_name> -n <namespace>

Enable debug mode in CARTO Self-Hosted deployment

Debug mode in CARTO allows you to gather additional information for troubleshooting and diagnosing issues. To enable it enable the Debug Mode in the configuration of your CARTO Self-Hosted platform.

Single VM deployments

Add the following line into your customer.env file and apply the changes:

CARTO_TRACING_MODE=local

Orchestrated container deployment

Update your customizations.yaml file and apply the changes:

importApi:
  extraEnvVars:
    - name: CARTO_TRACING_MODE
      value: "local"
      
importWorker:
  extraEnvVars:
    - name: CARTO_TRACING_MODE
      value: "local"

ldsApi:
  extraEnvVars:
    - name: CARTO_TRACING_MODE
      value: "local"

mapsApi:
  extraEnvVars:
    - name: CARTO_TRACING_MODE
      value: "local"

workspaceApi:
  extraEnvVars:
    - name: CARTO_TRACING_MODE
      value: "local"
      
workspaceSubscriber:
  extraEnvVars:
    - name: CARTO_TRACING_MODE
      value: "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.