> 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/error-tracking-and-uptime.md).

# Error Tracking and Uptime

This category covers error monitoring, uptime checking, and API testing platforms. These tools detect application errors, service outages, and failing health checks — and send alerts to ITOC360 so the responsible engineer is notified the moment something goes wrong.

***

### Integrations in this category

| Integration       | What it monitors                                                | Alert delivery |
| ----------------- | --------------------------------------------------------------- | -------------- |
| **Sentry**        | Application exceptions, performance regressions, release health | Webhook        |
| **Rollbar**       | Real-time error tracking across web and mobile applications     | Webhook        |
| **Pingdom**       | Website uptime, page speed, transaction monitoring              | Webhook        |
| **StatusCake**    | Uptime, SSL expiry, page speed, and domain monitoring           | Webhook        |
| **Postman**       | API monitor test failures, response time thresholds             | Webhook        |
| **Statuspage.io** | Public status page incidents and component degradations         | Webhook        |

***

### How it works

Error tracking and uptime tools run continuous checks against your applications, endpoints, and APIs. When a check fails, an error threshold is exceeded, or a service goes down, the tool sends an alert to your ITOC360 Source webhook URL. ITOC360 routes the alert through your escalation policy and notifies the on-call engineer so they can respond before users are impacted.

{% hint style="info" %}
ITOC360 generates a unique webhook URL per Source. Go to **Management › Alert sources**, create a Source, and paste the webhook URL into your tool's alert notification 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/error-tracking-and-uptime.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.
