In trying to create SLA reports, I've run across issues which I thought after seeing outside posts from 2010/2012 would have been resolved. It seems reports are just not accurate, and if even one isn't accurate, how can I/we trust any???????
I expect there is nothing crazy about my installation, it's running on CentOS 7, has been for years, and alerts etc have been running great. I've got 20 or so host groups, 125 or so hosts, sotrage, switches etc. I'm not a guru, but it all works (except for the reporting)
Today I upgraded from Core 4.1x to 4.3.2.
Although running this test for a single host for this discussion, the data also appears incorrect for hostgroups that contain this and other hosts. Same thing for some services. I picked a single host that I know was down for some short periods of time in order to verify it should not be %100. It was not "scheduled down", it was just down, which for purposes of this discussion is a good thing. In running a report for a single host, here are my findings.....
1. Availability for a single host, all defaults, Last 7 days. Report Time period None, yes, yes, yes, no, First Assumed Host State (Host Up),First Assumed Service State: (Service OK)
- looks fine, except why would "Host Log Entries:" include items from 2015 through 2017? weird because it's not in the Time period specified by the report. (no, I did not click "View full log entries")
- ok, now I get something other than %100 which is what we want and expect. Up is 99.508% (137d 16h 51m 54s) Down is .492% (0d 16h 19m 42s) The Host Log Entries outside of the report period persists, but include the January and early April down time---- take note.
- Here's the problem- Up 100%, Down 0%, Nothing in host log entries
So if we know the host was down in January and early April of this year (see #2), and that time range is included in the Custom Report time range, why does the report show uptime of 100%, and also not show the host log entries like it did before.
Is there a different mechanism for reports that is used for a custom date range?
Is there a way to produce the report query manually?
I briefly read something about a mysql interface..... is that a possibility?
I don't like it when I'm asked to provide data for us to publish, what I can easily provide is not accurate - sorry, but I didn't need this right now...
Thanks for any input,
Rich