Hey Bryan, I'm surprised this thread hasn't attracted more discussion and interest. Do you still consider this to be in beta? I think it's a cool idea for my simple use-case--I want to be warned if I have any Error-level messages in any log across my hubs. Guess I'm lazy--I don't want to have to remember to go check the logs occasionally. I'd rather the Hubitat alert me if there's something that needs my attention.
So I set up my hubs on Log Watchdog yesterday. I configured the keyset with the option to watch for logging level = "Error", and then added no other secondary or tertiary checks. I filled out the rest of the form and the log status indicated "Connected". As soon as I hit done, however, the log was flooded with the below error message every few milliseconds. Even when I deleted the app, the error kept coming. Only when I deleted the child and parent apps, and then rebooted the hub did things seem to return to normal. Wonder what I did wrong....is a secondary check a required element of a keyset?
Also -- curious to better understand what the "Log Watchdog Event" child is for? Couldn't find any clues in the community or on your github. When I click on it, I get an Error 404.
As always, so appreciate what you do......
dev:10132020-06-23 06:34:09.271 pm errorjava.lang.NullPointerException: Cannot invoke method collectEntries() on null object on line 174 (parse)