Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proxmox lxc container "not running" trigger #349

Open
linceaerian opened this issue Mar 27, 2024 · 0 comments
Open

Proxmox lxc container "not running" trigger #349

linceaerian opened this issue Mar 27, 2024 · 0 comments

Comments

@linceaerian
Copy link

linceaerian commented Mar 27, 2024

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:

  • Add an item 'tags'
  • Allow the trigger to be bypassed if the container is tagged in the application with "disabled"

image

I add the modification proposal in the JSON export file linked:
Proxmox VE by HTTP

Best regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant