I'm trying to create a menu structure for my app that can be dynamically populated. To do this, I was hoping to use the view source="all" match="blah" syntax.
This of course works when matching a simple substring of the view name, but I would like to take advantage of a naming convention in view names to split the menu in multiple ways.
For example, I have:
igpci_pattern07_WLSaccess_WL10_prod igpci_pattern07_WLSaccess_WL10_demo igpci_pattern07_RSTaccess_prod igpci_pattern07_RSTaccess_demo
I'd like to take advantage of both the WLS/RST (app abbreviation) and the prod/demo parts (environment) to build the menu like this:
<collection label="Log samples - pattern matching - By app">
<collection label="Restful/Tomcat Prod">
<view source="all" match="RST*prod"/>
</collection>
<collection label="Restful/Tomcat Demo">
<view source="all" match="RST*demo"/>
</collection>
<collection label="Weblogic Prod">
<view source="all" match="WLS*prod"/>
</collection>
<collection label="Weblogic Demo">
<view source="all" match="WLS*demo"/>
</collection>
</collection>
This method results in no matches, and another attempt I made just to add another match key/value didnt either (I didnt expect it to).
Is there a way to achieve this short of specifying each view individually? (I have LOADS of them).
Thats a negative ghostrider. Simple case insensitive matching with no special characters.
http://answers.splunk.com/questions/12744/navigation-menu-xml-match-help/12745#12745
Thats a negative ghostrider. Simple case insensitive matching with no special characters.
http://answers.splunk.com/questions/12744/navigation-menu-xml-match-help/12745#12745