Skip to main content

Deprecation of Incidents

Published: July 29, 2026

Effective: October 30, 2026

Deprecation notice

Coralogix will retire the Incidents view on October 30, 2026.

Incidents is deprecated in favor of Cases, the Coralogix home for incident response. Cases correlates the logs, metrics, and traces you need for triage, and adds ownership and assignment, response-time KPIs (Time to Acknowledge and Time to Resolve), Olly summaries, and two-way sync with PagerDuty, ServiceNow, and Slack.

Action is required to move your incident-response workflows to Cases before the effective date. The Incidents API keeps working, but we recommend migrating to the Cases API, available through MCP and the cx CLI.

Why this is happening

Cases runs on your existing alerts and the same underlying data, so it makes on-call response faster without a rebuild and preserves your full history. New Coralogix accounts already start on Cases.

What's affected

The Incidents view is being deprecated. This affects:

  • Teams that triage and manage incidents in the Incidents view.
  • Bookmarks or links that point directly to the Incidents view.
  • Integrations or scripts that read incident data through the Incidents API.

After the effective date, use Cases for all incident-response workflows.

What you need to do

Move to Cases

In Coralogix, select Alerts, then Cases. The page opens on the Case list tab and shows your current and past Cases. Review Cases and Incidents to map your workflows, and if you use the Incidents API, plan your migration to the Cases API.

No rebuild is required. Cases uses your existing alerts and data, and your history is preserved.

What will happen after October 30, 2026?

  • The Incidents view is removed from the Coralogix interface, and links or bookmarks to it stop working.
  • Incident-response workflows continue in Cases.
  • The Incidents API remains available, and the Cases API is the recommended path forward.
  • There is no impact to your alerts, data, or history.
  • Existing workflows continue in Cases, and migration is strongly recommended.

Need help?

Our team is here to help you migrate smoothly.

Is something blocking your move to Cases, such as a missing workflow or a reason your team cannot migrate by October 30? Reach out via our 24/7 in-app support or contact your Account Manager or Technical Account Manager before the deadline, and we'll guide you through the transition.

Last updated on