PATS Trading Breaches Plug-in
Geneos ["Geneos"]
Geneos
You are currently viewing an older version of the documentation. End of life for version 5.x.x is scheduled for 30 September 2025.
If you are currently using version 5.x.x, we advise you to upgrade to the latest version before the EOL date. You can find the latest documentation here.
Recommended Reads

PATS Trading Breaches Plug-in - Technical Reference

Introduction

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.

trading-breaches2

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.

Removing Breaches

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

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:

trading-breaches3

Plug-in Configuration

Sample configuration:

tasLogFilePath: **/pats/tas/logs/tas.log**
clearDataBetweenLogFiles: **true**

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

tasLogFilePath

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

Mandatory: Yes

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.

Mandatory: No
Default: True

breachActionsStorePath

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