Why this matters
Most cost spikes get looked into, whether that means checking a recent deploy or finding a batch job that ran long. You can now save what your team found, and whether the spike was expected, as notes on the incident.
Anyone who opens the incident later can see what your team found and decided. If the same service spikes again, you can start from the last investigation, and if finance asks about a jump in the bill, you can send them the incident.
What we built
Comments on Incidents. Add a comment directly in an incident’s Activity tab, alongside its status changes and assignments. You can edit and delete your own comments, and you can keep commenting after the incident is resolved.
Comments appear in the same timeline as the rest of the incident’s history. The record shows when the spike started, who looked at it, what they found, and how it was resolved.
How it works
Open an incident in Monitors and go to the Activity tab. Type your comment and post it. To change or remove one of your comments, use the options on that comment.
Try it now → https://docs.cloudzero.com/docs/monitors
