OS: Ubuntu (mostly 22.04 atm)
Zabbix_Server Version: 6.2.9
We are using Slurm to schedule cloud nodes on demand (i.e. instances are created in an OpenStack environment when needed). Currently, we just delete servers from Zabbix when they are powered down using pyzabbix, but that costs us all the logs of course as the servers are then gone for Zabbix which is not ideal. An ideal solution would let Zabbix know that this is a planned shutdown. However, planned shutdowns seem to need a starting and end time, but end times cannot be known in advanced given that nodes start on demand.
Also, servers that are started on demand, might be powered down (instances deleted) later and restart again afterwards when needed (instance created). The servers will differ physically, but have the same name. I am not entirely sure yet whether the best practice is to let Zabbix treat them as the same server (using DNS as the default interface in order to allow Zabbix to use the name not the ip to identify the "same" server https://www.zabbix.com/documentation...ault-interface).
I was unable to find much on this topic, but I am fairly sure that this is not a new problem so I am both looking for specific answers to my issue and links to other questions/solutions regarding this topic.
Zabbix_Server Version: 6.2.9
We are using Slurm to schedule cloud nodes on demand (i.e. instances are created in an OpenStack environment when needed). Currently, we just delete servers from Zabbix when they are powered down using pyzabbix, but that costs us all the logs of course as the servers are then gone for Zabbix which is not ideal. An ideal solution would let Zabbix know that this is a planned shutdown. However, planned shutdowns seem to need a starting and end time, but end times cannot be known in advanced given that nodes start on demand.
Also, servers that are started on demand, might be powered down (instances deleted) later and restart again afterwards when needed (instance created). The servers will differ physically, but have the same name. I am not entirely sure yet whether the best practice is to let Zabbix treat them as the same server (using DNS as the default interface in order to allow Zabbix to use the name not the ip to identify the "same" server https://www.zabbix.com/documentation...ault-interface).
I was unable to find much on this topic, but I am fairly sure that this is not a new problem so I am both looking for specific answers to my issue and links to other questions/solutions regarding this topic.