nrpe version 3

[SteveBeauchemin]

Question: Now that I am running nrpe version 3+ and I have the ability to get a larger payload response from a test, should I also make a DB table change that can hold the larger response without truncating it. If so, what would you suggest for the new size to become? Please provide syntax if there is a DB change that I should / could make.

Thanks

Steve B

[mcapra]

This article will allow for longer service/host check outputs in XI. Is that what you were looking for?
https://support.nagios.com/kb/article.php?id=478

[SteveBeauchemin]

That article is exactly what I am thinking about. I have read it before. I am trying to relate it to NRPE Version 3 and the larger responses we could be getting now.

In the past I recall changing to 1024 characters to see more status information. I have some hopefully basic and easy questions.

Is moving to 65 thousand characters overkill? Does it make sense?
Would it make my DBA cringe?
Are there any side effects?
Is there a performance hit caused by this?

Performance is important to me as I have a large install. Disk space usage is not a concern, I have plenty of space.
I will do anything to make the overall performance of my Nagios tool better.

Bottom line - If future Nagios releases incorporate NRPE 3, will a clean install still have those DB columns set to 256?
If you know today what you plan to use for the column sizes, let me know and I will make the same change today that you plan to introduce later.

Thanks

Steve B

[mcapra]

Is moving to 65 thousand characters overkill? Does it make sense?
Would it make my DBA cringe?
Are there any side effects?
Is there a performance hit caused by this?

To answer the general question of "can this cause undesired things" is: it depends. If every single plugin you have has 65k worth of characters in the output, then yes there will be a performance hit. However, as far as MySQL is concerned with storing something like this:

Code: Select all

OK - Some service output|'perfdata'=50%

There is no difference in whether or not that's in a VARCHAR(255) or a VARCHAR(65535) in terms of performance. It's just a cap on what the max length of the field is; It's not as if MySQL is setting aside ~198kB for a VARCHAR(65535) and ~7kB for a VARCHAR(255).

Bottom line - If future Nagios releases incorporate NRPE 3, will a clean install still have those DB columns set to 256?

Nope. Probably around the same time we start putting NRPE v3 in our config wizards is when the tables will change.

[SteveBeauchemin]

Thanks for the info. This can be closed.

Much appreciated...

Steve B