On Fri, March 13, 2015 11:27 pm, Shawn Heisey wrote:
On 3/13/2015 8:34 PM, Ralph Mitchell wrote:
What if the standard entry was extended:
log:/var/log/messages:10240
log:/var/log/file-with-html:10240:html
That would allow any log file to be designated for url-encoding before
being uploaded to Xymon, without breaking existing configurations.
Or did I miss the point of the original question?
That would be perfect, for the main reason you mentioned: Existing
configs will see no difference. The :html config could be included in
sample configs and in documentation ... new users will not be troubled
by the problem I've encountered, and an exiting user can convert their
config if they need that feature.
Tangent question: Is the color status icon for logfile entries generated
by the server, or the client with "&red" or similar text? If it is
generated by the server, then I don't think logfile HTML conversion
would need to worry about things like &red.
That would help, however it would also cause items that had gotten
URL-encoded to potentially be missed in analysis.d LOG regex's (which
don't URL-unencode).
Given that this is a display issue more than anything else, it might be
better handled as we're creating the status message from xymond_client.
This leaves the raw log message still available, while still protecting
the display from getting interpreted this way.
Regarding your other question, the '&red/yellow/green' interpretation is
done by the CGI displaying the status, but is generated after the message
comes in (by xymond_client), so there wouldn't be an issue there.
Regards,
-jc