Riverbed 499-01 Exam Made Easy: Step-by-Step Preparation Guide

Install agents on a limited number of machines.

Restart the server.

Agents self tune so there is no need to control the overhead.

Never install more than 5 agents.

Use multiple consoles.

Unplug the server.

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.

Enable the X-Forwarded-for field.

Route clients around the load balancer.

Create a firewall rule to ensure the client IP addresses are seen.

Specify a route in the router for the client IP addresses.

Both provide average data, but AppInternals Xpert has data at 1-second granularity while AppResponse Xpert has data at 1-minute granularity.

Measuring common requests, AppResponse Xpert data provides network and server processing delay while AppInternals Xpert provides server processing delay only.

Assuming response time is being evaluated for a common request available from both data sources, AppInternals Xpert data is the maximum response during each 1-second bucket while AppResponse Xpert data is averaged over a 1-minute bucket.

AppInternals Xpert "Max. Active" metrics on Servlet/JSP/Web Aggregate metrics should exactly match AppResponse Xpert "Connections" metric.

It is best to instrument at all tiers for maximum visibility.

It is best to instrument at the web tier, since that is typically the client entry point into the application.

It is best to instrument at the application tier, since it sits between the web and database tiers.

It is best to instrument at the database tier, since it holds the data the client is requesting.

AppInternals Xpert

AppResponse Xpert

AppTransation Xpert

Riverbed Performance Management Dashboards

AppResponse Xpert

AppTransaction Xpert

AppInternals Xpert

AppSensor Xpert

RPM Dashboards -> AppResponse Xpert -> AppInternals Xpert -> Transaction Trace Warehouse

BrowserMetrix -> AppTransaction Xpert

Transaction Trace Warehouse -> AppInternals Xpert -> AppResponse Xpert -> AppTransaction Xpert

RPM Dashboards -> BrowserMetrix -> Transaction Trace Warehouse

RPM Dashboards -> AppInternals Xpert -> AppTransaction Xpert

Use the built-in email and SNMP mechanism or a custom forensic script in AppInternals Xpert to send alerts to the existing system.

Configure alerts in AppResponse Xpert to send SNMP traps to the existing system.

Set up BrowserMetrix to send email alerts to an email gateway.

Add email alerts to the RPM Dashboard settings.

Configure Transaction Trace Warehouse to send email alerts to an email gateway when certain thresholds are met.

The private key might not be imported in AppTransaction Xpert from AppResponse Xpert.

AppTransaction Xpert cannot analyze HTTPS packets.

The user must provide the SSL to AppTransaction Xpert.

AppTransaction Xpert needs TCP handshaking packets to decrypt SSL traffic.