You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assignee: (none)
Status: Resolved (closed on 2016-02-23 15:10:03 +00:00)
Target Version: 2.2.0
Last Update: 2016-02-23 15:10:03 +00:00 (in Redmine)
i have a nsclient check on icinga1 that i use \n on the output to distinguish between short and long description on icinga and works fine with icinga1 but on icinga 2 it shows the long description on both service status and plugin output,
how can we distinguish between status message and plugin output in icinga2 web2
and i can see that this case is the same on all checks
when we have the status message it is easier to identify different messages while looking into services status. but now you have to look carefully on the screen to find the difference.
Updated by elippmann on 2016-02-18 16:34:11 +00:00
Subject changed from Display long output in overviews; maybe w/ explicit configuration to Textual representation of newline characters in plugin output not replaced w/
Hi,
I misinterpreted this issue. Will be fixed in our next release.
Updated by elippmann on 2016-02-23 15:05:11 +00:00
Subject changed from Textual representation of newline characters in plugin output not replaced w/ to Whitespace characters are ignored in the plugin output in list views
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10786
Created by xdije on 2015-12-07 15:00:09 +00:00
Assignee: (none)
Status: Resolved (closed on 2016-02-23 15:10:03 +00:00)
Target Version: 2.2.0
Last Update: 2016-02-23 15:10:03 +00:00 (in Redmine)
i have a nsclient check on icinga1 that i use \n on the output to distinguish between short and long description on icinga and works fine with icinga1 but on icinga 2 it shows the long description on both service status and plugin output,
how can we distinguish between status message and plugin output in icinga2 web2
and i can see that this case is the same on all checks
when we have the status message it is easier to identify different messages while looking into services status. but now you have to look carefully on the screen to find the difference.
Attachments
Changesets
2016-02-23 15:06:43 +00:00 by elippmann 35754fb
The text was updated successfully, but these errors were encountered: