Cheshire Cat Computing

Hey,

I've noticed that the event description gets truncated as its being filtered and sent out. Is there anyway to get around this? The crucial information is getting ignored!

If its a question of size limitations for nsca sending info, maybe it can be modified in the filter so at least it catches it?

This is a restriction of the size limits for NSCA, as you correctly mention. A Nagios message is supposed to be limited to 186 characters...

Currently, there is no way to change the output format without changing the code. I'm looking at making the next version support a flexible output format but this will take a bit of work (and no time for development at the moment)

At least you will be getting a notification at the Nagios end, and the windows admin can subsequently check the eventlog for more details.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

The character limit for NSCA is 512 characters but the Nagios EventLog agent is limited to ~250 characters (This is the total length of the message received and not just the event description ). It would be very nice if this limit could be increased but I have been unsuccessful in locating where the message size is determined in the source code ( MAX_PLUGINOUTPUT_LENGTH is set to 512 in nsca.h so it appears that the message is being cut before send_nsca is called ). Would you be able to please point me in the correct direction with the source code so that I can at least fix this problem before it is fixed in a future release?

Thanks,
Beeg

i've parsed the source code for the max lenght of event description with no result...

have someone find it?

i've the same problem here: event description get truncated (example: EventID: 672), i lost information about the ip of login client etc...

where i can modify this behaviour? i've done a lot of try but i'm not a good C programmer.

if it is possible, i'll expand from 256 to 512 bytes

thx in advance

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

very thanks!!!

I have the same problem. I changed the value to MAX_PLUGINOUT_LENGTH, but it seems not working. I already stopped and restarted the service. Are there anything else I am missing?

There is an error in the code that hardwires the array size at this point rather than using the #define. See the code change specified above to fix this.

Once I'm back on my feet and in to work again I'll try and get a new version with a larger pluginoutputlength posted.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

I followed the code change, but it is still not working. BTW, how to execute the file again after making the changes? I stopped eventlog agent and then restarted, but seems not working.

Many thanks for your help.

Stop the agent, replace the old binary with the new binary, and restart the agent.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11