I can't think of anything that could cause this really. We don't do any special collection for ESXi, it's just using the standard HOST-RESOURCES-MIB, etc.

I doubt any of that stuff has changed in a very long time.

You would need to capture a debugged discovery run where the entities are removed and then re-added. I'd guess it's just snmp timeouts.

adam.

Tony Guadagno via observium wrote on 29/03/2023 19:24:

· Hmm, we are using Observium 23.2.12520 (stable)

·

And I seem to have my ESXi info:

Tony

From: Lawrence Cruciana via observium <observium@lists.observium.org>
Sent: Wednesday, March 29, 2023 2:05 PM
To: Observium <observium@lists.observium.org>
Cc: Observium Network Observation System <observium@observium.org>; Lawrence Cruciana <LCruciana@corp-infotech.com>
Subject: [Observium] Re: DKIM Fail VMWare ESXi looses CPU information

Hello all,

I want to second this issue.

It began for us about 2 weeks ago.

We thought it was a set of host issues but we were able to stand up a parallel snmp collection system that was successful in collecting this data.

CPU, memory, and some network interface are the data that is impacted.

On Mar 29, 2023 09:32, Basile Bluntschli via observium <observium@lists.observium.org> wrote:

Hi Observium Team

since a few SVN updates, ESXi start loosing CPU information after full discovery.

It is not clear what triggers it... However the ESXi have not been updated, but Observium is at the latest version from rolling SVN.

What would you need to further debug it?

Kind regards

Basile

This email has been scanned for spam and viruses by Proofpoint Essentials. Click here to report this email as spam.
_______________________________________________
observium mailing list -- observium@lists.observium.org
To unsubscribe send an email to observium-leave@lists.observium.org

--

Sent from Postbox