> 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.md).

# Other Cloud Platforms Monitors

Learn how Sprinto tracks infrastructure health and availability for cloud providers beyond AWS, Azure, and GCP.

While most Sprinto integrations and monitors focus on major platforms like AWS, Azure, and GCP, Sprinto also supports basic infrastructure health monitoring for other cloud environments such as:

* **DigitalOcean**
* **Oracle Cloud Infrastructure (OCI)**
* **IBM Cloud**
* **Linode**, and others on a case-by-case basis

These monitors help ensure baseline system availability and performance for organisations operating in multi-cloud or alternative cloud setups.

***

#### What does Sprinto monitor?

<table><thead><tr><th width="191.4609375">Platform</th><th width="211.9609375">Service/Resource Type</th><th>Metric/Check Description</th></tr></thead><tbody><tr><td>DigitalOcean</td><td>Droplets (VM instances)</td><td>CPU utilisation monitoring</td></tr><tr><td>Oracle Cloud</td><td>VCN, ATP, Load Balancer</td><td>Flow logs, backup configuration, CPU usage, connection health</td></tr><tr><td>Others (case-by-case)</td><td>Varies by client</td><td>Availability, backup, encryption, and logging configuration</td></tr></tbody></table>

***

#### Monitors and How to Resolve Them

**1. DigitalOcean – Droplet CPU Utilisation**

* Go to **Monitoring > Metrics**
* Locate the `CPU usage` graph for each Droplet
* Set up alerting if usage consistently exceeds 80–90%
* Upload screenshots of metrics and alerts

**2. Oracle Cloud – Flow Logs (VCN)**

* Navigate to **Logging > Flow Logs** in OCI
* Ensure flow logs are enabled on all VCNs
* Retain logs for a minimum of 30–90 days
* Upload flow log configuration or log samples

**3. Oracle Cloud – ATP Backup Enablement**

* Go to **Autonomous Database > Backups**
* Ensure automatic backups are enabled
* Upload screenshot showing backup settings and frequency

**4. Oracle Load Balancer – Active Connection Count**

* Go to **Monitoring > Load Balancer Metrics**
* Track metric: `ActiveConnections`
* Upload metric graph and alert thresholds

**5. Oracle Compute – CPU Utilisation**

* Metric: `CPUUtilization`
* Check for consistent high usage or sudden spikes
* Attach metric screenshot and any configured alert policy

***

#### Evidence Guidelines

<table><thead><tr><th width="215.7265625">Evidence Type</th><th width="111.3125">Accepted</th><th>Description</th></tr></thead><tbody><tr><td>Metric Screenshot</td><td>Yes</td><td>Time-series graph with 7–30 day view</td></tr><tr><td>Configuration Screenshot</td><td>Yes</td><td>Proof of backup, log retention, or flow log activation</td></tr><tr><td>Alert Policy Config</td><td>Optional</td><td>JSON or screenshot showing thresholds and triggers</td></tr></tbody></table>

***

#### Notes

* Sprinto supports custom configurations for other providers on request.
* Monitoring support may vary depending on whether API or metrics access is available from the provider.
* Reach out to Sprinto support for guidance on configuring custom platform monitors.


---

# 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.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.
