Skip to content

Commit

Permalink
Merge pull request newrelic#15493 from miransar/vmware-tanzu-dotnet-b…
Browse files Browse the repository at this point in the history
…uildpack-docs

Added VMware Tanzu Dotnet Buildpack documentation.
  • Loading branch information
bradleycamacho authored Dec 31, 2023
2 parents 1f71417 + 68e4183 commit 3c23166
Show file tree
Hide file tree
Showing 3 changed files with 133 additions and 7 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,131 @@
---
title: New Relic .NET Extension Buildpack for VMware Tanzu
tags:
- Integrations
- Cloudfoundry
- Tanzu
metaDescription: Use our integration to gain increased visibility into the performance of your VMware Tanzu environment.
freshnessValidatedDate: never
---

import infrastructureVmwareTanzuDashboard from 'images/infrastructure_screenshot-crop_vmware-tanzu-dashboard.webp'

import infrastructureVmwareTanzuAlertChart from 'images/infrastructure_screenshot-crop_vmware-tanzu-alert-chart.webp'

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

The New Relic .NET Extension Buildpack for VMware Tanzu enables you to bind your .NET (Core and Framework) apps to New Relic .NET 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](https://network.pivotal.io/products/nr-firehose-nozzle/).

## Prerequisites [#prereqs]

This product has been tested and is compatible with VMware Tanzu OpsManager versions up to and including v3.0 and Tanzu Application Service 4.0.

New Relic .NET Extension Buildpack for VMware Tanzu requires the following:

* An active New Relic account with a license key. This is used to bind .NET apps to New Relic .NET 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](https://docs.pivotal.io/application-service/buildpacks/use-multiple-buildpacks.html) in the Cloud Foundry documentation.
* To use the .NET HWC extension, you need HWC buildpack 3.0.3 or later.
* To use the .NET Core extension, you need the dotnet core buildpack 2.1.5 or later.


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

<table>
<thead>
<tr>
<th>
Element
</th>

<th>
Details
</th>
</tr>
</thead>

<tbody>
<tr>
<td>
Tile version
</td>

<td>
1.1.12
</td>
</tr>
<tr>
<td>
Release date
</td>
<td>
August 15, 2023
</td>
</tr>
<tr>
<td>
Software component version
</td>
<td>
New Relic .NET Extension Buildpack 1.1.12
</td>
</tr>
<tr>
<td>
Compatible Ops Manager version(s)
</td>
<td>
2.9.x, 2.10.x, and 3.0.x
</td>
</tr>
<tr>
<td>
Compatible VMware Tanzu Application Service for VMs versions
</td>
<td>
2.10.x, 2.11.x, 2.12.x, 2.13.x, 3.0.x, and 4.0.x
</td>
</tr>
<tr>
<td>
BOSH stemcell version
</td>
<td>
Ubuntu Jammy
</td>
</tr>
<tr>
<td>
IaaS support
</td>

<td>
AWS, GCP, Azure, and vSphere
</td>
</tr>
</tbody>
</table>

## Installation [#install]

The New Relic .NET 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 .NET agents using the New Relic alerting subsystem.

The New Relic .NET 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 .NET Core Extension Buildpack for .NET Core Applications running on Ubuntu Jammy 1.* stacks. This extension buildpack is non-cached.
* New Relic .NET Core Extension Cached Buildpack for .NET Core Applications running on Ubuntu Jammy 1.* 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 .NET Framework Applications running on Windows 2019 stacks. This extension buildpack is non-cached.
* 3 New Relic HWC Extension Cached Buildpacks for .NET Framework Applications running on 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 .NET 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.

<Callout variant="important">
The cached version of this extension buildpack for both .NET Core and .NET Framework contains New Relic .NET Agents version `9.1.1`
</Callout>

## Feedback [#feedback]

If you have a feature request, questions, or information about a bug, please submit an issue on [github](https://github.com/newrelic/newrelic-dotnet-buildpack-tile/issues).
7 changes: 0 additions & 7 deletions src/nav/cloudfoundry.yml

This file was deleted.

2 changes: 2 additions & 0 deletions src/nav/integrations.yml
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,8 @@ pages:
pages:
- title: New Relic Nozzle for VMware Tanzu
path: /docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration
- title: New Relic Dotnet Buildpack for VMware Tanzu
path: /docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration
- title: Airflow with OpenTelemetry integration
path: /docs/more-integrations/open-source-telemetry-integrations/airflow/monitoring-airflow-ot
- title: Dojo integration
Expand Down

0 comments on commit 3c23166

Please sign in to comment.