[V13] Veeam appliance monitoring (SNMP?)

[kbr]

Hi,

I am currently using V13 for a small new customer and would like to have the option to monitor the appliances via our monitoring tool with SNMP. So this is not a way to monitor backups jobs but rather the appliances itself. Would think there might be errors possible on the appliance like CPU issues, disk issues or other events. At the moment i can only ping the appliance, nothing else. I logged a case (Case # 07848827) but they directed me to the Forum to do a request. It's like our vCenter appliances, we also have activited SNMP on the Appliance and it sends out alerts for hundreds of possible issues.

[Dima P.]

Hello Karl,

Thank you for your post, I've added your vote to this feature request!

[spiritie]

+1

[track1044]

+1

[Henrik.Grevelund]

+1

[mv@cloudio.dk]

+1

[mathiasd]

+1

[chaos]

+1

[Gostev]

Folks please use "Like" functionality if all you want to add is +1, this way we don't have to check the topic each time to see what was posted.
Although neither really helps us, what helps is expanding on use cases and/or sharing specific requirements for the integration.

[dm.bobylev]

Our Linux hosts have Prometheus node exporter installed. Without the exporter we can only ping the appliance and check port availability, but we cannot get CPU/RAM/Storage status. We would really appreciate it if the exporter could be included in the appliance or if we could install it manually.

[Henrik.Grevelund]

Hi Gostev,

I guess that is like writing somethings failed, fix it.

For monitoring i would like to be able to monitor these metric:
CPU load pr core
Memory size
Memory used
OS uptime
number of processes

Veeam services status

Disk:
IOPS pr disk
discqueue pr disk

Filesystem:
disk space pr mountpoint
Free space pr mountpoint
discqueue pr mountpoint

NIC:
link status
throughput
discards

TCP and UDP:
retransmit
resets
failed connections

[Gostev]

Thanks Hendrick.

Our Linux hosts have Prometheus node exporter installed. Without the exporter we can only ping the appliance and check port availability, but we cannot get CPU/RAM/Storage status. We would really appreciate it if the exporter could be included in the appliance or if we could install it manually.

My team seems to be inclined to prioritise the integration of Prometheus node exporter as well.

[bgagnon]

+1 on SNMP.
+1 on Prometheus.

[irosinsk]

+1 for SNMP, both on VSA and VIA. Even something as simple as snmpd built into every appliance would be great.

For both, CPU and RAM metrics are essential for us, especially in this early stage of v13 rollout. Our environment's always shifting, and we want to be able to keep an eye on machines that could eventually cause bottlenecks if their resource use increases. For VSA, we'd like to monitor the status of Veeam's services in case they crash at midnight. For VIA, monitoring disk space is a must, primarily for monitoring storage space on repositories, but also for tuning log rotation (not sure how well the appliances handle logs yet).

Veeam One can do some of this, but it's frankly not as responsive and a good bit more flaky than our SNMP client of choice, and all our other infrastructure is already monitored through SNMP, so there's a convenience/learning curve factor as well.

[pma]

Hi everyone, our current plan includes delivering the Node Exporter for Prometheus, along with similar integrations and rsyslog events forwarding to monitor the appliances, with the next minor version update. We also have SNMP implementation in our future roadmap, although it will be included later.

[mikeely]

I was going to ask if there were plans to include the Zabbix agent, but it then occurred to me that it might make more sense for Veeam to take a more generic "monitoring plugin" approach: create some provision for people to install a plugin for their preferred monitor which honestly could just be a package with an RPM and metadata since these are Rocky9 boxes at heart. That way you wouldn't need to chase each different monitoring platform that customers want. The trick would be sandboxing the plugin module so it can only do monitoring tasks.

[pma]

The Zero-Trust concept, which VSA and VIA are built upon, allows the execution of scripts in a sandbox environment but does not support the installation of permanent components outside of Veeam. To achieve this, several layers of protection with digital signature verification, including at the RPM package level, have been implemented. Thus, our objective is to independently support the primary monitoring tools that address the majority of requests in the upcoming releases.

Currently, our primary engineering effort is focused on centralized management of such monitoring configurations. Once this milestone is reached, it will expedite the integration of additional monitoring tools upon request.

Regarding Zabbix, since version 4.2, it can collect and parse metrics exposed in Prometheus text format, allowing it to read Prometheus Node Exporter directly from its /metrics endpoint. For more information, please refer to the following links:
https://www.zabbix.com/documentation/cu ... prometheus
https://blog.zabbix.com/zabbix-4-2-prom ... n/7558/#08

[spiritie]

Hi everyone, our current plan includes delivering the Node Exporter for Prometheus, along with similar integrations and rsyslog events forwarding to monitor the appliances, with the next minor version update. We also have SNMP implementation in our future roadmap, although it will be included later.

This sounds fantastic. Are you able to share which stuff you are planning to expose with Prometheus?

- I guess "base" OS monitoring, CPU, memory, disk, NIC and so on?
- Will we be able to monitor Veeam services and other health metrics?
- Available updates pending for VIA (The updates shown on the MGMT port 10443)?

[pma]

Yes, basic OS monitoring, utilizing a slightly modified set of default metrics, is planned for implementation in the upcoming version. Monitoring for Veeam services is also on our roadmap. However, for other VBR-related metrics, VeeamOne remains the recommended solution.

Regarding update availability, this seems to be a separate topic from system metrics, and exposing such information without administrator authentication could introduce security risks. Therefore, I believe it would be more appropriate to include update monitoring within VeeamOne rather than exposing it through Prometheus metrics.

While I recognize the value in tracking updates - particularly to expedite the installation of critical patches - I would appreciate your insights on any additional use cases you have in mind.
Thank you!