Incident Timeline

As you work your way through incidents, a common pain point is tracking the things that happen and when they happen.

This often means teams will have a "scribe" or "note taker" who follows along and manually notes the things that occurred during the incident. Or, more painstakingly, someone must comb through chat channels, transcripts, or other documents to cobble together the timeline after the incident, often manually.

With FireHydrant, all events that occur throughout - Runbook automation steps executing, or users taking actions and marking tasks as complete, or any chats/images posted into the incident channel, or more - are logged automatically in the timeline.

This alleviates a large burden from at least one team member having to manually track events.

Using the Timeline

No setup is required - as mentioned above, all events that occur in FireHydrant are logged automatically, including messages, images, and actions from Slack.

The timeline can be filtered to specific types of events if you're looking for something in particular.

Starring Events

You can Star events from both Slack as well as the app UI. Starring an event marks it as "important" and allows you to comment on it, and it also becomes a primary highlight during the Retrospective phase of an incident.

Next Steps

Now that you know everything is tracked automatically by FireHydrant, check out more of what FireHydrant has to offer:

• Assigning teams and users to roles
• Posting incident updates
• Managing incident tasks
• Running incidents entirely from Slack