Changelog

All new releases and improvements to Spike

Apply to all incidents, A new Alert Rule condition

Apply to all incidents alert rule

You can now apply actions to all incidents with the new "Apply to all incidents" condition in Alert Rules.

Previously, you had to use regex patterns like "incident title starts with /*/" to target all incidents. Now, just select "Apply to all incidents" and you're done.

This condition works for specific integrations and services too. For example, set all Datadog incidents to Sev1, or add resolve timers to all incidents from your payment service.

It’s a simpler, more convenient way to manage your incidents.

Introducing "Resolved by Timer"

Resolve Timer

We’ve added a new way to automatically resolve incidents: Resolve Timer. Incidents now close on their own after a set time, which keeps dashboards clear of stale incidents and prevents old incidents from suppressing new alerts. Resolve Timer is available on all Spike plans starting today.

You can apply Resolve Timer in:

  • Directly on integrations — for all incidents triggering on an integration

  • Alert Rules — only for alerts that match certain conditions

  • Playbooks — as part of your automation chain

Read the docs

Test your alert setup

test alerts

You can now test your alert channels instantly after setting them up.

Receive test alerts for phone calls, SMS, WhatsApp, Telegram, and Mobile app to make sure you are setup when incidents trigger.

Admins can test alert setups for other members as well.

You get 3 phone call and SMS tests per user per day.

Find it in Settings → Team → Send test alerts.

Test your alert setup →

You can now test your escalation policies with one click shortcut.

Just hit “Test Escalation” on any escalation policy to create an instant test incident and run through the entire escalation flow.

It’s an easy way to verify your rules and routing before a real incident occurs.

Test an escalation →

Anyone can create incidents from Slack

Incident creation from Slack

You no longer need to be a Spike user to create incidents from Slack.

Anyone in your workspace—clients, contractors, or teammates who aren't part of your on-call team can now use the /create-incident command.

Just add the Spike app to your Slack workspace, and everyone gets access to create incidents.

This makes it easier for your entire team to report issues, even if they're not part of your Spike account.

Learn more →

Read docs →

Improved Paessler PRTG integration

Paessler PRTG integration

We've updated our Paessler PRTG integration.

  • It now auto-resolves incidents when the underlying issues clear up, so you won't see stale alerts cluttering your dashboard.

  • Also, incident titles are more descriptive and easier to understand at a glance.

This helps you better manage alerts from PRTG’s powerful monitoring of your entire IT infrastructure—including networks, servers, bandwidth, data centers, and more.

Introducing Live Call Routing

Live Call Routing

Spike now supports Live Call Routing in beta.

It’s a direct line that connects incoming calls to on-call engineers automatically. No more transferring calls or hunting down the right person.

Setup is quick:

  1. Add your number and name it
  2. Configure who receives calls (on-call schedules and fallback rules)
  3. Customize welcome and voicemail messages

After the call, you can create a new incident or link the call to an existing one.

Also, every call is logged with its recording and details, and a notification appears in your Slack or Teams channel.

Live Call Routing is now available in your account, and it works with your current schedules.

Improved Integrations - AWS, CrowdStrike, and Sentry

AWS

Our AWS integration now works across multiple AWS products including CloudTrail, CloudFormation, and others. You can connect everything with a single integration. No change is needed on your end.

The improved integration has better incident titles, auto-resolution, and grouping of incidents. This helps your team spot what’s important, group related issues, and respond faster.

We’ve upgraded our CrowdStrike integration to give you a richer set of security events. The integration now supports detection summaries, auth and audit events, XDR, and more.

You get more context and fewer duplicates for faster triage—all without writing any Title Remappers.

Sentry

We’ve improved our Sentry integration to make incident titles much clearer and easier to understand. Now, error descriptions are more concise and to the point.

× Zoomed Image