New Relic Dotnet Extension Buildpack for VMware Tanzu

This documentation describes the New Relic Dotnet Extension Buildpack for VMware Tanzu and provides instructions on how to install the tile. The tile can bind New Relic agents to Dotnet Core or Dotnet Framework apps so you can monitor them in a VMware Tanzu environment.


New Relic Dotnet Extension Buildpack for VMware Tanzu Logo

Overview

The New Relic Dotnet Extension Buildpack for VMware Tanzu enables you to bind your Dotnet (Core and Framework) apps to New Relic Dotnet agents. This allows you to monitor the health and performance of these apps, analyze the data captured by agents, and additionally correlate the captured agent data with VMware Tanzu infrastructure metrics and events collected by the New Relic Firehose Nozzle.

The New Relic Dotnet Extension Buildpack for VMware Tanzu can be installed via the tile in Ops Manager. Alternatively, you can extract the .Pivotal file and install individual extension buildpacks using the cf Command Line Interface (CLI) command cf create-buildpack.

After you start monitoring your apps, you can set alerts based on any metrics that are collected by Dotnet agents using the New Relic alerting subsystem.

The New Relic Dotnet Extension Buildpack for VMware Tanzu installs one or more of the following buildpacks depending on the tile configuration (total of 8 extension buildpacks):

  • New Relic Dotnet Core Extension Buildpack for Dotnet Core Applications running on Ubuntu Xenial 16.04 stacks. This extension buildpack is non-cached.

  • New Relic Dotnet Core Extension Cached Buildpack for Dotnet Core Applications running on Ubuntu Xenial 16.04 in disconnected (isolated) VMware Tanzu deployments. This is for support of air-gapped environments where there is no access to the outside world.

  • 3 New Relic HWC Extension Buildpacks for Dotnet Framework Applications running on Windows 2012 R2 , Windows 2016, and Windows 2019 stacks. This extension buildpack is non-cached.

  • 3 New Relic HWC Extension Cached Buildpacks for Dotnet Framework Applications running on Windows 2012 R2 , Windows 2016, and Windows 2019 stacks in disconnected (isolated) VMware Tanzu deployments. This is for support of air-gapped environments where there is no access to the outside world.

All buildpacks use the multi-buildpack approach of Cloud Foundry and require either the standard Dotnet Core buildpack or HWC buildpack to be specified as the last buildpack in the buildpack chain, either in the app manifest or in the cf push command line.

Note: The cached version of this extension buildpack for both Dotnet Core and Dotnet Framework contains New Relic Dotnet Agents version 8.27.139.0

Product Snapshot

The following table provides version and version-support information about New Relic Dotnet Extension Buildpack for VMware Tanzu.

Element Details
Tile version 1.1.5
Release date May 15, 2020
Software component version New Relic Dotnet Extension Buildpack 1.1.5
Compatible Ops Manager version(s) 2.6, 2.7, 2.8, and 2.9
Compatible VMware Tanzu Application Service for VMs versions 2.6, 2.7, 2.8, and 2.9
BOSH stemcell version Ubuntu Xenial
IaaS support AWS, GCP, Azure, and vSphere

Compatibility

This product has been tested and is compatible with VMware Tanzu versions up to and including v2.9.

Requirements

New Relic Dotnet Extension Buildpack for VMware Tanzu requires the following:

  • An active New Relic account with a license key. This is used to bind Dotnet apps to New Relic Dotnet agents.

  • To use multi-buildpacks in the app manifest, you need cf CLI v6.38 or later. For general information about adding buildpacks to manifests, see Pushing an Application with Multiple Buildpacks in the Cloud Foundry documentation.

  • To use the Dotnet HWC extension, you need HWC buildpack 3.0.3 or later.

  • To use the Dotnet Core extension, you need the dotnet core buildpack 2.1.5 or later.

Trial License

If you do not already have a New Relic account, you can obtain an account with a free trial license.

Feedback

If you have feature requests, questions, or information about a bug, please submit an issue on github.