Closed (fixed)
Project:
Monitoring
Version:
8.x-1.x-dev
Component:
Sensors
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
6 Jan 2015 at 13:08 UTC
Updated:
4 Feb 2015 at 11:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
miro_dietikerPushed the test dependency to make sure this can run.
Still needs past to move to d.o. from github.
Comment #3
miro_dietikerImproving title, similar to other "New sensor" tasks.
Comment #4
Anushka-mp commentedUploading the config files created for monitor each severity for a review.
Comment #6
berdirHm, what about moving this to past like we did with simplenews?
The sensors are missing the right dependencies.
HEAD is broken, deleteTags() => invalidateTags().
We used to create this in code, just like dblog, not sure if we should still do that, but we should at least remove the hook now.
Comment #7
miro_dietikerI do like to add this in monitoring for now as long as we are refactoring monitoring... Less fragmentation with updates.
We can move before release into contribs. :-)
And yes, in monitoring.sensors.inc there's outdated code to drop with this patch.
Unsure about these two as they would be very critical and we should monitor them... but i guess core does not log on these levels ever.
We might want to add this to the description of the sensor...
I guess i would drop "occurred". I would prefer
Severity Alert
or Alert events.
Past event alerts occurred, unused severity by Drupal 8 core.
ocurred => occurred... and all others, too.
Comment #8
berdirAll past sensors were enabled by default in 7.x. We used value label "Events" there, label was just "Severity: @severity". Just like dblog.
We also had default thresholds for critical, which is what is used by default for fatal errors.
Comment #9
Anushka-mp commentedMade some changes as suggested.
module dependency added and alert sensor dropped along with outdated code in monitoring.sensors.inc
Comment #10
Anushka-mp commentedComment #13
miro_dietikerShould we ship with a zero tolerance threshold for critical and errors?
Also, yes, i almost started to do the final fixing and commit... and then again realised that there are no tests yet.
Back to work, looking forward to the next update. ;-)
Comment #14
Anushka-mp commentedAnd here are the tests. awaiting feedback :-)
Comment #15
Anushka-mp commentedComment #16
berdirNo longer needed, use @group instead as with others.
Comment all this so that you will still understand it if you look at it in two months. Explain why we are calling those functions.
missing docblock.
too many newlines here, and missing docs.
Comment #21
berdirProbably needs a commit and then a new dev build before the dependency will show up.
Another thing, needs a @requires module, like other integration tests.
Comment #22
Anushka-mp commentedChanges made according to Berdir's review.
Comment #23
Anushka-mp commented@requires past_db added.
Comment #27
miro_dietikerI fixed past fatal errors. Removed modules.
There is still work about broken HEAD:
#2404413: Fix tests / broken HEAD
Still retesting to see if it already can resolve and it passes.
Comment #29
berdir;)
No commit, no dev snapshot rebuild.
Comment #30
miro_dietikersensors.
Why not just do $severities_count amount logs? Creating 99 records eats up a lot (wasted) resources which is more waiting time for all future test runs.
And the tests are still failing. Past is now on d.o. so this should work.
Comment #31
Anushka-mp commentedstrange, local tests are all green. I'll give it another try.
Comment #34
berdirWhy does everyone ignore me :p
Comment #36
Anushka-mp commentedOkay, I have mistakenly uploaded the interdiff as a patch here :P
and also I see the 'real' patch passes the tests!
Comment #37
Anushka-mp commentedComment #38
miro_dietikerAgain a final space to fix on commit. :-)
Comment #40
berdirCommitted with some test cleanup.