For full information, please check the release notes
|Part 1||Part 2|
AppInternals Version 10.10.0 updates both the analysis server and agent software. It is available both as a SaaS and on-premises release. Version 10.10.0 of the agent requires 10.10.0 or later of the analysis server.
Edit options to display additional metric data. The new options are to display response time, transaction count, CPU usage, and total response time:
This feature is parallel with the Transaction Types Bulk Edit With Export and Import introduced in Version 10.8.0.
-Dcom.sun.management.jmxremote \ (IBM JVM only)
-Djava.rmi.server.hostname=<Host IP> \
-Dcom.sun.management.jmxremote.rmi.port=<Exposed port> \
-Dcom.sun.management.jmxremote.port=<Exposed Port> \
Unless the Collect End-User Experience Data option was enabled, the analysis server could not identify users’ locations. Now, if end-user experience data is not available, the analysis server attempts to find the user IP addresses in transaction trace data.
The calls analysis operator displays a table with performance data for method calls. New for this release, calls accepts the -group_by argument to add a column for the specified field. For example, group_by transactiontype:
Version 10.10 of the SaaS analysis server can be specified as a data source in SteelCentral Portal. (Previous SaaS releases did not work as SteelCentral Portal data sources.) This integration is supported by SteelCentral Portal Version 1.5.2 and later
Note that, when adding the data source in SteelCentral Portal, you must first determine if the AppInternals user has access to more than one company (also called account and realm in AppInternals). In AppInternals, users with access to multiple companies see them when they log in and in the Realm drop-down list:
If the AppInternals user has access to more than one company, you must specify the company ID along with the user name in the SteelCentral Portal Add Data Source dialog box. In AppInternals, find the company ID by clicking the ACCOUNT link in the top menu bar to open the Account Details page in a separate browser window. The company ID is underneath the company name:
Version 10.10 agents installed on Windows systems will now automatically report details of process activity to the SaaS analysis server. Previously, only agents on Linux systems reported this data. (This feature is not available for on-premises analysis servers.)
Version 10.10 agents installed on Windows systems can now be configured to report details of network activity to the SaaS analysis server. Previously, only agents on Linux systems reported this data. (This feature is not available for on-premises analysis servers.)
This feature requires that the WinPcap library be installed on the Windows system. The library is not included as part of the agent installation. You can download WinPcap at https://www.winpcap.org/install/default.htm. After installing WinPcap, restart the AppInternals agent.
The Network Data section of the Agent Details page has settings to control whether network data is reported and configure which traffic will be monitored. These are the same controls as for Linux systems.
The new monitor-system CLI command makes it easy to install the AppInternals agent on an analysis server. This is useful to monitor performance of that analysis server. Specifically, the agent monitors the webui service that controls the Tomcat server that hosts the analysis server web user interface.
Riverbed SteelCentral AppInternals Agent Setup Menu:
1) Install agent
2) Return to CLI
Select one of the options above and press enter :
1) Show agent status
2) Start agent
3) Stop agent
4) Restart agent
5) Uninstall agent
6) Return to CLI
Select one of the options above and press enter :
This release allows a single agent installation on a Docker host to monitor any number of containers running on the host. This is in contrast with previous releases that required that the agent be installed on each container. The new approach offers the following advantages:
The agent installed on the Docker host appears in the AppInternals interface agent like any other agent. For instance, it appears as an entry in the Agent List screen, can be configured in the Agent Details screen, and appears in the Servers tab like other agents.
By comparison, instrumented containers are not full-fledged agents. They do not appear in the Agent List screen and do not have their own Agent Details screen for configuration. The AppInternals interface uses the Docker icon () to indicate containers and instrumented processes running in them.
For example, the Servers tab shows the container ID and image name of Docker containers in the Server column of its table, denoted by the Docker icon. The Server Tagscolumn shows special “container tags” created automatically by the agent that give additional information about the container.
[started] PID: 3820 Name: dsa Command: [.\DsaServer.exe, -d]
[started] PID: 3520 Name: agentrt Command: [.\agentrt_agent.exe, -d]
[started] PID: 9744 Name: dotnetagent Command: [.\dotnetagent2.exe, -d]
[started] PID: 12296 Name: npm Command: [.\npm_agent.exe]
[started] PID: 9928 Name: osda Command: [.\os_agent.exe, -d]
[root@11A bin]# ls -al agent dsactl
-rwxr-xr-x 1 root root 7871 Jun 13 12:39 agent
lrwxrwxrwx 1 root root 33 Jun 15 15:24 dsactl -> /opt/Panorama/hedzup/mn/bin/agent
[root@11A bin]# ./agent ?
Valid commands are help, status, start, start <process name>, restart, restart <process name>, stop, stop <process name>
[root@11A bin]# ./agent status
[started] PID: 4717 Name: dsa Command: [./dsa, -d]
[SaaS Only] Name: npm Command: [npm_agent]
[started] PID: 4854 Name: agentrt Command: [./agentrt]
[started] PID: 4861 Name: osda Command: [./os_agent]
The Agent Support for Proxy Servers introduced in Version 10.8.0 allowed AppInternals agents to connect to the analysis server through a proxy server. However, agents did not support proxy servers that required authentication.
In this release, agents can connect to proxy servers that use Basic and Digest authentication (NTLM authentication is not supported). The agent installation on Windows and Unix-like operating systems prompts for details. For example, on Windows:
After installation, use the proxy_cred_util.sh script in <installdir>/Panorama/hedzup/mn/support directory (<installdir>\Panorama\hedzup\mn\support\proxy_cred_util.bat on Windows systems) to change or test proxy-server connections. Run the script without any arguments for usage details:
usage: proxy_cred_util -u userid:password [-r realm] [-p proxyHost:proxyPort -d url] -x
-u userid:password - user ID and password for proxy authentication. Mutually exclusive
with -x option.
-r realm - (optional) the authentication realm for the proxy. If omitted
the authentication will take place for any realm
-p proxyHost:proxyPort - (optional) if verifiying proxy settings, the proxy address
and port. If proxy port is omitted it defaults to 8080.
-d url - (optional) if verifiying proxy settings, the URL
we will use to make a test connection.
-x - No authentication is required. Mutually excusive with -u option.
The Riverbed Process Injection Driver (RPID) enables instrumentation for Java and .NET processes on Windows systems. After several releases of beta testing, it is enabled and started on Version 10.10 agent installations and upgrades.
RPID automatically injects into all .NET and Java processes without the use of the COR_* environment variables, JAVA_TOOL_OPTIONS, command line, script modifications, environment variables, or any other user intervention. There is no need to set environment variables, change command lines, or use tools such as JidaRegister.exe to set JAVA_TOOL_OPTIONS.
Riverbed Process Injection Control
Driver Version 10.10.586.0
Copyright 2014-2017. Riverbed Technology. All rights reserved.
Start type: system start