Introduction
The Geneos PATS plugin allows you to monitor the status and information about PATS components, user connections, and information about trading breaches by users on the PATS systems.
PATS Status
The Geneos PATS-STATUS Plug-In allows Geneos users to monitor the status and outstanding errors information about PATS components. The plugin collects these information by connecting to the PATS AMS website.
Views (for multiple views)
STATUS View
This view shows the status information of PATS components. For each component, if there are any errors that have not been cleared, a count of these will be displayed in the "Outstanding Errors" column.
OUTSTANDING-ERRORS View
This view shows the outstanding errors relating to PATS components. These are errors that have not yet been cleared using the AMS monitoring system.
PATS Status plugin configuration
The configuration for this plugin pertains to connecting and logging in to the PATS AMS website.
Mandatory configuration:
amsUrl: http://10.138.249.203/pats
amsAccessCode: admin123
OR
amsUrl: http://10.138.249.203/pats/login.cgi
amsStatusUrl: http://10.138.249.203/pats/status.cgi
amsAccessCode: admin123The following parameters can be configured for this plug-in:
amsUrl
The URL of the ams website, which typically end with '/pats'. The plugin would determine the login and status page URL's by addining '/login.cgi' and '/status.cgi' to this URL.
Alternatively, the login and status page URLs can be directly specifying using the amsLoginUrl and amsStatusUrl described below.
Mandatory: No
amsLoginUrl
The full URL of the login cgi script (typically would end with '/login.cgi'). If this setting is not specified, then amsUrl must be specified.
Mandatory: No
amsStatusUrl
The full URL of the status page cgi script (typically would end with '/status.cgi'). If this setting is not specified, then amsUrl must be specified.
Mandatory: No
PATS Trading Breaches
The Geneos PATS Trading Breaches plug-in allows Geneos users to monitor information about trading breaches by users on the PATS system. The plug-in collects this information by reading the log files put out by the PATS user server, TAS.
Single View
The plugin produces the following view, with a row for every breach. The headline variable shows details of the last encountered breach.
Actions
Acknowledging Breaches
Breaches can be marked as acknowledged by right-clicking on the relevant row in the view and selecting the "Acknowledge" option from the resulting menu.
PATS Trading Breaches plugin configuration
Sample configuration:
tasLogFilePath: **/pats/tas/logs/tas.log**
clearDataBetweenLogFiles: **true**The following parameters can be configured for this plug-in:
clearDataBetweenLogFiles
The plugin will by default clear its internal user state information when it detects that the TAS log file is being re-written. Setting this to false will cause the plugin to retain user state information even when the TAS log file is being re-written.
PATS Users
The Geneos PATS Users plug-in allows Geneos users to monitor information about user connections and connection attempts to the PATS system. The plug-in collects this information by reading the log files put out by the PATS user server, TAS.
View
The plug-in produces the following view:
PATS Users plugin configuration
Sample configuration:
tasLogFilePath: **/pats/tas/logs/tas.log**
clearDataBetweenLogFiles: **true**The following parameters can be configured for this plug-in:
clearDataBetweenLogFiles
The plugin will by default clear its internal user state information when it detects that the TAS log file is being re-written. Setting this to false will cause the plugin to retain user state information even when the TAS log file is being re-written.