How to handle relevance for probes

[strawgate]

Not sure how to handle relevance for probes.

I'm inclined to have it so that they either only apply if the age of the last report > up time of Operating System (once per reboot) or if the old report is at least 15 minutes old.

Currently there is a mix of treating them like tasks and using timing relevance (last report is > 15 minutes or > up time old).

I want to give an administrator the freedom to apply as often as they want but I dont want anybody to shoot themselves in the foot with consistent reapplication.

[strawgate]

@jgstew Thoughts?

[jgstew]

so I assume this is for tasks that run periodically to collect data for analyses?

I tend to try to come up with what I think is a sane minimum and have the relevance check that the last time the results were generated were > that minimum ago. In rare cases I may tie something to uptime, but not often.

This one I am effectively tying to uptime because I'm putting it into a folder that gets cleared out after every reboot automatically: https://www.bigfix.me/fixlet/details/20446

If I had an actual use case for that, then I would set a minimum period in addition to the checking for the folder existing.

[jgstew]

I could see wanting to generate data based upon a combination of uptime and minimum period.

I hadn't considered that some of the things I may use that dump out data at most once every 12 hours could do it based upon that or uptime.