Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-level OpsGenie API Key Override #876

Open
osnatashush opened this issue Oct 8, 2024 · 0 comments
Open

Multi-level OpsGenie API Key Override #876

osnatashush opened this issue Oct 8, 2024 · 0 comments

Comments

@osnatashush
Copy link

Describe the feature request

I would like to request an enhancement to the OpsGenie integration in Gatus that allows for more granular control over which API key is used for different alerts.
Specifically, the ability to override the OpsGenie API key at the group level and the individual alert level.

Proposed Feature:
Implement a hierarchical override system for OpsGenie API keys:

Proposed Configuration Structure:

alerting:
opsgenie:
api-key: ${DEFAULT_OPSGENIE_API_KEY}
priority: P3
overrides:
- group: groupA
api-key: ${GROUP_A_OPSGENIE_API_KEY}
- group: groupB
api-key: ${GROUP_B_OPSGENIE_API_KEY}

endpoints:

  • name: example-endpoint
    group: groupA
    alerts:
    • type: opsgenie
      description: "This alert uses a specific API key"

Why do you personally want this feature to be implemented?

No response

How long have you been using this project?

6 months

Additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant