RiverBed AppInternal Configuration

Alert Configuration Screen

Apdex scores are a standard method for reporting user satisfaction with software application performance. Scores
range from 0 to 1, where 1 is the best possible score and zero is the worst. See “Transactional Thresholds and Apdex
Scores“ for details on how the score is calculated.

Dampening

These settings limit the conditions that will generate an alert.
 The consecutive minutes setting specifies the interval over which the “Threshold Violation Conditions“ must

persist.
 The transactions each minute settings specifies a minimum number of transactions that must meet those

conditions.
Increase the values to decrease the sensitivity of the other conditions to generate alerts.
Setting both values to 1 effectively disables dampening. This is useful for testing whether other settings are working
as expected.

Transactional Alert Example

To understand how AppInternals determines when to send a transactional alert, consider the following transaction type,
threshold and alert configuration:

For this example, suppose this is the only transaction type, and that there are 100 matching transactions every minute,
as follows:

Riverbed SteelCentral AppInternals Version 10.0 55

Alert Configuration Screen

 51 take .5 seconds
 21 take 1 second
 The remainder take .2 seconds
This behavior will generate 51 minor threshold violations and 21 major violations every minute and meets both the
25% violation criteria in the alert configuration. However, as specified in the consecutive minutes criterion,
AppInternals will not generate an alert until after 5 minutes.
Also, the alert will not clear until BOTH major and minor violations drop below 25% of transactions for at least one
minute.

Email Recipients

These settings specify who receives the alert message, the format of the message, and whether to send a message when
an alert condition clears.
A message shows the status of e-mail configuration for alerts. The status message is a link to the “Email Screen“ where
you configure the settings if necessary.
Specify recipients as a comma-separated list of email addresses in the text box.

Note: Must Configure the Email Server First!
Before AppInternals can send any alert messages, you must separately configure the “Email Screen“ with the email
server to use.

From Email Address

The value to use in the From field of the e-mail message.

Email Message Format

Choose either Human Readable or JSON.

Human Readable

Choosing Human Readable results in an email message that looks similar to the following:

From:[email protected]
Sent:Thursday, May 28, 2015 4:49 PM
To:testing
Subject:ALERT: AppInternals - "nhx1-w2k12r2-4"
Attention, an alert has been triggered for the server "nhx1-w2k12r2-4" at 2015-05-28 16:40:00.
The average CPU utilization is 6.58.
To view additional details please login to your account.
https://nhv1-ams-5/#servers:time=23880757+5&serverTableKey=nhx1-w2k12r2-4

56 Riverbed SteelCentral AppInternals Version 10.0

Alert Configuration Screen

JSON

The JSON (JavaScript Object Notation) format is useful for sending notification to an automated system for parsing,
such as to generate a troubleshooting ticket). The JSON format contains an array of alerts that were triggered or
cleared for that minute. All times are expressed as the number of milliseconds since 1970 (“UNIX time”).

Here is an example of the JSON email format:

From: [email protected]
Sender: [email protected]
To: [email protected]
Subject: ALERT: from AppResponse Xpert BrowserMetrix
{

"alert_state": "active",
"alerts": [

{
"triggered_by_violations": true,
"triggered_time": 1380642300000,
"triggered_by_score": true,
"violations_percentage": 100,
"application": "My Application Name",
"response_time": 2000,
"transaction": "My Key Transaction Name",
"violations_minor": 1,
"violations_major": 0,
"page_views": 1,
"eue_score": 50

}
]
}

Send Email once alert is cleared

Select this setting to send a second notification once the alert clears. If you choose “Human Readable“, the second
notification looks similar to the following:

From: [email protected]
Sent:Wednesday, May 20, 2015 5:04 PM
To:testing
Subject:OK: AppInternals - "Home"

Attention, the alert for the Transaction Type "Home" was cleared on 2015-05-20 16:55:00.

During the alert period, 64.42% of the transactions were violations, and the Apdex score was 0.68
.

To view additional details please login to your account.
https://nhv1-ams-5/#transactions:time=23869162+95&ttTableKey=1

If you choose “JSON“, the second notification looks similar to the following:

From: [email protected]
Sent:Wednesday, May 20, 2015 5:04 PM
To:testing
Subject:OK: AppInternals - "Home"
MIME-Version: 1.0
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
{

"alert_state":"cleared",
"alerts":[

{
"triggered_by_violations":true,

Riverbed SteelCentral AppInternals Version 10.0 57

Alert Configuration Screen

"triggered_time":1416865320000,
"triggered_by_score":false,
"violations_percentage":20,
"application":"My Application Name",
"response_time":745,
"transaction":"My Key Transaction Name",
"violations_minor":1,
"violations_major":0,
"page_views":5,
"cleared_time":1416865380000,
"eue_score":90
}
]

58 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 9 Alert History Screen

When you receive an email telling you that an alert has occurred, you can open this screen by selecting Home > Alert
History from the menu bar.

This screens lists alerts that have been triggered by threshold violations.

The content of the columns in the Alert History table are explained in the table that follows.

Alert History Screen

Home > Alert History Path you select to arrive at this screen.

Active Red triangle containing an exclamation point indicates the alert has
Triggered been triggered by the metric value exceeding one of its limits for
more than the configured length of time. For instance, the CPU %
Usage metric might send you an alert when the CPU usage exceeds
80% for more than 180 seconds. The alert remains active until the
metric no longer is at 80% or after it returns to below 80% for the
180 seconds.

Time that the alert was triggered.

Cleared If the alert has been cleared, the most recent time the alert was
Metric cleared.

Name of the metric whose value you are being alerted to address.

Source Name of the server where the alert occurred.

Type Type of metric that was the source of the alert. For instance, an alert
Value could be triggered by an environmental metric or a transactional
metric. Environmental metrics from the operating system, like CPU
% Usage. Transactional metrics are from code transaction traces,
like Response Time.

Value of the metric when the alert was triggered, regardless of the
current status of the alert.

Riverbed SteelCentral AppInternals Version 10.0 59

Alert History Screen
60 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 10 Email Screen

Overview

As described in the “Alert Configuration Screen“ topic, you can specify settings that trigger an email notification when
threshold violations occur. (See “Threshold Overview Screen“ for details on thresholds.)
Settings in this screen configure the email server that AppInternals uses to send email notifications. Obtain the specific
settings for the email server from the server administrator.

Description of Fields

Specify the Email Server

Server Name

Name of the SMTP mail server to use for sending alert notifications. The server must support SMTP. Supply the server
name node.domain format (for example, pacer.mydomain.com).

Server Port

The network port for the mail server.

Use Secure Sockets Layer (SSL)

Whether to use SSL when sending messages.

Server Requires Authentication

Select this setting if the mail server requires users to log in to send email.

Riverbed SteelCentral AppInternals Version 10.0 61

Email Screen

User Name

A user name to access the mail server. This value is required if “Server Requires Authentication“ is selected and
disabled if it is not.

Password

The password to access the mail server. This value is required if “Server Requires Authentication“ is selected and
disabled if it is not.

Test Outgoing Mail Server Settings

You can check that the email server settings are working by providing a valid address in the Test Email Recipient
setting and clicking Send Test Email.
Send Test Email is disabled if any required settings are empty.
After you click Send Test Email, AppInternals attempts to send a test email message using the specified settings. It
displays a Results: message indicating the test results:
 Configuration verified

This message means the e-mail was successfully sent. In this case, the specified recipient will receive a message
similar to the following:

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: SMTP Configuration Test
From: [email protected]
To: [email protected]
Receiving this message confirms that your SMTP configuration settings are correct.

 Configuration was not verified, unable to send email
This message means the e-mail was not sent. Check your settings on this screen and that the e-mail server is
available.

Apply / Revert

Apply and Revert are enabled after you change any settings:
 Click Apply to save settings.
 Click Revert to return to the previously-saved settings.

62 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 11 Threshold Overview Screen

Overview

This screen lists the acceptable upper limits for server CPU usage and transaction response time. If a metric value
exceeds a limit, AppInternals generates a “minor” or “major” threshold violation.
There are two types of thresholds:
 “Environmental Thresholds“ specify the highest acceptable CPU usage for servers.
 “Transactional Thresholds“ specify the highest acceptable response time for transactions that match specific

transaction types. (You define transaction types on a separate screen. See “Transaction Types“ for details.)
AppInternals shows threshold violations in various tables and graphs in the user interface. In addition, threshold
violations can potentially trigger email alerts. Settings in the “Alert Configuration Screen“ control when violations
result in an email alert.

Operations and Controls

The Threshold Overview screen has separate tabs for environmental and transactional thresholds.
 Click the Environmental tab to show the single default environmental thresholds (with a Server value of *) and

any user-defined thresholds.
 Click the Transactional tab to show any user-defined transactional thresholds.
 To add a new threshold, click the add button above the thresholds list.

– On the Environmental tab, the Add Environment Threshold dialog opens.
– On the Transactional tab, the Add Transaction Threshold dialog opens.
 To edit an existing threshold, select the row for the threshold and click the edit icon ( ) above the thresholds
list. The edit threshold dialog opens with the settings for that threshold.
 To delete an existing threshold, click the delete icon ( ) above the thresholds list.

Riverbed SteelCentral AppInternals Version 10.0 63

Threshold Overview Screen

Environmental Thresholds

“Environmental thresholds” specify the highest acceptable CPU usage for servers. CPU usage is based on the total %
Processor Time metric that AppInternals reports for servers it is monitoring. AppInternals reports CPU usage every
second.

There is a single default threshold (with a Server value of *) that applies to all servers that AppInternals is monitoring:

 If 25 percent of the CPU usage samples across all servers are greater than or equal to 75%, AppInternals
generates a minor threshold violation.

 If 25 percent of the CPU usage samples across all servers are greater than or equal to 95%, AppInternals
generates a major threshold violation.

You can change the settings for the default threshold and add new thresholds for specific servers.

Note: Threshold Evaluation is Across All CPU Cores
To evaluate environmental thresholds, AppInternals compares the threshold value against the average of CPU usage
for all cores on a server. This means that a single core with 100% CPU usage will not necessarily violate a threshold.
Similarly, nor will a “roaming” process that exhausts whatever CPUs it uses.

For each server, you specify the CPU usage values that trigger a minor or major violation. Supply values as follows:

Server The name of the server for which to define thresholds. You cannot change this value for the default
threshold. This name must match a server already known to AppInternals. You cannot change this
Threshold Type value after clicking Save.
Minor
Major Whether to specify violations in terms of the average (Average) or as a percentage (Percentage) of
1-second samples over the last minute.

The CPU usage that triggers a major or minor violation. How you specify the usage depends on the
Threshold Type you chose.

For Average, specify the average CPU usage value. If the average CPU usage over the last minute
is greater than or equal to this value, AppInternals generates a violation.

For Percentage, specify two different values:

• The percentage of 1-second samples over the last minute that must be greater than or equal to the
specified CPU usage to generate a violation

• The CPU usage value

You must supply both a major and minor threshold value.

Transactional Thresholds

“Transactional” thresholds are based on transaction type response time. They specify the highest acceptable response
time for transactions that match specific transaction types. (You define transaction types on a separate screen. See
“Transaction Types“ for details.)

64 Riverbed SteelCentral AppInternals Version 10.0

Threshold Overview Screen

How AppInternals Determines Response Time for Thresholds

How AppInternals determines response time depends on the transaction type’s “Applies To“ setting. As described in
“What are “End to End Transactions” and “Transaction Segments”?“, this setting specifies the scope of transaction
trace data that the transaction type is evaluated against:

 If the Applies To setting is End-to-End Transactions or End-to-End Transactions and Transaction
Segments, response time depends on whether web-page performance data is available:

– If web-page performance data is available, response time is the “pageload.responsetime“ value. In other
words, it is the total response time from the perspective of the end user.

– If web-page performance data is not available, response time is the “server.responsetime“ value. In other
words, it is the combined response time across all servers represented in “stitched” application data that
AppInternals detects. It does not include web page response time.

 If the Applies To setting is Transaction Segments, response time is the “responsetime“ value of the “front-most”
server tier represented in “stitched” application data that AppInternals detects.

Specifying Transactional Thresholds

There are no default transactional thresholds. For each transaction type, you specify the response time values that
trigger a minor or major violation. Supply values as follows:

Transaction Type The name of the transaction type for which to define thresholds. This name must match an existing
transaction type. You cannot change this value after clicking Save. You cannot specify a transaction
Minor type that already has thresholds defined.
Major
The response time value that triggers a minor or major violation. Any transaction that matches the
transaction type and has a response time greater than or equal to this value will generate a violation.

You must supply both a major and minor threshold value.

Consider the following example:

AppInternals evaluates any transactions that match the Orders transaction type to see if their response time was .5 or
1 seconds or greater. If so, that transaction generates a minor or major threshold violation.

AppInternals keeps track of the number of transactional threshold violations for the transaction type and uses them to
calculate Apdex (see “Transactional Thresholds and Apdex Scores“) scores and to evaluate “Transactional Alerts“
configured in the “Alert Configuration Screen“.

Riverbed SteelCentral AppInternals Version 10.0 65

Threshold Overview Screen

Transactional Thresholds and Apdex Scores

AppInternals also uses “Transactional Thresholds“ violations to calculate an Apdex score.
Apdex scores are a standard method for reporting user satisfaction with software application performance. Scores
range from 0 to 1, where 1 is the best possible score and zero is the worst. See the following link for background on
Apdex scores: http://www.apdex.org/

How AppInternals Calculates Apdex Scores

AppInternals calculates Apdex scores every minute based on the count of transactions that match transaction types,
and which of those transaction had minor and major violations. Each transaction is scored as follows:
 No violation: 1 point
 Minor violation: 1/2 point
 Major violation: 0 points
The Apdex score is the total points divided by the number of transactions for the minute:

Apdex = (1.0 * no_violation_count + .5 * minor_violation_count)/number_transactions

How AppInternals Uses Apdex Scores

AppInternals uses Apdex scores as follows:
 In the “Apdex Card“ of the “Transaction Types Tab“
 To evaluate the “Apdex Score“ condition for “Transactional Alerts“
 To color-code components in the “Mini Application Map“ and “Application Map Tab“.

– If the Apdex value 0.85 or greater, it is green (good to excellent).
– If the Apdex value 0.5 or greater, it is yellow (poor to fair).
– If the Apdex value below 0.5, it is red (unacceptable).

66 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 12 Manage Applications Screen

This screen opens when you click the Application List option of the Configure menu.

If no applications have been defined, the Manage Applications table is empty. Click the Add an Application
definition button to open the “Define an Application Screen“.

If anyone has defined applications, they appear in the table and in the applications list (see “Applications
List—Filtering by Application Definition“) in all the data analysis tabs. You can sort the list on any column. The table
has the following columns and controls:

Name Name you gave the application. Must be unique.
Description Description you entered when you created the application definition.
Created Date and time you added the application definition to the list.
Modified Date and time you last edited the application definition.
Pencil and Paper Icon Click to edit the application definition. The “Define an Application
Screen“ opens for the application.
Delete Table Item Icon Click to delete the application definition.

Page Navigation Buttons By default, the table displays pages of 25 items. Use the navigation
buttons below the table to display the first, previous, next, and last pages
or change the number of items per page from 25 to 50 or 100.

Riverbed AppInternals 67

Manage Applications Screen
68 Riverbed AppInternals/Release 9.0

CHAPTER 13 Define an Application Screen

Use this screen to define an application. Navigate here by clicking the Add an Application Definition button in the
“Manage Applications Screen“.

Application definitions specify transaction types, servers, AppDomains, and JVMs whose data you want to display
together. Once created, applications appear in the All Applications > drop-down list (see “Applications
List—Filtering by Application Definition“). Users choose an application to display data that matches the criteria
specified in the application definition. AppInternals displays data that matches any of the criteria in the application
definition.

Options

Name Required. This name appears in the applications drop-down list (see
“Applications List—Filtering by Application Definition“) and in the
Description “Manage Applications Screen“.
Do you need to define transactions?
You cannot change this name after you first save the application
Transaction Types definition.

Optional. This name appears in the applications drop-down list (see
“Applications List—Filtering by Application Definition“) and in the
“Manage Applications Screen“.

Click on the link to open the Transaction Types screen and add
custom transaction types to the list titled Available Transaction
Types.

Select transaction types from those listed in the Available
Transaction Types table and click Add to move them into the
Selected Transaction Types table.

You must select at least one transaction type before you can save the
application map.

Riverbed SteelCentral AppInternals Version 10.0 69

Define an Application Screen

Available List of transaction types that the analysis server discovered by
Transaction Types interacting with agents on servers being monitored. Select the
transaction types you want to examine and click on the Add >
Selected button to add them to the Selected Transaction Types list.
Transaction Types
Buttons or Adding to/Removing from List of transaction types from this applications that you want to
Selected Lists examine. You add these transaction types from the Available
Add > Transaction Types list.
Add All >>
<< Remove All These buttons apply to the Transactions, Servers, and
< Remove AppDomains/JVMs lists in the Define an Application screen.
Servers
Add selected items in the Available list to the Selected list.
Available
Servers Add all items in the Available list to the Selected list.

Selected Remove all items from the Selected list.
Servers
Remove selected items from the Selected list.

(If you see Server, click on it to see Servers) Servers that you
want to include in the application definition, even when no
transactions of the types you have defined and added to the
application definition occurred on the server during the time period
you have selected.

If you do not select servers here, the servers you see in the
application map are servers where transactions of the type you
selected under Transaction Types have occurred during the time
range you selected. Those servers dynamically appear in the map if
transactions occurred on them during the time range.

Select servers from those listed in the Available Servers table and
click Add > to move them into the Selected Servers table.

List of servers being monitored that the Analysis Server discovered
by interacting with Agents on those servers.

Select servers in this list that you want to examine and click on the
Add > button to add them to this Selected Servers list. Or click
Add All >> to add all servers.

List of servers with this applications that you want to examine. You
select these servers from the Available Servers list and click on the
Add > button to add them to this list.

Before you click Save, you can also remove one or more servers
from this list by selecting them and clicking < Remove or remove
all servers by clicking << Remove All.

70 Riverbed SteelCentral AppInternals Version 10.0

AppDomains/JVMs Define an Application Screen

Available (If you see AppDomains/JVMs, click on it to see
Selected AppDomains/JVMs) AppDomains or JVMs that you want to see
Save
Add Relationships... in the map, even when no transaction types that you have added to
the application definition were invoked by the AppDomain or JVM
during the time period you have selected. If you do not select an
AppDomain or JVM here, the only AppDomains or JVMs you see
in the application map are that invoked the transactions of the
transaction types you added the application definition.

Select the AppDomains or JVMs you want to add to the application
definition from the Available AppDomain/JVMs table and click
Add> to move them into the Selected AppDomain/JVMs table.

List of AppDomains or JVMs from instrumented processes of this
application that the analysis server discovered by interacting with
the agent and the DotNet or JIDA sub-agents running on servers
being monitored. Select AppDomains or JVMs in this list that you
want to examine and click on the Add > button to add them to this
Selected list.

List of AppDomains or JVMs for this application that you want to
examine. You add these AppDomains or JVMs from the Available
AppDomains/JVMs list.

Before you click Save, you can also remove an AppDomain or JVM
by selecting it and clicking < Remove or remove all
AppDomains/JVMs by clicking << Remove All.

Click this button to add the application to the Manage Applications
list.

Add Relationships appears only when you are modifying an
existing application definition. Click to manually add a relationship
to an application map. See “Add Relationships“ for details.

Defining Applications

To add an application whose performance you want to manage:

1. In the menu bar, select Configure > Applications List.

2. When the Manage Applications screen appears, click the Add. button.
? The Define Application screen appears.

3. Name—Required. Enter a name that helps you identify the application. The executable name might not be useful,
whereas a name like Finance helps clarify the purpose of the application.

4. Description—Optional. Enter a description for the application if you think it requires one.

Riverbed SteelCentral AppInternals Version 10.0 71

Define an Application Screen
5. Transaction Types—Select transactions from those listed in the Available Transactions table and click Add
> to move them into the Selected Transactions table.
Select transaction types in the
Available list and click Add > to
add them to the Selected list.

If you do not have any transaction types (you see none in the list), click on Do you need to define transaction
types? and AppInternals takes you to the Transaction Types screen to define them.
After you have selected the transaction types in the application, you can click Transaction Types to hide the
list (the arrow turns sideways), then click on Servers to expand the list of servers to choose.
6. Servers—Select servers from those listed in the Available Servers table and click Add > to move them into
the Selected Servers table.
Click on to hide
the Transaction

Types list.
Then click to
open up the Servers

list.

72 Riverbed SteelCentral AppInternals Version 10.0

Define an Application Screen

7. AppDomain/JVMs—Select AppDomains or JVMs resulting from processes of the application instrumented
during configuration. Select them from those listed in the Available AppDomain/JVMs table and click Add >
to move them into the Selected AppDomain/JVMs table. To add a large number, you can click Add All > and
then select single instances to remove and click < Remove for each one.

8. Click Save to save the list of application and see it appear in the Manage Applications list.
The Manage Applications list appears, where you see all defined applications.

Add Relationships

These options are available only when you edit an existing application definition. They are not available when you first
define an application.

When you edit an application, you can also modify the application map to add relationship arrows between servers and
AppDomain/JVMs that are not showing as connected in the map.

As first defined, an application’s map may not show all relationships between tiers. To add relationships to the
application map, you edit the related application definition and indicate those relationships in the Add Relationship
section at the bottom of the Define an Application screen.

Riverbed SteelCentral AppInternals Version 10.0 73

Define an Application Screen

For more on viewing and interpreting the application map, see the “Application Map Tab“ topic.

Add Relationship Click to add another row to the list of relationships. AppInternals adds a dotted-line relationship
arrow between the two elements to show they are connected.

From In the drop-down list, select the server and AppDomain or JVM to connect from. The name in
To the list starts with the server name followed by a colon, then lists the web site name followed by
#, then gives the AppDomain or JVM name.

In the drop-down list, select the AppDomain or JVM to connect to.

Click to delete the relationship in that row from the list.

Click to add the relationships to the application and save the changed application definition.

Click to cancel the relationships you have added and exit the Add Relationships screen.

When you view the application map, you see relationships between tiers of the application drawn as arrows connecting
servers and the AppDomains/JVMs from instrumented processes. The map might not show all relationships. If you
know of a relationship that is not showing in the map, you can add that relationship by selecting the application in the
Manage Applications list and editing the application. Follow these steps:

1. In the list, click on the to the right of application that you want to edit.

74 Riverbed SteelCentral AppInternals Version 10.0

Define an Application Screen

2. The Define an Application screen appears. Scroll down until you see the Add Relationships area and click
the to expand the area.
? You then see an application map reflecting the most recent month’s worth of application activity.

3. When you see the Add Relationships application map, look below the map and click the Add Relationship
button to add a relationship.
? A row with a From drop-down list to the left and a To drop-down list to the right appears.

4. In the From drop-down list, select the server and AppDomain or JVM to connect from. The name you see is in
this format: <server>:<web-site-name>#<AppDomain/JVM>

5. On the same line, in the To drop-down list, select the server and AppDomain or JVM to connect to.
? Dotted lines draw the connection in the actual application map.
? Note that no remote application tiers are shown in the list, only servers and AppDomain/JVMs.

6. To add more relationships, repeat the preceding steps starting with step 3.

7. To delete a relationship, click the to the far right in that row.

8. When you have connected all servers and AppDomains/JVMs that should be connected in the map and deleted
any extraneous relationships you might have added, click Save to save the revised application definition.

9. When you next view the map in the “Application Map Tab“, the relationships you added manually will show in
the map. They do not affect the behavior of the application and are strictly for the purpose of clarifying internal
application connections for those who view the map.

Riverbed SteelCentral AppInternals Version 10.0 75

Define an Application Screen
76 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 14 Transaction Types

Overview

A transaction type is a series of patterns that match some set of interesting transactions. You specify one or more
patterns and associate them with a friendly transaction type “Name“.
AppInternals shows transaction types directly in “Data Analysis Tabs“ and also uses them indirectly to configure
application definitions, alerts, and thresholds. Transaction types are used as follows:
 The “Top Transaction Types Card“ in the “Overview Tab“ shows a bubble chart with the transaction types that

matched the most transactions.
 Users can specify the name as the “transactiontype“ search field value in the “Search Tab“.
 The name of matching transaction types appear in the Transaction Type column of the results table of the

“Search Tab“.
 Application definitions can specify transaction type name as one of the criteria that define an application. (See

“Define an Application Screen“ for details.)
 The “Alert Configuration Screen“ uses the “Priority“ for the transaction type as a condition to determine whether

to trigger an email alert.
 “Transactional Thresholds“ specify a transaction type and response time values:

– If a matching transaction violates a threshold (in other words, exceeds the response time), AppInternals
evaluates conditions specified in the “Alert Configuration Screen“.

– AppInternals also uses transactional threshold violations to calculate Apdex scores, as described in
“Transactional Thresholds and Apdex Scores“.

What are “End to End Transactions” and “Transaction
Segments”?

In addition to specifying patterns that match interesting transactions, all transaction types must specify the scope of the
performance data they are evaluated against. The scope of the data indicates which part of a potentially-complex series
of related transactions you are interested in investigating.

Riverbed SteelCentral AppInternals Version 10.0 81

Transaction Types

The scope of the data is related to whether AppInternals generates it from monitoring applications or web pages:
 Application performance: AppInternals monitors application performance at a JVM (for Java) or appdomain

(for .NET) level. JIDA or the dotNet sub-agent instrument processes on the application tiers where they are
configured. (You enable instrumentation by choosing “processes to instrument” in the “Agent Details Screen“
screen.)
This application monitoring generates transaction trace data at the JVM or appdomain level. AppInternals detects
related transactions from different traces on multiple application tiers and “stitches” them together.
 Web page performance: AppInternals monitors web page performance by collecting data on page loads and (if
configured in the “Customize Snippet“ options of the “Configuration Settings Screen“) AJAX requests in users’
web browsers. This data reflects application performance from the perspective of the end user.
The options available in the “Applies To“ setting specify which type of data the transaction type will be evaluated
against:
 Transaction Segments: Evaluate against application performance data only, and only the individual,
“unstitched” transaction traces. This data is always specific to a single server and will never include web page
performance data.
 End-to-End Transactions: Evaluate against web page performance data and stitched application performance
data. Do not evaluate against unstitched transaction traces.
 End-to-End Transactions and Transaction Segments: Evaluate against web page performance data, stitched
application performance data, and unstitched transaction traces.

“Transaction Segments” Not Allowed with Certain Criteria

Note that some fields in the “Match Field List“ are not allowed with Transaction Segments and End-to-End
Transactions and Transaction Segments. Specifying these fields would result in a transaction type that never
matches any transaction segments. Although the transaction type could potentially match end-to-end trace data, to
avoid confusion, AppInternals does not allow you to specify these fields with either option that includes Transaction
Segments:
 Any field that is generated from web page performance data (such as “Page Titles“). These fields will never

match data in a transaction segment.

82 Riverbed SteelCentral AppInternals Version 10.0

Transaction Types
 The “Servers“ field, in a criterion that specifies Match all and more than one pattern to match. Transaction

segment data always refers to a single server, so specifying that a transaction must match multiple server patterns
will never match data in a transaction segment:

Create a Simple Transaction Type

This example shows how to create a simple transaction type. This example matches any invocation of the orders.aspx
ASP.NET page:

1) In the “Manage Transaction Types Screen“, click Add a Transaction Type.
2) The “Define a Transaction Type Screen“ opens. Supply a transaction type name (Orders)

Riverbed SteelCentral AppInternals Version 10.0 83

Transaction Types
3) In the “Add Criteria“ area choose url in the Match any of these list and supply a pattern of */orders.aspx:

4) Click Save.
In the “Search Tab“, users can then specify the Orders transaction type to search for that URL pattern:

84 Riverbed SteelCentral AppInternals Version 10.0

Transaction Types

Manage Transaction Types Screen

This screen lists any transaction types that have been defined. Use this screen to add, edit, or delete transaction types,
and change their precedence.
Click the row for an existing transaction type to select it. Details for that transaction type appear below the list.

Operations and Controls

 To add a new transaction type, click Add a Transaction Type. The “Define a Transaction Type Screen“
opens.

 To edit an existing transaction type, click the edit icon ( ) in the row for the transaction type you want to edit.
The “Define a Transaction Type Screen“ opens with the settings for that transaction type.

 To delete an existing transaction type, click the delete icon ( ) in the row for the transaction type you want to
delete. When you delete a transaction type, any “Transactional Thresholds“ that refer to it are also deleted. When
you delete a transaction type, you receive a warning if any application definitions refer to it.

 To change the precedence of a transaction type, click the number in the Precedence column in the row for the
transaction type. See “Transaction Type Precedence“ for details.

 To sort the list, click on any column heading to sort the column it in ascending order based on the column value.
Click the column heading again to sort in descending order. An icon indicates ascending or descending sort order.

Transaction Type Precedence

Transaction data (scoped as specified in the “Applies To“ setting) can match only a single transaction type.
AppInternals evaluates transaction types in the order specified in the Precedence column (precedence 1 is evaluated
first, 2 second, and so on). AppInternals assigns the first transaction type that matches a specific transaction and
ignores any subsequent transaction types that match.
When you create a new transaction type, AppInternals assigns the next available precedence.
Change the precedence of a transaction type by selecting its row and clicking the Precedence number. Supply a valid
precedence value (from 1 to the highest precedence) in the text box that opens.
AppInternals assigns the new precedence and shifts the other precedence values as appropriate. For example, if you
have 10 transaction types and change the precedence of the transaction type currently assigned precedence 5 to be 8,
then Transaction Types with precedence from 6 to 8 will be adjusted to 5 to 7.

Define a Transaction Type Screen

This section describes the fields that define a transaction type.

Name

A name that identifies the transaction type throughout the user interface. The name must be unique among transaction
types. The names are case-insensitive, so you cannot have two transaction types named “FOO” and “foo”. You cannot
change the name once you save the transaction type.

Riverbed SteelCentral AppInternals Version 10.0 85

Transaction Types

Applies To

The scope of transaction trace data that this transaction type will be evaluated against.
As noted in “Match Field List“, not all criteria are allowed with End to End Transactions and Transaction Segments
and Transaction Segments.
See “What are “End to End Transactions” and “Transaction Segments”?“ for more details.

Priority

Specifies the priority of the transaction type. The “Transactional Alerts“ section of the “Alert Configuration Screen“
specifies which transaction type priorities can potentially trigger alerts.
Assign a priority that corresponds to the importance of the transactions that will match the transaction type. For
example, a “shoppingCart” transaction might be critical while “internalWiki” might be low priority.
You can then choose to configure alerts so they only trigger on transaction type of given priorities.

Description

An optional description that appears in the “Manage Transaction Types Screen“.

Match the following criteria

This area specifies the patterns that you want this transaction type to match.
Click “Add Criteria“ to specify one or more criteria that each specify patterns. Each criterion specifies a field to match
(see “Match Field List“) and one or more corresponding patterns to match.
By combining multiple criteria and, within a criterion, multiple patterns, you can create flexible sets of pattern matches
using logical AND and OR operations:
 A transaction must match all criteria specified for a transaction type. (In other words, AppInternals evaluates

multiple criteria as a logical AND operation).
 Within a criterion, you can choose whether the specified transaction field value matches any of the corresponding

patterns (a logical OR operation) or must match all of them (a logical AND operation).

Add Criteria

When you add a new transaction, the screen opens with a single “Criterion Details“ area. Click Add Criteria to add
more criteria.

Criterion Details

For each criterion, you must specify a transaction field and one or more patterns you want its value to match. If you
specify multiple patterns, you also need to specify whether the field value matches any or all of them.

Match any / Match all

This setting has an effect only if you specify multiple patterns in a criterion:
 Choose any if the field value needs to match only one of the patterns (a logical OR operation).

86 Riverbed SteelCentral AppInternals Version 10.0

Transaction Types

 Choose all if the field value must match all of the patterns (a logical AND operation).

Match Field List

Values in the Match any/all of these list are similar to search fields described in “Search Field Reference“.

Match Field Matches
AppDomain/JVMs
The name of a .NET app domain or Java JVM that AppInternals is monitoring. AppInternals
HTTP Headers discovers processes automatically and lists them in the “Agent Details Screen“ where you
Page Titles can choose to “instrument” and monitor them. The AppDomain/JVM value is the same as
that matched by the “instance“ search field in the Transaction Search tab.
Process Users
Rootclasses An arbitrary header value in an HTTP request within the transaction. This is similar to the
“header“ search field in the Transaction Search tab.
Rootclass.methods
Rootclass.method.para The title of the web page as specified by the HTML <title> tag in the page.
meters
Servers Specifying Page Titles is not allowed with “Applies To“ settings of either End to End
Transactions and Transaction Segments or Transaction Segments. See “What are “End to
End Transactions” and “Transaction Segments”?“ for details.

User name of the operating system user that launched the application process. This is similar
to the “processuser“ search field in the Transaction Search tab.

Class name of a top-level call (the outermost call in an application thread). This is similar to
the “class“ search field in the Transaction Search tab.

Note: The Rootclass match fields are more restrictive about which transactions they match
than the corresponding search fields. While the search fields match any transaction that calls
the specified class and method name, the Rootclass fields match only those transactions where
the class and method are the outermost call in the application thread.

Class and method name of a top-level call (the outermost call in an application thread). This
is similar to but more restrictive (see the note in “Rootclasses“) than the “class.method“
search field in the Transaction Search tab.

Class, method, and parameter name of a top-level call during the transaction. This is similar
to but more restrictive (see the note in “Rootclasses“) than the “class.method.parameter“
search field in the Transaction Search tab.

The system name of a system running the AppInternals managed node software that
generated the trace data. This is similar to the “server“ search field in the Transaction Search
tab.

Specifying Servers is not allowed with the following combination of settings:

• “Applies To“ setting of either End to End Transactions and Transaction Segments or
Transaction Segments

• “Match any / Match all“ setting of all

• Multiple “Match Pattern“ specifications

See “What are “End to End Transactions” and “Transaction Segments”?“ for details.

Web Service Methods The name of a web service method called during the transaction. This is similar to the
“webservicemethod“ search field in the Transaction Search tab.
SQL Families
An SQL statement group executed by a method call in the application. This is similar to the
SQL “sqlfamily“ search field in the Transaction Search tab.
Statements/Procedures
An SQL statement or procedure executed as part of a JDBC or ADO.NET call. This is
similar to the “sql“ search field in the Transaction Search tab.

Riverbed SteelCentral AppInternals Version 10.0 87

Transaction Types

Match Field Matches
URLs
URL Outbounds “Inbound” URLs in transactions. This is similar to the “url“ search field in the in the
URL Parameters Transaction Search tab.
Page Tags
“Outbound” URLs in transactions. This is similar to the “urloutbound“ search field in the
Transaction Search tab.

A parameter in the query string of an “inbound” URL requested by another tier. This is
similar to the “urlparameter“ search field in the Transaction Search tab.

Values of “Page Tags“ specified as custom fields in the JavaScript snippet that AppInternals
uses to monitor web page performance. Specify page tags in the “Customize Snippet“
settings of the “Configuration Settings Screen“. This is similar to the
“pageload.time.backend“ search field in the Transaction Search tab.

Specifying Page Tags is not allowed with “Applies To“ settings of either End to End
Transactions and Transaction Segments or Transaction Segments. See “What are “End to
End Transactions” and “Transaction Segments”?“ for details.

Match Pattern

Specify the pattern you want the value of the field to match. To specify multiple patterns that the field value must
match, click the + button.

 Patterns are not case sensitive.

 Patterns can use an asterisk (*) as a wildcard to match zero or more characters and a question mark (?) to match a
single character. Use a backslash (\) as an escape character before either wildcard to match that character in a
string. You can use wildcards anywhere within the pattern. For example, the following pattern will match systems
named vh6-rh5-4 and vh8-w2k8-1, but not vh14-w2k8-3 or ttw1:

vh?-*-?

88 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 15 IP Geography Mappings Screen

Overview

AppInternals tries to determine the geographic location of users that are accessing monitored applications from the IP
address of the user’s system. The location is included with performance data for specific page views.

However, for some IP addresses (secondary addresses, for example), the geographic location is reported as unknown
or other.

If you know the location for specific IP addresses, you can override the default location detection process and manually
map a custom location with any address.

The IP Geography Mappings screen lists any custom mappings. To create new mappings, click the + icon and open
the IP Geography Mapping dialog box.

IP Geography Mapping Dialog Settings

To add a custom mapping, supply an IP address or addresses and a corresponding country and region.

IP Range An IP address or range of addresses, using IPv4 dot-decimal notation. (IPv6 notation is not supported.) You
Country can provide the address in any of the following forms:
• A single IP address. For example:

10.46.35.253

• A range of IP addresses separated by a hyphen. For example:

10.46.35.0-10.46.35.255

• An IP address with asterisks (*) as wildcard characters. You can supply a wildcard in the first and fourth
octet. For example:

10.46.35.*
*.46.35.*

• A CIDR (Classless Inter-Domain Routing) prefix/mask representation of an address range. For example,
here is the CIDR representation of the range 10.46.35.0-10.46.35.255:

10.46.35.0/24

The country to associate with the value in the IP Range setting. Choose a value from the list.

Riverbed SteelCentral AppInternals Version 10.0 89

IP Geography Mappings Screen

Region The region within a country to associate with the value in the IP Range setting. Choose a value from the list.
Lat/Long (Choosing a region is optional.)

Description The latitude and longitude of the user’s location. This setting is optional and has no effect on the country and
region that AppInternals associates with a particular IP address. Its only use is to provide coordinates to
Google maps. Supplying coordinates here causes the icon to appear in the Location line of “Overview“
block of the “Transaction Details“ screen. Users click the icon to open Google maps in a separate
browser window with a map that is centered on the coordinates.

Specify values in decimal format (90 to -90 for latitude, 180 to -180 for longitude). For example, for
Nashua, New Hampshire, USA:

Lat 42.765366

Long -71.467566

You can find coordinates for any location from web sites such as http://www.latlong.net.

An optional description that appears in the list of custom mappings.

90 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 16 Search Context Configuration
Screen

This screen specifies search strings users can choose in the “Search Area“ of the “Search Tab“ to further limit searches.
Users choose from search context strings in a list that appears in the “Show the top“area. For example:

If there are no search context strings defined in this tab, the For list does not appear in the Find the Top area.
A typical use for search contexts is to create search strings that differentiate among different applications that
AppInternals is monitoring.
AppInternals implicitly adds the search string using the AND logical operator. The string is not visible in the search
text, but is added after any user-supplied search string but before any “Search Analysis Operators“.
To add a search context string, click Add a Search Context and supply these values in the dialog box that opens:
 Display Name: the name that will appear in the search context list
 Description: an optional description that appears when users select the search context and pause the mouse

pointer over the name
 Query: the search string to implicitly add to the user’s search. The search string can specify “Compound Filter

Conditions“, but cannot specify an analysis operator. For example:

Click Save to close the dialog box and save changes. 93
Riverbed SteelCentral AppInternals Version 10.0

Search Context Configuration Screen
94 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 17 Collector Configuration Screen

The collector is the AppInternals component that receives web page performance data through browsers. This data is
generated by embedding a JavaScript snippet in web pages. The JIDA and dotNet sub-agents embed this snippet
automatically when you select the “Enable JavaScript Instrumentation (End-User Experience)“ option in the
“Configuration Settings Screen“.
This screen controls the address and port (HTTP and HTTPS) for the collector. Changes here affect the JavaScript
snippet for all configurations.
By default, the settings on this screen are the same as those for the rest of the analysis server. This default is suitable
in environments where all client browsers that access pages you want to monitor can also access the analysis server
host name. However, in cases where the analysis server host name is not resolvable to all browsers, you need to provide
an address that is.

Settings

Collection Server Address

The address for browsers to send web page performance data. This corresponds to the collector: property in the
JavaScript snippet. (Click “View Snippet“ in the “Configuration Settings Screen“ to see the snippet.)
When AppInternals is first installed, this value is the placeholder analysis server host name appinternals.local. As
long as the Collection Server Address is appinternals.local, it will be updated when the analysis server host name
changes. (You can change the analysis server host name in the “Network Configuration Screen“, through the network
“wizard” (the CLI command “networkcfg“) or the CLI command “hostname“.)
Once you change the collector address changes, however, changing the analysis server host name will not also change
this value. This behavior allows the initial network configuration (as described in “Configuring Networking on the
Virtual Machine“) to provide a reasonable collector address, but preserves the collector address if you change it here.

HTTP Port

The HTTP port for browsers to send web page performance data. This corresponds to the collectorHttpPort: property
in the JavaScript snippet. (Click “View Snippet“ in the “Configuration Settings Screen“ to see the snippet.)

Riverbed SteelCentral AppInternals Version 10.0 95

Collector Configuration Screen

HTTPS Port

The HTTPS port for browsers to send web page performance data. This corresponds to the collectorHttpsPort:
property in the JavaScript snippet. (Click “View Snippet“ in the “Configuration Settings Screen“ to see the snippet.)

Proxy Considerations for Collecting Traffic from External End
Users

One case where you need to supply a different value for the “Collection Server Address“ is when there is a firewall (or
similar, such as a proxy server, load balancer, or Internet accelerator) between the AppInternals analysis server system
and external client browsers on the Internet that access web pages you want to monitor.
The following steps show how to direct traffic from the external browsers, only, to the AppInternals collector
component that consumes it. Other traffic, such as internal users that connect to the AppInternals web interface, will
not be affected.
 Configure the external-facing firewall to only send traffic with the URL */beacon.gif* directly to the

analysis server host name on port 80. Consider handling SSL termination at this point here as well. This avoids
having to configure the external-facing certificate in the “TLS Certificate Configuration Screen“ and reduces the
load on the analysis server.
 In this screen, set the “Collection Server Address“ and “HTTPS Port“ to match the external-facing domain name.

96 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 18 Date/Time Configuration Screen

Overview

Settings in this screen specify the time source for the system time on the virtual machine where the analysis server is
running. This is important because the analysis server time must be synchronized with the system time on the agents
it monitors.
You need to configure all agents and the analysis server system to be synchronized with an external time service.
 If the system time on agents in your environment are already synchronized, specify the network time server or

servers for your environment.
 If system times are not synchronized, you must also configure time synchronization on the agents in addition to

specifying the time sources here. See “Agent Time Synchronization“ for details.

Description of Fields

Current Date/Time

Displays the current time on the analysis server virtual machine.

NTP Servers

Specify the fully-qualified domain name or IP address of one or more time servers with which to synchronize the
system time. When you click Apply, the values specified here are written to the file /etc/ntp.conf.
Before specifying time servers here, you can use the configuration-mode CLI commands “ntpq“ and “ntpstat“ to see
whether the analysis server is already synchronized, and to which time servers.
Typically, specify the same local time servers used by the agent systems that the analysis server is monitoring.
If you specify multiple servers, the virtual machine uses all of the servers to determine the correct time.

Riverbed SteelCentral AppInternals Version 10.0 99

Date/Time Configuration Screen

Server Time Zone

Specify the time zone for the analysis server. This setting has limited effect. It changes the time zone displayed by the
“date“ CLI command. It also changes the time zone used in system logs, network headers, and when the analysis server
connects to other systems (for example, to SMTP servers for e-mail alerts).
This setting does not control the time zone used in the Web interface. The Web interface uses the time zone for the
user’s system as determined by the browser. It also does not affect the time stamps used in analysis server logs.

100 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 19 Diagnostic Bundle Screen

A “diagnostic bundle” is a compressed package of analysis server log files and output from commands and
troubleshooting scripts. Typically, you generate a diagnostic bundle at the request of Riverbed support.
This screen provides links to generate and download diagnostic bundles for the analysis server. It also has links to
download diagnostic bundles for agents created from the “Agent Details Screen“.
Note that you can use the “Configuration Mode“ CLI commands “debug generate“ and “debug generate detailed“ to
create diagnostic bundles if the Web interface is not available.
This screen also has an option to enable “Diagnostic Mode“.

Generate Diagnostic Bundle

Click this link to generate a diagnostic bundle for the analysis server. A link to copy the resulting .zip file appears in
the “Server Diagnostic Bundles“ area.

Generate Detailed Diagnostic Bundle

Click this link to generate a more-detailed diagnostic bundle for the analysis server. A link to copy the resulting .zip
file appears in the “Server Diagnostic Bundles“ area.

Server Diagnostic Bundles

This area shows links to download previously created diagnostic bundles for the analysis server. Click a link to copy
the file to your local system. Only the two most-recently generated diagnostic bundles appear here.

Riverbed SteelCentral AppInternals Version 10.0 101

Diagnostic Bundle Screen

Agent Diagnostic Bundles

This area shows links to copy previously created diagnostic bundles for agents. (You generate diagnostic bundles for
agent by clicking the “Download the agent logs and diagnostic files“ link in the “Agent Details Screen“.)
Click a link to copy the file to your local system.

Diagnostic Mode

Select this option to show advanced details, such as additional fields in search results, throughout AppInternals.
Enable diagnostic mode to help troubleshooting problems in AppInternals.
The effects of enabling diagnostic mode include:
 Inclusion of the Download Trace link at the top of the “Transaction Details“ window.
 Display of additional fields in the “Call Details Tab“ in the Transaction Details window.
 Ability to refresh cards in the “Data Analysis Tabs“ by clicking their title. This is useful for troubleshooting

because it causes the query that the card makes to be written to one of the log files (silo_query-queries.log)
included in analysis server diagnostic bundle.

102 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 20 Filter Rules Screen

This screen displays JSON text that specifies filters that prevent uninteresting transactions from being indexed and
stored in the AppInternals database. Use this screen to modify the default filters. This is not required and is typically
not necessary.

Overview

Some transactions are not useful in diagnosing performance issues. Most applications have internal processing that
may generate slow transactions but that are not performance problems. For example, Java application servers may have
internal threads that routinely make long-running socket calls as part of normal processing.

Riverbed SteelCentral AppInternals Version 10.0 103

Filter Rules Screen

Because they are long running, transactions from these calls can dominate search results in the “Search Tab“. The
following example shows how internal socket calls appear as the slowest over the time period:

Also, because such calls are often the only call in the thread, their transactions are not interesting for users to
investigate further in the “Transaction Details“ window.
To address these issues, AppInternals by default excludes transactions that are not useful for diagnosing performance
issues. This filtering reduces uninteresting “noise” transactions without affecting interesting transactions.
You can change this behavior by modifying the default filters. This is not required and is typically not necessary.

Default Filters

Use the default filters as examples you can adapt. For example, the following filters exclude transactions containing a
single top-level Java socket call to specific methods:

{
"rootcomponent": "remote",
"rootmethodname": "read",
"rootclassname": "java.net.SocketInputStream",
"maxcallcount": 1

},
{

"rootcomponent": "remote",
"rootmethodname": "write",
"rootclassname": "java.net.SocketOutputStream",
"maxcallcount": 1
},

104 Riverbed SteelCentral AppInternals Version 10.0

Filter Rules Screen

Some of the default filters are less restrictive. For example, these filters exclude transactions containing top-level calls
to any methods in specific Java socket classes:

{
"rootclassname": "java.net.SocksSocketImpl"

},
{

"rootclassname": "java.net.AbstractPlainSocketImpl"
},

Modifying the Default Filters

You can modify the existing filters or add new ones. Adapt the default filters to suit your purposes.

Note: Be Careful—Filters Can Exclude Transactions Required to Connect Related Transactions
Exercise care in creating or modifying filters. It is possible to exclude interesting transactions. In particular, filters can
exclude transactions that AppInternals requires for detecting cross-tier activity. When this happens, it effectively
disables the ability to include related transactions in the Transaction Details Window.

Make changes to the JSON text in the text box and click Save. If you supply invalid JSON, the screen displays an error
and disables the Save button. (You can use an external JSON and validator, such as http://jsonlint.com/, for
more-detailed validation.

Filter Usage Notes

Each filter specifies one or more field-value pairs:
 Most fields correspond to search fields you can specify in the Transaction Search screen.
 Each value must specify a complete match for the corresponding field. No wildcards are allowed.
 Values are not case sensitive.
 Only those transactions that match all the specifications of the filter will not be indexed or stored in the database.

In other words, AppInternals uses a logical AND operation on filter criteria to determine whether a transaction
matches.

Filter Field Values

The following table lists valid fields in a filter specification. Links in the table are to descriptions in the “Transaction
Search Reference“ material:

Field Name Description
instance
maxcallcount The “instance“ of the transaction.

maxduration The maximum number of calls in the transaction. Transactions with a larger number of calls will not
be excluded. Typically, specify a value of 1 in combination with other fields to help insure that
interesting transactions will not be excluded.

The maximum “responsetime“ of the transaction. Transactions with a larger duration will not be
excluded.

Riverbed SteelCentral AppInternals Version 10.0 105

Filter Rules Screen

Field Name Description
rootcomponent The “category“ of the top-level call in the transaction.
rootclassname The “class“ of the top-level call in the transaction.
rootmethodname The “method“ of the top-level call in the transaction.

Filters are only evaluated against transactions that the AppInternals stores after you make changes. They have no effect
on earlier transactions.

Restoring Default Filters

This section shows the complete set of default filters. You can use this to restore the default behavior if you want to
revert from changes that did not behave as expected. Copy and paste this text in its entirety to the text box and click
Save.

[
{
"rootcomponent": "remote",
"rootmethodname": "read",
"rootclassname": "java.net.SocketInputStream",
"maxcallcount": 1
},
{
"rootcomponent": "remote",
"rootmethodname": "write",
"rootclassname": "java.net.SocketOutputStream",
"maxcallcount": 1
},
{
"rootcomponent": "remote",
"rootmethodname": "connect",
"rootclassname": "System.Net.Sockets.Socket",
"maxcallcount": 1
},
{
"rootcomponent": "remote",
"rootmethodname": "close",
"rootclassname": "System.Net.Sockets.Socket",
"maxcallcount": 1
},
{
"rootcomponent": "remote",
"rootmethodname": "send",
"rootclassname": "System.Net.Sockets.Socket",
"maxcallcount": 1
},
{
"rootcomponent": "remote",
"rootmethodname": "EndReceive",
"rootclassname": "System.Net.Sockets.Socket",
"maxcallcount": 1
},
{
"rootcomponent": "generic",
"rootmethodname": "accept",

106 Riverbed SteelCentral AppInternals Version 10.0

Filter Rules Screen

"rootclassname": "org.apache.jk.common.ChannelSocket",
"maxcallcount": 1
},
{
"rootcomponent": "remote",
"rootmethodname": "accept",
"rootclassname": "System.Net.Sockets.Socket",
"maxcallcount": 1
},
{
"rootclassname": "java.net.SocksSocketImpl"
},
{
"rootclassname": "java.net.AbstractPlainSocketImpl"
},
{
"rootclassname": "com.sun.net.ssl.internal.ssl.AppInputStream"
},
{
"rootclassname": "com.sun.net.ssl.internal.ssl.AppOutputStream"
},
{
"rootclassname": "com.ibm.jsse.a"
},
{
"rootclassname": "com.ibm.jsse.b"
},
{
"rootclassname": "com.ibm.jsse2.e"
},
{
"rootclassname": "com.ibm.jsse2.j"
},
{
"rootclassname": "sun.security.ssl.AppOutputStream"
},
{
"rootclassname": "sun.security.ssl.AppInputStream"
},
{
"rootclassname": "java.net.PlainSocketImpl"
}
]

Riverbed SteelCentral AppInternals Version 10.0 107

Filter Rules Screen
108 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 21 System Status Screen

The Status screen shows statistics about data stored in the analysis server and the resources they consume.

Note: Refresh the Page to See Changes
The status page does not update automatically. You must refresh the web page display to see changes. (Or you can
navigate to another screen and back.)

Current Disk Usage shows the disk space used on the analysis server. It shows the size of the disk on the virtual
machine and the amount used. (See “Adding Data Storage“ for details on increasing the disk space.) When disk usage
exceeds 90 percent of the available disk space, AppInternals deletes the oldest data it has stored.
Indexed Transactions shows the number of transactions the analysis server has stored and the dates of the earliest and
latest transaction.
Environment Metrics shows the number of metric values the analysis server has stored and the dates of the earliest
and latest sample.

Riverbed SteelCentral AppInternals Version 10.0 109

System Status Screen
110 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 22 Agents License Configuration
Screen

When AppInternals is first installed, it operates under a trial license. Trial licenses provide full functionality up to 14
days after the first user logs in to AppInternals. After 14 days, the trial license expires and the AppInternals interface
will not display data after users log in.

Obtaining a License Key

After the license expires, you must buy an AppInternals license and obtain a license key (also called an activation key).
Click the link below (or in the license screen) to start the purchase process:

http://www.riverbed.com/appinternals/buy/?s_rbp=product

After you buy a license, you will receive an e-mail message from Riverbed support. The e-mail provides credentials
to log on to the Riverbed support site and instructions for obtaining the license key.

Before you obtain a license key, be sure that the analysis server has been configured with a fully-qualified host name.
You need that host name to obtain the license key. See “Configuring Networking on the Virtual Machine“ in the
“Analysis Server Installation“ documentation for details.

Adding a License

Paste the license activation key from the Riverbed support site in text box and click Save. Log out and back in to the
AppInternals interface. AppInternals checks license status only when users log in, so all users must log out and in to
take advantage of a new license.

License Status Messages and Meaning

AppInternals checks license status only when users log in. Here are the possible license status messages:

Message Notes

This is a trial license that Trial licenses provide full functionality up to 14 days after the first user logs in to
expires <timestamp>. AppInternals. With a trial license, this message appears 10 minutes after users log in. After
14 days, the trial license expires and the AppInternals interface will not display data.
Warning: this license will
expire <timestamp>. When a valid (non-trial) license is within 30 days of expiring this message appears 10
minutes after users log in.

Riverbed SteelCentral AppInternals Version 10.0 111

Agents License Configuration Screen

Message Notes

Expired license. You need a This message appears after a license expires. Users can access all screens in the AppInternals
new license key to see data. interface, but see “no data” messages or errors where data should display. In addition,
License is invalid messages appear on some screens.
Could not determine license
state. Log in again and call If AppInternals cannot determine the license state, it displays this message and the behavior
support if the problem is the same as with an expired license.
persists.

112 Riverbed SteelCentral AppInternals Version 10.0