I've got this template working for some Oracle log file monitoring on a couple of Oracle servers, and wondered if there is a better way I could be more efficiently executing monitoring. In the template, I have 11 unique individual 'newly discovered' keyword string component monitors, however, I need to search for these strings across 5 unique log files, located in different directories on same node. So, in order to search for each of the 11 unique strings, I created a master template for one of the five paths to a given alert_* file, then copied the master to create the other four, each updated individually with it's respectively different file path. So, though the templates appear to be working, I have the same '11' keyword/string components x 5 = 55 elements, polling against the same server (not to mention other templates also running on this node). I staggered the polling frequency for each of the templates so they don't all hit at the same time, but this seems very inefficient. What I would like is for one template, to be able to poll across all 5 unique directory paths. I played with using asterisk thinking it would wildcard the search across multiple paths (/orabase/*/diag/rdbms/*/*/trace/alert*.log), but failed (not a perl programmer). Interestingly, in order to get this script to work, I had to copy the script out on the target node, and have Orion executing the script remotely.
1.) Is there a better approach/strategy perhaps I'm overlooking, as I know often get dreaded 'unknown' status for polls with this many elements hitting the same box on other application monitors.
2.) Executing the script remotely appears to work, but not sure I've populated the script correctly having both the argument and script fields filled (see below).
See screenshots below.
list of components, list of application templates applied, example component monitor.
