Aternity APM for VMware Tanzu

Summary of Steps

Aternity® APM for VMware Tanzu includes an Aternity APM Service Broker and a BOSH add-on for the APM Agent. Install and configure the tile to deploy the agent on VMware Tanzu VM hosts. Create an APM service instance. Then, bind each application you want to monitor to the APM service instance.

alt-text=""

One-time steps in the VMware Tanzu environment:

  1. In VMware Tanzu Ops Manager, import the tile.
  2. In VMware Tanzu Ops Manager, configure the tile to specify connection details for the analysis server that will host the agent data.
  3. In Pivotal Apps Manager, create an instance of the APM service.

Steps for each application (repeat these steps when the application changes):

  1. Set Environment Variables for the application, usually in its manifest.
  2. Bind the application to the APM service instance.
  3. Restage the application.

Product Snapshot

The following table provides version and version-support information about the Aternity APM for VMware Tanzu.

Element Details
Tile version v11.7.1-BL518
Release date September 25, 2020
Software component version v11.7.1
Compatible Ops Manager version(s) v2.7.x, v2.8.x, v2.9.x
Compatible VMware Tanzu Application Service for VMs version(s) v2.7.x, v2.8.x, v2.9.x
BOSH stemcell version Ubuntu Xenial
IaaS support AWS, GCP, vSphere, Azure, and OpenStack
IPsec support? Yes

Requirements

You must have an APM analysis server available to harvest transactional and environmental data from your application generated by the APM agent. You specify the analysis server when you configure the APM service broker.

As described in Licensing, the analysis server must be licensed in order to display data harvested from agents.

Offline Buildpack Instructions

Alternatively, deploy Aternity® APM for VMware Tanzu by simply adding the buildpack and environment variables to your application’s manifest.

alt-text=""

One-time Setup Steps

Buildpack

Create a versioned offline buildpack.

cf create-buildpack aternity-apm-dotnet-core-buildpack-11_7_1_BL518 aternity-apm-dotnet-core-buildpack-11.7.1_BL518.zip

Versioning the buildpacks allow you to use different versions of the instrumentation with different applications.

Application Security Group

The APM instrumentation communicates to the Analysis Server using port 7090 by default. An application security group must be defined to enable this communication.

Example JSON configuration, where Analysis Server IP is 192.0.2.1.

[
  {
    "protocol": "tcp",
    "destination": "192.0.2.1",
    "ports": "7090",
    "log": true,
    "description": "Allow instrumentation traffic to Analysis Server"
  }
]

Create the security group and then bind it.

cf create-security-group NAME PATH-TO-JSON-FILE
cf bind-running-security-group NAME

Instrumenting An Application

Add environment variables to the env block of your application’s manifest.yml.

  env:
    RVBD_APP_CONFIG: <config-name>
    RVBD_APP_INSTANCE: <instance-name>
    RVBD_ANALYSIS_SERVER: 192.0.2.1

Add the versioned Aternity APM buildpack to the buildpacks block in your application’s manifest.yml.

  buildpacks:
  - aternity-apm-dotnet-core-buildpack-11_7_1_BL518
  - dotnet_core_buildpack

Push your application.

cf push

Limitations

This version does not support Applications on Windows stemcells.

Feedback

For VMware Tanzu feature requests, questions, or information about a bug, email VMware Tanzu Feedback.

For APM support:

Licensing

The APM analysis server is available as a Software as a Service (SaaS) offering and as an on-premises installation.