Analyzing Login Transaction Management Metrics

Analyze Login Transaction Management (LTM) metrics using charts on the Transactions dashboard.

Click any LTM transaction to open the Current View tab, containing a detailed report of the transaction's performance, as follows:

• the Collection Point sub tab shows the performance chart for each individual collection point. Use the drop-down list at the top of the dashboard to select the collection point of your focus.

• the Compare sub tab shows the performance chart for all the collection points.

By default, information on the Current View tab is displayed for the current day. For information on how to change the time period for your reports, see the Generating Reports for Different Time Periods section in Working with Oracle Pulse.

The chart name uses the following format:

{Location} {Transaction Long Name} {Beacon Name}

where

• Location is @Oracle or @Customer.

• Transaction Long Name is the long name of the transaction.

• Beacon Name is the name of the beacon running the transaction.

The performance chart shows the response time for the user interaction over the specified reporting interval, allowing you to determine when the performance issue started, as well as the user zone affected by the issue. The performance threshold and the historical median are included on the chart for reference. The performance threshold is the longest acceptable response time set for the LTM transaction. You can set the threshold in Oracle Enterprise Manager in consultation with your Oracle SDM. The historical median is the value lying at the midpoint of the range of response times measured.

Click the Open Table View option in the lower right corner of the chart to open the table view in expanded mode, then click Export in the upper right corner to export the data, as explained in the Generating Reports for Different Time Periods section in Working with Oracle Pulse.

Depending on the selected time period, different information is available for each record in the performance profile flip view, as explained below:

• the one-day report shows the following information:

  • Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the LTM transaction.

  • Date/Time: Indicates the time when the metrics displayed were collected.

  • Time (sec): Specifies the length of time between the moment when the user interaction start request was received and the moment when the LTM transaction was completed, in seconds.

  • 30 Day Avg (sec): Specifies the running mean of all response times for the LTM transaction over the preceding 30 days.

  • Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.

  • Metric Status: Indicates where the transaction resides in the resolution process.

  • Transaction Type: Indicates the category the transaction is organized into.

• the one-week report shows the following information:

  • Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the LTM transaction.

  • Date/Hour: Indicates the time when the metrics displayed were collected.

  • Avg (sec): Specifies the average runtime for transaction responses in the past hour for the given transaction or beacon.

  • 30 Day Avg (sec): Specifies the running mean of all response times for the LTM transaction over the preceding 30 days.

  • Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.

  • Historical Median: Specifies the median runtime value for all transaction responses in the past 90 days.

• the one-month report shows the following information:

  • Collection Point: Specifies the name of the Oracle Enterprise Manager beacon monitoring the LTM transaction.

  • Time (Average): Specifies the daily average value of responses for the transaction, in seconds.

  • Threshold: Specifies the longest acceptable runtime for the transaction, in seconds.

  • 30 Day Average: Specifies the running mean of all response times for the LTM transaction over the preceding 30 days.