Which channels does PeakNode use for alerts?
PeakNode sends alerts via email, Microsoft Teams, Slack, Telegram, Discord and webhook. For each monitor you choose which channels receive the alert, several at once if your plan allows it. With the webhook you reach ticket systems and your own services.
What does “I'm on it” mean?
With “I'm on it”, a person confirms that they are taking over an ongoing outage. The acknowledgement stops reminders and escalation for this outage, and the portal shows that someone is on it. It does not end the outage itself: the incident only closes when the service is running again.
What happens if nobody responds to an alert?
Then PeakNode sends reminders to the same channels at the configured interval and, after the configured time, notifies further channels once. You have to switch both on for the monitor; by default they are off. Reminders stop on acknowledgement or when the service is running again.
Can I acknowledge an alert from the email?
Yes. The “I'm on it” button in the alert email opens a page where you complete the acknowledgement without signing in to the portal. The link applies only to this specific outage and stops working once the outage has ended.
Which notifications have acknowledgement and escalation?
Outages: an uptime monitor is offline, a heartbeat was missed, a server monitor stopped reporting data. Threshold alerts, hardware events, DNS changes and reminders about expiring domains or certificates go to the channels as a single notification, without acknowledgement, without escalation and without an all-clear.
How do alerts get into our ticket system?
Through the webhook channel. On an alert and on the all-clear, PeakNode sends a POST request with the fields of the event to your URL. Which fields these are and how a ticket system acknowledges an incident via the API is described under API and webhooks.
What happens if Slack or the mail server is unreachable at the moment?
PeakNode retries delivery after 1, 5, 15, 30, 60 and 120 minutes. Only then is the notification discarded. The outage itself is stored in the portal regardless, and the channel shows the reason for the last failed delivery.
What is an escalation level?
An escalation level defines who is notified when an alert has not been acknowledged after a certain time. PeakNode has one such level: after 15, 30 or 60 minutes without acknowledgement, exactly one notification goes to additional channels. PeakNode does not model multi-level chains or on-call schedules.
How do I avoid alert fatigue?
With the settings PeakNode provides for this: threshold alerts only fire after 1 to 10 consecutive checks, an uptime monitor only alerts after a failed recheck, and maintenance windows suppress the expected alerts of planned work. Hardware events of one report arrive bundled in one message, and NodeCare collects plannable tasks in a summary at 08:00.