> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/monitors/cloud-and-infrastructure-monitoring/other-cloud-platforms-monitors/how-to-resolve-sprinto-check-for-monitoring-digitalocean-droplet-cpu-utilization.md).

# How to resolve Sprinto check for monitoring DigitalOcean Droplet CPU utilization

### [Sprinto Support](mailto:www.support@sprinto.com)About

Sprinto Check: DigitalOcean Droplet CPU utilization should be monitored

Monitoring the CPU utilization of your DigitalOcean Droplet is crucial for optimizing performance and ensuring the efficient operation of your applications. Sprinto provides a streamlined process to set up an alert for monitoring Droplet CPU utilization.

### Purpose

The purpose of the Sprinto check for DigitalOcean Droplet CPU Utilization is to actively monitor and alert on the CPU usage of your Droplet. This monitoring helps you:

* Performance Optimization: Ensure optimal performance by tracking CPU utilization and identifying potential bottlenecks.
* Resource Management: Proactively manage resources by receiving alerts if CPU utilization exceeds defined thresholds.
* Prevent Downtime: Detect and address issues promptly to prevent downtime and maintain application availability.

### How to Configure

To set up an alert for monitoring DigitalOcean Droplet CPU Utilization, follow these steps within the DigitalOcean platform:

#### Before you Begin

* Ensure that you have the necessary permissions to create alerts on DigitalOcean.
* Log in to Sprinto as an administrator.

#### Configuring Alert

1. Log in to the[ DigitalOcean website](https://www.digitalocean.com/) using your credentials.
2. Navigate to the top navigation bar and select Monitoring.
3. Choose the specific Droplet for which you want to create an alert. Click on the Droplet's name to access its monitoring page.
4. On the monitoring page, click Create Alert Policy to open the alert policy creation form.
5. In the alert policy creation form, specify the details of your alert policy:
   * Alert Conditions: Define the conditions triggering the alert, selecting the metric with the API name v1/insights/droplet/cpu.
   * Notification Channels: Choose email, Slack, or Webhooks as notification channels.
   * Notification Frequency: Specify how often you want to receive alerts when the condition is met.
6. Review your alert policy settings and click Save Alert Policy to create the alert.

Once the alert is set up, Sprinto retrieves the changes and updates the Droplet CPU Utilization check status to "Passing."

For further assistance with the Sprinto check, please get in touch with Sprinto Support.


---

# 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://docs.sprinto.com/monitors/cloud-and-infrastructure-monitoring/other-cloud-platforms-monitors/how-to-resolve-sprinto-check-for-monitoring-digitalocean-droplet-cpu-utilization.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.