Most system and service outages are caused by some kind of change—a new configuration, a new feature launch, or a new type of user traffic. Keeping track of all changes, when they happened, and what components were affected is critical to mitigating incidents.
A Change Event is any change to your system, such as a deployment to an environment or turning on a feature flag. Change Events are usually created by an integration (or a bot). However, you can also create them manually from the FireHydrant UI.
Adding a Change Event
To add a change event:
In the left nav, click Infrastructure > Change events, then click +Create event.
On this page, provide of information related to the change event. A summary of the event and details about when it occurred are required; all other details are optional.
- Description is a markdown-enabled field that appears when a change event is shown on a page in FireHydrant (such as on the main page of an incident).
- Labels allow you to add key/value pairs that make it easier to filter and find change events. Labels are string to string pairs.
- Time Range allows you to set either a point in time or range of time. This is valuable if you're making an immediate change (such as changing a feature flag from off to on) as opposed to a change associated with a longer duration (such as a rolling update to a set of servers).
- Environments are all of the development spaces that the change event can impact. You can specify multiple environments (or none).
- Services are all services relating to this change event. You can specify multiple services (or none).
After entering all of the relevant information, click Submit to create the change event.