Cosa abbiamo rilasciato.

ottobre 2026

1. 20 ott 2026, link a questa voce
   Risolto 20 ott 2026, link a questa voce Link copiato

   Un avviso di chiusura quando manutenzione, pausa o eliminazione chiudono un incidente

   An incident that ended because a maintenance window started, or because someone paused, changed the address of or deleted a monitor that was down, used to close silently. Slack and email never heard it was over, and the PagerDuty incident stayed open.

   Now every channel that got the down alert gets a notice that says why the incident closed, and PagerDuty resolves it.

   Leggi di più: Come collegare PagerDuty, Google Chat, ntfy e altri

2. 20 ott 2026, link a questa voce
   Risolto 20 ott 2026, link a questa voce Link copiato

   Niente falsi avvisi per cron job e server dopo un’interruzione dei nostri controlli

   When our own monitoring had a gap, cron job and server monitors could alert as soon as it ended. They now pause during the gap and start their clock again when it ends.

   Alerts also go out six at a time instead of one by one, so a single slow webhook can no longer hold up the rest.

   Leggi di più: Monitoraggio dei cron job