ObservationTimestamp in CPULoad and CPUMultiLoad show different timezone values after retention.

Hi all,

I am writing a SWQL that will join CPULoad and CPUMultiLoad tables. But old retention records of ObservationTimestamp column can not be joined because of different value.

The CPUMultiLoad.ObservationTimestamp is 00:00:00 after retention, CPULoad.ObservationTimestamp is 16:00:00.

My local timezone is +8:00, after ToLocal() function.

CPUMultiLoad.ObservationTimestamp become 08:00:00, CPULoad.ObservationTimestamp become 00:00:00.

So only CPULoad is correct.

Why the retention has different behavior to these two tables?

Is it the setting problem, or bugs?

Thanks!

NPM Version. 2020.2.4

CPUMultiLoad

CPULoad

Find more posts tagged with

retention

cpuload

problem

multiple cpus

timezone

Accepted answers

All comments

longchihang

In the latest ObservationTimestamp records, two table values are same. It means CPUMultiLoad.ObservationTimestamp is correctly stored as UTC time. Therefore, ToLocal(ObservationTimestamp) will get the local time. However, the first retention record of ToLocal(CPUMultiLoad.ObservationTimestamp) will be 08:00:00, ToLocal(CPULoad.ObservationTimestamp) be 00:00:00. Although they are the same day, retention records can not be joined in SWQL, only non-retention records can.

CPUMultiLoad - First record / Last record

CPUMultiLoad - First record CPU MultiLoad - Last record

CPULoad - First / Last record
CPULoad - First record

CPULoad -Last record

sum_giais

This all looks correct and perfectly normal.

If you look under Settings --> All Settings --> Polling Settings, you can see the retention settings and there's a reason that's important.

The defined polling retention settings tell Orion when to summarize data.

The flow is usually like this and the summarizations occur during the nightly maintenance.

1) Initial data poll... collected and stored as "Detailed Statistics" (usually retained for 7 to 14 days)

2) 14 day mark hit... "Detailed Statistics" now get summarized into "Hourly Statistics" (usually retained for 30, 60, 90 days)

3) 60 day mark hit... "Hourly Statistics" now get summarized into "Daily Statistics" (usually retained for 180 days)

These retention settings can all be changed, just be cautious as it can affect the size of your database.

longchihang

Thank you for reply, but my main problem is the CPULoad.ObservationTimestamp and CPUMultiLoad.ObservationTimestamp showing different value after record retention. When table records become to one record a day, CPULoad.ObservationTimestamp has timezone offset (+8 timezone), CPUMultiLoad.ObservationTimestamp is +0 timezone.