Create Incident Channel

Example incident channel created for an incident

Example incident channel created for an incident

Organizing your communication is critical during an incident. FireHydrant gives you control over if and when a centralized channel is opened for your incident.

Slack

Create or Rename Incident Channel

Slack "Create or Rename Incident Channel" step

Slack "Create or Rename Incident Channel" step

This Runbook step creates or renames the incident channel in Slack:

  • If the channel does not exist, this step will create a new incident channel per your configurations.
  • If the channel exists because another Runbook step executed it elsewhere, subsequent runs of this step will rename the channel if there are changes from the original.
  • If the channel exists because it was created outside of FireHydrant, then FireHydrant cannot delete or rename that existing channel and will create a new one. This new channel will be named according to your specified conventions, and a dynamically calculated hash will be appended to the end because Slack requires channel name uniqueness.

The available fields to configure are:

  • Channel name format - Name format of the channel. FireHydrant sees organizations using a variety of identifiers here, including the name or number of the incident, severity, and sometimes even external ticketing identifiers.
    • Slack limits channel names to only alphanumerics, dashes, and underscores, with 80 characters as the maximum length. If the name ends up being longer than 80 character, FireHydrant will truncate it to 80 characters.
    • This field supports Template Variables
  • Channel visibility - Set the Slack channel as public or private. Note that

πŸ“˜

Note:

  • Subsequent runs of this Runbook cannot change an existing channel's privacy, even if the settings are different.
  • At this time, FireHydrant only supports one channel created and tracked in the timeline per incident.
  • Create a communications channel? - This is an option that's available for organizations that want to spin up multiple channels - one for primary incident response and then another just for comms.
    • Any updates or changes made on the incident will be posted to both channels. However, any chat messages or other activity within the comms channel will not be included in the timeline.
    • This use case is recommended for organizations that want a separate channel where people can chat, ask questions, etc., but without polluting the primary responders' channel or timeline.

Microsoft Teams

Create Incident Channel

MS Teams "Create Incident Channel" step

MS Teams "Create Incident Channel" step

This Runbook step creates an incident channel in Microsoft Teams. The Name field supports Template Variables.

πŸ“˜

Note:

We currently cannot create private channels in Microsoft Teams or rename them in subsequent runs like Slack.

Channel Naming Conventions

Some examples of channel naming conventions our customers use:

  • incident-{{ number }} will become incident-42. This is the default
  • -inc-{{ date }} will become -inc-2019-10-22
  • {{ incident.severity }}-incident-{{ name }}-{{ date }} will become sev1-incident-bobbys-big-spill-2019-10-22
  • -inc-{{ date | replace: '-', '' }} will become -inc-20191022