OpsGenie

TraceStax integrates with OpsGenie using its Alerts API. When a TraceStax alert fires, an OpsGenie alert is created and routed through your OpsGenie team’s notification rules and escalation policies. When the alert resolves, the OpsGenie alert is closed automatically.

---

Setup

1. Create an API integration in OpsGenie

   In OpsGenie, go to Settings → Integrations → Add integration → search for API → select it.

   Give the integration a name (e.g. “TraceStax”) and assign it to the team that should receive alerts. Click Save Integration.

2. Copy the API Key

   After saving, OpsGenie shows the integration’s API Key — a UUID that looks like:

   xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

   Copy it.

3. Note your region

   OpsGenie has two API regions:

   • US — api.opsgenie.com (default for most accounts)
   • EU — api.eu.opsgenie.com (if your account was created in the EU)

   Check your OpsGenie account URL or settings page to confirm which region you’re on.

4. Add the credentials in TraceStax

   In the TraceStax dashboard, go to your project → Integrations → OpsGenie → enter the API Key and select your region → Save.

Note

The integration-level API key scopes the alerts to a specific team in OpsGenie. If you want alerts to route to multiple teams, create a separate integration per team and add each one in TraceStax.

---

What triggers an OpsGenie alert

Any alert policy that fires creates an OpsGenie alert with:

• Message — the TraceStax alert title
• Priority — mapped from alert severity (critical → P1, warning → P2, info → P3)
• Alias — the TraceStax alert ID (used for deduplication and auto-close)
• Details — project name, affected entity, alert type

When the alert condition clears, TraceStax sends a close request using the alias. OpsGenie closes the alert automatically.

---

Troubleshooting

Alerts not appearing in OpsGenie

• Verify the API Key is exactly as copied (no extra spaces or line breaks).
• Confirm the correct region is selected — using the wrong region causes all requests to fail silently.
• Check that the OpsGenie integration is enabled (not paused).

Alerts not closing automatically

• Auto-close relies on the alert alias matching. If you’ve manually changed alert aliases in OpsGenie, this may break. Use the default OpsGenie configuration.