Spike.sh
DashboardWebsite
Search…
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?
Alerts
Phone
SMS
E-mail
Slack
Microsoft Teams
WhatsApp
Telegram
Pushover
Discord
Alert rules
Vacation mode
Title Remapper
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
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
Status Pages
Create Status page
Create public Incident 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
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 Sentry webhook
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 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
Administration
Roles and access
SSO
Our notification numbers
Contact the support team
Adding team members
Check if team is getting alerts
Removing team members
Additional resources
Create a badge
Alert Modes
Deep Work Mode
Cooldown Mode
Out of office mode
Powered By GitBook
What is Spike.sh?
Spike.sh is a simple incident management platform. We help you by alerting the right team members about incidents that affect your customer.

Focusing on simplicity

Spike.sh's mission is to reduce the complexity of managing incidents and make it simple so teams of all sizes use it.
Our platform consists of a few modules -
  1. 1.
    Integrations
  2. 2.
    Services
  3. 3.
    Escalations
  4. 4.
    Alerts
  5. 5.
    On-call schedules
  6. 6.
    Alert rules
  7. 7.
    Reports
To get in depth, please reach out to us at [email protected] or book a call directly on our calendar.

Integrations

We integrate with a number of services and tools so you can use Spike as a central intelligence as we gather incidents and alert the right person for each incident. You can add unlimited number of integrations to your account. Each integration would have a separate identifiable token so you needn't worry about incidents mixing up and rest knowing that we have got you covered.
We recently released Quick Setup for integrations. You can add new integrations to already existing services in just 10 seconds.
We have a growing list of integrations. If you don't see an integration you need then email us at [email protected] and we will build it for you.

Services

Services on spike
You can think of services as a microservice. Services are a way to scope your internal services from your architecture. Each of your service can have multiple integrations and you can create unlimited number of services. We highly encourage you to create different services for each of your different modules.
You can create services by just adding a name to it. No other field is required. With the power of unlimited services, you can create a blueprint of your entire architecture on Spike. This way, we will tell which service is affected and what is the current health status in terms of open incidents.

Escalations

Multiple escalation policies
We provide simplicity by un-complicating escalation policies by allowing you to choose your alert channels. Anyone from your team can create escalation policies you can easily use. With the power of unlimited escalations, you can create escalations policies just for your self or one for your team and one for every team in your organization.

Reports

Reports and data you will actually use
No matter the size of your team, we believe everyone should have access to reports to bring in transparency to know how your platform measures in terms of open incidents. We provide graphs to get a sense of total incidents, new incidents and repeated incidents for a given time period.
​
Previous
Introduction
Next - Incidents
What is an incident?
Last modified 11mo ago
Copy link
On this page
Focusing on simplicity
Integrations
Services
Escalations
Reports