Cortex

Installing the Cortex integration into FireHydrant streamlines service management and incident response for organizations with complex microservice architectures. By synchronizing service and team information from Cortex to FireHydrant, teams can leverage Cortex's comprehensive service catalog while managing incidents and tracking service health within FireHydrant. This integration ensures that service ownership, team structures, and other critical metadata are consistently maintained across both platforms.

This guide outlines the process of integrating Cortex with FireHydrant, allowing you to synchronize team and service information between the two platforms.

Prerequisites

• An active Cortex account with teams and services configured
• You will need Owner permissions to configure integrations on FireHydrant

Installing the Cortex integration

Generate Cortex API Key

1. Log in to your Cortex account
2. Navigate to Settings
3. Click on the "API keys" button
4. Generate a new API key with "Viewer" role permissions

📘

Note:

It's recommended to use only Viewer permissions for security purposes

Configure FireHydrant

1. Log in to your FireHydrant account
2. Navigate to the integrations or settings section
3. Locate the Cortex integration configuration
4. Input the Cortex API key that you previously generated
5. If you're using an on-premises version of Cortex:
   • Add the appropriate endpoint in the designated field
   • For cloud-based Cortex users, leave the endpoint field blank
6. Save your changes

Synchronization Process

After saving the configuration:

1. FireHydrant will automatically initiate a synchronization job
2. This job will import your Cortex teams and their associated services into FireHydrant
3. Subsequent updates in Cortex are synchronized with FireHydrant every hour

What Gets Synchronized

• Teams from Cortex
• Services owned by each team
• Team members (limited to those with FireHydrant accounts)

Troubleshooting

If you encounter issues with the integration:

1. Verify that the API key has been entered correctly
2. Ensure the API key has at least Viewer permissions in Cortex
3. For on-premises Cortex users, double-check the endpoint URL