Definite Scoring
Last updated
Last updated
Definite scoring only considers the unexpected events in v2 and does not compare . These events may or may not be present in the baseline. Definite scoring is simple and easy to interpret. Definite scoring works based on the following factors:
For every unexpected cluster that is in v2 and not in v1, the overall score is reduced.
For all unexpected clusters present in both v1 and v2, overall score is reduced only when the number of logs of that cluster are higher in v2.
There is no normalization, hence definite scoring may not work if the log file is too large.
Score Reduction is higher at higher sensitivity levels.
By default, definite scoring will give a score of 0 (fail) whenever there is a critical error.
Score Reduction is higher for clusters with higher criticality.
To set the Definite Scoring algorithm follow the steps below:
User can select the Definite Scoring algorithm while creating a Log Template for the verification gate. Users can set the Definite Scoring algorithm after creating a pipeline to the application.
To create an application, refer here.
To create a pipeline, refer here.
To know more about how to create a Log Template, refer here.
After creating a pipeline, go to Pipeline Builder page and select your pipeline and then click Add Stage.
Next, you get the option to select the type of stage. Select the Verification Gate from the drop down menu.
After selecting Verification gate, the following options appear and click "+" Symbol to create a log template:
The New Log Template form appears as shown below:
Select Definite Scoring from the drop-down while creating a new Log Template as shown below:
