Improved Integrations - AWS, CrowdStrike, and Sentry

1. 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.

2. CrowdStrike

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.

3. 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.

Mentioning @here in Slack escalations is now optional

You can now choose who gets mentioned in Slack alerts from your escalation policies. Instead of always tagging everyone with @here, you can select:

• @here
• @channel
• Specific users
• Or no mention at all

This helps you cut down on noise and send alerts only to the right people. No more pinging the whole team for low-priority issues.

Note: By default, all your existing escalation policies mention @here.

Quality-of-life improvements in Slack

• Alerts now support multi-line titles, so messages are cleaner and easier to read.
• Slack messages now show who acknowledged an incident, so everyone knows who’s on it.

---

Customize Slack in Escalations →

Learn more about Slack bot →

Spot Auto-Resolved incidents easily

We’ve made it easier to spot incidents that were auto-resolved.

On your dashboard and mobile app, these incidents now clearly show as Auto-Resolved instead of the regular status badge.

This makes it simpler to review incidents at a glance — especially with the growing number of auto-resolved alerts.

Better Auto-Resolver for Grafana

We’ve updated our Grafana integration to handle multiple events per alert more intelligently. Our data shows that nearly 6% of incidents from Grafana include multiple events — and now Spike will automatically destructure them to detect and apply any auto-resolving events.

This means fewer noisy incidents and better alignment with what’s actually happening in your systems.

No changes needed on your end. It just works.

Dedicated Slack & Teams alerts for each on-call schedule

You can now receive on-call shift notifications on specific Slack channels or Microsoft Teams channels for each schedule, instead of one global channel for everything.

Set up different channels for different on-call teams—Backend notifications go to #backend-oncall, Frontend to #frontend-oncall, and so on. You can also add multiple channels to one schedule if needed.

To set it up:

→ Go to your on-call schedule, click settings, and select Slack or Teams

→ Add your preferred Slack or Teams channels

Now, each team only sees the shift changes that matter to them. This cuts down noise and keeps notifications relevant, so important alerts don’t get buried in unrelated team updates.

Set your custom alerts →

On-call notifications on Webhooks

On-call shift changes can now trigger webhooks to external systems—perfect for teams to extend automation when shifts rotate.

When shifts start or end, Spike triggers a GET/POST/PUT request to your webhook with shift details. Use this to notify external team members via SMS, mobile app, or any other system.

Find the Webhook section in your on-call settings and get started.

Set Webhook alerts →

Separate escalations for midnight incidents

With our new Time of day alert condition, you can now trigger different actions for the same incident based on when it happens.

For instance, you can configure a Slack notification during the day, but a phone call alert if the same issue happens at midnight.

You can also

• Change the escalation policy to wake people at midnight

• Lower noise from low-severity alerts after hours

• Set a higher priority on incidents after hours

To set it up:

1. Go to Automation > Alert rules
2. Add the Time of day condition
3. Select your time range and timezone
4. Choose the actions you want for incidents during those hours

Set up Time of day condition

Learn more about alert rules

On-call and alert settings for mobile app

Full on-call visibility

The Spike mobile app now shows your complete on-call calendar.

You can stay informed with:

• Who's on-call now
• Who's up next
• All your team's layers
• Upcoming overrides

This gives you total visibility into your schedule, making team coordination simpler.

---

On-Call Overrides

You can now create on-call overrides directly from your phone.

Whether you're stepping into a meeting or need to swap shifts with a teammate, you can make these changes instantly without opening your laptop.

This flexibility saves you time and reduces the stress of last-minute schedule changes.

---

New Alert Settings

We've revamped the mobile Settings section to match the desktop experience, with new options:

• Phone call settings - Select your preferred call speed and voice
• Messaging options - Customize how you receive notifications
• Alert preferences - Control how and when you get resolve and on-call alerts

The redesigned layout offers clearer categories and a cleaner interface for faster adjustments.

Add Notes from Slack to Incidents

You can now add notes to incidents on Spike — without ever leaving Slack.

Just open the incident’s Slack channel or find the incident alert on Slack,

• Click the More actions menu, and select Add note.
• Type your update, hit submit, and your note will show up instantly on the incident page in Spike.

This helps teams capture context and decisions while staying in the flow of incident response—no need to switch tabs or open the dashboard.

Learn more about Slack + Spike