XI 2014R1.2 Ent Ed
This Report is giving wrong figures for Total Alerts and Latest Alert.
Please see attached state history for SST_KUL_CDM_S798_OMRON
Where did this report get total alerts as 14 and latest alert as 2014-07-03 18:24:59
Please check on this.
Wrong Alerts Report
Wrong Alerts Report
You do not have the required permissions to view the files attached to this post.
5 x Nagios 5.6.9 Enterprise Edition
RHEL 6 & 7
rrdcached & ramdisk optimisation
RHEL 6 & 7
rrdcached & ramdisk optimisation
Re: Wrong Alerts Report
The latest alert for "SST_KUL_CDM_S798_OMRON" was on 07/03, according to the "Top Alert Producers". The "State History" reports starts on 7/10 and ends on 7/31.
I wonder if you entered "07/10/2014" instead of "07/01/2014" in the "From" filed when you were setting up your custom time period in the web UI...
I wonder if you entered "07/10/2014" instead of "07/01/2014" in the "From" filed when you were setting up your custom time period in the web UI...
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Wrong Alerts Report
The latest alert for SST_KUL_CDM_S798_OMRON was on 31/07/2014. It is shown on the details however the main report is showing wrong information.lmiltchev wrote:The latest alert for "SST_KUL_CDM_S798_OMRON" was on 07/03, according to the "Top Alert Producers". The "State History" reports starts on 7/10 and ends on 7/31.
I wonder if you entered "07/10/2014" instead of "07/01/2014" in the "From" filed when you were setting up your custom time period in the web UI...
No I did not select any date, I clicked the link from the report.
I checked again and the report stopped at 10/07. This looks like another bug to me.
5 x Nagios 5.6.9 Enterprise Edition
RHEL 6 & 7
rrdcached & ramdisk optimisation
RHEL 6 & 7
rrdcached & ramdisk optimisation
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Wrong Alerts Report
When you click on the number of alerts and the item in question is a host, the state history that is displayed will be for all alerts on the host.
One possible explanation for what you are seeing is if you have Admin -> Performance Settings -> Database Tab -> "Max State History Age:" set to something low like 20 days, there would not be enough retained information to populate the report.
One possible explanation for what you are seeing is if you have Admin -> Performance Settings -> Database Tab -> "Max State History Age:" set to something low like 20 days, there would not be enough retained information to populate the report.
Re: Wrong Alerts Report
No, the statehistory contains both the host and services alerts.scottwilkerson wrote:When you click on the number of alerts and the item in question is a host, the state history that is displayed will be for all alerts on the host.
I just checked again BTW, it the details, the State type keeps on auto selecting Hard even though I have selected Both from the initial screen or even in the state history screen.
Must be some other reason. It is set to 730.scottwilkerson wrote: One possible explanation for what you are seeing is if you have Admin -> Performance Settings -> Database Tab -> "Max State History Age:" set to something low like 20 days, there would not be enough retained information to populate the report.
You do not have the required permissions to view the files attached to this post.
5 x Nagios 5.6.9 Enterprise Edition
RHEL 6 & 7
rrdcached & ramdisk optimisation
RHEL 6 & 7
rrdcached & ramdisk optimisation
Re: Wrong Alerts Report
I just had a client report an issue where: selecting a hostgroup from the dropdown will no longer report alerts from services. Could this be related to the alert issues you are experiencing?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: Wrong Alerts Report
The services get reported fine, the listing of alerts is fine also.abrist wrote:I just had a client report an issue where: selecting a hostgroup from the dropdown will no longer report alerts from services. Could this be related to the alert issues you are experiencing?
Just the main report page is giving wrong information. See my initial post.
5 x Nagios 5.6.9 Enterprise Edition
RHEL 6 & 7
rrdcached & ramdisk optimisation
RHEL 6 & 7
rrdcached & ramdisk optimisation
Re: Wrong Alerts Report
Maybe I'm just a bit confused here, but the csv you posted is for SST_SGR_CDM_S475_OMRON but you're talking about SST_KUL_CDM_S798_OMRON. Are you sure we're looking in the right place?
Former Nagios employee
Re: Wrong Alerts Report
Ok. Here is another exampletmcdonald wrote:Maybe I'm just a bit confused here, but the csv you posted is for SST_SGR_CDM_S475_OMRON but you're talking about SST_KUL_CDM_S798_OMRON. Are you sure we're looking in the right place?
Look at the latest alert date Look at the detail, which shows another latest alert date, even if this is referring to host error the date is still wrong.
Refer to the attachment to alerts list.
You do not have the required permissions to view the files attached to this post.
5 x Nagios 5.6.9 Enterprise Edition
RHEL 6 & 7
rrdcached & ramdisk optimisation
RHEL 6 & 7
rrdcached & ramdisk optimisation
Re: Wrong Alerts Report
Just to further troubleshoot as I am sure there are some issues with this component:
Is the reported "Latest Alert" time the same as the latest alert for the host itself (not any of the services)?
Is the reported "Latest Alert" time the same as the latest alert for the host itself (not any of the services)?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.