Don't save results for 'Do not monitor' artifacts
We have quite a lot of servers, and thus quite a few artifacts we monitor. However, we have way more artifacts (NTServices, SQL jobs, etc.) that we do not monitor. But I notice these artifacts still add rows to the table b360alertMonitor_LogStateCheck (with ExpectedState 2). This gives us a lot of useless rows in this table for things we don't want to monitor anyway. Is there a way to turn this off? We now have 17 million rows in this table, and we only keep this data for a week (the cleanup job works fine).
I can write a job myself to delete these rows with ExpectedState 2 at a higher frequency than 7 days (more like every hour), but I was hoping there was an option to actually indeed 'do not monitor' them at all
By Marc van de Klashorst
New State called 'UnMapped' is introduced to maintain the artifacts which are not mapped for monitoring. Now the entries are not updated in the LogStateCheck table.