Hello Community,
I am fetching VMotion events from dynatrace with the purpose of locally analyzing them and trying to establish observability reports.
I use the events v2 API with the event selector for the properties of event type:
"ESXI_HOST_VM_MOTION_ARRIVED", "ESXI_HOST_VM_MOTION_LEFT", "ESXI_HOST_VM_MOTION"
What I don't seem to be able to do is to figure out how much time a VMotion took to occur. I know these exist on all of the three event types:
"startTime": 1720718012639,
"endTime": 1720718012641,
However, these times don't make a lot of sense. VMotions taking 0.002 seconds to happen isn't expected at all, I don't even think it's possible.
So what exactly do these timestamps represent?
Things I've tried:
- Matching the LEFT and ARRIVAL entries by the value of dt.event.description, which contains the name of the VM. Sadly, some VMs have 100+ LEFT entries and only about 2 ARRIVAL entries. The numbers don't add up.
- Using the startTime and endTime on the json with ESXI_VM_MOTION entries. But the startTime and endTime are often very close to each other, which results in VMotions having occurred within 0.002 seconds and that doesn't make sense.
Any ideas to try and figure out how long a VMotion took?
Any help or bouncing off of ideas is appreciated.
To make an error is human. To spread the error across all servers in an automated way is DevOps.
