User story #7729
closed
User story #7686: Improve documentation organization and add missing sections
Add a section in administration about integration with other tools
Added by Alexis Mousset almost 9 years ago.
Updated almost 9 years ago.
Description
monitoring Rudder
document log files to check for errors
the format of non-compliance-reports.log
hexample of compliance API
give an example of logstash grok for non-compliance
rudder agent health on 3.3.
how to use the API to integrate with Rundeck, Ansible, etc.
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Pull Request set to https://github.com/Normation/rudder-doc/pull/151
- Is duplicate of Bug #6220: Document /var/log/rudder/compliance/non-compliant-reports.log added
- Status changed from Pending technical review to Rejected
- Status changed from Rejected to Pending technical review
- Assignee changed from Alexis Mousset to Jonathan CLARKE
- Status changed from Pending technical review to In progress
- Assignee changed from Jonathan CLARKE to Alexis Mousset
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Jonathan CLARKE
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.18, 3.0.13, 3.1.6 and 3.2.0 which were released today.
Also available in: Atom
PDF