That’s genius - though I do have one small issue trying to sort out
Created the watch – it works - called it NewEventModel
Created the GC – called it NewEventGC – it works – Real Time update looking for Event Models that have a NewEventModel value less than 300
Applied a policy which sets the model in the Global Collection into maint mode – that works too
So when a new model is created it goes straight into that GC and enters maint mode
Additionally I have a GC which just stores all event models in maint mode (kind of double checker) – called ADMIN-MAINT – again real time – event models in maint only
The issue is – I need models to be automatically removed from NewEventGC after the 300 seconds
The only time it removes them is when the GC rule realizes the time has been exceeded – but that’s not happening automatically
So if I check a model and go to its attribute tab, and have NewEventModel as the attribute shown, the GC rule kicks in and removes it from NewEventGC
I assume that this is because the Watch was on demand
So to test this I created a second watch – this time using a polling interval
The behavior is the same using a polling interval or a evaluate on demand
The issue I have is I need to have an easy mechanism for operators to remove the models created from Maint Mode – at present they can’t as the Maint mode is set by a Policy based on GC membership
I had though about creating another GC to remove maint mode but then I go down a rabbit hole of needing to make sure devices that had intentionally been added to maint mode aren’t impacts
Thoughts anyone?