Cortex Integration with ITOC360
Cortex extends Prometheus into a horizontally scalable, multi-tenant monitoring backend used by teams running large-scale cloud-native infrastructure. Like Prometheus, Cortex evaluates alert rules continuously and routes firing alerts through Alertmanager. But Alertmanager routes to passive destinations. An alert that reaches only a Slack channel or email at 3 AM waits until someone checks it. ITOC360 connects to Cortex as a native Alertmanager webhook receiver, converting every firing alert into an active escalation that guarantees human response.
Cortex is built for scale, monitoring thousands of metrics across multi-tenant environments. When a rule fires, Alertmanager processes and routes it within seconds. But if the destination is a passive channel, that speed advantage is lost the moment no one is actively watching. In distributed teams with follow-the-sun coverage or shared on-call rotations, passive alerting creates coverage gaps.
How ITOC360 Connects to Cortex
80% of outages are avoidable. Cortex identifies the issue; ITOC360 ensures a human response matches that detection speed.
Notification via preferred channel
On-call engineers receive alerts via Voice Call, SMS, or Email based on their own preferences.
Native Alertmanager webhook receiver
Add ITOC360 as a receiver in alertmanager.yml, no additional tooling required.
Zero PromQL or ruler changes
Existing Cortex alert rules, tenants, and routing logic remain completely untouched.
Automatic alert resolution
When Cortex sends a resolved event, ITOC360 closes the alert and stops all escalations.
Why Cortex Alerts Need Active Escalation
Cortex is built for scale, monitoring thousands of metrics across multi-tenant environments. When a rule fires, Alertmanager processes and routes it within seconds. But if the destination is a passive channel, that speed advantage is lost the moment no one is actively watching. In distributed teams with follow-the-sun coverage or shared on-call rotations, passive alerting creates coverage gaps.
ITOC360 fills that gap. When Alertmanager fires a webhook to ITOC360, the system immediately identifies the on-call engineer from your schedule, contacts them through their preferred channel, and escalates automatically if the alert goes unacknowledged within the configured timeout.
Cortex Detection Meeting Active Escalation
Cortex identifies the issue, but passive channels cannot guarantee a human response. ITOC360 bridges that gap, notifying the right expert via their preferred channel and escalating until someone responds.
How Do Teams Typically Set This Up?
Common questions about integrating Cortex with ITOC360.
Via Prometheus Alertmanager. Add ITOC360 as a webhook receiver in your alertmanager.yml and point Cortex Ruler to that Alertmanager instance. No changes to your Cortex ruler rules or PromQL expressions are required.
No. Manage all rotations, schedules, and escalation policies inside ITOC360. Alertmanager only sends the trigger.
Yes. Use Alertmanager routing rules with label matchers (e.g., severity: critical) to control which alerts are forwarded to the ITOC360 receiver.
Yes. Silenced alerts do not fire a webhook, so they never reach ITOC360 and do not trigger on-call notifications.
ITOC360 provides a full incident timeline for every Cortex alert: when the rule fired, when the first notification went out, who acknowledged it, and the complete escalation path taken.
