"today" ends at 8pm in... California?

I'm not specifically seeing this issue, but I am seeing something odd on one of my reports. They appear to be running an hour behind. In other words, all servers are in UTC but when I read the reports, the most recent database updates appear to be timestamped one hour before (based on the value of the column 'LastSystemUpTimePollUtc' in the 'dbo.nodes' table.

For instance, when I'm looking for servers which have a SNMP response time outside the global polling interval, I'm seeing the most recent entries as one hour behind. Which has caused a few BOHICA moments for the service desk when they thought that critical nodes had stopped responding to SNMP an hour ago....

Not sure what's causing it. I'm running NPM 11.0.1 at present. 

What is the timezone on your solarwinds server set to? It sounds like it is set incorrectly. I'm on 11.0.1 and don't have an issue.

superfly99 wrote: What is the timezone on your solarwinds server set to? It sounds like it is set incorrectly. I'm on 11.0.1 and don't have an issue.

If it was set incorrectly, it'd affect way more than the time today's stats get reset. Like, timestamps on all events.

So it's about 6:18pm and here's today's discards and errors stats. Let's see what happens around 8pm.

As of 11:26pm, the stats hadn't reset yet. Perhaps yesterday's full Configuration Wizard rebuild fixed the issue.

Stats reset correctly at midnight. The 11.5 upgrade or perhaps even the 11.1 one bungled things up. Doing a full run of the "Configuration Wizard" on services, database and Orion seems to have fixed the issue.

silverbacksays‌ - have you tried this to see if it fixes your issue?

Nope, I have't akhasheni‌!

I'll give it a bash and report how it goes

Running the config wizard didn't help, but my Google-fu found out why my report is off:

SQL DATETIME HELP

My query is using DATEDIFF, and apparently it's rounding the time down.