Add option to exclude hidden events

[AlanCoding]

Tested locally with the demo job template, and confirmed that the events produced reduces from 7 to 6, which removes the playbook_on_start event, as expected.

[matburt]

Do you think this is something that a lot of folks would use? I'd say the number of non-stdout producing events might be pretty low.

[AlanCoding]

I'd say the number of non-stdout producing events might be pretty low.

What evidence would it take for you to agree otherwise? In the demo playbook, there is 1 empty event, only because it targets no hosts. As the number of hosts / actual tasks increases, it limits to half of the events.

But that's not the reason for this - the reason for this is the problem you were trying to address. Run these scenarios:

ansible/ansible#68914

The point here is that the playbook is swamped by skipped events, which have ansible-runner associated events, but no output with these settings. Those events still get saved, and the ultimate reason that the user has no way out of the flood of events is because there is no way to turn off saving of these events.

That example still undersells the real motivation - which is a very large user who has decided that they only need the failed events reported. In that case, they want to silence the skipped, ok, and changed events, and they should reasonably expect congruence between how they do that with the ansible-playbook CLI and AWX. In these cases, there should be potentially millions of events with no output, and a handful of failed events.