I noticed that the current template does not allow for a counter to be "stopped" while this can be a "normal" status.
In current proxmox version there's no "disabled" parameter => if you do not use a container, it can be just "stopped".
Due to this the current trigger: "Proxmox: LXC [{#NODE.NAME}/{#LXC.NAME} ({#LXC.ID})]: Not running" will be down even if it can be "normal". I would propose to either add macro filtering regex with MATCHES/NOT_MATCHES for the discovery or what I did on the template:
Add an item 'tags'
Allow the trigger to be bypassed if the container is tagged in the application with "disabled"
I add the modification proposal in the JSON export file linked:
Proxmox VE by HTTP
Hello Maintainers,
I noticed that the current template does not allow for a counter to be "stopped" while this can be a "normal" status. In current proxmox version there's no "disabled" parameter => if you do not use a container, it can be just "stopped".
Due to this the current trigger: "Proxmox: LXC [{#NODE.NAME}/{#LXC.NAME} ({#LXC.ID})]: Not running" will be down even if it can be "normal". I would propose to either add macro filtering regex with MATCHES/NOT_MATCHES for the discovery or what I did on the template:
I add the modification proposal in the JSON export file linked: Proxmox VE by HTTP
Best regards