mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-10-03 23:14:02 -07:00
4ca4d36ae6
If you look at the meaning of the different syslog levels, NOTICE means that the event may need someone to look at it. Whereas INFO is pure informational. Since module invocations are in fact requested (deliberate) actions, they shouldn't need any additional post-processing, and therefore should not be logged as NOTICE. This may seem like hairsplitting, but correctly categorizing system events helps weeding through the noise downhill. According to Wikipedia: https://en.wikipedia.org/wiki/Syslog 5 Notice notice Events that are unusual but not error conditions . 6 Informational info Normal operational messages -no action required. Example an application has started, paused or ended successfully. |
||
|---|---|---|
| .. | ||
| cli | ||
| compat | ||
| config | ||
| errors | ||
| executor | ||
| galaxy | ||
| inventory | ||
| module_utils | ||
| modules | ||
| new_inventory | ||
| parsing | ||
| playbook | ||
| plugins | ||
| template | ||
| utils | ||
| vars | ||
| __init__.py | ||
| constants.py | ||
| test-requirements.txt | ||