$('a[name]').remove(); $('#ic-homepage__footer').before('
'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('
'); $("#ic-homepage__feed-tips").wrapInner('
'); });
IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide IBM Tivoli Monitoring, Version 6.3
Monitor output from a script
When application data is not available through a standard management interface, a script or external program can be used to collect data for an attribute group.
Data can be collected from either a local or remote system. The output of the script or program must contain only values for each attribute within the attribute group. To return multiple rows of data, the data for each row must be separated by a line break. The attributes in each row of data are separated by the separators you define. For more information about separators, see Script parsing and separators
The command can use environment and configuration variables within the user-created script, executable file, query, or system command. The command cannot use environment or configuration variables on the command-line invocation of the command, with only the following exceptions available: AGENT_BIN_DIR, AGENT_ETC_DIR, AGENT_LIB_DIR, CANDLE_HOME, and CANDLEHOME.
The agent monitors script output that is written using the same locale and code page that the agent runs in.
- Collect script data from a remote system
To collect script or program data from a remote system, Agent Builder uses a Secure Shell (SSH)
- Script parsing and separators
You can change and assign specific script separators to one or more attributes.
- Steps for monitoring output from a script
Configure your agent to receive data from a script data source.