Update to Proxmox 6.1 broke metrics

ChristianW

New Member
Feb 13, 2020
6
0
1
41
Hi,
we just upgraded Proxmox to 6.1. Everything seems fine so far, but most of our monitoring data will be dropped, maybe because of an mtu issue:

Code:
08:55:30.176550 IP 172.16.200.250.47503 > 172.16.200.6.2003: UDP, bad length 10348 > 1472
08:55:30.242207 IP 172.16.200.250.47871 > 172.16.200.6.2003: UDP, bad length 50789 > 1472
08:55:30.245716 IP 172.16.200.250.47871 > 172.16.200.6.2003: UDP, bad length 50654 > 1472
08:55:30.246359 IP 172.16.200.250.47871 > 172.16.200.6.2003: UDP, bad length 8260 > 1472
08:55:30.580892 IP 172.16.200.250.60298 > 172.16.200.6.2003: UDP, bad length 2793 > 1472
We configured metrics in /etc/pve/status.cfg:
Code:
graphite:
    server eusib-deb-mon
    port 2003
    path proxmox-wir
Before the update:
Bildschirmfoto 2020-02-13 um 09.39.03.png

After update:
Bildschirmfoto 2020-02-13 um 09.39.28.png

On the other hand the Host data itself is still complete (ex. proxmox-wir->nodes->host->cpustat->cpu)
In trouble is only all of the VM data (ex. proxmox-wir->qemu->108->cpu)

Any ideas?
 

mailinglists

Well-Known Member
Mar 14, 2012
449
40
48
Idea: did you check MTU size on PM hosts network interfaces, like what do you see when running:
ip l l
?
 

ChristianW

New Member
Feb 13, 2020
6
0
1
41
By the way:
On VMs we use collectd to send metrics and they are all fine. So we have:
- Host metrics by Proxmox = ok
- Metrics out of VMs = ok
- VM metrics by Proxmox = faulty

Besides, how are metrics collected in Proxmox?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!