Exporting Data
FireHydrant has multiple ways to export data from its platform.
API
FireHydrant approaches all development API-first. For the vast majority of functions and capabilities in the FireHydrant platform, a public-facing API endpoint is available for customers to programmatically access.
To access the API, visit the API documentation here. There will be example API calls on the site for each endpoint.
Webpages
Analytics
Individual graphs and tables within the Analytics pages provide a button to Download CSV. This allows users to filter the data on the pages at the top and then export tables according to the visuals they're looking for.
Incidents
The Incidents page allows filtering the list of incidents and exporting that list to CSV file. Clicking "Export to CSV" will trigger an asynchronous background job to generate the data. Once finished, you will receive an email with a link to access the generated CSV.
The list of columns that will be included on the Incidents page export are as follows:
Field Name | Description | Docs Link |
---|---|---|
number | FireHydrant-assigned number. Counts incrementally up from 1 from the start of the organization's incident history on FireHydrant. This number is not editable. | N/A |
environments | List of comma-delimited Environments impacted on the incident | Intro to Service Catalog |
functionalities | List of comma-delimited Functionalities impacted on the incident | Intro to Service Catalog |
services | List of comma-delimited Services impacted on the incident | Intro to Service Catalog |
name | Name of the incident | N/A |
severity | The severity of the incident | Severities and Priorities |
priority | The priority of the incident | Severities and Priorities |
slack | The name of the Slack channel, if one was created for the incident | Create or rename Incident Slack channel |
tickets | Comma-delimited list of follow-ups created in the incident, listed via their ticket codes (e.g., ABC-123) | Managing Follow-Ups |
active_duration | Total duration of the incident listed in PT##S format where the number represents the total duration | Incident Milestones |
started_at detected_at acknowledged_at investigating_at identified_at mitigated_at resolved_at postmortem_started_at postmortem_completed_at | The exact timestamps of when the incident reached each milestone | Incident Milestones |
opened_at | The timestamp of when the incident was opened | N/A |
started_by | The person who create the incident in the format of Name (email) | Starting Incidents |
customer_impact_summary | The customer impact statement | The Command Center |
assigned_teams | Comma-delimited list of teams that were assigned to the incident if any | Team Management |
tags | Comma-delimited list of tags on the incident if they exist | Incident Tags |
(any custom fields) | Any custom fields defined by your organization | Incident Custom Fields |
Users
The Users page on FireHydrant shows a complete directory of all users in your organization. You can also filter the list of users according to what you're looking for before exporting everything to CSV.
Downloading the CSV will generate the CSV in the browser and open a download modal for you to choose a location to save the file. The downloaded CSV will include:
Field | Description |
---|---|
id | The UUID assigned by FireHydrant to the user |
name | User's full name |
User's email address | |
role | The access role the user has |
enabled | Whether the user is active ("TRUE") or disabled ("FALSE") |
slack_connected | Whether the user's FireHydrant account is linked with their Slack account |
alert_notification_methods | Which alerting methods the user has configured for Signals alerting. Values available are: email , slack , sms , voice , whatsapp , and push . |
Updated 4 months ago