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
Integrations guideline
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
Administration
Roles and access
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
Why does message parsing fail?
We parse the data integrations send in JSON to human readable format. Sometimes it fails. What does it mean and why does it happen?

Message parsing failed

After you setup integrations on Spike.sh, these integrations send us payload of JSON data for every new incident. We convert this JSON data into a human-readable format which is then used on the incidents table and in phone calls, emails, Slack etc.
Sometimes, this parsing fails and your table might see an entry like below -
Example of incident message parsing fail

Report with a single click

When you see this, please report this issue to us so we can start looking into this. The more you report the better this parsing gets.
Report with a single click

Why does this happen?

We try our best to parse all the payloads and convert it into a gist you can actually read and get a sense of the incident. Each integration has tons of cases and our parser fails to understand it and that's what causes Incident message parsing fail.

Does it affect my alerts?

Yes, your alerts will not have the message.

Would I still receive alerts?

Yes. Alerts will still be sent however the exact incident message will not be available.

Is the incident affected?

No. The details of your incident are still available. You can click on the #ID of the incident and see all the details as you do with other incidents.

Should we take any action?

We would love it if you can please report the incident.
Once the parser is fixed, it will not change the message for existing incidents but it will surely pave the way for future incidents
​
Incidents - Previous
Sharing incidents
Next - Alerts
Phone
Last modified 1yr ago
Copy link
Contents
Message parsing failed
Report with a single click
Why does this happen?
Does it affect my alerts?
Would I still receive alerts?
Is the incident affected?
Should we take any action?