Linking FireHydrant as a source
This source is currently in alpha. The interface and available tables may change.
The FireHydrant connector syncs your incident management data into the PostHog Data warehouse, so you can analyze your incidents and response workflows alongside your product data.
Prerequisites
You need a FireHydrant account with permission to create an API key. Bot tokens are recommended for automation that isn't tied to a specific user.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking FireHydrant, you'll need:
- API key – create a bot token or personal API key in your FireHydrant API keys settings.
- Region – pick the region your FireHydrant account is hosted in, either US (
api.firehydrant.io) or EU (api.eu.firehydrant.io).
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
This source is full-refresh only. FireHydrant has no uniform server-side incremental cursor, so every table is fully re-synced on each run.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
incidents | Incidents declared in FireHydrant, including their lifecycle, severity, impact, and assignments. | Full refresh | — | id |
alerts | Alerts ingested by FireHydrant, including Signals alerts and third-party alerts. | Full refresh | — | id |
changes | Changes tracked in FireHydrant that may be correlated with incidents. | Full refresh | — | id |
change_events | Discrete change events (e.g. deploys) recorded in FireHydrant. | Full refresh | — | id |
environments | Environments (e.g. production, staging) defined in your FireHydrant catalog. | Full refresh | — | id |
functionalities | Functionalities (capabilities your product provides) defined in your FireHydrant catalog. | Full refresh | — | id |
services | Services in your FireHydrant service catalog. | Full refresh | — | id |
teams | Teams configured in FireHydrant. | Full refresh | — | id |
users | Users in your FireHydrant organization. | Full refresh | — | id |
incident_roles | Incident roles (e.g. Incident Commander) defined in FireHydrant. | Full refresh | — | id |
incident_types | Incident types that pre-fill incident attributes when declared. | Full refresh | — | id |
incident_tags | Tags that can be applied to incidents. | Full refresh | — | name |
priorities | Incident priorities (e.g. P1, P2) defined in FireHydrant. | Full refresh | — | slug |
severities | Incident severities defined in FireHydrant. | Full refresh | — | slug |
custom_field_definitions | Definitions of the custom fields available on incidents. | Full refresh | — | field_id |
integrations | Integrations connected to your FireHydrant organization. | Full refresh | — | id |
runbooks | Runbooks that automate incident response steps. | Full refresh | — | id |
runbook_executions | Executions of runbooks against incidents. | Full refresh | — | id |
webhooks | Webhooks configured to receive FireHydrant events. | Full refresh | — | id |
signals_on_call | FireHydrant Signals on-call schedules across the organization. | Full refresh | — | id |
post_mortem_reports | Retrospective (post-mortem) reports generated for incidents. | Full refresh | — | id |
scheduled_maintenances | Scheduled maintenance windows tracked in FireHydrant. | Full refresh | — | id |
task_lists | Reusable task lists that can be attached to incidents. | Full refresh | — | id |
checklist_templates | Checklist templates used during incident response. | Full refresh | — | id |
Troubleshooting
- If you see an authentication error, your API key is invalid or has been revoked. Create a new API key in your FireHydrant settings, then reconnect.
- If you see a permissions error, the key is missing the permissions needed to sync this data. Grant the required permissions in your FireHydrant settings, then reconnect.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.