Forum Discussion

mnagel's avatar
mnagel
Icon for Professor rankProfessor
8 years ago

add "required datasource" capability

I am not quite sure how to express this in the UI, but there needs to be a way to indicate that for certain device types, a minimum set of datasources are required to be associated.  We just had a case where the WinExchangeMBGeneral datasource (32 datapoints, some critical) just didn't get associated and we only found out after a major event.  The active discovery stuff is very nice, but it is a "fail open" sort of thing where if AD does not successfully operate, you just have no way to know without heavy investigation.  My idea is that once a device has been identified as a particular type (like Exchange server), there are a set of datasources that must be discovered and failure to do so is called out as an alert condition.  At this point, you end up relying largely on luck to figure out whether this problem has happened.

 

datasource

1 Reply

Sort By
Replies have been turned off for this discussion
  • SchuylerC's avatar
    SchuylerC
    8 years ago

    I'd like to see something like this to. Which datapoints alert on no data is pretty hit and miss and I beleive only WMI alerts when the creds are wrong. Can be hard to figure out if you are polling everything needed. We've done a workaround before by editing the applies to field of a datasource to point to a group where we know the datasource should be applied and then alerting if no data. Although this may not work if AD fails to find any instances as is what looks like happend here.