Use Zabbix Agent 2 on the VPS, enable its built-in Docker plugin, connect the host to Zabbix’s official Linux template, and then add Docker item discovery and triggers. Choose passive checks when the Zabbix server or proxy can reach the VPS; choose active checks when allowing outbound connections from the VPS is easier to secure. This design lets you see container inventory, state, daemon health, images, and resource statistics, and alert when a container stops or a host runs short of CPU, memory, or disk.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
What the monitoring path looks like
“Zabbix agent is the process responsible for gathering data.” For Docker monitoring, Agent 2 gathers data from the Docker daemon through its built-in plugin and sends it to the Zabbix server directly or through a proxy. The server stores the values, displays them in Monitoring → Hosts → Latest data, evaluates triggers, and sends notifications through configured media and actions.
As an Amazon Associate I earn from qualifying purchases.
The plugin is described by Zabbix as “Monitoring of Docker containers.” It can query the daemon, enumerate containers and images, collect container information and statistics, and report Docker data usage. Installing an agent alone does not automatically produce every container metric: the Docker plugin must be able to reach the daemon, and the relevant items or low-level discovery rules must exist on the host.
Decide the versions, network direction, and scope first
Keep Agent 2 compatible with the server
Zabbix recommends installing an agent version that matches the Zabbix server version. The current official Linux integration page states that the Linux by Zabbix agent template requires Zabbix Agent 7.4 or newer. The examples below therefore use a Zabbix 7.4-style installation; substitute the major version used by your server and repository rather than mixing unrelated releases.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Check the server and proxy versions before installing anything. If a proxy performs collection, the agent must be reachable from that proxy, not necessarily from the central server. Plan an upgrade window when the server, proxy, agent, and templates will move between major versions.
Choose passive or active checks
| Design | Connection initiator | Firewall direction | NAT and outage behavior | Best fit |
|---|---|---|---|---|
| Passive | Zabbix server or proxy requests each value from Agent 2 | Allow the server or proxy to reach the agent’s listening port, normally TCP 10050 | Works only while the monitoring side can route to the VPS; inbound filtering, NAT, and changing addresses must be handled | A VPS on a private network or with a stable, tightly restricted management path |
| Active | Agent 2 polls the server or proxy for its configuration and sends values out | Allow outbound traffic from the VPS to the server or proxy, normally TCP 10051; no inbound agent port is required | Usually easier through NAT; an outbound outage prevents new values from arriving, so configure a no-data alert | Internet-facing VPSs where inbound access is difficult but outbound access is controlled |
Active checks require an exact name match: the Hostname in the agent configuration must equal the host name configured in the Zabbix frontend. Passive checks do not have that same discovery requirement, but the agent interface address and port must be reachable and permitted by the firewall.
Free tools Windows power users keep installed
One-click scans. No signup required.
Define what “healthy” means
- Container presence: which containers must exist, and which are allowed to be short-lived jobs?
- Availability: should a stopped container create an immediate problem, or only if it remains stopped for a defined period?
- Capacity: what CPU, memory, filesystem, and Docker data-usage thresholds are meaningful for this VPS?
- Change: do image additions, removals, or unexpected containers need an alert?
Writing these rules before enabling discovery prevents a flood of alerts from one-shot jobs, maintenance containers, or intentionally scaled services.
Install Zabbix Agent 2 on the VPS
Package installation
For most VPSs, a native package is the simplest operational choice. Enable the repository for the same Zabbix major version as the server, then install Agent 2 with the distribution package manager. On a Debian- or Ubuntu-based VPS, the package step is typically:
sudo apt update
sudo apt install zabbix-agent2
sudo systemctl enable --now zabbix-agent2On an RPM-based VPS using the matching repository, the equivalent package step is:
sudo dnf install zabbix-agent2
sudo systemctl enable --now zabbix-agent2Package names and repository setup vary by distribution. Confirm that the installed package is the 7.4 major version (or the major version used by your server) before configuring it. The service normally reads /etc/zabbix/zabbix_agent2.conf.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Configure a passive agent
Set the server or proxy address that is allowed to request data, give the host a stable name, and point the Docker plugin at the daemon socket if the default is not sufficient:
Server=10.0.0.10
Hostname=vps-docker-01
Plugins.Docker.Endpoint=unix:///var/run/docker.sockReplace 10.0.0.10 with the real server or proxy address. Restrict the host firewall so only that monitoring address can reach TCP 10050. Restart the service after editing:
sudo systemctl restart zabbix-agent2
sudo systemctl status zabbix-agent2Configure an active agent
For active checks, set the server or proxy used for active configuration retrieval, use the exact frontend host name, and do not expose an unnecessary inbound agent port:
ServerActive=10.0.0.10
Hostname=vps-docker-01
Plugins.Docker.Endpoint=unix:///var/run/docker.sockAllow outbound TCP 10051 to the selected server or proxy. If you leave a passive interface on the host by mistake, Zabbix may show passive errors even though active collection is working; configure the host for the mode you actually selected.
Recommended Free Tools
Run Agent 2 as a container
Zabbix publishes official images for agents, Agent 2, servers, proxies, web frontends, the Java gateway, web service, and SNMP traps. A containerized Agent 2 can fit an immutable VPS workflow, but it must be supervised, upgraded, and given access to the Docker daemon. The documented container deployment path lists Docker 1.12 or later and Docker Compose 2.24.0 or later as prerequisites; verify those requirements against the current image documentation before deployment because they are version-sensitive.
A container deployment normally needs the agent configuration supplied as environment variables or a mounted file and the Docker socket mounted into the agent container. Align the container’s user and group permissions with the socket, keep the mount as restricted as the plugin permits, and make sure the container restarts automatically. A native package generally offers simpler service supervision and direct access to distribution logging; a container offers image-based rollback and a more uniform upgrade process.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
| Installation form | Advantages | Costs and failure modes |
|---|---|---|
| Native package | System service integration, straightforward logs, ordinary package upgrades, direct host networking | Repository changes affect upgrades; rollback depends on package availability; host policy must permit Docker socket access |
| Agent 2 container | Versioned image, reproducible deployment, easy rollback to a prior image | Requires socket or daemon-endpoint plumbing, container supervision, correct UID/GID mapping, and a plan for image updates |
Give the Docker plugin controlled access
Understand the socket risk
The Docker Unix socket is highly privileged. A process that can issue unrestricted Docker API requests can often create a privileged container, mount the host filesystem, or otherwise obtain root-equivalent control of the VPS. Adding the Zabbix service account to the broad docker group has the same fundamental security consequence as granting administrative Docker access.
Prefer the narrowest workable design:
- Keep the socket on the local filesystem instead of exposing an unauthenticated Docker TCP endpoint.
- If a remote daemon endpoint is unavoidable, use mutually authenticated TLS and firewall it to the monitoring source.
- Use a controlled socket proxy or dedicated daemon endpoint only after reviewing exactly which read operations the Docker plugin needs; a proxy that accidentally permits container creation is not least privilege.
- Apply the VPS’s SELinux, AppArmor, and filesystem policies, and document the exception that allows Agent 2 to query Docker.
- Do not mount the host socket into unrelated monitoring or application containers.
Test access before enabling discovery
First verify that the service account can reach the endpoint. Then test the plugin from the Agent 2 installation:
sudo -u zabbix zabbix_agent2 -t docker.pingThe exact executable path can differ by package. A successful test should return a value indicating that the Docker daemon is reachable. Permission-denied, timeout, and socket-not-found results should be fixed locally before creating dozens of discovery items.
After changing socket permissions, restart Agent 2 and inspect its service log. Do not “solve” a permission error by making the socket world-writable or by exposing Docker on an open TCP port.
Create the VPS host in Zabbix
- Open Data collection → Hosts (called Configuration → Hosts in older frontend layouts) and select Create host.
- Enter the host name exactly as it appears in
Hostnamefor active checks. Assign a host group that matches your operational ownership. - On the Templates tab, link Linux by Zabbix agent for passive collection or Linux by Zabbix agent active for active collection.
- For passive mode, add an Agent interface with the VPS address and TCP 10050, then restrict the interface to the server or proxy that will poll it.
- For active mode, follow the template’s active-check setup and leave the passive agent interface unset when the guide calls for that arrangement.
- Save the host, wait for the next collection interval, and open Monitoring → Hosts → Latest data.
The Linux template supplies host operating-system checks; it does not, by itself, guarantee that every Docker container metric is present. Docker plugin items and discovery rules must be enabled and returning values.
Collect Docker inventory, state, and resource data
Use the built-in item keys deliberately
Agent 2’s Docker plugin includes these keys:
| Key | Purpose | Typical use |
|---|---|---|
docker.ping |
Tests Docker daemon reachability | Detect a stopped daemon, a broken socket, or a permission failure |
docker.info |
Returns Docker daemon information | Track daemon-level state and configuration changes |
docker.containers |
Returns container information | Build summary views or check aggregate container state |
docker.containers.discovery |
Discovers containers for per-container monitoring | Create item and trigger prototypes for each discovered container |
docker.container_info |
Returns information for a selected container | Track status, names, identifiers, and configuration details |
docker.container_stats |
Returns container resource statistics | Monitor CPU, memory, network, and block-I/O behavior |
docker.images and docker.images.discovery |
Reports images and discovers them for per-image items | Watch image inventory and cleanup-related growth |
docker.data_usage |
Reports Docker data usage | Detect storage growth in Docker’s data area |
Enable discovery only for useful objects
Start with container discovery and the statistics needed by your service owners. Add image discovery or data-usage items when image churn and disk growth are operational concerns. Exclude known short-lived jobs or maintenance containers through discovery filters where appropriate. Otherwise, every job can create new items and problems that no one needs to act on.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Use meaningful macros or labels in the discovered entity names so a problem identifies the service, environment, and container rather than only a long container ID. Keep discovery intervals slower than the resource-statistics interval; inventory changes do not need to be sampled as often as CPU or memory.
Check the first values
In Monitoring → Hosts → Latest data, filter by the VPS host and search for docker.. Confirm that the daemon ping, at least one discovered container, and a statistics item have recent timestamps. An item that is “unsupported” is different from an item that has no data: open its error text and correct the key, permission, endpoint, or returned data format before writing triggers.
Build alerts that lead to an action
Container stopped or missing
For long-running services, create a trigger prototype from the discovered container status item. Alert when the status is not running for a deliberate hold period, and exclude containers whose normal lifecycle is short. If a container is removed rather than stopped, use discovery loss or a separate expected-container check so that a missing service cannot silently disappear from monitoring.
Docker daemon unavailable
Use docker.ping to detect an unreachable daemon. Combine a failed value with a short persistence period or a no-data condition to avoid paging on one transient collection error. A daemon problem should have higher severity than an individual container problem because it can invalidate all Docker metrics on the VPS.
CPU and memory saturation
Use docker.container_stats for per-container usage and alert on sustained high values rather than a single sample. Set thresholds from the container’s CPU limit, memory limit, and normal workload. A percentage without its denominator can mislead: a container using 80% of a small limit may be at greater risk than one using 60% of a much larger allocation.
When memory limits are configured, alert separately on approaching the limit and on an observed restart or out-of-memory event. CPU alerts should distinguish a throttled container from one that is simply busy but meeting its latency objective.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Filesystem and Docker data pressure
The Linux template can report host filesystem utilization, while docker.data_usage helps show Docker-specific growth. Alert early enough to leave room for logs, image pulls, and container restarts. A full filesystem can break both Docker and Zabbix, so treat host disk pressure as an infrastructure problem rather than only a container problem.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesConnect problems to notifications
- Configure at least one media type and assign it to the people responsible for the VPS.
- Create an action under the alerting configuration that matches the trigger severity, host group, and service hours.
- Route daemon-unavailable and host-disk problems differently from lower-severity resource warnings.
- Include the host, container name, trigger condition, last value, and timestamp in the message so an operator can act without opening the frontend.
- Use recovery operations and escalation only where they add a clear response; repeated messages for one unchanged condition create alert fatigue.
Validate the complete path safely
- Confirm Agent 2 is running and the Docker plugin test succeeds on the VPS.
- Confirm the selected firewall direction: server or proxy to TCP 10050 for passive, or VPS to TCP 10051 for active.
- Open Latest data and verify fresh daemon, container, and statistics values.
- Open Monitoring → Problems and check that no-data or unsupported-item errors are present.
- Use a disposable test container, stop it briefly, and verify the expected problem and recovery. Do not stop a production container merely to test alerting.
- Restore the test container, confirm recovery notifications, and record the test date and observed delay.
Troubleshoot by symptom
| Symptom | Likely cause | What to check |
|---|---|---|
| Host is unavailable in passive mode | Firewall, wrong interface address, or the server cannot route to the VPS | TCP 10050 rules, the Agent interface, listening service status, and whether a proxy—not the server—should connect |
| Active host never receives values | Hostname mismatch or blocked outbound connection |
Exact frontend host name, ServerActive, outbound TCP 10051, and Agent 2 logs |
docker.ping is permission denied |
Zabbix service account cannot access the socket | Socket ownership, group membership, MAC policy, and the configured endpoint; do not make the socket world-writable |
| Docker items are unsupported | Plugin endpoint, key syntax, or returned data is incompatible | Item error text, Agent 2 version, plugin configuration, and a local zabbix_agent2 -t test |
| Discovery finds nothing | Discovery rule is disabled, daemon access fails, or filters exclude every object | Discovery status, filters, latest discovery data, and Docker daemon output |
| One-shot jobs create constant alerts | Every discovered container is treated as a permanent service | Discovery filters and trigger prototypes; classify jobs separately from long-running containers |
| Values stop during an outbound outage | Active agent cannot reach the server or proxy | Outbound routing, DNS, firewall logs, and a no-data trigger that reflects the expected polling interval |
Operate the setup over time
Upgrade in a controlled order
Keep the server, proxy, Agent 2, and linked templates on compatible major versions. Read the release notes before upgrading because item keys, plugin behavior, package names, and frontend labels can change. Upgrade a non-production VPS first, verify Docker discovery and trigger evaluation, then roll out to the remaining hosts.
Review scope and privileges
At each review, remove unused discovery rules, stale hosts, and unnecessary notification recipients. Recheck who can read or alter the Docker endpoint. If the VPS begins hosting workloads with different trust levels, consider separating monitoring endpoints or proxies rather than giving one agent broad access to every daemon.
Measure usefulness, not just collection
A green item is not proof that the application is healthy. Pair container state and resource data with service-level checks where available, and verify that every high-severity trigger has an owner and a tested response. The goal is a small set of trustworthy signals: the daemon is reachable, expected containers exist and run, resources remain within their budgets, and the host has enough disk to recover.
Frequently Asked Questions
Can I monitor Docker without opening the agent port to the Internet?
Yes. Use active checks and permit only the VPS’s outbound connection to the Zabbix server or proxy. The agent still needs controlled access to the local Docker daemon, but no inbound TCP 10050 rule is required.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhy does linking the Linux template not show my containers?
The Linux template covers operating-system monitoring. Container metrics require Agent 2’s Docker plugin, working daemon access, and enabled Docker items or discovery rules such as docker.containers.discovery and docker.container_stats.
Should every discovered container generate a stopped alert?
No. Exclude short-lived jobs and maintenance containers, and apply stopped-state trigger prototypes only to containers that are expected to run continuously.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
