Election of db server engine

[lsantagostini]

Hello, my name is Leonardo Santagostini and im working for a one large Datacenter in Argentina.

My question is wich is the best database engine / database strategy for growing at 1.5M items, nearly 9k hosts and 9.5k nvps

Actually im only monitoring two vmware clusters (9 k hosts 130000 items), i have to monitor: 14 xen clusters, 10 storages and about 20 6500 catalyst cisco. Im using mariadb 10.2 with maxscale in master -> multislave replication. But im concerned that maybe isnt sufficient.

I was thinking of using PostgreSQL with partioning. Cant use physical hosts for DB servers so RTC really sucks.

Hope you can give me some clue.

Yours, Leonardo

[ingus.vilnis]

Hello and welcome to Zabbix forums!

In short - use the database engine you know the best. It does not matter if it is MySQL or PostgreSQL. Without a knowing administrator you will have very poor performance and if any issues will happen then you will have no help. Performance at this level is not significantly different. However, you will need to do lots of administration and tuning on the DB of your size anyways so it is better to use a tool which you can operate properly.

In your case I would personally go with MySQL and from the very beginning use partitioning with a script as described here: http://zabbix.org/wiki/Docs/howto/mysql_partitioning
Since you plan a cluster then MySQL has great Master - Master clustering built in using GTID.

Additionally I have found that googling for issues about MySQL is easier than for Postgres. Hope this helps you with the decision.

Best Regards,
Ingus

[elemarmb]

With a 1TB DB using MySql, I had a lot of problems. I migrated to Postgres about three years ago, since then I not have problems.

[lsantagostini]

Thanks for your reply and comment. Do you use some clustering / replication strategy ?

Leonardo.

[lsantagostini]

Hello and welcome to Zabbix forums!

In short - use the database engine you know the best. It does not matter if it is MySQL or PostgreSQL. Without a knowing administrator you will have very poor performance and if any issues will happen then you will have no help. Performance at this level is not significantly different. However, you will need to do lots of administration and tuning on the DB of your size anyways so it is better to use a tool which you can operate properly.

In your case I would personally go with MySQL and from the very beginning use partitioning with a script as described here: http://zabbix.org/wiki/Docs/howto/mysql_partitioning
Since you plan a cluster then MySQL has great Master - Master clustering built in using GTID.

Additionally I have found that googling for issues about MySQL is easier than for Postgres. Hope this helps you with the decision.

Best Regards,
Ingus

Thanks Ingus !!!

[lsantagostini]

Ok, i will tell you my current setup (non productive yet).

I ve made a mysql innodb cluster consisting in five instances, one rw and 4 ro, with a mysqlrouter and an admin console. For storage ceph was elected.

Two zabbix server, active - passive mode, one ui, and proxies for all =)

I have partitioned most of the history tables.

Kind regards!

[lsantagostini]

Ok, i have one philosophical question.

I put al my zabbix infraestructure in one vlan, and the fronted (ui) on another. I would like to use two keepalived+haproxy to manage incoming connections from proxies.

Is it possible? I say haproxy because is the software i know better.

Thanks so much.

Yours, L

[lsantagostini]

Well well well, after a couple of weeks for setting up the environment, its all working perfect,

But i still notice the slow query x.yyyy sec, "commit" message on server,

I attached the image of the infraestructure for giving you an idea on how i have mounted Zabbix.

OS: Red Hat Enterprise Linux Server release 7.5 (Maipo)
DB: mysql-community-server-5.7.22-1.el7.x86_64
Zabbix:
zabbix-agent-3.4.11-1.el7.x86_64
zabbix-server-mysql-3.4.11-1.el7.x86_64
zabbix-proxy-mysql-3.4.12-1.el7.x86_64

Mysql Configuration, related to perfomance
group_replication_unreachable_majority_timeout = 0
log_error_verbosity=3

binlog_cache_size = 16M
innodb_large_prefix = on
innodb_page_size = 16k
innodb-file-per-table = true
innodb_flush_method = O_DIRECT
innodb_log_buffer_size = 8M
innodb_log_file_size = 1G
innodb_buffer_pool_size = 18G
innodb_doublewrite = 0
innodb_support_xa = 0
innodb_checksums = 0
innodb_buffer_pool_instances = 36
innodb_buffer_pool_chunk_size = 512M
innodb_read_io_threads = 5
innodb_write_io_threads = 5
key_buffer_size = 8M
max_connections = 1024
max_connect_errors = 10
max_allowed_packet = 16M
max_heap_table_size = 64M
query_cache_type = 1
query_cache_limit = 256M
query_cache_min_res_unit = 128M
query_cache_size = 80M
join_buffer_size = 644M
query_cache_min_res_unit = 128M
query_cache_limit = 256M
skip-name-resolve =
thread_cache_size = 32
innodb_io_capacity_max=6000
innodb_io_capacity=3000
# optimizer_switch='index_condition_pushdown=off'
innodb_log_file_size = 1G

FS for mysql: ext4 nobarrier,noatime,nodiratime

History* tables partioned

CEPH test using FIO
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.1%, 64=0.0%, >=64=0.0%
issued : total=r=65536/w=0/d=0, short=r=0/w=0/d=0
latency : target=0, window=0, percentile=100.00%, depth=32
reader2: (groupid=0, jobs=1): err= 0: pid=104979: Tue Sep 11 12:34:25 2018
read : io=262144KB, bw=8428.9KB/s, iops=2107, runt= 31101msec
slat (usec): min=5, max=5105, avg=42.19, stdev=84.93
clat (usec): min=243, max=2146.1K, avg=15132.01, stdev=71741.78
lat (usec): min=360, max=2146.2K, avg=15174.89, stdev=71742.41
clat percentiles (usec):
| 1.00th=[ 524], 5.00th=[ 692], 10.00th=[ 828], 20.00th=[ 1064],
| 30.00th=[ 1336], 40.00th=[ 1656], 50.00th=[ 2096], 60.00th=[ 2704],
| 70.00th=[ 3600], 80.00th=[ 5408], 90.00th=[15936], 95.00th=[62208],
| 99.00th=[268288], 99.50th=[391168], 99.90th=[1056768], 99.95th=[1466368],
| 99.99th=[1875968]
bw (KB /s): min= 1196, max=17720, per=100.00%, avg=8455.83, stdev=3521.97
lat (usec) : 250=0.01%, 500=0.63%, 750=6.47%, 1000=10.23%
lat (msec) : 2=30.81%, 4=24.83%, 10=14.53%, 20=3.47%, 50=3.32%
lat (msec) : 100=2.11%, 250=2.38%, 500=0.87%, 750=0.14%, 1000=0.09%
lat (msec) : 2000=0.11%, >=2000=0.01%
cpu : usr=3.43%, sys=12.27%, ctx=30368, majf=0, minf=58
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=100.0%, >=64=0.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.1%, 64=0.0%, >=64=0.0%
issued : total=r=65536/w=0/d=0, short=r=0/w=0/d=0
latency : target=0, window=0, percentile=100.00%, depth=32
updater1: (groupid=0, jobs=1): err= 0: pid=104980: Tue Sep 11 12:34:25 2018
read : io=16416KB, bw=129156B/s, iops=31, runt=130152msec
slat (usec): min=12, max=3039, avg=158.49, stdev=267.73
clat (usec): min=373, max=1413.5K, avg=8052.75, stdev=47807.51
lat (usec): min=397, max=1413.6K, avg=8213.24, stdev=47804.68
clat percentiles (usec):
| 1.00th=[ 502], 5.00th=[ 620], 10.00th=[ 700], 20.00th=[ 844],
| 30.00th=[ 972], 40.00th=[ 1112], 50.00th=[ 1272], 60.00th=[ 1512],
| 70.00th=[ 1848], 80.00th=[ 2576], 90.00th=[ 5856], 95.00th=[19328],
| 99.00th=[150528], 99.50th=[280576], 99.90th=[602112], 99.95th=[872448],
| 99.99th=[1417216]
bw (KB /s): min= 4, max= 358, per=3.27%, avg=135.91, stdev=77.72
write: io=16352KB, bw=128653B/s, iops=31, runt=130152msec
slat (usec): min=14, max=886498, avg=2728.71, stdev=24876.24
clat (msec): min=1, max=1645, avg=21.28, stdev=55.45
lat (msec): min=1, max=1645, avg=24.01, stdev=60.65
clat percentiles (usec):
| 1.00th=[ 1928], 5.00th=[ 2480], 10.00th=[ 3024], 20.00th=[ 4256],
| 30.00th=[ 5856], 40.00th=[ 7520], 50.00th=[ 9792], 60.00th=[12736],
| 70.00th=[16320], 80.00th=[23424], 90.00th=[37632], 95.00th=[68096],
| 99.00th=[230400], 99.50th=[313344], 99.90th=[634880], 99.95th=[757760],
| 99.99th=[1646592]
bw (KB /s): min= 5, max= 343, per=6.30%, avg=134.66, stdev=70.36
lat (usec) : 500=0.48%, 750=6.13%, 1000=9.73%
lat (msec) : 2=20.94%, 4=15.23%, 10=19.09%, 20=14.12%, 50=9.41%
lat (msec) : 100=2.33%, 250=1.83%, 500=0.50%, 750=0.13%, 1000=0.02%
lat (msec) : 2000=0.05%
cpu : usr=0.77%, sys=1.63%, ctx=8518, majf=0, minf=27
IO depths : 1=99.6%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.2%, 32=0.1%, >=64=0.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
issued : total=r=4104/w=4088/d=0, short=r=0/w=0/d=0
latency : target=0, window=0, percentile=100.00%, depth=32

Run status group 0 (all jobs):
READ: io=540704KB, aggrb=4154KB/s, minb=126KB/s, maxb=10575KB/s, mint=24787msec, maxt=130152msec
WRITE: io=278496KB, aggrb=2139KB/s, minb=125KB/s, maxb=2499KB/s, mint=104866msec, maxt=130152msec

Disk stats (read/write):
dm-1: ios=135158/138449, merge=0/0, ticks=1774758/5758244, in_queue=7561360, util=100.00%, aggrios=135179/92211, aggrmerge=0/46403, aggrticks=1777235/3970816, aggrin_queue=5754662, aggrutil=100.00%
rbd0: ios=135179/92211, merge=0/46403, ticks=1777235/3970816, in_queue=5754662, util=100.00%


And zabbix server conf file
# This is a configuration file for Zabbix server daemon
# To get more information about Zabbix, visit http://www.zabbix.com

############ GENERAL PARAMETERS #################

### Option: ListenPort
# Listen port for trapper.
#
# Mandatory: no
# Range: 1024-32767
# Default:
ListenPort=10051

### Option: SourceIP
# Source IP address for outgoing connections.
#
# Mandatory: no
# Default:
# SourceIP=

### Option: LogType
# Specifies where log messages are written to:
# system - syslog
# file - file specified with LogFile parameter
# console - standard output
#
# Mandatory: no
# Default:
# LogType=file

### Option: LogFile
# Log file name for LogType 'file' parameter.
#
# Mandatory: no
# Default:
# LogFile=

LogFile=/var/log/zabbix/zabbix_server.log

### Option: LogFileSize
# Maximum size of log file in MB.
# 0 - disable automatic log rotation.
#
# Mandatory: no
# Range: 0-1024
# Default:
# LogFileSize=1

LogFileSize=10

### Option: DebugLevel
# Specifies debug level:
# 0 - basic information about starting and stopping of Zabbix processes
# 1 - critical information
# 2 - error information
# 3 - warnings
# 4 - for debugging (produces lots of information)
# 5 - extended debugging (produces even more information)
#
# Mandatory: no
# Range: 0-5
# Default:
# DebugLevel=5

### Option: PidFile
# Name of PID file.
#
# Mandatory: no
# Default:
# PidFile=/tmp/zabbix_server.pid

PidFile=/var/run/zabbix/zabbix_server.pid

### Option: SocketDir
# IPC socket directory.
# Directory to store IPC sockets used by internal Zabbix services.
#
# Mandatory: no
# Default:
# SocketDir=/tmp

SocketDir=/var/run/zabbix

### Option: DBHost
# Database host name.
# If set to localhost, socket is used for MySQL.
# If set to empty string, socket is used for PostgreSQL.
#
# Mandatory: no
# Default:
DBHost=<mysql router>
DBName=zabbix
DBUser=zabbix
DBPassword=<>
DBPort=6446

### Option: HistoryStorageURL
# History storage HTTP[S] URL.
#
# Mandatory: no
# Default:
# HistoryStorageURL=

### Option: HistoryStorageTypes
# Comma separated list of value types to be sent to the history storage.
#
# Mandatory: no
# Default:
# HistoryStorageTypes=uint,dbl,str,log,text

############ ADVANCED PARAMETERS ################

### Option: StartPollers
# Number of pre-forked instances of pollers.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartPollers=5

### Option: StartIPMIPollers
# Number of pre-forked instances of IPMI pollers.
# The IPMI manager process is automatically started when at least one IPMI poller is started.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartIPMIPollers=0

### Option: StartPreprocessors
# Number of pre-forked instances of preprocessing workers.
# The preprocessing manager process is automatically started when preprocessor worker is started.
#
# Mandatory: no
# Range: 1-1000
# Default:
# StartPreprocessors=3

### Option: StartPollersUnreachable
# Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).
# At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers
# are started.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartPollersUnreachable=1

### Option: StartTrappers
# Number of pre-forked instances of trappers.
# Trappers accept incoming connections from Zabbix sender, active agents and active proxies.
# At least one trapper process must be running to display server availability and view queue
# in the frontend.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartTrappers=5

### Option: StartPingers
# Number of pre-forked instances of ICMP pingers.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartPingers=1

### Option: StartDiscoverers
# Number of pre-forked instances of discoverers.
#
# Mandatory: no
# Range: 0-250
# Default:
# StartDiscoverers=1

### Option: StartHTTPPollers
# Number of pre-forked instances of HTTP pollers.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartHTTPPollers=1

### Option: StartTimers
# Number of pre-forked instances of timers.
# Timers process time-based trigger functions and maintenance periods.
# Only the first timer process handles the maintenance periods.
#
# Mandatory: no
# Range: 1-1000
# Default:
# StartTimers=1

### Option: StartEscalators
# Number of pre-forked instances of escalators.
#
# Mandatory: no
# Range: 0-100
# Default:
# StartEscalators=1

### Option: StartAlerters
# Number of pre-forked instances of alerters.
# Alerters send the notifications created by action operations.
#
# Mandatory: no
# Range: 0-100
# Default:
# StartAlerters=3

### Option: JavaGateway
# IP address (or hostname) of Zabbix Java gateway.
# Only required if Java pollers are started.
#
# Mandatory: no
# Default:
# JavaGateway=

### Option: JavaGatewayPort
# Port that Zabbix Java gateway listens on.
#
# Mandatory: no
# Range: 1024-32767
# Default:
# JavaGatewayPort=10052

### Option: StartJavaPollers
# Number of pre-forked instances of Java pollers.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartJavaPollers=0

### Option: StartVMwareCollectors
# Number of pre-forked vmware collector instances.
#
# Mandatory: no
# Range: 0-250
# Default:
StartVMwareCollectors=20

### Option: VMwareFrequency
# How often Zabbix will connect to VMware service to obtain a new data.
#
# Mandatory: no
# Range: 10-86400
# Default:
# VMwareFrequency=60

### Option: VMwarePerfFrequency
# How often Zabbix will connect to VMware service to obtain performance data.
#
# Mandatory: no
# Range: 10-86400
# Default:
# VMwarePerfFrequency=60

### Option: VMwareCacheSize
# Size of VMware cache, in bytes.
# Shared memory size for storing VMware data.
# Only used if VMware collectors are started.
#
# Mandatory: no
# Range: 256K-2G
# Default:
VMwareCacheSize=80M

### Option: VMwareTimeout
# Specifies how many seconds vmware collector waits for response from VMware service.
#
# Mandatory: no
# Range: 1-300
# Default:
# VMwareTimeout=10

### Option: SNMPTrapperFile
# Temporary file used for passing data from SNMP trap daemon to the server.
# Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file.
#
# Mandatory: no
# Default:
# SNMPTrapperFile=/tmp/zabbix_traps.tmp

SNMPTrapperFile=/var/log/snmptrap/snmptrap.log

### Option: StartSNMPTrapper
# If 1, SNMP trapper process is started.
#
# Mandatory: no
# Range: 0-1
# Default:
# StartSNMPTrapper=0

### Option: ListenIP
# List of comma delimited IP addresses that the trapper should listen on.
# Trapper will listen on all network interfaces if this parameter is missing.
#
# Mandatory: no
# Default:
ListenIP=0.0.0.0

# ListenIP=127.0.0.1

### Option: HousekeepingFrequency
# How often Zabbix will perform housekeeping procedure (in hours).
# Housekeeping is removing outdated information from the database.
# To prevent Housekeeper from being overloaded, no more than 4 times HousekeepingFrequency
# hours of outdated information are deleted in one housekeeping cycle, for each item.
# To lower load on server startup housekeeping is postponed for 30 minutes after server start.
# With HousekeepingFrequency=0 the housekeeper can be only executed using the runtime control option.
# In this case the period of outdated information deleted in one housekeeping cycle is 4 times the
# period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.
#
# Mandatory: no
# Range: 0-24
# Default:
# HousekeepingFrequency=1

### Option: MaxHousekeeperDelete
# The table "housekeeper" contains "tasks" for housekeeping procedure in the format:
# [housekeeperid], [tablename], [field], [value].
# No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])
# will be deleted per one task in one housekeeping cycle.
# SQLite3 does not use this parameter, deletes all corresponding rows without a limit.
# If set to 0 then no limit is used at all. In this case you must know what you are doing!
#
# Mandatory: no
# Range: 0-1000000
# Default:
# MaxHousekeeperDelete=5000

### Option: CacheSize
# Size of configuration cache, in bytes.
# Shared memory size for storing host, item and trigger data.
#
# Mandatory: no
# Range: 128K-8G
# Default:
CacheSize=1G

### Option: CacheUpdateFrequency
# How often Zabbix will perform update of configuration cache, in seconds.
#
# Mandatory: no
# Range: 1-3600
# Default:
# CacheUpdateFrequency=60

### Option: StartDBSyncers
# Number of pre-forked instances of DB Syncers.
#
# Mandatory: no
# Range: 1-100
# Default:
# StartDBSyncers=4

### Option: HistoryCacheSize
# Size of history cache, in bytes.
# Shared memory size for storing history data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
HistoryCacheSize=256M

### Option: HistoryIndexCacheSize
# Size of history index cache, in bytes.
# Shared memory size for indexing history cache.
#
# Mandatory: no
# Range: 128K-2G
# Default:
HistoryIndexCacheSize=24M

### Option: TrendCacheSize
# Size of trend cache, in bytes.
# Shared memory size for storing trends data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
TrendCacheSize=40M

### Option: ValueCacheSize
# Size of history value cache, in bytes.
# Shared memory size for caching item history data requests.
# Setting to 0 disables value cache.
#
# Mandatory: no
# Range: 0,128K-64G
# Default:
ValueCacheSize=36M

### Option: Timeout
# Specifies how long we wait for agent, SNMP device or external check (in seconds).
#
# Mandatory: no
# Range: 1-30
# Default:
# Timeout=3

Timeout=4

### Option: TrapperTimeout
# Specifies how many seconds trapper may spend processing new data.
#
# Mandatory: no
# Range: 1-300
# Default:
# TrapperTimeout=300

### Option: UnreachablePeriod
# After how many seconds of unreachability treat a host as unavailable.
#
# Mandatory: no
# Range: 1-3600
# Default:
# UnreachablePeriod=45

### Option: UnavailableDelay
# How often host is checked for availability during the unavailability period, in seconds.
#
# Mandatory: no
# Range: 1-3600
# Default:
# UnavailableDelay=60

### Option: UnreachableDelay
# How often host is checked for availability during the unreachability period, in seconds.
#
# Mandatory: no
# Range: 1-3600
# Default:
# UnreachableDelay=15

### Option: AlertScriptsPath
# Full path to location of custom alert scripts.
# Default depends on compilation options.
#
# Mandatory: no
# Default:
# AlertScriptsPath=${datadir}/zabbix/alertscripts

AlertScriptsPath=/usr/lib/zabbix/alertscripts

### Option: ExternalScripts
# Full path to location of external scripts.
# Default depends on compilation options.
#
# Mandatory: no
# Default:
# ExternalScripts=${datadir}/zabbix/externalscripts

ExternalScripts=/usr/lib/zabbix/externalscripts

### Option: FpingLocation
# Location of fping.
# Make sure that fping binary has root ownership and SUID flag set.
#
# Mandatory: no
# Default:
# FpingLocation=/usr/sbin/fping

### Option: Fping6Location
# Location of fping6.
# Make sure that fping6 binary has root ownership and SUID flag set.
# Make empty if your fping utility is capable to process IPv6 addresses.
#
# Mandatory: no
# Default:
# Fping6Location=/usr/sbin/fping6

### Option: SSHKeyLocation
# Location of public and private keys for SSH checks and actions.
#
# Mandatory: no
# Default:
# SSHKeyLocation=

### Option: LogSlowQueries
# How long a database query may take before being logged (in milliseconds).
# Only works if DebugLevel set to 3, 4 or 5.
# 0 - don't log slow queries.
#
# Mandatory: no
# Range: 1-3600000
# Default:
# LogSlowQueries=0

LogSlowQueries=3000

### Option: TmpDir
# Temporary directory.
#
# Mandatory: no
# Default:
# TmpDir=/tmp

### Option: StartProxyPollers
# Number of pre-forked instances of pollers for passive proxies.
#
# Mandatory: no
# Range: 0-250
# Default:
# StartProxyPollers=1

### Option: ProxyConfigFrequency
# How often Zabbix Server sends configuration data to a Zabbix Proxy in seconds.
# This parameter is used only for proxies in the passive mode.
#
# Mandatory: no
# Range: 1-3600*24*7
# Default:
# ProxyConfigFrequency=3600

### Option: ProxyDataFrequency
# How often Zabbix Server requests history data from a Zabbix Proxy in seconds.
# This parameter is used only for proxies in the passive mode.
#
# Mandatory: no
# Range: 1-3600
# Default:
# ProxyDataFrequency=1

### Option: AllowRoot
# Allow the server to run as 'root'. If disabled and the server is started by 'root', the server
# will try to switch to the user specified by the User configuration option instead.
# Has no effect if started under a regular user.
# 0 - do not allow
# 1 - allow
#
# Mandatory: no
# Default:
AllowRoot=0

### Option: User
# Drop privileges to a specific, existing user on the system.
# Only has effect if run as 'root' and AllowRoot is disabled.
#
# Mandatory: no
# Default:
# User=zabbix

### Option: Include
# You may include individual files or all files in a directory in the configuration file.
# Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
#
# Mandatory: no
# Default:
# Include=

# Include=/usr/local/etc/zabbix_server.general.conf
# Include=/usr/local/etc/zabbix_server.conf.d/
# Include=/usr/local/etc/zabbix_server.conf.d/*.conf

### Option: SSLCertLocation
# Location of SSL client certificates.
# This parameter is used only in web monitoring.
#
# Mandatory: no
# Default:
# SSLCertLocation=${datadir}/zabbix/ssl/certs

### Option: SSLKeyLocation
# Location of private keys for SSL client certificates.
# This parameter is used only in web monitoring.
#
# Mandatory: no
# Default:
# SSLKeyLocation=${datadir}/zabbix/ssl/keys

### Option: SSLCALocation
# Override the location of certificate authority (CA) files for SSL server certificate verification.
# If not set, system-wide directory will be used.
# This parameter is used only in web monitoring and SMTP authentication.
#
# Mandatory: no
# Default:
# SSLCALocation=

####### LOADABLE MODULES #######

### Option: LoadModulePath
# Full path to location of server modules.
# Default depends on compilation options.
#
# Mandatory: no
# Default:
# LoadModulePath=${libdir}/modules

### Option: LoadModule
# Module to load at server startup. Modules are used to extend functionality of the server.
# Format: LoadModule=<module.so>
# The modules must be located in directory specified by LoadModulePath.
# It is allowed to include multiple LoadModule parameters.
#
# Mandatory: no
# Default:
# LoadModule=

####### TLS-RELATED PARAMETERS #######

### Option: TLSCAFile
# Full pathname of a file containing the top-level CA(s) certificates for
# peer certificate verification.
#
# Mandatory: no
# Default:
# TLSCAFile=

### Option: TLSCRLFile
# Full pathname of a file containing revoked certificates.
#
# Mandatory: no
# Default:
# TLSCRLFile=

### Option: TLSCertFile
# Full pathname of a file containing the server certificate or certificate chain.
#
# Mandatory: no
# Default:
# TLSCertFile=

### Option: TLSKeyFile
# Full pathname of a file containing the server private key.
#
# Mandatory: no
# Default:
# TLSKeyFile=

This is the slow query from zabbix server
47552:20180911:123722.137 slow query: 3.144245 sec, "commit;"
47521:20180911:123722.139 slow query: 3.149223 sec, "commit;"
47518:20180911:123722.221 slow query: 3.022553 sec, "commit;"

All db's server are 10 vcpu and 24gb ram

zabbix server is 4 vcpu and 8gb

If you can give me some clue, i would really appreciate. Zabbix now is a productive system

Important values

Number of hosts (enabled/disabled/templates)	4132	4030 / 20 / 82
Number of items (enabled/disabled/not supported)	149941	114668 / 879 / 34394
Number of triggers (enabled/disabled [problem/ok])	3913	3883 / 30 [39 / 3844]
Number of users (online)	5	1
Required server performance, new values per second	2192.03

Sorry for the giant email.

[Donaldcotton]

I would suggest you go with lsantagostini the only answer that I like.