Hello Team,
With reference to my earlier post on how to generate availability using BPI metrics: https://support.nagios.com/forum/viewto ... 16&t=38580
I have encountered a problem with accuracy in the reports.
Please find attached files for more details on the issue I have with the accuracy in the BPI groups results and BPI Service Group in Availability Reports.
Thanks in advance.
Regards,
Swapnil
Inaccuracy in Availability Report while using BPI Service Gr
Inaccuracy in Availability Report while using BPI Service Gr
Last edited by sgiworks on Mon Aug 22, 2016 3:43 pm, edited 1 time in total.
Re: Inaccuracy in Availability Report while using BPI Servic
What version of XI are you running, I do know there were some bug fixes released in the last few versions.
Also, what does it show in the state history for that service (please attach a screenshot of that timeframe)?
What I'm thinking is that the BPI page showed it as CRITICAL but because the service check is based on the check_interval it may have not picked it up yet, there could be a delay up to the check_interval length. Does that make sense or do I need to reword?
Also, what does it show in the state history for that service (please attach a screenshot of that timeframe)?
What I'm thinking is that the BPI page showed it as CRITICAL but because the service check is based on the check_interval it may have not picked it up yet, there could be a delay up to the check_interval length. Does that make sense or do I need to reword?
Re: Inaccuracy in Availability Report while using BPI Servic
Please reword!
Re: Inaccuracy in Availability Report while using BPI Servic
1. What version of XI are you running?ssax wrote:What version of XI are you running, I do know there were some bug fixes released in the last few versions.
Also, what does it show in the state history for that service (please attach a screenshot of that timeframe)?
What I'm thinking is that the BPI page showed it as CRITICAL but because the service check is based on the check_interval it may have not picked it up yet, there could be a delay up to the check_interval length. Does that make sense or do I need to reword?
2. Please attach a screenshot of the state history for that service that we can see as well.
Former Nagios Employee
Re: Inaccuracy in Availability Report while using BPI Servic
We are on Nagios 5.2.3
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Inaccuracy in Availability Report while using BPI Servic
One thing I will point out is that the Availability report cannot calculate the amount of time the host/service was down until the host/service has recovered.
So if your report is an open ended timeframe such as "Today", This Week", "This Month", and the service is still critical, it is not part of the calculations.
So if your report is an open ended timeframe such as "Today", This Week", "This Month", and the service is still critical, it is not part of the calculations.
Re: Inaccuracy in Availability Report while using BPI Servic
Please find attached problem details document, where I have explained the problem with data in BPI and Availability Report.
You do not have the required permissions to view the files attached to this post.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Inaccuracy in Availability Report while using BPI Servic
When the service you create comes out of the critical state the Availability report will be able to calculate the quantity of time the service was down and report appropriately.
Re: Inaccuracy in Availability Report while using BPI Servic
Ok fine, I will wait.
Can you confirm that rest all configuration is correct?
Can you confirm that rest all configuration is correct?
Re: Inaccuracy in Availability Report while using BPI Servic
The configuration looks fine. Let us know if you have any more questions/issues.
Be sure to check out our Knowledgebase for helpful articles and solutions!