perfdata trimmed

[bofh666]

Dear Support Team,

i have a Problem that the Performance data i send to nagios XI will be trimmed. also when you check the nagios core view (Service Status Detail -> Advanced -> See this Service in nagios core). i tried to extend the column perfdata in table nagios_servicestatus, but this didn't solve my Problem. it seem's that there must be an Overall Limit, because if i shorten the Status Information, more Performance data will be received.
the whole string (Status Information + Performance data) i send to nagios is about 900 characters. i set the columns Output and perfdata in table nagios_servicestatus to varchar(1024).

thank's in advance.

regards,
roland

[scottwilkerson]

To make sure no data is trimmed in the DB there are several fields that would need to be modified like so

Code: Select all

echo "
alter table nagios_servicestatus modify output varchar(65535) not null,modify long_output varchar(65535) not null,modify perfdata varchar(65535) not null;
alter table nagios_hoststatus modify output varchar(65535) not null, modify long_output varchar(65535) not null,modify perfdata varchar(65535) not null;
alter table nagios_servicechecks modify output varchar(65535) not null,modify long_output varchar(65535) not null,modify perfdata varchar(65535) not null;
alter table nagios_hostchecks modify output varchar(65535) not null,modify long_output varchar(65535) not null,modify perfdata varchar(65535) not null;
" | mysql -pnagiosxi nagios

[bofh666]

hello scott,

unfortunately this didn't solve my Problem. perfdata still get's trimmed.
do you have an other Suggestion?

my workaround is to send the perfdata first and afterwards the Status Information.

regards,
roland

[abrist]

Are the problematic checks coming from nrpe checks? I ask because nrpe has a cap at 1024. There is a branch to increase the checkresult character limit, but you will need to update both the agent and check_nrpe:
https://github.com/abrist/nrpe/tree/payload_size

[bofh666]

hello abrist,

this passive check comes from a Windows Server via send_nsca.
the whole string i send to nagios ia about 900 characters.
e.g.
MSSQL PerfCounter: BufferCacheHitRatio: 100 (TH gt 90), PageLife: 780479 (TH gt 300), BatchRequests: 51721071, SQLCompilations: 6851826, SQLReCompilations: 2090461, BatchExecutionPerCompileRatio: 13 (TH lt 10), SQLReCompilationsRatio: 31 (TH lt 10), LockWaitsTotal: 749, PageSplits: 626232, PageSplitsRatio: 1 (TH lt 20), ProcessesBlocked: 0, CheckpointPages: 3703633, FreeListStalls: 0 (TH lt 2), MemoryGrantsPending: 0, LazyWrites: 0 (TH lt 20)|BufferCacheHitRatio=100; PageLife=780479; BatchRequests=51721071; SQLCompilations=6851826; SQLReCompilations=2090461; BatchExecutionPerCompileRatio=13; SQLReCompilationsRatio=31; LockWaitsTotal=749; PageSplits=626232; PageSplitsRatio=1; ProcessesBlocked=0; CheckpointPages=3703633; FreeListStalls=0; MemoryGrantsPending=0; LazyWrites=0;


from my Point of view there must be an Overall Limit in nagios core (Service Status Detail -> Advanced -> See this Service in nagios core), because if i trim the Status Information, the more Performance data are transmitted.

regards,
roland

[abrist]

I only count 784 characters in the above output. At what quantity of characters is it always truncated at? 1023?

I don't think this is an issue with core, as nrpe (with patches to nrpe), nrdp, and standard active checks can handle much larger checkresults.

[lmiltchev]

I believe NSCA ver. 2.9 supports up to 4000 characters output.

https://github.com/NagiosEnterprises/ns ... /Changelog

[Box293]

Can you please provide some screenshots that show where the problem is happening.

[bofh666]

hello Folks,

let me answer your questions:

@abrist
you are right, for this particular check there are only 784 characters. the string i send this time was:
MSSQL PerfCounter: BufferCacheHitRatio: 100 (TH gt 90), PageLife: 20495 (TH gt 300), BatchRequests: 269008, SQLCompilations: 97811, SQLReCompilations: 151, BatchExecutionPerCompileRatio: 36 (TH lt 10), SQLReCompilationsRatio: 0 (TH lt 10), LockWaitsTotal: 13, PageSplits: 620, PageSplitsRatio: 0 (TH lt 20), ProcessesBlocked: 0, CheckpointPages: 17052, FreeListStalls: 0 (TH lt 2), MemoryGrantsPending: 0, LazyWrites: 0 (TH lt 20)|BufferCacheHitRatio=100; PageLife=20495; BatchRequests=269008; SQLCompilations=97811; SQLReCompilations=151; BatchExecutionPerCompileRatio=36; SQLReCompilationsRatio=0; LockWaitsTotal=13; PageSplits=620; PageSplitsRatio=0; ProcessesBlocked=0; CheckpointPages=17052; FreeListStalls=0; MemoryGrantsPending=0; LazyWrites=0;

the string get's trimmed at character 512 (see screenshot 1 (nagios core view) -> Performance data).


@lmiltchev
we are using nsca v2.4.

@box293
find 3 screenshots attached.

[bofh666]

hello Folks,

it seems that the problem is related to the send_nsca client on our windows servers. since we are using version 2.4, the MAX_PLUGINOUTPUT_LENGTH is 512 per default.
unfortunately i couldn't find a newer send_nsca client version (e.g. 2.9.1) for windows to download. maybe one of you guy's know where to download it.

thank's in advance!