Configuration

The tools are the foundation of Leankoala. Their behaviour is well matched with the needs of the most websites. Nevertheless, every administrator is able to fine tune the settings.

Overwriting the default configuration for the Leankoala tools is very easy. Just click on the switch button and turn overwrite "on". Afterwards, it is possible to overwrite the main attributes. 

Every tool has an unique identifier that cannot be changed. Sometimes one tool is separated into many identifiers so they can configured more precise.

The name and the description of a tool only have informative value. The name is used on the status dashboard after every event identifier. 

When changing the name of a tool the connected tests have to be run again to see the effect. Normally the name will change within the next hour.

Leankoala knows three severities low, medium and high. Severities are used ordering the incidents on the status dashboard and to configure the alerting.

The "in a row" option is used to create more stable checks. The default behaviour of a check is that it creates an incident if it fails once. This can create a flickering situation in Leankoala that triggers more alerts than needed. The "Performance (load)" tool is a good example. Sometimes third party components or other integrations can be slow and trigger from time to time high times to load. But if this only occurs once a day it is not worth an alert. 

To reduce the number of unimportant incidents Leankoala is able to set the errors in a row option individually for every project. This applies to failures and successes. 

If the "errors in a row" option is for example set to "2" a check must fail twice before it creates an incident. 

Besides this feature, there are other options to handle flaky checks .