-
Type:
Problem report
-
Resolution: Unresolved
-
Priority:
Trivial
-
None
-
Affects Version/s: 8.0.0rc1 (master)
-
Component/s: Templates (T)
-
Environment:8.0.0 beta2, EL9
-
Support backlog
Hello,
8.0.0 Beta2 containts new template:
https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/podman/podman_agent?at=refs%2Ftags%2F8.0.0beta2
To take a look how template actually works, i've configured basic Podman container which runs selenium:
# cat selenium.container
[Unit]
Description=Selenium Standalone chrome selenium
After=network-online.target
[Container]
Image=docker.io/selenium/standalone-chrome:latest
PublishPort=127.0.0.1:4444:4444
ShmSize=1G
PodmanArgs=--memory=1g --memory-swap=1g -e JAVA_OPTS=-Xmx512m -e SE_NODE_MAX_SESSIONS=2 -e SE_NODE_OVERRIDE_MAX_SESSIONS=true
[Service]
Restart=always
[Install]
WantedBy=multi-user.targe
With enabled Podman API discovery rules correctly create new items, but one problem is that for just one container which is running:
# podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 2f3b8b8fef08 docker.io/selenium/standalone-chrome:latest /opt/bin/entry_po... 8 minutes ago Up 8 minutes 127.0.0.1:4444->4444/tcp, 4442-4443/tcp, 5900/tcp, 9000/tcp systemd-selenium
I still get data from both not running containers and also from not used images.
It would be worth to consider to by default filter out state of podman container, for now macro
"{$PODMAN.CONTAINER.FILTER.STATE.MATCHES}"
is set to match everything.
Filter for images would be also great, so to filter out only images which are acutally in use.
Also, here:
example how to configure podman API contains port "8080", but Zabbix's macro:
{$PODMAN.PORT}
is set to "8088" - could be worth to change it to "8080" as it is in example.