influxdata / influxdata/kapacitor
HipChat config test resulting in 405 error causes Kapacitor to keep firing an error
Open
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Contributor guide
Research direction
The issue provides only a GIF showing a 405 response during a HipChat configuration test. Start by locating Kapacitor's HipChat configuration-test entry point and reproduce the request to identify why the error keeps firing. Done means the configuration test handles the 405 appropriately and Kapacitor no longer repeatedly reports the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100