The problem looks like it is defaulting to “all services” if you use such a regex inside the quicksearch.
With 2.0 you have exactly the same problem / behaviour.
h: ne.*xt → leads to
If you use the “ne.*xt” inside the host search view you get the correct result.
Exactly the same happens for a service search inside the quicksearch field.
Check the character before * if it’s another common regular expression character and in this case not substitute it. The outcome of abc.*xyz is different to abc..*xyz from an regular expression point. This, I think, is not intuitive at all.
which I think is a good feature to get all needed systems on one screen.
I understand it may be confusing to people who just want to use globbing but I think regular expressions are a pretty important feature. Making it work like 95% would be very confusing as Martin wrote.
Sorry, i did not follow this thread because we discussed this internally and came to the conclusion as stated.
So we will not change that behaviour in the near future
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.