Nagios Support Forum

I guess I don't understand what your last post is requesting. You will need to reproduce the store-and-forward modifications made in the referenced documentation, they may well require additional perl modules - we did not write the doc.

Can you help on below query,

XI server is down 30 minutes and we cache 15 service checks for a filesystem.
When the XI comes back up, it will receive 15 checks (with potentially different CPU utilization values) all with the same XI time stamp.
That doesn’t fill gaps in a graph; it just gives 15 concurrent data gaps after a 30-minute hole.
The same would happen for cpu, swap, processes, databases, etc.

After 30 min data will write in database with which time stamp Nagios XI time stamp or with check time stamp and it will fill gaps in a graph ?

it depends on the agent you're using, but as far as performance graphs are concerned that time has moved on.

Thanks for the assist, @tacolover101!

@tacolover101!

We are implementing 20 Nagios XI servers and each server having 1000 Hosts and 20000 services with different polling intervals.

If server down more 1 hours and above mention Host / Service checks are stored on client, this is collect huge data.

Need to understand during writing huge data, MariaDB handle this load ?
Will MariaDB and all other databases facing any issue ?

You have any details, regarding how write stored data in MariaDB please share.

Unfortunately, the support team is not equipped to help with custom development. If you'd like consulting or custom development done by our team you will need to reach out to [email protected] to get a quote.

That said, with 1k host and 20k services, any customization that does anything other than decrease load is not likely to end well.

I don't see why mariadb wouldn't be able to handle 20000 (mostly passive) services. We don't have such a large environment, so it's hard to test this in house. The good news is that each Nagios XI license is approved for up to three installations: one primary monitoring/production, one backup/failover, and one test environment. You can (and should) always try things on your test server, prior to moving them to production. I see much to often cases, when people make huge changes to their production servers without testing them first, and break their systems.

Thanks for sharing information, will check this approval and do the testing.

The good news is that each Nagios XI license is approved for up to three installations: one primary monitoring/production, one backup/failover, and one test environment. You can (and should) always try things on your test server, prior to moving them to production.

You can close this thread.