It looks like for reference, one has to dig through the /var/log/vobd.log for the specific VOB to watch for. Such as:
2014-09-12T18:03:52.482Z: [APDCorrelator] 80896847968us: [vob.storage.apd.start] Device or filesystem with identifier [1b09c9f2-98386c11] has entered the All Paths Down state.
2014-09-12T18:03:52.482Z: [APDCorrelator] 80896848649us: [esx.problem.storage.apd.start] Device or filesystem with identifier [1b09c9f2-98386c11] has entered the All Paths Down state.
2014-09-12T18:04:04.506Z: [APDCorrelator] 80908872064us: [vob.storage.apd.start] Device or filesystem with identifier [b1d404c3-e892086b] has entered the All Paths Down state.
2014-09-12T18:04:04.506Z: [APDCorrelator] 80908872761us: [esx.problem.storage.apd.start] Device or filesystem with identifier [b1d404c3-e892086b] has entered the All Paths Down state.
Inside the brackets is the VOB entry to trigger on, which means jsut about anything could be made into an alarm, which is awesome!