[dev.icinga.com #10903] GELF multi-line output #3805
Comments
Updated by mfriedrich on 2016-01-11 13:17:53 +00:00
Please look into that thanks. |
Updated by mfriedrich on 2016-03-18 14:58:24 +00:00 Any updates? Thanks. |
Updated by mariussturm on 2016-03-18 22:56:54 +00:00
The problem is the use of 'CompatUtility::GetCheckResultLongOutput' for the GELF full_message field. short_message: as is right now (only first line + escaped) looks best in my opinion. I have appended a screenshot of that, (short_message: "Connection refused", full_message: "Connection refused\nHTTP CRITICAL - Unable to open TCP socket") Here is the change for this: |
Updated by mariussturm on 2016-04-10 19:49:27 +00:00 Looks like nobody has objections. |
Updated by mfriedrich on 2016-08-09 07:51:10 +00:00
Didn't find that feature branch over at git.icinga.org therefore I fetched the github patch and applied it. |
Updated by Anonymous on 2016-08-09 07:55:04 +00:00
Applied in changeset 451cd73. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10903
Created by akrus on 2015-12-22 13:47:39 +00:00
Assignee: mariussturm
Status: Resolved (closed on 2016-08-09 07:55:04 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-09 07:55:04 +00:00 (in Redmine)
Hello!
We have an issue here with GELF multi-line output.
This dummy check:
vars.dummy_text = "Service status:\n123\n\321"
Looks in Icinga Web 2 as:
Service status:
123
321
but in Graylog we see:
message: Service status:
full_message: 123\n321
I think full_message should instead contain both message+full_message and with correct line breaks.
Attachments
Changesets
2016-08-09 07:51:17 +00:00 by (unknown) 451cd73
The text was updated successfully, but these errors were encountered: