influxdata / influxdata/kapacitor
Feature request: Allow customizing priority for opsgenie alerts
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Currently (kapacitor 1.5) when using opsGenie2 node critical alerts go out with priority P1. This might be an overkill and we are currently overriding this on the opsgenie level, but it would be nice to be able to do that directly from kapacitor.
Just an ability to specify the priority inside an alert:
|alert()
.crit(lambda: TRUE)
.priority('P2')
.opsGenie2()```
Also, it would be good to allow a default value for this in the opsgenie2 settings section in the config.Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the OpsGenie2 node entry point and its settings section in the Kapacitor codebase, then inspect how alert priorities are currently assigned. Confirm the expected behavior from the issue: an alert-level priority such as P2 should be supported, with a configurable default in the OpsGenie2 settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100