mnagel
6 years agoProfessor
SDT "groups"
We have clients who have planned maintenance on specific locations requiring SDT. This should be easy, but in fact is not at all easy and in fact is very error prone due to the level of manual eff...
3 minutes ago, JSmith said:A couple of thoughts that may help.... Have you tried utilizing device properties to create dynamic groups? Ex. In our MSP model we have different clients assigned to resource groups, within their resource groups we make properties for location, type, etc. Then we also set a 'level property'. This would allow us to create a dynamic group with a query like join(system.staticgroups,",") =~ "ClientGroup1/ClientGroup2" && hasCategory("MicrosoftDomainController") || priority.level =~ "P1"
Have you also tried the mapping process and using the alert roll up? We cannot find a use case to work for us (yet) but, it seems like it may be good here.
We use groups extensively to manage resource downtime (I have a different F/R in regarding that as we cannot simultaneously grant access to the group for contents management without also exposing the group itself to damage). The problem here is cross-type SDT. Consider that a site outage may involve resources down, cross-site website checks down and collectors down, perhaps others. We need to in one fell swoop be able to mark all related elements in SDT without having to track them down through all the dark corners of the UI. As someone noted, this could be handled by an API script, but that is not something we can easily provide to clients.