Skip to content
InnoStak Pulse

Monitoring

Incidents and alerts

How Pulse decides something is broken, who gets told, and how it avoids alert fatigue.

Updated Rolling out

Rolling out. This feature is rolling out to pilot customers, so it may not be in your workspace yet.

Opening and resolving incidents

By default, a monitor opens an incident after 3 consecutive failures and resolves it after 2 consecutive successes. That filters out one-off network blips.

Acknowledge, assign and resolve

Every acknowledgment, assignment, comment and resolution is recorded in the incident's history, so you can always see who did what and when.

Alerts that respect your time

  • Email alerts, plus opt-in SMS.
  • Choose which severities reach you, and set quiet hours in your time zone.
  • One recovery notice instead of repeated alerts for the same incident.
  • Maintenance windows pause alerts you already expect.

If Pulse can't collect data, it opens a monitoring issue. It never assumes your site is healthy when data is missing.

Don't wait for something to break.

Start your pilot and get alerts within minutes, with the evidence attached. Business email required.

Backup when you need it

Your developer's stuck? Ours aren't.

Pulse is built by InnoStak, a software engineering and automation partner. When a fix is beyond your team, hand it over with the evidence attached. Optional, and quoted separately from your Pulse plan.

Talk to InnoStak (opens innostak.com in a new tab)