> 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/incidents-and-alerts/sources.md).

# Sources

By creating a Source, you generate a unique endpoint (Webhook) that allows ITOC360 to receive, parse, and route alerts from your infrastructure.

#### Creating a New Source

To start receiving alerts, you must first configure a source:

1. Navigate to Management > **Sources**.
2. Click the **Create Source** button.
3. **Name:** Enter a descriptive name for this source (e.g., "Production Zabbix Server").
4. **Provider:** Select the integration type from the dropdown menu.
   * ***Supported Providers include:*** Zabbix, Grafana, Manage Engine, New Relic, Prometheus, PRTG, Solarwinds, and an expanding library of 100+ integrations.

#### Configuring the Alert Display

Once a provider is selected, ITOC360 presents the **Alert Display Builder**. This powerful tool allows you to map the incoming data fields from your monitoring tool to the alert format displayed in ITOC360.

* Customize Fields: You can select specific fields (e.g., Hostname, Severity, Error Message) available from the provider's payload.
* Preview: Configure how the alert title and description will appear to your on-call engineers. This ensures that the most critical information is visible at a glance without needing to parse raw JSON.

#### Source Settings

Before finalizing, you can configure the lifecycle and status of the source:

* **Expires At (Optional):** If this source is temporary (e.g., for a specific POC, migration project, or penetration test), you can set an expiration date. The source will automatically stop accepting alerts after this date.
* **Active:** Toggle this ON to enable the source immediately. If switched OFF, the source is created but will reject any incoming data (useful for maintenance modes).

Click **Create** to finish the setup.

#### Retrieving the Webhook Token

After creating the source, you need to connect your external tool to ITOC360.

1. On the **Sources** page, click on the name of the source you just created.
2. Locate the Token section.
3. Copy this Token.
4. Paste this into the notification/webhook configuration settings of your external monitoring tool (e.g., paste it into the Zabbix Media Type script or Grafana Notification Channel).

> Security Tip: Treat your Webhook Token like a password. Anyone with this token can send alerts to your system.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.itoc360.com/incidents-and-alerts/sources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.