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
Pushover
Discord
Alert rules
Vacation mode
Services
Introduction to services on Spike
Escalations
Introduction to escalations
How to create an escalation policy?
Repeat escalations
Archive escalation policy
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
Powered By GitBook
SSO
Configure Single Sign-On on Spike.sh
​
This guide explains the settings you’d need to use to configure SAML with your Identity Provider. Once this is set up you should get an XML metadata file which you can provide to Spike and start using SSO.
​

Step 1

Follow the configurations given below while configuring your SAML with your IdP.
  • Assertion consumer service URL / Single Sign-On URL / Destination URL: https://app.spike.sh/sso/oauth/saml
  • Entity ID / Identifier / Audience URI / Audience Restriction: https://app.spike.sh
  • Response: Signed
  • Assertion Signature: Signed
  • Signature Algorithm: RSA-SHA256
  • Assertion Encryption: Unencrypted
​
For example, in the case of Okta users, this is how the configuration looks
SAML configurations

Step 2

Add user mappings as shown below. Note that email , firstName and lastName are mandatory.
Mappings
​

Step 3

Once the SAML is configured, head over to Spike.sh and open organisation settings.
Paste the IdP XML Metadata and save.
​

Step 4

Once configured, you can find the organisation slug from organisation settings.
​
​
​
Use that slug at the time of login.
​
Check out the steps to configure SAML with Azure AD here.
Administration - Previous
Roles and access
Next - Administration
Our notification numbers
Last modified 4d ago
Copy link
Contents
Step 1
Step 2
Step 3
Step 4