EOL

Effective 15 September 2022, PATS reached end of life. This documentation is archived and will no longer be updated.

PATS

Introduction Copied

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 Copied

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) Copied

STATUS View Copied

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 Copied

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 Copied

The configuration for this plugin pertains to connecting and logging in to the PATS AMS website.

Mandatory configuration:

The following parameters can be configured for this plug-in:

amsUrl Copied

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 Copied

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 Copied

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

amsAccessCode Copied

An access code for the plugin to login to the AMS website to get status information

Mandatory: Yes

PATS Trading Breaches Copied

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 Copied

The plugin produces the following view, with a row for every breach. The headline variable shows details of the last encountered breach.

Actions Copied

Acknowledging Breaches Copied

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.

Removing Breaches Copied

Breaches can be removed from the view completely by right-clicking on the relevant row and selecting the “Remove” option from the resulting menu.

Breach Details Pop-up Copied

Additional information about a particular trading breach can be requesting by right-clicking on the relevant row in the view and selecting the “Show Breach Details…” option from the resulting menu.

This would produce a window with the breach details such as follows:

PATS Trading Breaches plugin configuration Copied

Sample configuration:

The following parameters can be configured for this plug-in:

tasLogFilePath Copied

The full path (including the filename) of the TAS log file

Mandatory: Yes

clearDataBetweenLogFiles Copied

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.

Mandatory: No

Default: True

breachActionsStorePath Copied

The location to store information on beach actions (acknowledgements and removals). By default, this information is stored in the location that the netprobe is run from.

Mandatory: No

PATS Users Copied

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 Copied

The plug-in produces the following view:

PATS Users plugin configuration Copied

Sample configuration:

The following parameters can be configured for this plug-in:

tasLogFilePath Copied

The full path (including the filename) of the TAS log file

Mandatory: Yes

clearDataBetweenLogFiles Copied

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.

Mandatory: No

Default: True