Observe and alert on tests failing due to VSphere issues
Open
area/e2e
team/cli
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
Observe E2E test logs for errors which are diagnostic of issues connecting to the VSphere API --
503s
VSphere connection validation failures
Alerts which will cut tickets or slack messages to inform oncall that issues with the test environment (such as session limit) are present
Contributor guide
Research direction
Start by locating the E2E test logs and the checks for VSphere API connection failures, including 503 responses and validation failures. Define completion as detecting these test-environment problems and notifying on-call through tickets or Slack, including session-limit issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100