Slack
The Spike app for Slack sends incident and on-call alerts to your channels and offers slash commands for creating incidents and checking on-call responders.
Last updated
The Spike app for Slack sends incident and on-call alerts to your channels and offers slash commands for creating incidents and checking on-call responders.
Last updated
The Spike app for Slack keeps your team informed and responsive during incidents.
Key features include:
Incident alerts and acknowledge / resolve / escalate them
On-Call shift notifications
Private channel support
Create incidents directly from Slack
View currently on-call responders
Visit the Alerts section in settings and click on Add to Slack.
Visit the Alerts section inside your settings and click on Add to Slack. Our Slack app asks for some basic permissions.
Add Slack as a step in your escalation policy to get incident notifications. You can choose between public or private channels for these alerts.
Use the /help command on Slack for further help. Spike app cannot read any of your messages on Slack
Here are all the available /slash commands -
/create-incident Create a new incident directly from Slack. Anyone in your workspace can use this command.
/oncall now or /oncall me Check who is currently on-call or view your on-call schedule.
/connect Connects your Slack account in the workspace with Spike.
/help Display a help message with guidance on using the Spike app in Slack.
Using the /create-incident command in Slack opens an intuitive view to create incidents directly from your workspace. Here's how:
Anyone in your Slack workspace can create incidents
Spike's incident alerts will mention @here to notify everyone online on the channel. The incident contains some key details like Title, Responders, Links, and Integration.
Available Actions for Each Incident
Acknowledge
Resolve
Escalate
Discuss in a New Channel
{% hint style="info" } Visit the Alerts section inside your settings and click on Add to Slack. Our Slack app asks for some basic permissions.
Add Slack as a step in your escalation policy to get incident notifications. You can choose between public or private channels for these alerts.
Each incident includes the option to discuss in a new channel. When this action is initiated, a dedicated channel is created for collaboration on resolving the incident. Initially, only the user who initiates the action will be added to the new channel.
Spike does not have access to read messages in these channels, maintaining your privacy.
We recommend archiving the channel once the incident is resolved to prevent stale channels in your workspace.
If a Slack alert has been sent for a new incident and it is resolved—whether automatically, via Phone, SMS, Email, or the Dashboard—the Slack message will automatically update to reflect the resolved status, eliminating any ambiguity about the incident’s state.
Private channels access can be configured in Settings > Alerts
When managing escalations, only users who have connected their Slack account with Spike can view private channels. However, they can only access private channels that:
They are a member of.
The @Spike.sh app has been added to.
Both the user and the @Spike.sh app must be part of the private channel for it to appear under escalations.
To continue to receive alerts on your private Slack channels, it is important to add the @Spike.sh app to those channels. This step is mandatory, particularly for escalations configured before 11th December 2024, as alerts will not be delivered without the bot being added.
Once a private channel is added to an escalation, its name is visible only to users who:
Have connected their Slack account with Spike.
Are members of the same private channel.
Users without these permissions will not see the private channel name, ensuring enhanced privacy.
Visit Settings > Alerts to select Slack channels to receive on-call shift alerts.
You can enable notifications for both shift start and shift end.
