You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DBA Dash collects CPU utilization from ring buffer using this query. Check what data you have in the ring buffer for the missing time period.
One possibility is the CPU is reporting over 100% in the ring buffer. DBA Dash will filter these out on import. I've had one user report that this is an issue but I'm not clear on the root cause of this or how it should be fixed. It seems to occur only on bare metal instances and maybe certain CPU configurations.
Let me know if you are getting values over 100. If you are what the CPU configuration (physical CPUs, core counts, NUMA nodes etc) looks like on your system and if it's bare metal or hypervisor. It could be worth a support ticket with MS for an official explanation - I'd like to, but I'm not able to reproduce this issue.
DBADASH wont collect CPU data when cpu is pegged or is close to be pegged. It shows empty.
The text was updated successfully, but these errors were encountered: