> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/integrations/inbound-integrations/cloud-monitoring.md).

# Cloud Monitoring

This category covers native monitoring services from major cloud providers. These tools track resource consumption, service health, budget thresholds, and platform-level events across AWS, Google Cloud, Azure, and Alibaba Cloud — and forward alerts to ITOC360 when action is required.

***

### Integrations in this category

| Integration              | What it monitors                                | Alert delivery        |
| ------------------------ | ----------------------------------------------- | --------------------- |
| **Amazon CloudWatch**    | AWS resource metrics, logs, alarms              | Webhook (SNS)         |
| **AWS Budget**           | AWS cost and usage thresholds                   | Webhook (SNS)         |
| **AWS GuardDuty**        | Threat detection across AWS accounts            | Webhook (EventBridge) |
| **Google Cloud Monitor** | GCP resource metrics and uptime checks          | Webhook               |
| **Azure Log Alerts**     | Log Analytics query-based alert rules           | Webhook               |
| **Azure Metric Alerts**  | Azure Monitor metric threshold alerts           | Webhook               |
| **Azure Activity Logs**  | Azure subscription-level activity events        | Webhook               |
| **Azure Cost Budget**    | Azure spending threshold alerts                 | Webhook               |
| **Azure Service Health** | Azure platform incidents and maintenance events | Webhook               |
| **Alibaba CloudMonitor** | Alibaba Cloud resource metrics and events       | Webhook               |

***

### How it works

Cloud monitoring services generate alerts when resource metrics, cost thresholds, or platform health events meet defined conditions. These alerts are forwarded to ITOC360 via webhooks — typically through notification channels like AWS SNS, Azure Action Groups, or Google Cloud notification channels. ITOC360 receives the payload, parses the alert details, and routes the incident to the responsible on-call team based on your escalation policies.

{% hint style="info" %}
ITOC360 generates a unique webhook URL per Source. Go to **Management > Sources**, create a Source, and paste the webhook URL into your cloud provider's notification or action group settings.
{% endhint %}

***

### Get started


---

# 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.itoc360.com/integrations/inbound-integrations/cloud-monitoring.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.