From e21ee9ae0b4bd4ffa6647e66f90f28f5bc3d0954 Mon Sep 17 00:00:00 2001 From: mansar Date: Wed, 13 Dec 2023 03:06:18 +0530 Subject: [PATCH 1/4] Added VMware Tanzu Dotnet Buildpack documentation. --- ...are-tanzu-dotnet-buildpack-integration.mdx | 141 ++++++++++++++++++ src/nav/cloudfoundry.yml | 2 + src/nav/integrations.yml | 2 + 3 files changed, 145 insertions(+) create mode 100644 src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx diff --git a/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx b/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx new file mode 100644 index 00000000000..a65a6c171ee --- /dev/null +++ b/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx @@ -0,0 +1,141 @@ +--- +title: New Relic Dotnet 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. +redirects: + - /docs/cloudfoundry/vmware-tanzu/vmware-tanzu-dotnet-buildpack-integration +dataSource: vmware-tanzu +--- + +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 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. + +## Overview [#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](https://network.pivotal.io/products/nr-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 Jammy 1.* stacks. This extension buildpack is non-cached. +* New Relic Dotnet Core Extension Cached Buildpack for Dotnet 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 Dotnet Framework Applications running on Windows 2019 stacks. This extension buildpack is non-cached. +* 3 New Relic HWC Extension Cached Buildpacks for Dotnet 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 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 `9.1.1` + + +## Product Snapshot [#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.12 +
+ Release date + + August 15, 2023 +
+ Software component version + + New Relic Dotnet Extension Buildpack 1.1.12 +
+ Compatible Ops Manager version(s) + + 2.9.x, 2.10.x, and 3.0.x +
+ Compatible VMware Tanzu Application Service for VMs versions + + 2.10.x, 2.11.x, 2.12.x, 2.13.x, 3.0.x, and 4.0.x +
+ BOSH stemcell version + + Ubuntu Jammy +
+ IaaS support + + AWS, GCP, Azure, and vSphere +
+ +## Compatibility [#compatibility] + +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. + +## Requirements [#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](https://docs.pivotal.io/application-service/buildpacks/use-multiple-buildpacks.html) 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. + + +## 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). diff --git a/src/nav/cloudfoundry.yml b/src/nav/cloudfoundry.yml index 88c8a6b92a2..35d9329b082 100644 --- a/src/nav/cloudfoundry.yml +++ b/src/nav/cloudfoundry.yml @@ -5,3 +5,5 @@ pages: pages: - title: Firehose Nozzle integration path: /docs/cloudfoundry/vmware-tanzu/vmware-tanzu-firehose-nozzle-integration + - title: Dotnet Buildpack Integration + path: /docs/cloudfoundry/vmware-tanzu/vmware-tanzu-dotnet-buildpack-integration diff --git a/src/nav/integrations.yml b/src/nav/integrations.yml index 333a21a30f7..7a0bf784263 100644 --- a/src/nav/integrations.yml +++ b/src/nav/integrations.yml @@ -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: Dojo integration path: /docs/more-integrations/open-source-telemetry-integrations/dojo/dojo-io-integration - title: Dropwizard integration From 5fa5465019c41f88b738d26493194096ed331692 Mon Sep 17 00:00:00 2001 From: alexa <81787716+akristen@users.noreply.github.com> Date: Tue, 12 Dec 2023 17:10:01 -0600 Subject: [PATCH 2/4] feat(integrations): added frontmatter, removed redirect, structural edits I chunked any compatibility/prereqs into one section. I moved some Overview info into the intro, but made no content edits. I updated the overview header to be install, as the intro says the purpose of this doc is to install the build pack. --- ...are-tanzu-dotnet-buildpack-integration.mdx | 60 ++++++++----------- 1 file changed, 25 insertions(+), 35 deletions(-) diff --git a/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx b/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx index a65a6c171ee..7660c3aacb8 100644 --- a/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx +++ b/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx @@ -5,44 +5,30 @@ tags: - Cloudfoundry - Tanzu metaDescription: Use our integration to gain increased visibility into the performance of your VMware Tanzu environment. -redirects: - - /docs/cloudfoundry/vmware-tanzu/vmware-tanzu-dotnet-buildpack-integration -dataSource: vmware-tanzu +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 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. +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. -## Overview [#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 +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](https://network.pivotal.io/products/nr-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): +## Prerequisites [#prereqs] -* New Relic Dotnet Core Extension Buildpack for Dotnet Core Applications running on Ubuntu Jammy 1.* stacks. This extension buildpack is non-cached. -* New Relic Dotnet Core Extension Cached Buildpack for Dotnet 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 Dotnet Framework Applications running on Windows 2019 stacks. This extension buildpack is non-cached. -* 3 New Relic HWC Extension Cached Buildpacks for Dotnet 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. +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. -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. +New Relic Dotnet Extension Buildpack for VMware Tanzu requires the following: - - **Note**: The cached version of this extension buildpack for both Dotnet Core and Dotnet Framework contains New Relic Dotnet Agents version `9.1.1` - +* 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](https://docs.pivotal.io/application-service/buildpacks/use-multiple-buildpacks.html) 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. -## Product Snapshot [#product-snapshot] The following table provides version and version-support information about New Relic Dotnet Extension Buildpack for VMware Tanzu. @@ -121,20 +107,24 @@ The following table provides version and version-support information about New R -## Compatibility [#compatibility] +## Install the buildpack [#install] -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. +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`. -## Requirements [#requirements] +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. -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](https://docs.pivotal.io/application-service/buildpacks/use-multiple-buildpacks.html) 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. +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 Jammy 1.* stacks. This extension buildpack is non-cached. +* New Relic Dotnet Core Extension Cached Buildpack for Dotnet 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 Dotnet Framework Applications running on Windows 2019 stacks. This extension buildpack is non-cached. +* 3 New Relic HWC Extension Cached Buildpacks for Dotnet 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 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. + + + The cached version of this extension buildpack for both Dotnet Core and Dotnet Framework contains New Relic Dotnet Agents version `9.1.1` + ## Feedback [#feedback] From f1212c80009a9201b7ac30881a21f4fbdbc39463 Mon Sep 17 00:00:00 2001 From: alexa <81787716+akristen@users.noreply.github.com> Date: Tue, 12 Dec 2023 17:20:25 -0600 Subject: [PATCH 3/4] feat(more integrations): changed instances of dotnet to .NET, removed extraneous yml file There was a second .yml file added that duplicated the already existing Cloud Foundry docs in a separate part of the docs site. I've removed that and kept the docs housed in more integrations --- ...are-tanzu-dotnet-buildpack-integration.mdx | 36 +++++++++---------- src/nav/cloudfoundry.yml | 9 ----- 2 files changed, 18 insertions(+), 27 deletions(-) delete mode 100644 src/nav/cloudfoundry.yml diff --git a/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx b/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx index 7660c3aacb8..b6b8959d5a7 100644 --- a/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx +++ b/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx @@ -1,5 +1,5 @@ --- -title: New Relic Dotnet Extension Buildpack for VMware Tanzu +title: New Relic .NET Extension Buildpack for VMware Tanzu tags: - Integrations - Cloudfoundry @@ -12,25 +12,25 @@ import infrastructureVmwareTanzuDashboard from 'images/infrastructure_screenshot import infrastructureVmwareTanzuAlertChart from 'images/infrastructure_screenshot-crop_vmware-tanzu-alert-chart.webp' -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. +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 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 +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 Dotnet Extension Buildpack for VMware Tanzu requires the following: +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 Dotnet apps to New Relic Dotnet agents. +* 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 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. +* 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 Dotnet Extension Buildpack for VMware Tanzu. +The following table provides version and version-support information about New Relic .NET Extension Buildpack for VMware Tanzu. @@ -68,7 +68,7 @@ The following table provides version and version-support information about New R Software component version @@ -109,21 +109,21 @@ The following table provides version and version-support information about New R ## Install the buildpack [#install] -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`. +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 Dotnet agents using the New Relic alerting subsystem. +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 Dotnet Extension Buildpack for VMware Tanzu installs one or more of the following buildpacks depending on the tile configuration (total of 8 extension buildpacks): +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 Dotnet Core Extension Buildpack for Dotnet Core Applications running on Ubuntu Jammy 1.* stacks. This extension buildpack is non-cached. -* New Relic Dotnet Core Extension Cached Buildpack for Dotnet 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 Dotnet Framework Applications running on Windows 2019 stacks. This extension buildpack is non-cached. -* 3 New Relic HWC Extension Cached Buildpacks for Dotnet 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. +* 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 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. +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. - The cached version of this extension buildpack for both Dotnet Core and Dotnet Framework contains New Relic Dotnet Agents version `9.1.1` + The cached version of this extension buildpack for both .NET Core and .NET Framework contains New Relic .NET Agents version `9.1.1` ## Feedback [#feedback] diff --git a/src/nav/cloudfoundry.yml b/src/nav/cloudfoundry.yml deleted file mode 100644 index 35d9329b082..00000000000 --- a/src/nav/cloudfoundry.yml +++ /dev/null @@ -1,9 +0,0 @@ -title: Cloudfoundry -path: /docs/cloudfoundry/vmware-tanzu -pages: - - title: VMware Tanzu Integrations - pages: - - title: Firehose Nozzle integration - path: /docs/cloudfoundry/vmware-tanzu/vmware-tanzu-firehose-nozzle-integration - - title: Dotnet Buildpack Integration - path: /docs/cloudfoundry/vmware-tanzu/vmware-tanzu-dotnet-buildpack-integration From 68e4183eddcc74d72da961ba7527545e10e6c827 Mon Sep 17 00:00:00 2001 From: mansar Date: Fri, 22 Dec 2023 01:18:48 +0530 Subject: [PATCH 4/4] Changed step name. --- .../vmware-tanzu-dotnet-buildpack-integration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx b/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx index b6b8959d5a7..878dbd62922 100644 --- a/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx +++ b/src/content/docs/more-integrations/cloudfoundry-integrations/vmware-tanzu-dotnet-buildpack-integration.mdx @@ -107,7 +107,7 @@ The following table provides version and version-support information about New R
- New Relic Dotnet Extension Buildpack 1.1.12 + New Relic .NET Extension Buildpack 1.1.12
-## Install the buildpack [#install] +## 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`.