Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Manager i10.62

Develop > Service Health > Service Health Rules API > Write to log files from the Rules API code

Write to log files from the Rules API code

Within your API rules, you can write to log files from rule methods using a logger object. There are five log levels: debug, info, warn, error and fatal. Each of these uses a specific logger method.

By default, only log method invocations of error and fatal severity are written to the log files. You can modify this within the log configuration files.

To write to log files using the Rules API:

Within the rule method, implement one of the following methods (listed in ascending order of severity):

logger.debug("<API rule name> : log message");
logger.info("<API rule name> : log message");
logger.warn("<API rule name> : log message");
logger.error("<API rule name> : log message");
logger.fatal("<API rule name> : log message");

Type the name of your API rule inside the log message to identify each log message with its source rule.

The Rules API log files are found in the <OMi_HOME_DPS>/log/marble_supervisor/RulesAPI directory.

Open one of the following files to view the log messages (depending on your rule type):

groupAndSiblingRule.log (for API Group and Sibling rules)
sampleRule.log (for API Sample rules)
durationBasedSampleRule.log (for API Duration-Based sample rules)

To modify the severity level written to a log file:

By default, only log method invocations of error and fatal severity are written to log files. To modify this setting, open the log configuration file located in <OMi_HOME_DPS>/conf/core/Tools/log4j/marble_supervisor/dashboard_rules.properties.
In the line corresponding with your rule type, replace the string ${loglevel} with the severity level you want logged (either DEBUG, INFO, WARN, ERROR, or FATAL). Edit one of the following lines, depending on your rule type:

Group and Sibling rules: log4j.category.com.mercury.am.rules.dashboard.blDashboardRules.
simplifiedRule.groupAndSiblingRule.DashboardGroupAndSiblingRule = ${loglevel}, bam.app.rules.api.group.appender
Sample rules: log4j.category.com.mercury.am.rules.dashboard.blDashboardRules.
simplifiedRule.leaf.DashboardSimplifiedSampleBasedRule = ${loglevel}, bam.app.rules.api.leafsample.appender
Duration-Based Sample rules: log4j.category.com.mercury.am.rules.dashboard.blDashboardRules.
simplifiedRule.leaf.DashboardSimplifiedTimeBasedRule = ${loglevel}, bam.app.rules.api.leafduration.appender

Send Help Center feedback