499-01 Riverbed Certified Solutions Professional – Application Performance Management Questions and Answers

By default, the DSA attempts to keep 1-second data for 2 hours. The length of this time period is specified by the RawDataPersistDuration attribute in the dsa.xml file.

The DSA deletes the oldest 1-second data from the database If there is less than 10 percent of free disk space (the default for the RawDataPersistFreeSpaceTargetPercent attribute)

The DSA deletes the oldest 1-second data from the database if the database file is larger than specified in the RawDataPersistMaxDiskTarget attribute (unlimited as default).

If both the RawDataPersistFreeSpaceTargetPercent and RawDataPersistMaxDiskTarget attributes are satisfied, the DSA deletes data, if necessary, to retain only as much data as specified by RawDataPersistDuration.

At startup, and every 2 hours thereafter (or the frequency specified by RawDataPersistPurgeInterval), the DSA deletes the oldest 1-second data from the database.

Create New Panel icon

Data Sources icon

Link icon

Create New Dashboard icon

MovingWindowPercentile

MovingWindowSigma

HourlyLimits

HistoricalBaseline

HardLimits

EJBs: classes that implement the javax.ejb.EntityBean or javax.ejb.SessionBean interfaces

JDBC - classes that implement any of several interfaces in the java.sql package

JNDI - classes that implement the javax.naming.Context or javax/naming/directory/DirContext interfaces

Portlets - classes that implement the javax.portlet.Portlet interface

Generic classes

Changes in jida.config

Enabling monitoring of generic classes with config.package metrics

Changes in the -agentpath parameter

Enabling cross-tier transactions

Response time for SQL statements

Database usage by application and user

It tracks throughput in terms of database calls, transactions, rows, bytes, and active sessions.

A link to "View Database SQL queries" insights

IP addresses

Hostnames

IP address range

Subnets

It is based on packet loss reported on routers.

It is useful to correlate packet loss with round trip time (RTT).

I should not check against packet retransmission rate.

It is based on the percentage of packets from transmission control protocol (TCP) servers that were retransmitted.

Hostname or internet protocol (IP) address and capture agent port

Hostname or IP address and server description

XenApp server version and hostname or IP address

Capture agent port and XenApp server version

User response time (servers)

User response time (clients)

Server response time (servers)

Server response time (clients)

Initial application response time (TCP clients)

Snapshot buffer

Packets can be written to a storage area network (SAN) disk array

Rolling buffer

Packet extension buffer

From AppTransaction Xpert, use the AppTransaction Xpert capture manager

From AppSensor Xpert, when defining synthetic tests

From AppResponse Xpert, use the packet download manager

Using the distributed agent controller

From the packet trace warehouse

Application dependency

Data from the server to itself

Latency effect

Unaccounted data

TCP out of sequence

TCP retransmission

TCP frozen window

TCP reset

TCP connection failed

Congestion, latency, protocol, and bandwidth

Congestion, tier processing, protocol, and bandwidth

Congestion, latency, windowing, and retransmissions

Connection resets, latency, bandwidth, and protocol

AppInternals Xpert

AppResponse Xpert

AppSQL Xpert

Riverbed Performance Management Dashboards

This transaction takes about 4 seconds to complete and this analysis proves the user's belief that additional WAN bandwidth would improve application performance.

The majority of activity is between the two servers.

Most of the traffic consists of small messages.

Much of the application response time is caused by the Wide Area Network (WAN).

Ports cannot be changed after the installation.

Change the server.xml HTTP_PORT and HTTPS_PORT specifications in the installation folder.

Changes are need on both server.xml and bindings-jboss-beans.xml.

Log in to the BrowserMetrix default web user interface.

An end-user page view

The web server tier

The web application

The server node for the transaction

Use Riverbed Steelhead to inject the script at run time from the web server.

Use Riverbed Stingray to inject the script at run time from the web server.

Manually paste the Javascript in any web page you want to monitor with BrowserMetrix.

Edit a master file for the application by adding the Javascript to the header section of the file.

Back-end delay

Front-end delay

Network delay

Server delay

Safari does not support the W3C Navigation Timing specification.

Safari is a more responsive browser.

BrowserMetrix does not process "time to first byte" currently.

This is the user's first visit to the site or the previous page was not one of the instrumented pages.

The prompt always appears when you use this workflow. It means AppResponse Xpert passed a parameter to AppTransaction Xpert, causing it to search the specified Transaction Trace Warehouse server for supporting server trace information.

The AppTransaction Xpert preferences were set to always import Transaction Trace Warehouse trace data no matter how the packets were obtained.

While importing the packets, AppTransaction Xpert noticed HTTP headers indicating the presence of transaction tracing. It is asking for the hostname and credentials of the appropriate Transaction Trace Warehouse server to download the specific transaction traces referenced in the HTTP headers of the packet trace.

When the AppInternals Xpert instrumentation is set to create trace files, it marks the TCP headers for each packet in that transaction so AppTransaction Xpert knows to look for supporting transaction data.

AppInternals Xpert

AppResponse Xpert

AppTransation Xpert

Riverbed Performance Management Dashboards

Each web page associated with the application

A back-end data adapter that identifies and tracks all tiers of the application

The front-end web application with JavaScript and the application tiers with agents

The front-end web application with agents and the back-end with specified scripts

TCP window scaling

Maximum transmission unit (MTU)

TCP maximum segment size

Packet size