I've been interested to buy 32 licenses for my studio.
After having 0 response to https://forum.proxmox.com/threads/audiodev-driver-pa-support.62317/ and https://forum.proxmox.com/threads/cpu-usage-metrics-in-external-metrics-server-not-reported.63051/
I'm going to go to your competitors: trying...
so I have a "solution" for this.
run "drop series from system" in influx up until you win russian roulette and the package with non-integer uptime comes first.
This is a pretty horrible solution and should be easy to fix on proxmox side: make whatever submits metrics not report `0.0` as `0`.
More errors in this area
ts=2020-01-09T02:55:44.131034Z lvl=info msg="Failed to write point batch to database" log_id=0KE3J33G000 service=udp db_instance=proxmox error="partial write: field type conflict: input field \"uptime\" on measurement \"system\" is type float, already exists as type...
Solution from https://forum.proxmox.com/threads/enable-mtu-9000-jumbo-frames.34523/post-199525 worked for me
still, this seems like an easy to fix bug and should probably be fixed on proxmox side.
Edit: nope, metrics are still not showing up
Maybe a red herring, but
root@pve:~# tcpdump -i vmbr0 udp port 8089
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmbr0, link-type EN10MB (Ethernet), capture size 262144 bytes
17:51:54.645951 IP localladdr.44223 > metrics-srv.8089: UDP, bad length 4132...
I've followed the guide in
https://pve.proxmox.com/wiki/External_Metric_Server
and I can see metrics such as cpu usage overall
SELECT mean("cpu") FROM "cpustat" WHERE GROUP BY time(1m) fill(null)
, but the "system" set seems incomplete:
Eg.
SELECT last("cpu") FROM "system" GROUP BY time(1m)...
Here is why I believe it was disabled at build time.
$ /usr/bin/qemu-system-x86_64 -audio-help
Environment variable based configuration deprecated.
Please use the new -audiodev option.
Equivalent -audiodev to your current environment variables:
(Since you didn't specify QEMU_AUDIO_DRV...
Dear Proxmox creators and Community,
first of all, thank you for building such a great product. Here is context of what I'm doing
I'm an owner of effects studio in California and am considering buying it to optimize capacity of machinces that my employees use.
They currently run 32 medium-sized...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.