FireHydrant comes with a simple but powerful Changelog that you can send changes to via the API or UI. These changes attach to environments and components and offer a quick way of getting to the root cause of incidents. Most incidents occur due to change, so keeping it all in one place makes FireHydrant a great candidate for this.
FireHydrant can keep track of several fields on changes, for example:
- Change Type (Added, Upgraded, Removed, etc)
- Time of Occurrence
- Relevant Environment and Components
- Labels (key / value)
- Links (Github PR, Spinnaker Pipeline, etc)
By keeping all of these in one record in the change log, FireHydrant can quickly allow you to find relevant changes when you need them. If an incident occurs due to a piece of bad code being shipped, check the changelog first.
Adding a Change Entry
Viewing Change Entries
The FireHydrant UI allows you to list and find change entries by visiting https://firehydrant.io/changes. This page also allows you to quickly filter change type, environments, and components.