feature/sensor-to-check-if-api-is-down #24
Conversation
merge updates from forked
sensors/solarwinds_api_check.py
Outdated
| self._logger.debug("SolarWinds API query successful") | ||
| self._logger.debug(orion_data) | ||
| except ConnectionError: | ||
| self._logger.debug('Dispatch SolarWinds services restart trigger') |
There was a problem hiding this comment.
Would not not be a good idea to add a way of disabling these restarts? What if this triggered while you were doing an upgrade?
There was a problem hiding this comment.
I renamed the trigger to solarwinds_api_down because this doesn't restart anything until a rule is made to map the trigger to an action and it can be disabled in that rule.
sensors/solarwinds_api_check.yaml
Outdated
| class_name: "SolarwindsApiCheck" | ||
| entry_point: "solarwinds_api_check.py" | ||
| description: "Verify that the SolarWinds API is up and accepting connections." | ||
| poll_interval: 30 |
There was a problem hiding this comment.
Let's increase this to 60 seconds please.
sensors/solarwinds_api_check.yaml
Outdated
| class_name: "SolarwindsApiCheck" | ||
| entry_point: "solarwinds_api_check.py" | ||
| description: "Verify that the SolarWinds API is up and accepting connections." | ||
| poll_interval: 60 |
There was a problem hiding this comment.
@jschoewe can you increase this polling interval to a higher-value, maybe 15 minutes?
|
@jschoewe it looks like there is a mistral workflow that is hanging out in this pack that is breaking testing, can you please convert it to Orquesta using |
|
|
4 participants
Added sensor to check if the orion API is down and fire a trigger if it is