Structure¶
The checkup module can be used standalone through CLI or using the Alinex Server. The latter one allows to also support any monitoring system, server deploy and startup script to run a checkup or use the scheduler.
Note
The grey arrows shows planned extensions which are not yet implemented.
Some functionality is only usable if used in a server like scheduler and cache.
What exactly to do is completely configured using a easy structured config files:
- one for the cli system setup (if server is used this is within the server)
- one with all the possible cases
Suite and Runner¶
The suite stores the configuration and keeps an cache to run the same test only once a time and not directly again.
Tests¶
The Tests will be:
- defined in case
- generated by dynamic groups
- hidden tests from fix
Except the last type all tests will store their result to be output by runner.
Attention
Some tests may contain values based on changes over time. These are only calculated while using the scheduler from the second call on. Checks based on this values will also only be taken into account then.
Fixes¶
The fixes sometimes has two parts. At first an analyzation method will further investigate, collect information and present the interpreted results. If autofix
is enabled, it will also try to repair.
Sub Tests¶
If a fix needs to further analyze or track down the problem it may be done with the use of other tests. The logs will be automatically added but how far the results are included depends on the implementation. The sub tests won't be displayed within the test list.