# Monitoring Traffic

## Contents
Overview Enabling Traffic Monitor Viewing the Message Traffic Log Viewing Transaction Details Troubleshooting

## Overview
This topic introduces the Traffic Monitor tool, which is used for operational diagnostics. Traffic Monitor provides a web-based message log of the HTTP and HTTPS traffic processed by the Enterprise Gateway. You can filter messages on a range of criteria (for example, transaction ID, service name, or remote host), drill down to the message contents, and change logging settings on-the-fly.
## Enabling Traffic Monitor
Before you can start viewing messages the Traffic Monitor tool, you must first ensure that Traffic Monitor has been enabled for the Enterprise Gateway process. To enable traffic monitoring in the Policy Studio, perform the following steps: In the Services tab on the left, right-click the Oracle Enterprise Gateway process, and select Monitoring -> Traffic. In the Traffic Monitor Settings dialog, ensure Enable Traffic Monitor is selected. Click OK.
## Viewing the Message Traffic Log
The Message Traffic Log provides an historical log of the HTTP and HTTPS traffic processed by the Enterprise Gateway. To view the Message Traffic Log, click the Traffic Monitor link on the Welcome to Oracle Enterprise Gateway page, which is available from `http://localhost:8090/index.html`. For example, the Message Traffic Log page is displayed as follows:
Message Traffic Log
Filtering the Message Traffic Log You can click the Filter button on the top right of the screen to filter the messages displayed based on a range of criteria. The default filters include transaction ID, message from (client or gateway), maximum results, and time. The Enterprise Gateway inserts a transaction ID in all HTTP and HTTPS traffic, which has a header named `X-CorrelationID`. Click the Add Search Criteria to search on different criteria (for example, service name, remote host, authentication subject, and operation). When you have selected your search criteria, click the Search button. Configuring Settings You can click the Settings button on the top right of the screen to set logging settings on-the-fly. You do not need to refresh or deploy to the Enterprise Gateway. The System Settings enable you to specify whether inbound and outbound transactions, the circuit path, and message trace are recorded. You can also select the HTTP interface in the tree on the left to override these settings and configure the interface trace level. Select the Enterprise Gateway process on the left to configure the process trace level. Finally, you can also select a Relative Path or Web Service on the left, and select Logging levels and Message Payload Logging on the right.
## Viewing Transaction Details
You can click a message entry in the Message Traffic Log to view transactions details for that message. The transaction details include the filter execution path, the contents of the outbound and inbound HTTP request and response messages, and the message trace. You can click to view one of these sections in the screen. Alternatively, click the Expand All button at the top right of the screen. Filter Execution Path The filter execution path shows the filters that the message passes through in the policy circuit, for example:
Filter Execution Path
Request from Client and Response from Gateway The contents of an example request message from the client and the response message from the Enterprise Gateway are displayed as follows:
Request from Client and Response from Gateway
Request from Gateway and Response from Web Service The contents of an example request message from the Enterprise Gateway and the response message from the Web Service are displayed as follows:
Request from Gateway and Response from Web Service
When viewing message contents, you can click the Save link to download the contents of the request or response message body. You can also click the Download button on the top right of the screen to download the entire transaction in binary format. This provides diagnostic information for the Oracle Support team. Trace The trace output for the message is displayed at the currently set trace level (for example, `DEBUG`). You can configure trace levels for the Enterprise Gateway process or HTTP(S) interface using the Settings button on the right.
## Troubleshooting
When you have viewed the message traffic and message contents, you can learn more about how to configure tracing for the Enterprise Gateway, and how to configure logging for specific message filters. For details, see Troubleshooting.