5.2.3.2. Automated Troubleshooting

In this section we can find automated checks that allow us to know the state in which an environment is and to be able to identify the errors it contains.

We also have the option, by activating a flag, to be able to automatically fix all possible errors.

Important

Before executing the checks it is necessary to configure the inventory.yml and the ansible.cfg.

These automated checks can be find in the all_checks.yml file of the following path:

cd /usr/share/opennac/ansible/

By executing the following command without tags, it returns a full json with all the information.

ansible-playbook -i inventory all_checks.yml

By executing the aforementioned playbook with tags, it returns a json with the information corresponding to the tag.

Here is the index with the different available checks and tags:

• 5.2.3.2.1. Iptables checks
  • 5.2.3.2.1.1. Checks
  • 5.2.3.2.1.2. Tags
  • 5.2.3.2.1.3. Data Structure
  • 5.2.3.2.1.4. Example
• 5.2.3.2.2. Healthcheck checks
  • 5.2.3.2.2.1. Checks
  • 5.2.3.2.2.2. Tags
  • 5.2.3.2.2.3. Data Structure
  • 5.2.3.2.2.4. Example
• 5.2.3.2.3. Redis checks
  • 5.2.3.2.3.1. Checks
  • 5.2.3.2.3.2. Tags
  • 5.2.3.2.3.3. Data Structure
  • 5.2.3.2.3.4. Example
• 5.2.3.2.4. ELK checks
  • 5.2.3.2.4.1. Checks
  • 5.2.3.2.4.2. Tags
  • 5.2.3.2.4.3. Data Structure
  • 5.2.3.2.4.4. Example
• 5.2.3.2.5. Proxy Radius checks
  • 5.2.3.2.5.1. Checks
  • 5.2.3.2.5.2. Tags
  • 5.2.3.2.5.3. Data Structure
  • 5.2.3.2.5.4. Example
• 5.2.3.2.6. Trending checks
  • 5.2.3.2.6.1. Checks
  • 5.2.3.2.6.2. Tags
  • 5.2.3.2.6.3. Data Structure
  • 5.2.3.2.6.4. Example
• 5.2.3.2.7. VPNGW checks
  • 5.2.3.2.7.1. Checks
  • 5.2.3.2.7.2. Tags
  • 5.2.3.2.7.3. Data Structure
  • 5.2.3.2.7.4. Example