Hello everyone,
kindly asking you for the help and best practises about the tuning of zabbix server and proxies.
What have I got:
server side : 6 GB RAM, 4 cores from Xeon CEP E5620 2.40 GHz , zabbix environment is working under docker containers (server 5.4.2 + postgreSLQ + nginX), 100 GB HDD
proxies side (working in active mode, using sqllite3) : 4 GB RAM, 2 processors Xeon CPU E5-2620 v3, 10GB HDD
PostgreSQL conf tune is the following (if not listed -> default values)
Server conf (if not listed -> default values)
Proxies conf (if not listed -> default values) :
From the server graphs I can see the following information about the server status:


It looks ok, but the server performance is horrible :

I'm using some LLD discovery scripts to detect the network interfaces parameters and status of Wireless APs at the controller side. From time to time I'm facing very strange situation among the items : using the same discovery rule some items are working fine, and in the same time others not :


Kindly asking for your help!!
With best regards, Max.
kindly asking you for the help and best practises about the tuning of zabbix server and proxies.
What have I got:
server side : 6 GB RAM, 4 cores from Xeon CEP E5620 2.40 GHz , zabbix environment is working under docker containers (server 5.4.2 + postgreSLQ + nginX), 100 GB HDD
proxies side (working in active mode, using sqllite3) : 4 GB RAM, 2 processors Xeon CPU E5-2620 v3, 10GB HDD
PostgreSQL conf tune is the following (if not listed -> default values)
max_connections = 198
shared_buffers = 1536MB
effective_cache_size = 4608MB
maintenance_work_mem = 768MB
checkpoint_completion_target = 0.9
wal_buffers = 16MB
default_statistics_target = 500
random_page_cost = 4
effective_io_concurrency = 2
work_mem = 1985kB
min_wal_size = 4GB
max_wal_size = 16GB
max_worker_processes = 4
max_parallel_workers_per_gather = 2
max_parallel_workers = 4
max_parallel_maintenance_workers = 2
shared_buffers = 1536MB
effective_cache_size = 4608MB
maintenance_work_mem = 768MB
checkpoint_completion_target = 0.9
wal_buffers = 16MB
default_statistics_target = 500
random_page_cost = 4
effective_io_concurrency = 2
work_mem = 1985kB
min_wal_size = 4GB
max_wal_size = 16GB
max_worker_processes = 4
max_parallel_workers_per_gather = 2
max_parallel_workers = 4
max_parallel_maintenance_workers = 2
ZBX_STARTPOLLERS: 90
ZBX_STARTPREPROCESSORS: 60
ZBX_STARTPOLLERSUNREACHABLE: 30
ZBX_STARTPINGERS: 100
ZBX_TIMEOUT: 30
ZBX_IPMIPOLLERS: 10
ZBX_STARTTRAPPERS: 20
ZBX_STARTDBSYNCERS: 5
ZBX_CACHESIZE: 128M
ZBX_VALUECACHESIZE: 128M
ZBX_HISTORYCACHESIZE: 60M
ZBX_HISTORYINDEXCACHESIZE: 30M
ZBX_TRENDCACHESIZE: 30M
ZBX_MAXHOUSEKEEPERDELETE: 10000
ZBX_STARTPREPROCESSORS: 60
ZBX_STARTPOLLERSUNREACHABLE: 30
ZBX_STARTPINGERS: 100
ZBX_TIMEOUT: 30
ZBX_IPMIPOLLERS: 10
ZBX_STARTTRAPPERS: 20
ZBX_STARTDBSYNCERS: 5
ZBX_CACHESIZE: 128M
ZBX_VALUECACHESIZE: 128M
ZBX_HISTORYCACHESIZE: 60M
ZBX_HISTORYINDEXCACHESIZE: 30M
ZBX_TRENDCACHESIZE: 30M
ZBX_MAXHOUSEKEEPERDELETE: 10000
DBName=/tmp/zabbix_proxy.db
StartPollers=40
StartPollersUnreachable=5
StartTrappers=10
StartPingers=10
CacheSize=124M
StartDBSyncers=10
HistoryCacheSize=32M
HistoryIndexCacheSize=12M
Timeout=15
StartPollers=40
StartPollersUnreachable=5
StartTrappers=10
StartPingers=10
CacheSize=124M
StartDBSyncers=10
HistoryCacheSize=32M
HistoryIndexCacheSize=12M
Timeout=15
It looks ok, but the server performance is horrible :
I'm using some LLD discovery scripts to detect the network interfaces parameters and status of Wireless APs at the controller side. From time to time I'm facing very strange situation among the items : using the same discovery rule some items are working fine, and in the same time others not :
Kindly asking for your help!!
With best regards, Max.
Comment