influxdata / influxdata/kapacitor
Testing pagerduty service not returning all errors
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
I was trying to test pagerduty and was using the wrong api key. The problem is that Kapacitor cut off the actual error message returned from PagerDuty so i had no idea what was wrong.
Testing on pagerduty returns:
```
{
"status": "invalid event",
"message": "Event object is invalid",
"errors": [
"Service key is the wrong length (should be 32 characters)"
]
}
```
but testing through Kapacitor only returns:
```
{
"success": false,
"message": "Event object is invalid"
}
```
Contributor guide
Research direction
Start by reproducing the PagerDuty test with an incorrectly sized service key and compare the direct PagerDuty response with Kapacitor's response. Trace the PagerDuty testing entry point and its error-response handling; done means the returned response preserves the PagerDuty errors array as well as the existing message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100