Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Max length for service output #3

Open
mohierf opened this issue Nov 21, 2013 · 1 comment
Open

Max length for service output #3

mohierf opened this issue Nov 21, 2013 · 1 comment

Comments

@mohierf
Copy link
Collaborator

mohierf commented Nov 21, 2013

The maximum length for service output is fixed to 255 character in the database (glpi_plugin_monitoring_serviceevents and glpi_plugin_monitoring_hosts) whereas maximum output in Nagios/Shinken is 512 bytes.

Checks output like hereunder (NSClient CheckMem) are not stored completely :

;OK: physical memory: 7.04G, virtual memory: 343M, paged bytes: 9.2G, page file: 9.2G|'physical memory %'=59%;75;90 'physical memory'=7.043G;8.94999;10.74;0;11.933 'virtual memory %'=0%;75;90 'virtual memory'=343.309M;6291455.906;7549747.087;0;8388607.875 'paged bytes %'=38%;75;90 'paged bytes'=9.20299G;17.898;21.478;0;23.864 'page file %'=38%;75;90 'page file'=9.20299G;17.898;21.478;0;23.864

mohierf referenced this issue in mohierf/glpi_monitoring Nov 22, 2013
@mohierf
Copy link
Collaborator Author

mohierf commented Jan 19, 2014

Ok, but should be interesting to make a patch because the table glpi_plugin_monitoring_hosts stores check output in two fields : event and output. This patch needs a fix in Monitoring AND in Shinken broker. As of it, it should be interesting to check whether a long output with line breaks is correctly stored in database.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant