Feature #23180
submission_agent should alarm when it receives repeated errors
Start date:
08/28/2019
Due date:
% Done:
0%
Estimated time:
Scope:
Internal
Experiment:
-
Stakeholders:
Description
Last week when they upgraded landscape, we started getting errors because we were specifying from: and not to: for the time range; previously to: defaulted to "now"... so all of our time-window requests for lens data were returning errors, and we weren't seeing any new jobs.
We should watch for continuous errors, and alarm -- vie email? ticket?
Also, where we alarm should be in a config file, and while we're at that, we should move other items into the config file:
- alarm destinations
- lens server
- poms server
- lens query string templates
- sleep time/poll rate