OpsMx
Ask or search…
K
Links

Definite Scoring

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:
  • The overall score is reduced for every unexpected cluster in v2 and not in v1.
  • For all unexpected clusters present in both v1 and v2, the overall score is reduced only when the cluster logs 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:
Users can select the Definite Scoring algorithm while creating a "Log Template". Users can set the Definite Scoring algorithm after creating an application.
If you haven’t created an application already, click here.
To know more about how to create a Log Template, refer here.
  1. 1.
    From the application dashboard, click "Setup" and click “Analysis Templates” and then click "+New Template" button.
  2. 2.
    After clicking “+New Template” button, two options appear for you to choose the type of template you want to create. Select the “Log Template” from the available options as shown in the below image.
  3. 3.
    Click the Scoring Algorithm drop-down and select the Definite Scoring as shown in the image below: