Hi @Abbas_5 ,
1. I would recommend the following:
a. Look at the current failures being reported. Are these failures truly failures and if they are, the client should resolve these before the next job run. Repeat until the job is complete. The goal is to keep the CI failure count low.
b. If these failures are not actually failures, review the health rules for each metric. Revise them and wait until the next job execution. Repeat until the job is complete.
c. These are failures and the client does not want to take action until the job is complete. In this case, you can go to the settings page in Health Preference -> Health Metrics. In each metric in the drop down, there is a Max Failure threshold field. OOB, it is set to 50K. The client can choose to increase this, but keep in mind, it may make the job take longer. I do not recommend going above 500k failures for this reason, but the client can choose to do so if they wish. We are capping out the max failures in X release for performance reasons, so bear that in mind. I can send you the documentation when available.
2. Can you show some screenshots or elaborate? The cmdb_health_result table contains all the failures. It gets filtered when you click through the CMDB View charts. You are free to change the filter to metric=<your_desired_metric> if you wish.
