Spike.sh
DashboardWebsiteHUB
Spike.sh
Spike.sh
  • Introduction
  • What is Spike.sh?
  • Incidents
    • What is an incident?
    • Incident lifecycle
    • Incident statuses
    • How to change incident status?
    • Acknowledge timeout
    • Grouping incidents
    • Priority and Severity
    • Mute alerts
    • Reassign incidents
    • Sharing incidents
    • Why does message parsing fail?
    • Rate limiting on duplicate incidents
  • Alerts
    • Phone
    • SMS
    • Mobile app alerts
    • E-mail
    • Slack
    • Microsoft Teams
    • WhatsApp
    • Telegram
    • Pushover
    • Discord
    • Alert rules
    • Title Remapper
    • Personal alerts management
      • During office hours
      • Out of office
      • Resolved incident alerts
      • Deep work & Cooldown modes
  • Services
    • Introduction to services on Spike
  • Escalations
    • Introduction to escalations
    • How to create an escalation policy?
    • Repeat escalations
    • Archive escalation policy
  • Collaboration
    • Task management integrations
      • JIRA Cloud
      • JIRA server (self-hosted)
      • ClickUp
      • Linear
      • Shortcut
    • Helpdesk integrations
      • Zendesk
      • Freshdesk
      • Supportpal
    • War rooms
  • On-call schedules
    • Introduction to On-call schedules
    • Create On-call schedule
    • Introduction to Slots in schedules
    • Introduction to Layers in on-call schedules
    • Override an on-call
    • Add on-call schedule to your calendar
    • Notifications for on-call shifts
    • Change on-call rotation day
  • Playbooks
    • Introduction to Playbooks
    • Actions in Playbooks
    • Automating your Playbooks
    • Run Playbooks manually
  • Status Pages
    • Create Status page
    • Style your status page
    • Incidents on status page
    • Create Planned Maintenance on status page
    • Edit Planned Maintenance
    • Add custom domain to status page
    • Manage your subscribers
    • Embed status page notifications on your website
    • Live status widget
  • Uptime
    • Create Uptime monitor
    • Link uptime to Status Page
  • Integrations guidelines
    • Create integration and service on our dashboard
    • Setup integrations
    • Archive an integration
    • Integrating with Webhooks
    • Integrate Spike with Email
    • Integrate Spike with AWS
    • Integrate Spike with Google Cloud
    • Integrate Spike with Sematext
    • Integrate Spike with Healthchecks
    • Integrate Spike with Pingdom
    • Integrate Spike.sh with Sentry
    • Integrate Spike with Apex ping
    • Integrate Spike with Uptime Robot
    • Integrate Spike with Twilio
    • Integrate Spike with Microsoft Azure
    • Integrate Spike with Honeybadger
    • Integrate Spike with Rollbar
    • Integrate Spike with Travis CI
    • Integrate Spike with Heroku
    • Integrate Spike with Datadog
    • Integrate Spike with Axiom
    • Integrate Spike with Needle.sh
    • Integrate Spike with Cronitor
    • Integrate Spike with Bugsnag
    • Integrate Spike with Grafana
    • Integrate Spike with Prometheus
    • Integrate Spike with Instana
    • Integrate Spike with Zapier
    • Integrate Spike with Librato
    • Integrate Spike with Checkly
    • Integrate Spike with AppSignal
    • Integrate Spike with New Relic
    • Integrate Spike with Site24x7
    • Integrate Spike with Stackify
    • Integrate Spike with Scout-apm
    • Integrate Spike with Oh-Dear
    • Integrate Spike with Nixstats
    • Integrate Spike with Server Density
    • Integrate Spike with Raygun
    • Integrate Spike with Lightstep
    • Integrate Spike with Runscope
    • Integrate Spike with Honeycomb
    • Integrate Spike with Graylog
    • Integrate Spike with Checkmk
    • Integrate Spike with Hyperping
    • Integrate Spike with Epsagon
    • Integrate Spike with Uptime
    • Integrate Spike with Splunk
    • Integrate Spike with Sumo Logic
    • Integrate Spike with Thousand Eyes
    • Integrate Spike with Loggly
    • Integrate Spike with Elastic Cloud
    • Integrate Spike with App Optics
    • Integrate Spike with NodePing
    • Integrate Spike with Scalyr
    • Integrate Spike with Moogsoft
    • Integrate Spike with AppDynamics
    • Integrate Spike with Dynatrace
    • Integrate Spike with CopperEgg
    • Integrate Spike with Coralogix
    • Integrate Spike with ElastAlert
    • Integrate Spike with LogDNA
    • Integrate Spike with Zebrium
    • Integrate Spike with LibreNMS
    • Integrate Spike with Uptime Kuma
    • Integrate Spike with Logentries
    • Integrate Spike with Logz
    • Integrate Spike with Ghost Inspector
    • Integrate Spike with Hetrix Tools
    • Integrate Spike with LogRocket
    • Integrate Spike with StatusCake
    • Integrate Spike with Sysdig
    • Integrate Spike with Wavefront
    • Integrate Spike with Buildkite
    • Integrate Spike with Semaphore
    • Integrate Spike with Better Uptime
    • Integrate Spike with Hexowatch
    • Integrate Spike with PM2
    • Integrate Spike with Cloudflare
    • Integrate Spike with Zabbix
    • Integrate Spike with Tenderly
    • Integrate Spike with Xitoring
    • Integrate Spike with Crowdstrike
    • Integrate Spike with GitHub Workflows
    • Integrate Spike with Solarwinds Orion
    • Integrate Spike with Airbrake.io
    • Updown.io
  • Administration
    • Roles and access
    • SSO
    • Enforce login
    • Our notification numbers
    • Contact the support team
    • Adding team members
    • Check if team is getting alerts
    • Removing team members
  • Additional resources
    • Create a badge
Powered by GitBook
On this page
  • Introduction
  • How to set up
  • Slash commands
  • Create incidents from Slack
  • Incident Alerts
  • Discussing in a new channel
  • Auto-Updating Slack messages
  • Private channels setup
  • On-call alerts
  • FAQs

Was this helpful?

Edit on GitHub
  1. Alerts

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.

PreviousE-mailNextMicrosoft Teams

Last updated 4 months ago

Was this helpful?

Introduction

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

How to set up

  • Other team members can also link their Slack accounts to receive direct messages for important updates.

  • Run the /connect command to connect

Use the /help command on Slack for further help. Spike app cannot read any of your messages on Slack


Slash commands

Here are all the available /slash commands -

  1. /create-incident Create a new incident directly from Slack. Anyone in your workspace can use this command.

  2. /oncall now or /oncall me Check who is currently on-call or view your on-call schedule.

  3. /connect Connects your Slack account in the workspace with Spike.

  4. /help Display a help message with guidance on using the Spike app in Slack.

Create incidents from Slack

Using the /create-incident command in Slack opens an intuitive view to create incidents directly from your workspace. Here's how:

1

Add a Title and Details

Provide a clear and meaningful title along with relevant details, including JSON data or links if applicable.

2

Select Integration and Escalation Policy

Choose the appropriate integration and escalation policy to ensure the incident is routed correctly.

3

Submit

Click to create the incident. It's that simple!

Anyone in your Slack workspace can create incidents


Incident Alerts

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

  1. Acknowledge

  2. Resolve

  3. Escalate

  4. Discuss in a New Channel

Discussing in a new channel

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.

Who can create these channels?

Anyone in your workspace can initiate this action and create new channels.

Can the same channel be reused for multiple incidents?

No, a new channel is created for each incident to keep discussions organized and focused.

What happens to the channel after the incident is resolved?

The channel remains in your workspace until it is manually archived. We recommend archiving the channel after resolving the incident to keep your workspace tidy.

Can non-Spike users participate in the channel?

Yes, anyone in your workspace can be invited to join the discussion, regardless of their Spike account status.

We recommend archiving the channel once the incident is resolved to prevent stale channels in your workspace.

Auto-Updating Slack messages

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.

Will the Slack message update if an incident is resolved automatically?

Yes, the Slack message will automatically update to show the resolved status.

What if I try to resolve an incident on Slack that has already been resolved elsewhere?

The Slack app will notify you that the incident has already been resolved, preventing duplicate actions.


Private channels setup

Adding private channels to escalations

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:

  1. They are a member of.

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

Private channel visibility in escalations

Once a private channel is added to an escalation, its name is visible only to users who:

  1. Have connected their Slack account with Spike.

  2. Are members of the same private channel.

Users without these permissions will not see the private channel name, ensuring enhanced privacy.

I can’t find a channel in the dropdown. What should I do?

You can find the channel by pasting its ID from Slack. To locate the channel ID, open the channel, go to the About section, and find the unique ID.

Why can’t I see a private channel in the escalation dropdown?

You must be a member of the private channel and have connected your Slack account with Spike. Additionally, the `@Spike.sh` app must be added to the private channel.

To connect, run the /connect command on Slack

Can all team members view the private channels added to escalations?

No, only users who are members of the private channel and have connected their Slack account with Spike can view its name in escalations.

How do I add the @Spike.sh app to a private channel?

Invite by typing `/invite @Spike.sh` in the channel.

Can I add a private channel to escalations without connecting my Slack account?

No, your Slack account must be connected to Spike to add or view private channels in escalations.

What happens if I disconnect my Slack account after adding private channels to escalations?

You will no longer be able to view the private channel names in escalations, even if you are a member of those channels.

Can I see private channels added by other users in the escalation policy?

Only if you are a member of the same private channel and have your Slack account connected to Spike.

What if I’m an admin on Slack but not a member of the private channel?

Admin privileges on Slack do not grant visibility to private channels unless you are explicitly added as a member of the channel.


On-call alerts

You can enable notifications for both shift start and shift end.


FAQs

Can anyone create an incident? Is there an extra charge?

No, anyone can create an incident, and there is no additional cost.

User A and B are part of a private channel in the escalation policy, but B can’t see the channel name in Escalation. Why?

This happens when User B hasn’t connected their Slack account with Spike. To connect, they can: - Search for the Spike.sh bot in Slack and send a direct message to connect. - Run the `/connect` command to connect

Visit the in settings and click on Add to Slack.

Visit the inside your settings and click on Add to Slack. Our Slack app asks for some basic permissions.

Add Slack as a step in your to get incident notifications. You can choose between public or private channels for these alerts.

Visit to select Slack channels to receive on-call shift alerts.

{% hint style="info" } Visit the inside your settings and click on Add to Slack. Our Slack app asks for some basic permissions.

Add Slack as a step in your to get incident notifications. You can choose between public or private channels for these alerts.

Private channels access can be configured in

Visit to select Slack channels to receive on-call shift alerts.

Install Spike app on Slack
App on Slack marketplace
Set incident alerts with escalations
Set on-call alerts
Alerts section
Alerts section
escalation policy
Settings > Alerts
Alerts section
escalation policy
Settings > Alerts
Settings > Alerts