MattClausen,
Thanks for the idea. Unless I'm doing something wrong, that report looks to contain historical data as it reported on any device that was ever included in that GC. I've taken a different approach and decided to report on events, over a 24 hour cycle, against all models, containing event types 0x10222 (in maintenance mode), 0x10223 (out of maintenance mode), 0x10226 (in hibernation mode), and 0x10227 (out of hibernation mode). This has a added benefit of letting me know when and who put a model in maintenance mode.
Per pages 80-82 of the Report Manager Installation and Administration Guide, I copied event-filter.xsd from $SPECROOT/tomcat/webapps/spectrum/WEB-INF/repmgr/config/events/ to $SPECROOT/custom/repmgr/config/events/ and then created a simple .xml file w/ in the $SPECROOT/custom/repmgr/config/events/ directory (provided below) including those 4 event types.
event_maint_mode.xml
<?xml version="1.0" encoding="UTF-8" ?>
<!-- Filter that can be used to include/exclude Maintenance Mode events, which orginate as traps or are produced through trap handling. -->
<filter xmlns="http://www.aprisma.com"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.aprisma.com ./event-filter.xsd">
<!-- Device Model Put in Maintenance Mode Traps -->
<event_type>0x10222</event_type>
<!-- Device Model Taken Out of Maintenance Mode Traps -->
<event_type>0x10223</event_type>
<!-- Device Model Put in Hibernation Mode Traps -->
<event_type>0x10226</event_type>
<!-- Device Model Taken Out of Hibernation Mode Traps -->
<event_type>0x10227</event_type>
</filter>