How is monitor_scope used?
Article ID: KB0085514
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
By default the RTmon's monitor_scope is "/*" which means it will only match
RTclients whose unique subject is a single hierarchy (the first level of the
hierarchical subject namespace such as "/foo"). To see an RTclient's unique
subject which has multiple hierarchies, such as TutCommandParseStr("setopt
unique_subject /foo/bar"); , change the monitor_scope to "/...". This will match
all names, such as "/foo/bar", and all monitoring information will be enabled,
so all filtering is disabled. See "Project Monitoring" in the User's Guide for
more information on this option.
By default the RTmon's monitor_scope is "/*" which means it will only match
RTclients whose unique subject is a single hierarchy (the first level of the
hierarchical subject namespace such as "/foo"). To see an RTclient's unique
subject which has multiple hierarchies, such as TutCommandParseStr("setopt
unique_subject /foo/bar"); , change the monitor_scope to "/...". This will match
all names, such as "/foo/bar", and all monitoring information will be enabled,
so all filtering is disabled. See "Project Monitoring" in the User's Guide for
more information on this option.
Issue/Introduction
How is monitor_scope used?
Feedback
Yes
No
Powered by
