Nagios Support Forum

Hello everyone,
We have two Nagios XI instances running in a virtualized environment. Since enabling NRDP to send data from one Nagios XI to the other, the receiving machine has started generating several performance alerts.
The receiving VM is high resources with 24 CPUs and 32 GB of RAM. However, performance appears to be degrading despite these resources.
you'll find the screenshot attached with the generated alerts to provide a clearer picture of the issue.
We would appreciate any advice on how to optimize or improve the performance of the receiving Nagios XI in this NRDP setup.

Hello,

It sounds like the issue with your NagiosXI instance isn't resource based but rather purely something with database configurations. This is likely because of the amount of data being passed to the XI instance from NRDP, and the disk doesn't have enough time to process all the information. A recommended script for this that I found is mysqltuner.pl (https://github.com/major/MySQLTuner-perl) which can help give configuration advice (Note: you may need to install a few perl packages). I'm not an expert when it comes to database tuning, but hopefully this helps get you in the right direction.

If you have any more questions I'd be happy to try and help.

- Caleb

Hi,
here the output:
[root@nagios tmp]# ./mysqltuner.pl
>> MySQLTuner 2.7.0
* Jean-Marie Renouard <[email protected]>
* Major Hayden <[email protected]>
>> Bug reports, feature requests, and downloads at http://mysqltuner.pl/
>> Run with '--help' for additional options and output filtering

ℹ Skipped version check for MySQLTuner script
ℹ Using mysql to check login
Please enter your MySQL administrative login: root
Please enter your MySQL administrative password: ✔ Operating on 64-bit architecture

-------- Storage Engine Statistics -----------------------------------------------------------------
ℹ Status: +ARCHIVE +BLACKHOLE +CSV -FEDERATED +InnoDB +MEMORY +MRG_MYISAM +MyISAM +PERFORMANCE_SCHEMA
ℹ Data in InnoDB tables: 802.0M (Tables: 122)
ℹ Data in MyISAM tables: 361.8M (Tables: 64)
✔ Total fragmented tables: 0

✔ Currently running supported MySQL version 8.0.41

-------- Log file Recommendations ------------------------------------------------------------------
✔ Log file /var/log/mysql/mysqld.log exists
ℹ Log file: /var/log/mysql/mysqld.log (88M)
✔ Log file /var/log/mysql/mysqld.log is not empty
✘ Log file /var/log/mysql/mysqld.log is bigger than 32 MB
✔ Log file /var/log/mysql/mysqld.log is readable.
✘ /var/log/mysql/mysqld.log contains 289 warning(s).
✘ /var/log/mysql/mysqld.log contains 16536 error(s).
ℹ 24 start(s) detected in /var/log/mysql/mysqld.log
ℹ 1) 2025-08-28T12:55:41.694902Z 0 [System] [MY-010931] [Server] /usr/libexec/mysqld: ready for connections. Version: '8.0.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution.
ℹ 2) 2025-08-28T12:55:41.694830Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/lib/mysql/mysqlx.sock
ℹ 3) 2025-08-28T10:53:09.993494Z 0 [System] [MY-010931] [Server] /usr/libexec/mysqld: ready for connections. Version: '8.0.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution.
ℹ 4) 2025-08-28T10:53:09.993376Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/lib/mysql/mysqlx.sock
ℹ 5) 2025-07-24T09:40:50.953204Z 0 [System] [MY-010931] [Server] /usr/libexec/mysqld: ready for connections. Version: '8.0.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution.
ℹ 6) 2025-07-24T09:40:50.953088Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/lib/mysql/mysqlx.sock
ℹ 7) 2025-06-24T14:10:01.447937Z 0 [System] [MY-010931] [Server] /usr/libexec/mysqld: ready for connections. Version: '8.0.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution.
ℹ 8) 2025-06-24T14:10:01.447601Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/lib/mysql/mysqlx.sock
ℹ 9) 2025-06-11T09:24:05.581367Z 0 [System] [MY-010931] [Server] /usr/libexec/mysqld: ready for connections. Version: '8.0.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution.
ℹ 10) 2025-06-11T09:24:05.581283Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/lib/mysql/mysqlx.sock
ℹ 12 shutdown(s) detected in /var/log/mysql/mysqld.log
ℹ 1) 2025-08-28T12:55:24.036282Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.41) Source distribution.
ℹ 2) 2025-08-28T10:52:45.203900Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.41) Source distribution.
ℹ 3) 2025-07-24T09:40:51.014046Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.41) Source distribution.
ℹ 4) 2025-06-24T14:09:41.024745Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.41) Source distribution.
ℹ 5) 2025-06-11T09:23:45.212156Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.36) Source distribution.
ℹ 6) 2025-06-09T12:03:17.575137Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.36) Source distribution.
ℹ 7) 2025-06-09T11:44:32.103415Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.36) Source distribution.
ℹ 8) 2025-05-30T08:06:34.978206Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.36) Source distribution.
ℹ 9) 2025-05-28T14:55:28.315981Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.36) Source distribution.
ℹ 10) 2025-03-26T14:20:51.959113Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.36) Source distribution.

-------- Analysis Performance Metrics --------------------------------------------------------------
ℹ innodb_stats_on_metadata: OFF
✔ No stat updates during querying INFORMATION_SCHEMA.

-------- Views Metrics -----------------------------------------------------------------------------

-------- Triggers Metrics --------------------------------------------------------------------------

-------- Routines Metrics --------------------------------------------------------------------------

-------- Security Recommendations ------------------------------------------------------------------
ℹ Source distribution - 8.0.41
ℹ Skipped due to unsupported feature for MySQL 8.0+

-------- CVE Security Recommendations --------------------------------------------------------------
ℹ Skipped due to --cvefile option undefined

-------- Performance Metrics -----------------------------------------------------------------------
ℹ Up for: 12d 23h 40m 15s (461M q [411.096 qps], 849K conn, TX: 160G, RX: 67G)
ℹ Reads / Writes: 59% / 41%
ℹ Binary logging is enabled (GTID MODE: OFF)
ℹ Physical Memory : 31.1G
ℹ Max MySQL memory : 33.3G
ℹ Other process memory: 0B
ℹ Total buffers: 240.0M global + 33.7M per thread (1000 max threads)
ℹ Performance_schema Max memory usage: 233M
ℹ Galera GCache Max memory usage: 0B
✔ Maximum reached memory usage: 5.6G (17.89% of installed RAM)
✘ Maximum possible memory usage: 33.3G (107.31% of installed RAM)
✘ Overall possible memory usage with other process exceeded memory
✔ Slow queries: 0% (1K/461M)
✔ Highest usage of available connections: 15% (155/1000)
✔ Aborted connections: 0.00% (2/849955)
✘ Name resolution is active: a reverse name resolution is made for each new connection which can reduce performance
ℹ Query cache has been removed since MySQL 8.0
✔ Sorts requiring temporary tables: 0% (6 temp sorts / 1M sorts)
✘ Joins performed without indexes: 8183
✔ Temporary tables created on disk: 0% (112 on disk / 42K total)
✔ Thread cache hit rate: 85% (122K created / 849K connections)
✔ Table cache hit rate: 85% (414M hits / 486M requests)
✘ table_definition_cache (416) is less than number of tables (513)
✔ Open file limit used: 0% (20/10K)
✔ Table locks acquired immediately: 99% (439M immediate / 441M locks)
✔ Binlog cache memory access: 99.99% (2677081 Memory / 2677348 Total)

-------- Performance schema ------------------------------------------------------------------------
ℹ Performance_schema is activated.
ℹ Memory used by Performance_schema: 233.1M
ℹ Sys schema is installed.

-------- ThreadPool Metrics ------------------------------------------------------------------------
ℹ ThreadPool stat is disabled.

-------- MyISAM Metrics ----------------------------------------------------------------------------
✘ Consider migrating 64 following tables to InnoDB:
ℹ * InnoDB migration request for `nagios`.`nagios_acknowledgements` Table: ALTER TABLE `nagios`.`nagios_acknowledgements` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_commands` Table: ALTER TABLE `nagios`.`nagios_commands` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_commenthistory` Table: ALTER TABLE `nagios`.`nagios_commenthistory` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_comments` Table: ALTER TABLE `nagios`.`nagios_comments` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_configfiles` Table: ALTER TABLE `nagios`.`nagios_configfiles` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_configfilevariables` Table: ALTER TABLE `nagios`.`nagios_configfilevariables` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_contact_addresses` Table: ALTER TABLE `nagios`.`nagios_contact_addresses` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_contact_notificationcommands` Table: ALTER TABLE `nagios`.`nagios_contact_notificationcommands` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_contactgroup_members` Table: ALTER TABLE `nagios`.`nagios_contactgroup_members` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_contactgroups` Table: ALTER TABLE `nagios`.`nagios_contactgroups` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_contactnotificationmethods` Table: ALTER TABLE `nagios`.`nagios_contactnotificationmethods` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_contactnotifications` Table: ALTER TABLE `nagios`.`nagios_contactnotifications` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_contacts` Table: ALTER TABLE `nagios`.`nagios_contacts` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_contactstatus` Table: ALTER TABLE `nagios`.`nagios_contactstatus` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_customvariables` Table: ALTER TABLE `nagios`.`nagios_customvariables` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_customvariablestatus` Table: ALTER TABLE `nagios`.`nagios_customvariablestatus` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_dbversion` Table: ALTER TABLE `nagios`.`nagios_dbversion` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_downtimehistory` Table: ALTER TABLE `nagios`.`nagios_downtimehistory` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_eventhandlers` Table: ALTER TABLE `nagios`.`nagios_eventhandlers` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_externalcommands` Table: ALTER TABLE `nagios`.`nagios_externalcommands` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_flappinghistory` Table: ALTER TABLE `nagios`.`nagios_flappinghistory` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_host_contactgroups` Table: ALTER TABLE `nagios`.`nagios_host_contactgroups` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_host_contacts` Table: ALTER TABLE `nagios`.`nagios_host_contacts` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_host_parenthosts` Table: ALTER TABLE `nagios`.`nagios_host_parenthosts` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_hostchecks` Table: ALTER TABLE `nagios`.`nagios_hostchecks` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_hostdependencies` Table: ALTER TABLE `nagios`.`nagios_hostdependencies` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_hostescalation_contactgroups` Table: ALTER TABLE `nagios`.`nagios_hostescalation_contactgroups` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_hostescalation_contacts` Table: ALTER TABLE `nagios`.`nagios_hostescalation_contacts` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_hostescalations` Table: ALTER TABLE `nagios`.`nagios_hostescalations` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_hostgroup_members` Table: ALTER TABLE `nagios`.`nagios_hostgroup_members` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_hostgroups` Table: ALTER TABLE `nagios`.`nagios_hostgroups` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_hosts` Table: ALTER TABLE `nagios`.`nagios_hosts` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_hoststatus` Table: ALTER TABLE `nagios`.`nagios_hoststatus` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_instances` Table: ALTER TABLE `nagios`.`nagios_instances` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_logentries` Table: ALTER TABLE `nagios`.`nagios_logentries` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_notifications` Table: ALTER TABLE `nagios`.`nagios_notifications` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_objects` Table: ALTER TABLE `nagios`.`nagios_objects` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_processevents` Table: ALTER TABLE `nagios`.`nagios_processevents` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_programstatus` Table: ALTER TABLE `nagios`.`nagios_programstatus` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_rebalance_affected_instances` Table: ALTER TABLE `nagios`.`nagios_rebalance_affected_instances` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_regions` Table: ALTER TABLE `nagios`.`nagios_regions` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_runtimevariables` Table: ALTER TABLE `nagios`.`nagios_runtimevariables` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_scheduleddowntime` Table: ALTER TABLE `nagios`.`nagios_scheduleddowntime` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_service_contactgroups` Table: ALTER TABLE `nagios`.`nagios_service_contactgroups` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_service_contacts` Table: ALTER TABLE `nagios`.`nagios_service_contacts` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_service_parentservices` Table: ALTER TABLE `nagios`.`nagios_service_parentservices` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_servicechecks` Table: ALTER TABLE `nagios`.`nagios_servicechecks` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_servicedependencies` Table: ALTER TABLE `nagios`.`nagios_servicedependencies` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_serviceescalation_contactgroups` Table: ALTER TABLE `nagios`.`nagios_serviceescalation_contactgroups` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_serviceescalation_contacts` Table: ALTER TABLE `nagios`.`nagios_serviceescalation_contacts` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_serviceescalations` Table: ALTER TABLE `nagios`.`nagios_serviceescalations` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_servicegroup_members` Table: ALTER TABLE `nagios`.`nagios_servicegroup_members` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_servicegroups` Table: ALTER TABLE `nagios`.`nagios_servicegroups` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_services` Table: ALTER TABLE `nagios`.`nagios_services` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_servicestatus` Table: ALTER TABLE `nagios`.`nagios_servicestatus` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_statehistory` Table: ALTER TABLE `nagios`.`nagios_statehistory` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_systemcommands` Table: ALTER TABLE `nagios`.`nagios_systemcommands` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_timedeventqueue` Table: ALTER TABLE `nagios`.`nagios_timedeventqueue` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_timedevents` Table: ALTER TABLE `nagios`.`nagios_timedevents` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_timeperiod_exception_timeranges` Table: ALTER TABLE `nagios`.`nagios_timeperiod_exception_timeranges` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_timeperiod_exceptions` Table: ALTER TABLE `nagios`.`nagios_timeperiod_exceptions` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_timeperiod_exclusions` Table: ALTER TABLE `nagios`.`nagios_timeperiod_exclusions` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_timeperiod_timeranges` Table: ALTER TABLE `nagios`.`nagios_timeperiod_timeranges` ENGINE=InnoDB;
ℹ * InnoDB migration request for `nagios`.`nagios_timeperiods` Table: ALTER TABLE `nagios`.`nagios_timeperiods` ENGINE=InnoDB;
ℹ General MyIsam metrics:
ℹ +-- Total MyISAM Tables : 64
ℹ +-- Total MyISAM indexes : 65.0M
ℹ +-- KB Size :32.0M
ℹ +-- KB Used Size :7.6M
ℹ +-- KB used :23.8%
ℹ +-- Read KB hit rate: 99.1% (22B cached / 194M reads)
ℹ +-- Write KB hit rate: 74.3% (465M cached / 345M writes)
ℹ MyISAM Metrics are disabled since MySQL 8.0.

-------- InnoDB Metrics ----------------------------------------------------------------------------
ℹ InnoDB is enabled.
ℹ InnoDB Thread Concurrency: 0
✔ InnoDB File per table is activated
✔ InnoDB Buffer Pool size ( 128.0M ) under limit for 64 bits architecture: (17179869184.0G )
✘ InnoDB buffer pool / data size: 128.0M / 802.0M
ℹ InnoDB Redo Log Capacity is set to 100.0M
ℹ Hourly InnoDB log write rate: 41M/hour
✔ Your innodb_redo_log_capacity is sized to handle more than 1 hour of writes.
ℹ The suggested innodb_redo_log_capacity (1G) is more than 25% of your total InnoDB data size. This might be unnecessarily large.
✔ InnoDB buffer pool instances: 1
ℹ Number of InnoDB Buffer Pool Chunk: 1 for 1 Buffer Pool Instance(s)
✔ Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances
✔ InnoDB Read buffer efficiency: 97.26% (805772576 hits / 828432119 total)
✘ InnoDB Write Log efficiency: 77.09% (69571003 hits / 90244047 total)
✔ InnoDB log waits: 0.00% (0 waits / 20673044 writes)

-------- Aria Metrics ------------------------------------------------------------------------------
ℹ Aria Storage Engine not available.

-------- TokuDB Metrics ----------------------------------------------------------------------------
ℹ TokuDB is disabled.

-------- XtraDB Metrics ----------------------------------------------------------------------------
ℹ XtraDB is disabled.

-------- Galera Metrics ----------------------------------------------------------------------------
ℹ Galera is disabled.

-------- Replication Metrics -----------------------------------------------------------------------
ℹ Galera Synchronous replication: NO
ℹ No replication slave(s) for this server.
ℹ Binlog format: ROW
ℹ XA support enabled: ON
ℹ Semi synchronous replication Master: Not Activated
ℹ Semi synchronous replication Slave: Not Activated
ℹ This is a standalone server

-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
/var/log/mysql/mysqld.log is > 32MB, you should analyze why or implement a rotation log strategy such as logrotate!
Check warning line(s) in /var/log/mysql/mysqld.log file
Check error line(s) in /var/log/mysql/mysqld.log file
Reduce your overall MySQL memory footprint for system stability
Dedicate this server to your database for highest performance.
Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=ON
We will suggest raising the 'join_buffer_size' until JOINs not using indexes are found.
See https://dev.mysql.com/doc/refman/8.0/en ... uffer_size
MyISAM engine is deprecated, consider migrating to InnoDB
Buffer Key MyISAM set to 0, no MyISAM table detected
Variables to adjust:
*** MySQL's maximum memory usage is dangerously high ***
*** Add RAM before increasing MySQL buffer variables ***
skip-name-resolve=ON
join_buffer_size (> 256.0K, or always use indexes with JOINs)
table_definition_cache (416) > 513 or -1 (autosizing if supported)
key_buffer_size=0
innodb_buffer_pool_size (>= 802.0M) if possible.
innodb_log_buffer_size (> 16M)


got any ideas on how to change the indicated parameters?

Thank you for that output,

The first thing I notice is the amount of errors in your mysql.log I would be curious what those are because that could give insight into some issues possibly with the performance. Also as it is recommending since the log file is large I would ensure that there is some way of rotating the logs if the log file fills up fast. One thing about the database that I've looked at is some tables are using the MyISAM engine (at least by default on one of my instances), which isn't particularly great compared to the recommended InnoDB, but also might not be easily changeable (when time permits I'll look further into it). In particular the service and host check tables and statistics are in the MyISAM tables which could be something limited the XI instance.

For right now I think the best recommendations that it is giving is to increase your innodb_buffer_pool_size to more than 802MB, so giving it a few gigabytes might help. Along with that it appears it wants innodb_log_buffer_size to be increased more than 16MB. Then turn on skip-name-resolve. Finally ensure that mysql.log is getting rotated as well.

To actually modify these values I believe you can modify /etc/my.cnf.d/mysql-server.cnf (at least on CentOS 9) and add the required parameters. If that file doesn't exist I would try and find a similar file that should be in /etc or /etc/my.cnf.d and it should contain different mysqld options. After modify it just save the file, restart mysqld, and then to ensure it worked run "SHOW VARIABLES LIKE 'innodb_buffer_pool_size';" in mysql (which shows the innodb_buffer_pool_size value in bytes) and ensure the changes are reflected for each variable.

I will try to look further into the issue, but for now try tweaking those config options and ensure you have a backup of the sever and/or the config just incase any unexpected problems occur.

- Caleb

Hi,
I added the parameters you suggested but now the stale lasts 2224 seconds (against the previous 700/800)

Hello,

I'm sorry to hear those changes made it worse. This could be because of a variety of reasons, but I wouldn't be able to give a concrete answer. I would highly recommend opening a ticket with our support department as they will have more experience than I do with this issue. You can contact them here https://support.nagios.com/. I will also talk to some colleagues today to see if they have any information on this type of issue. I would also recommend rolling back the MySQL configuration if you haven't already.

- Caleb