Contents
The Traffic Monitor settings enable you to configure the traffic monitoring available in the web-based API Gateway Manager tool. For example, you can configure where the data is stored and what message transaction details are recorded in the message traffic log.
To access the Traffic Monitor settings, click the Sever Settings node in the Policy Studio tree, and click Monitoring > Traffic Monitor. Alternatively, in the main menu select Tasks > Manage Gateway Settings, and click Monitoring > Traffic Monitor. To confirm updates to these settings, click Apply changes at the bottom right of the screen.
To access traffic monitoring in API Gateway Manager, go to http://localhost:8090, and click
the Traffic button in the toolbar.
![[Important]](../common_oracle/images/admon/important.png) |
Important |
|---|---|
|
Traffic monitoring may have a negative impact on performance. If you wish to maximize performance, you can disable traffic monitoring. |
You can configure the following Traffic Monitor settings:
Enable Traffic Monitor:
Select whether to enable the web-based Traffic Monitor tool. This is enabled by default.
Transaction Store Location Settings:
Enter the Transaction Directory: that stores the traffic monitoring data files
and database. You must enter the location relative to the API Gateway instance directory, which
is the location where the server instance runs (for example,
<install-dir>/apigateway/groups/<group-id>/<instance-id>).
The Transaction Directory defaults to conf/opsdb.d. If this directory
or the database does not exist when the API Gateway starts up, they are recreated automatically.
Persistence Settings:
You can configure the following data persistence settings:
| Record inbound transactions | Select whether to record inbound message transactions received by the API Gateway. This is enabled by default. |
| Record outbound transactions | Select whether to record outbound message transactions sent from the API Gateway to remote hosts. This is enabled by default. |
| Record policy path | Select whether to record the policy path for the message transaction, which shows the filters that the message passes through. This is enabled by default. |
| Record trace | Select whether to record the trace output for the message transaction. This is enabled by default. |
| Record sent data for transactions | Select whether to record the sent payload data for the message transaction. This is enabled by default. |
| Record received data for transactions | Select whether to record the received payload data for the message transaction. This is enabled by default. |
![[Note]](../common_oracle/images/admon/note.png) |
Note |
|---|---|
|
These settings are global for all traffic passing through the API Gateway. You can override these persistence settings at the port level when configuring an HTTP or HTTPS interface. For more details, see the API Gateway User Guide. |
Transaction Expiry Settings:
The following settings configure when a new transaction file is created. This occurs when the maximum transaction file size is exceeded or when the maximum number of transactions is reached (whichever occurs first).
| Target transaction file size |
Enter the target size of the transaction file, and select the units from
the list. Defaults to 8 MB. When this limit is exceeded, no
new transactions are added to the file, and a new file is created.
|
|||
| Maximum number of transactions per file |
Enter the maximum number of transactions stored in the file. Defaults
to 100000 transactions. When this limit is reached, no new
transactions are written. The current file is closed when all current
transactions using the file are completed.
|
|||
| Maximum number of transaction files |
Enter the maximum number of transaction files to store on disk at any one
time. Defaults to 128. When this limit is reached, old files
that have no open transactions are purged.
|
