Thank you for such an amazing change. I like that you are moving towards decentralized processes. But in my opinion, you also need to work through the server part. For an example, problems which should be faced: 1 - Zabbix .nodata() trigger from a hosts always work when a proxy crashes. This can be corrected by dependence on a trigger proxy, but I think that this option cannot be adequately implemented for> 1000 hosts. Which is again strange when you transfer the load to the proxy. 2 - HA. Zabbix server is monolithic and does not have built-in cluster support to avoid moments of failure of a DC or one of the playground where it is located, which is rather strange nowadays. This also applies to the database. The only available option is custom scripts, etc. 3 - nested LLDs. For example, there is a server with a database, there are several of them, each has tables, and each has indices. All these things I would like to add to the monitoring for more accurate diagnosis.
A video on web monitoring / http agent would be great as well .. specifically how to login to a website and do some preprocessing to count urls or even navigate those links and make sure they work ( expected text ). Perhaps making use of the new javascript abilities
Hi I am getting this error multiple time tried to re-installation but same error while old version was working fine for me please look it it. Configuration file error DB type "MYSQL" is not supported by current setup. Possible values POSTGRESQL.
Awesome! Thanks! I'm going to try Zabbix 4.2 right away! I was on Zabbix 2.2 in 2017, Zabbix 3.4 in 2018 and currently on Zabbix 4.06 in 2019. As I'm finishing a significant project, today today 2019-04-02_0526 SourceForge.net advises there is a latest Zabbix-4.2.0.tar.gz released on 2019-04-01. lolol Dmitry Lambert, great tutorials! Oh yeah, how about SNMP for feeding a Network Management Control Center (NMCC)? For Alerting and Remediation. And what about Performance Monitoring, in Dev and Prod infrastructure systems? Food for thought... Thanks!
Please do a more in depth video on throttling please. How it impacts graphs, triggers, do's/don'ts, etc.
Thank you for such an amazing change.
I like that you are moving towards decentralized processes.
But in my opinion, you also need to work through the server part.
For an example, problems which should be faced:
1 - Zabbix .nodata() trigger from a hosts always work when a proxy crashes. This can be corrected by dependence on a trigger proxy, but I think that this option cannot be adequately implemented for> 1000 hosts. Which is again strange when you transfer the load to the proxy.
2 - HA. Zabbix server is monolithic and does not have built-in cluster support to avoid moments of failure of a DC or one of the playground where it is located, which is rather strange nowadays. This also applies to the database. The only available option is custom scripts, etc.
3 - nested LLDs. For example, there is a server with a database, there are several of them, each has tables, and each has indices. All these things I would like to add to the monitoring for more accurate diagnosis.
Cool to see support for pronetheus format, no more ugly glue code to make it work !
A video on web monitoring / http agent would be great as well .. specifically how to login to a website and do some preprocessing to count urls or even navigate those links and make sure they work ( expected text ). Perhaps making use of the new javascript abilities
Prometheus howto video please .. can't wait to play with 4.2
FYI : zabbix.webex.com/mw3300/mywebex/default.do?nomenu=true&siteurl=zabbix&service=6&rnd=0.8142129235353913&main_url=https%3A%2F%2Fzabbix.webex.com%2Fec3300%2Feventcenter%2Fevent%2FeventAction.do%3FtheAction%3Ddetail%26%26%26EMK%3D4832534b00000004ad450ddd8645e7062281853c5af81be10c52d8125baba1a4c9ebe989bab82a83%26siteurl%3Dzabbix%26confViewID%3D120432465453077982%26encryptTicket%3DSDJTSwAAAAQC5Xms3eR3ccvrP3w0AOQTnCDSxNCwInzFSniZ-32M6A2%26
1282 Pacific base
Hi I am getting this error multiple time tried to re-installation but same error while old version was working fine for me please look it it.
Configuration file error
DB type "MYSQL" is not supported by current setup. Possible values POSTGRESQL.
now i tried with PostgreSQL but still same error.
Awesome! Thanks! I'm going to try Zabbix 4.2 right away! I was on Zabbix 2.2 in 2017, Zabbix 3.4 in 2018 and currently on Zabbix 4.06 in 2019. As I'm finishing a significant project, today today 2019-04-02_0526 SourceForge.net advises there is a latest Zabbix-4.2.0.tar.gz released on 2019-04-01. lolol
Dmitry Lambert, great tutorials!
Oh yeah, how about SNMP for feeding a Network Management Control Center (NMCC)? For Alerting and Remediation.
And what about Performance Monitoring, in Dev and Prod infrastructure systems?
Food for thought...
Thanks!
Bush was supported
2.18
Awesome! Thanks! please I need videos for couchdb2.0, postgressql and application logs monitoring videos
2.11:2.18
Number c+3ed
6.3
Port Change 80:443:8772:
Frankfort
+2
8 c
ужасный инглишь!
Нормальный инглиш.
Good & clear english!