influxdata / influxdata/kapacitor
Celery alert output
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
I was wondering if you would be open to accepting a PR that adds a new Alert output node which adds a task to the task queue of Celery, with the alert data as the argument. In our infrastructure, we have Kapacitor POST to a HTTP endpoint which fires the appriate celery tasks, and it would make our setup a bit simpler if we could just skip the POST and go directly to the Celery tasks queue.
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
The issue names no files, tests, or entry points. Start by locating existing alert output nodes and their tests, then determine how an output can enqueue alert data in Celery; done means a documented Celery output node with coverage for the queued alert argument.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100