prometheus / prometheus/alertmanager
Jira Integration reaching Rate Limits of Atlassian Cloud
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
What did you do?
Atlassian Cloud enforces different kinds of rate limits, see documentation here.
While Alertmanager has a potential back off mechanism implemented
https://github.com/prometheus/alertmanager/blob/main/notify/notify.go#L895
This seems not to be good enough for Jira Cloud as we´re running constantly in 429 errors.
What did you expect to see?
respect the Retry-After header
log the RateLimit-Reason in debug log
when X-RateLimit-NearLimit is activated focus on only creating new issues not updating existing ones
What did you see instead? Under which circumstances?
HTTP 429 errors
System information
No response
Alertmanager version
Alertmanager configuration file
Prometheus version
Prometheus configuration file
Logs
Contributor guide
No contributing guide indexed for this repository
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
Start in notify/notify.go around the linked backoff mechanism and review Atlassian Cloud's rate-limiting documentation. Trace the Jira notifier's handling of HTTP 429 responses and identify where Retry-After, RateLimit-Reason, and X-RateLimit-NearLimit can be handled. Done means these three requested behaviors are implemented and covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100