Importing from external providers

This article covers importing catalog items from external providers as net new entries in FireHydrant's Catalog. If you already have FireHydrant services, functionalities, or environments, and wish to link them to external providers, see instead Linking to external services.

Depending on what category the provider falls in, it enables a number of different capabilities.

• For alerting providers like Opsgenie, PagerDuty, and Splunk On-Call:
  • Importing will create entries in FireHydrant's Catalog for each external service/routing key imported, as well as automatically link the external service to the FireHydrant service.
  • This then enables capabilities like seeing who's on-call and paging the service.
• For repository providers like GitHub:
  • Importing creates entries in FireHydrant's Catalog for each repository imported and links the repo to the service.
  • This enables the ingestion of Change Events, where any merges to the main branch of your repository register as change events, giving your responders a handy avenue to explore when an incident occurs for a service.
• For Atlassian Statuspage (Functionalities only):
  • Importing Statuspage components will create Functionality entries in FireHydrant's Catalog and links the Statuspage component to the FireHydrant Functionality.
  • This link enables automatically marking the right component impacted on the Statuspage if the linked Functionality is impacted in a FireHydrant incident and if the Statuspage incident is created.

Note: A FireHydrant service can have links to multiple types of external services (e.g. alerting and repository). To handle this, we recommend importing from only one of the types of providers, and then initiating outbound links for other providers.

Prerequisites

Ensure you've configured the integration for one of the following providers:

• Atlassian Opsgenie
• PagerDuty
• Splunk On-Call (VictorOps)
• GitHub

Importing Services

1. In the navigation, click on Catalog.
2. This should take you to the Services page of the Catalog. On the right side, click on the Add service dropdown and select Import from third party.
3. On this page, click the Import button next to your provider of choice.

4. Select whether you want to import all the services or if you'd like to pick and choose. If you selected Import all as new services then skip to step 7.

5. If you clicked Select services to import, FireHydrant will load all of the services it can read and display them in a list. Select the checkbox for each service you want to import. Then, using the dropdown menu, indicate whether you want to import each service as net new or link it to an existing service. For creating new, leave it as-is on Create New.

6. When you're done selecting, click Import X select services to initiate the importing and linking process.

7. Once the import is finished, you should be taken to a summary page showing the new services you've created/imported as well as the link to the external service from which it was imported.

Importing Functionalities

On top of the alerting and repository providers for Services, Functionalities also have Statuspage components to choose from. The steps are the same as for importing Services above, but instead choose Statuspage as the provider.

Importing Environments

As of today, FireHydrant only supports importing PagerDuty services as FireHydrant environments. The steps are the same as above for importing Services.

Next Steps

Now that you've read about importing and linking services from external tools:

• See how you can look up and page whoever's on call for a Service or Functionality.
• Read some more about Change Events and how they can potentially speed up identifying problematic recent changes.
• Learn more about FireHydrant's Atlassian Statuspage integration for posting updates to external end users.