Yes. the full output in nagios CLI, you can see the full messages with "END 013" but in nagios web, it only display "END 009" which means 9 messages displayed.
From the below command result, How can we confirm the characters capacity set to 50000?
I would say you're running into a NagiosXI limitation at this point, not an NRPE limitation. One thing I've noticed is that the first line of status output is limited to 255 characters. Beyond that I can only display about 6KB of information in longstatusoutput.
Do you really seek to display 50KB of information on your monitor? The use case seems quite narrow to me. 50KB of test would require a monitor resolution greater than 2560x1600 to display if the text went from border to border. If that's really what you'd like I suggest putting in a bug request at tracker.nagios.org.
I will explain this situation to operation team for nagios limitation for 6k information. If now we set the 6K information for long output. Any concern to DB side? If yes, how can we housekeep to prevent DB grow unlimited. Because we located /usr/local/nagios in a 300G mount point.
There is some, you may notice the affected tables growing very large over time. Also, it may slow down queries.
michaelli wrote:If yes, how can we housekeep to prevent DB grow unlimited.
Well, we do provide some performance tuning options in: Admin --> Performance Settings --> Databases. You will need to watch disk space usage for the path: /var/lib/mysql/nagios as that is where the database tables are located. If the tables are growing to a too large of size, you may need to tune the performance settings.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
It may take some time for the developers to address this, and it is not guaranteed that it will be implemented. As pointed out it is somewhat of a narrow use case.
Also when filing bugs/features, please match the priority and severity to what the problem realistically is. Currently it is set to "Priority: Urgent" and "Severity: Major" - those settings are reserved for bugs that cause major outages or even damage to a system. I will be adjusting this feature request accordingly.
You really need to compile this yourself. GCC is an open source compiler available for Solaris amongst a zillion other platforms. If we compiled it in-house there would be too many variables (OS version, std library versions etc) that could cause problems when you try to run it on your system.
I cannot see any update for my post. Could you help to query your developer what is the status? It is because I have to update the issue to my manager.
We don't push the developers, they prioritize things as they see fit. Right now they are working on 2 major upgrades to the commercial products. They won't be addressing community needs unless security related until after those releases. In your case there are no promises that they won't just deny the feature request. The nature of your request could lead to other performance issues for our customers with large deployments.
If you have an immediate need for code changes please contact sales for a custom development quote.