Currenty non-security updates are marked as 'INFO', while drupal core marks them as REQUIREMENT_WARNING. So to be consistent with core, it would seem logical to mark the sensor result as warning too. Patch incoming.
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | monitoring_module_update_sensor_as_warning-3107066-14.patch | 2.62 KB | jonasanne |
| #11 | monitoring_module_update_sensor_as_warning-3107066-11.patch | 2.49 KB | jonasanne |
Issue fork monitoring-3107066
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
jelle_sComment #3
jelle_sAlternatively, we could make the mapping of the
REQUIREMENT_*constants toSensorResultInterface::STATUS_*configurable on the sensor, but I'm not sure if that is desired?Comment #4
berdirI'd prefer to keep them as info because I don't really consider it a warning that we need to see in our monitoring infrastructure. So it would need to be configurable then..
Comment #5
berdirThat said, a single checkbox as setting for this specific case might be enough and we don't need full-blown status mapping UI.
Comment #6
jelle_sNew patch attached.
Comment #7
jelle_sOops, IDE was a bit enthusiastic adding a method return type.
Comment #8
berdirWe need to document this setting in the config schema in monitoring.schema.yml. Also now that we have this UI, we need to make sure that we don't break the type configuration setting which is currently there as a non-configurable setting.
Comment #11
jonasanne commentedI converted Jelle his changes into a MR and added the change in monitoring.schema.yml.
Also uploaded the diff of the MR as patch here.
Comment #12
jonasanne commentedComment #13
jonasanne commentedDoes anything needs to be done for this ticket?
Comment #14
jonasanne commentedRebase MR & added diff to use as patch