zabbix-docker | Official Zabbix Dockerfiles | Monitoring library

by zabbix Shell Version: 6.4.3 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | zabbix-docker Summary

zabbix-docker is a Shell library typically used in Performance Management, Monitoring applications. zabbix-docker has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has medium support. You can download it from GitHub.

Zabbix is an enterprise-class open source distributed monitoring solution. Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning. For more information and related downloads for Zabbix components, please visit and

Support

Quality

Security

License

Reuse

Support

zabbix-docker has a medium active ecosystem.

It has 1888 star(s) with 1254 fork(s). There are 76 watchers for this library.

It had no major release in the last 12 months.

There are 2 open issues and 735 have been closed. On average issues are closed in 15 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of zabbix-docker is 6.4.3

Quality

zabbix-docker has no bugs reported.

Security

zabbix-docker has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

zabbix-docker is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

zabbix-docker releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of zabbix-docker

Get all kandi verified functions for this library.

zabbix-docker Key Features

No Key Features are available at this moment for zabbix-docker.

zabbix-docker Examples and Code Snippets

No Code Snippets are available at this moment for zabbix-docker.

Community Discussions

Trending Discussions on zabbix-docker

Unable to understand network section of this docker file (zabbix)

QUESTION

Unable to understand network section of this docker file (zabbix)

Asked 2019-Mar-13 at 08:52

I am using this zabbix docker compose file to run zabbix in a VM but I dont understand the subnets that have been defined at the botton.

https://github.com/zabbix/zabbix-docker/blob/4.0/docker-compose_v3_ubuntu_mysql_latest.yaml

In my internal network I use 2 subnets (one is for private subnet & one is for public subnet e.g. web servers and they start in 10.121.153.x & 10.121.152.x, zabbix is in private subnet)

2 Questions:

Would I need the subnet specified in this docker file
If I do, what values do I use here?

Zabbix is currently running on Ubuntu VM but all the clients are in Windows. I went down this rabbit hole because I wasnt able to run zabbix_get command from windows machine. This is the command I was trying

...

ANSWER

Answered 2019-Mar-13 at 01:29

Docker will create two bridge interfaces with those subnets but they will be used by the containers, it means containers will have IPs in those ranges

e.g. 172.16.238.10 will be a container in the frontend network

TL;DR it doesn't matter, they will expose the ports through the docker host IP

Please check they are reachable, is there a firewall blocking these ports?

Source https://stackoverflow.com/questions/55132351

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install zabbix-docker

You can download it from GitHub.

Support

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can. Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Find more information at: