prometheus / prometheus/alertmanager
amtool does not have a way to specify a time to test with.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
amtool config routes test does not have a way to specify a time to test with.
What did you do? Try to use amtool to validate alerting configuration based on time_intervals
What did you expect to see? Be able to do it
What did you see instead? Under which circumstances? No option to specify a time for validation
Environment N/A
-
System information: N/A
-
Alertmanager version: N/A
-
Prometheus version: N/A
-
Alertmanager configuration file: N/A
-
Prometheus configuration file: N/A
-
Logs: N/A
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 at the amtool config routes test command, which currently lacks an option for choosing the validation time. Trace how it evaluates time_intervals and define done as allowing a supplied time to be used when validating the alerting configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100