VMware

VMware vFabricTM AppInsight 1.1.1 Release Notes

vFabric AppInsight 1.1.1| 30 May 2012 | Build 72400

Last Document Update: 23 May 2012

These release notes cover the following topics:

What's New?

AppInsight 1.1.1 adds the following enhancements to the AppInsight 1.1 release.

  • Scalability and performance enhancement, including the ability to split AppInsight and the AppInsight database to manage performance in large environments.
  • Resolution of certain issues that were detected in AppInsight 1.1.

VMware vFabric AppInsight 1.1 Documentation

VMware vFabric AppInsight Installation Guide

VMware vFabric AppInsight User's Reference

VMware vFabric AppInsight Developer's Guide

System Requirements for VMware vFabric AppInsight 1.1 Installation

Before you begin the installation, make sure you have these system requirements available. You also need to have specific ports open for the AppInsight server virtual machine and network probe.

System Requirements

You require the following disk space and memory for the AppInsight server virtual machine and the network probe:

  • AppInsight Server virtual machine: 50 GB disk space; 8 GB memory*, 4 vCPU**
     * In an environment of more than 300 application components, increase the memory of the AppInsight Server virtual machine to 12 GB.
    ** In an environment of less than 30 application components, 2vCPU are sufficient.
  • Network probe: 6 GB disk space; 1 GB memory, 2 vCPU

In addition, you require the following open ports for the AppInsight server virtual machine and the network probe:

  • AppInsight Server virtual machine
    • TCP Port 80, 8443 - For the AppInsight user interface connection from the external client.
    • TCP Port 1194 - For the network probe connection to this AppInsight server virtual machine
    • TCP Port 21234 - (Optional) Code agent connection with the AppInsight server
  • Network Probe
    • TCP Port 1194 - For the connection to the AppInsight server virtual machine
    • UDP Port 123 - For the NTP on the AppInsight server virtual machine
    • TCP Port 5671 - (When multiple collectors are installed) For the connection to the AppInsight message queue

Supported Screen Resolution

AppInsight is supported on screen resolutions of 1024 x 768, and higher.

VMware recommends that you view vFabric AppInsight in full screen mode.

Web Interface Support

Supported Web browsers:

  • Microsoft Internet Explorer 8, 9
  • Google Chrome 12
  • Mozilla FireFox 3.6
  • Safari 4.0.4

Installation Notes

Refer to the VMware vFabric AppInsight Installation Guide for installation instructions.

Upgrading to AppInsight 1.1.1

To upgrade from AppInsight 1.1 to AppInsight 1.1.1:

  1. Download -appinsight.1.1.1.update.tar.gz from the web site to the AppInsight server virtual machine.
  2. Run # tar xzf appinsight.1.1.1.update.tar.gz to extract the TAR file.
  3. From the current directory, run #update.sh script.
    The script stops AppInsight, performs the upgrade, and restarts AppInsight.

Following the upgrade:

  • Reinstall the network probes by deleting the old probes and installing new ones, as described in the Installation Guide.
  • If you have monitored applications that use GemFire, reinstall the code agents by uninstalling the existing code agent and installing a new one, also described in the Installation Guide.

Configuring AppInsight For Monitoring Large Datacenters

If you are monitoring a datacenter comprising more than one hundred virtual machines, you can separate the AppInsight server and database functions to optimize monitoring performance.

Use the following procedure to split the server and database functions. You must have installed AppInsight before you begin this procedure.

To split the AppInsight server and database to run on separate virtual machines

  1. On the AppInsight server, run /opt/bhive/conductor/bin/before-split-procedure.
  2. Stop the AppInsight process.
    1. Type conmanage.py and press Enter.
    2. Type stop_appinsight and press Enter.
    3. Type quit and press Enter.
  3. Power off the AppInsight server virtual machine.
  4. Take a snapshot of the AppInsight server virtual machine.
  5. Clone the AppInsight server virtual machine to create the database virtual machine.
    It is a best practice to locate the database virtual machine on the same ESX server as the AppInsight server virtual machine.
  6. Power on the AppInsight server virtual machine.
  7. On the database virtual machine, set the memory size to 4GB.
  8. Power on the database virtual machine.
  9. On the database virtual machine, run /opt/bhive/conductor/bin/split-procedure-db.
    The script receives the IP address of the AppInsight server virtual machine as an argument
    /opt/bhive/conductor/bin/split-procedure-db <IP address of the AppInsight server virtual machine>.
  10. On the database virtual machine, type ifconfig tun0 to identify the internal IP address of the database virtual machine.
    The internal IP address is the IP address of the tun0 interface (OpenVPN network). Make a note of this IP address.
  11. Reboot the database virtual machine.
  12. On the AppInsight server virtual machine, type ps -ef | grep etc_init.d_conductor to check if the etc_init.d_conductor start process is still running.
  13. If the process is running, type kill -9 process ID to stop the process.
  14. On the AppInsight server virtual machine, stop the AppInsight process
    1. Type conmanage.py and press Enter.
    2. Type stop_appinsight and press Enter.
    3. Type quit and press Enter.
  15. On the AppInsight server virtual machine, run /opt/bhive/conductor/bin/split-procedure-brain.
    The script receives the internal IP address of the database server virtual machine as an argument.
    /opt/bhive/conductor/bin/split-procedure-brain --db-ip <IP address you noted in step 10>.
  16. Run service postgresql status to verify that the database virtual machine is running.
  17. Start the AppInsight process on the AppInsight virtual machine.
    1. Type conmanage.py and press Enter.
    2. Type start_appinsight and press Enter.
    3. Type quit and press Enter.

Starting and Stopping the AppInsight Server and Database Virtual Machines

You must always stop the AppInsight server virtual machine before you stop the database virtual machine.
You must always start the database virtual machine before you start the AppInsight server virtual machine.

Resetting the System Configuration on the Split Virtual Machines

To run a state reset on the split system, you must define the APP_IP environmental variable that specifies the IP address of the database virtual machine. Type export APM_IP=<IP address of the database virtual machine>.

Resolved Issues in the VMware vFabric AppInsight 1.1 and 1.1.1 Releases

The following issues have been resolved since the last AppInsight release:

Installation

  • If you use static IP addresses, VMware recommends that you use only one DNS server during installation. If you require more than one DNS server, add it manually to the /etc/resolv.conf file.
  • The version number of AppInsight 1.1 (build 71134) is incorrectly displayed as version 1.0.0.0 (build 638550) when running the OVA deployment, and in the vSphere Client summary tab.

User Interface

  • Incorrect colors might appear for widgets in the dashboard. Click Refresh to correct the widgets' colors.
  • VMware recommends that you wait until a view has finished loading before you switch to another view.
  • The Most Used Application widget in the dashboard appears disabled when you have not actived the Usage KPI.
  • The time picker does not show the entire selected time period. For example, if you select the 10 minute resolution, the time picker might show 10:41:30-10:50:30, which is only nine minutes.
  • You cannot download the code agent installation ZIP file or server snapshot from the AppInsight server using Internet Explorer 8. Download the file using one of the other supported browsers.

KPIs

    In the Components Health KPI, values that you set for the tolerate threshold are not effective.

Adapter Management

    If extra spaces are included in the Hostname text box when registering an adapter, AppInsight will not connect with the adapter.

vCenter Chargeback Integration

    If you unregister the Chargeback adapter from AppInsight, the application cost continues to appear in the General Details of the application.

Monitoring

    Changes that are made in external data sources, (vCenter, Hyperic, Chargeback and Orchestrator), might take up to 23 hours before monitored data is available.

User Management

  • A user who does not have Write permissions can add, edit and delete an application's alerts.
  • A user who has Write permissions for some applications, can create or edit a single "all applications" rule.
  • Application owners can view alerts for applications for which they do not have Application Owner permissions.

Known Issues with VMware vFabric AppInsight 1.1 and 1.1.1

The following known issues affect the AppInsight 1.1 and AppInsight 1.1.1 releases:

Installation

  • If there is a mismatch between the name of a vSwitch and the name of the AppInsight port group on the vSwitch, network probe deployment fails.
  • You cannot install a code agent on a Windows 2008 Server 64-bit running Tomcat 7.0.25 as a service. Upgrade to the next Tomcat version.
  • You cannot install a code agent on a tc server that is configured to use a wrapper.
  • The initial AppInsight installation takes significant time. There is no progress indicator during the installation process.

User Interface

  • When you add or remove a metric to a configurable chart, the colors of all existing lines change.
  • In Internet Explorer, a Certificate Error message appears.
  • Occasionally, "Application Infrastructure KPI" appears in the user interface instead of "Middleware KPI".
  • The name of a virtual machine that is powered off does not appear in the user interface. A different IP-based platform name appears.
  • Occasionally, hints do not show content. Refresh the page to show the content.
  • AppInisght only supports languages that read left-to-right.
  • When you filter the Notifications List, the Notification Details pane does not update.
  • Occasionally while large queries are being processed, KPI calculations are missed and data takes time to appear in the user interface.
  • When you try to log into AppInsight on Internet Explorer 9 on Windows 2008 R2, you get a blank page. Either disable Internet Explorer Enhanced Security Configuration, or configure it to allow access to the AppInsight server by changing the security level to medium.

KPIs

  • The Cost KPI is measured per hour, not per day as stated in the signpost help popup.
  • The Middleware KPI does not display metrics for MySQL Stats 5.1.x database or Tomcat 7.0 instances.
    To display metrics for a MySQL Stats database, in your AppInsight server console, edit /opt/vmware/apm/conf/am-adapter.properties as follows:
    1. Go to the Hyperic.adapter.component.mappings section and after DB= add MySQL Stats 5.1.x.
    2. Save the file.
    3. Restart the AppInsight service.
    To display metrics for Tomcat 7.0, in your AppInsight server console, edit /opt/vmware/apm/conf/am-adapter.properties as follows:
    1. Go to the Hyperic.adapter.component.mappings section and after WEB= add Tomcat 7.0.
    2. Save the file.
    3. Restart the AppInsight service.

vCenter Integration

  • In the case in which duplicate IP addresses exist in vCenter Server, which generally only occurs with internal IP addresses, AppInsight might display an incorrect virtual machine name.
  • Ensure that the virtual machines on the vCenter Server on which AppInsight is installed, do not share internal IP addresses.

Code Agent

  • Database transactions, other than JDBC, are not recognized by the code agent.
  • When you install multiple code agents, the temp folder becomes full, causing the AppInsight server to stop working.
    Delete the content in the /opt/vmware/apm/insight-dashboard/temp directory after each code agent installation.

vFabric Hyperic Integration

  • During startup, if an adapter connection fails, AppInsight will not start.
    1. Stop the Hyperic server.
    2. Start AppInsight.
    3. Restart the Hyperic server.
    4. Reestablish the adapter connection.
  • Data that is retrieved from Hyperic might be inaccurate if the Hyperic time is not synchronized with APM Server time.
  • If the vFabric Hyperic server is restarted, AppInsight does not reconnect to Hyperic.
    You need to delete and reregister the vFabric Hyperic adapter.

vCenter Orchestrator Integration

    If a vCO is configured with multiple vCenter Servers and an action is performed on a virtual machine that uses the same name in multiple vCenter Servers, the action is not performed, to prevent errors. A message appears in the user interface log.

Topology

  • Correlations between network components that use a transparent proxy are not available.
  • When a server has two IP addresses, one for incoming traffic and another for outgoing traffic, hints related to outgoing traffic are not available.
  • If there is a correlation between components in the left-most tier of an application's topology, redundant transactions are created.
  • Rarely, when metrics are added or removed from vCenter or Hyperic, the change does not appear in the topology in AppInsight. Try restarting AppInsight to resolve the issue.
  • If you attempt to add a cloned virtual machine with a static IP address to the topology of an AppInsight application, the virtual machine will not be added.
  • Servers that use a range of ports are not supported. In AppInsight, the server is identified as a single application component.
  • When you add a new tier to the topology as the left-most tier, all existing transaction data is deleted. New transaction data is displayed on the new left-most tier, as it is detected by AppInsight.

Alerts

  • Only users with the Administrator role can create alerts for applications.
  • When you attempt to create a duplicate alert the message Server error:query did not return a unique result:2 appears.
  • You cannot define a single alert for multiple virtual machines.

Server

  • AppInsight supports PEM- and PKCS-format SSL keys. In the event that you are unable to manually add WebSphere SSL certificates, verify that your keys are of a supported format.
  • When the host clock for a probe is not synchronized with the clock on the server host, probe deployment will fail until the time on the probe host matches the time when the server was first installed on the server host.
  • In applications that are built from the same page template, for example Wiki, transactions are not learned by AppInsight.

Monitoring

  • AppInsight does not recognize Oracle errors. In such cases, 0% errors appears instead of the correct error rate.
  • When you create a new application component group, it might take up to 25 minutes before monitored data appears in the application's topology.
  • When you create a new application component group, the monitored data is not correct until each of the components in group have existed for the entire time resolution. For example, if an application group has three components that are being monitored in a time resolution of one hour, but one of the components was only created 45 minutes earlier, the displayed application component group data is only accurate after one hour and 15 minutes (after the most recently created component is in existence for one hour.)