Rudder

I would like to be able to search based on data that is not in LDAP currently, but known to rudder.
It could be stored back into LDAP, or the searches could include data that is not from the LDAP source.
All of this data can be quite safely cached

Directly of most interest

• nodes with no recent compliance data (no reports for 24h+, 7d+, no reports since archive_ttl)
• nodes with very low compliance
• nodes with no recent inventory (24h+, 7d+, no inventory since archive_ttl)

It would be very helpful in this if rudder could differentiate between "never before received a report from this node" and "not received a report since archive_ttl"
Right now, that information is never recorded and after archive ttl a node is said to have "never" sent something if it drops out too long.
Current behaviour is technically wrong with notable impact on operational safety.

Putting to @fanf42 for initial thoughts :-)

If there's a simple way to do this I'd propose it internally for sponsoring :-)