The third filter DOES NOT match entries in the asset database where "pollercategory" is still NULL. It does find entries that are set to "0", or any other vaule that is not "1", or "2", but newly discovered hosts, with a NULL entry remain unpolled.
Environment
Operating System: Linux
Platform: PC
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Ronny Trommer July 9, 2015 at 7:37 PM
Too old, reopen if this issue still exist.
Benjamin Reed October 6, 2008 at 11:52 AM
moving to 1.6.1 target milestone; only things left pending for 1.6.0 are blocker-level bugs
Ray Frush February 27, 2006 at 5:56 PM
OH... Verified to still be a problem in 1.2.7 (debian).
I have three Packages in poller-configuration.xml, and each package as a
filter:
<filter>pollerCategory == 2</filter>
<filter>pollerCategory == 1</filter>
<filter>(pollerCategory != 1) & (pollerCategory != 2)</filter>
The third filter DOES NOT match entries in the asset database where
"pollercategory" is still NULL. It does find entries that are set to
"0", or any other vaule that is not "1", or "2", but newly discovered
hosts, with a NULL entry remain unpolled.