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
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:17:45 +00:00 (in Redmine)
The new filter function in Icinga 1.9.0 is sweet, but there are a few things I stumbled over in the last weeks.
The filter doesn't have the host_address attribute in the available elements list.
It would be nice to be able to filter hosts e.g. by their IP address (e.g. some of our network guys have only numbers in their heads, but no idea what the devices are called in icinga :D)
The filter is case sensitive, and there doesn't seem to be an option to make in case insensitive.
If I'm not wrong, the live search uses DB indeces extensively to speed up results, which is understandable, however, it would be cool to be able to at least have the choice to click a "ignore case" checkbox and take the performance hit, if one doesn't have to think about capilization in exchange
Similar issue maybe as 2. - but it would be nice to have support for the typical wildcards (* and ?).
It seems as if the automatic dropdown when creating a filter already understands wildcards, (e.g. it will show FW-Location-PRI when I filter for FW*PRI) but once the filter is applied, "No Data" is shown in the main tab. (This part might actually be more of a bug than a feature request.)
The text was updated successfully, but these errors were encountered:
This issue has been migrated from Redmine: https://dev.icinga.com/issues/4323
Created by gradecke on 2013-06-17 12:46:21 +00:00
Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:17:45 +00:00 (in Redmine)
The new filter function in Icinga 1.9.0 is sweet, but there are a few things I stumbled over in the last weeks.
The text was updated successfully, but these errors were encountered: