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 manually comb through chat channels, transcripts, or other documents to cobble together the timeline after the incident.

With FireHydrant, all events that occur throughout - Runbook automation steps executing, users taking actions and marking tasks as complete, 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.

Certain types of timeline events, such as messages posted directly in the UI, provide the ability to edit or copy the message. You can find these action buttons on the right side next to the star.

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.

These settings, defaults, and emojis can be configured in your Slack integration settings.

Next Steps

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

• Adding Responders
• Posting Updates
• Managing Tasks
• Slack Responder Guide
• UI Responder Guide