Generate external documentation pages for the overview/setup of integ…

…rations
wavefrontHQ · Jul 8, 2024 · ceeffad · ceeffad
1 parent ea31aaa
commit ceeffad
Show file tree

Hide file tree

Showing 41 changed files with 12 additions and 160 deletions.
diff --git a/integrations/amazon_alb.md b/integrations/amazon_alb.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_apigateway.md b/integrations/amazon_apigateway.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_auto_scaling.md b/integrations/amazon_auto_scaling.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_beanstalk.md b/integrations/amazon_beanstalk.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_cloudfront.md b/integrations/amazon_cloudfront.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_cloudsearch.md b/integrations/amazon_cloudsearch.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_cloudtrail.md b/integrations/amazon_cloudtrail.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_dc.md b/integrations/amazon_dc.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_dms.md b/integrations/amazon_dms.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_dynamodb.md b/integrations/amazon_dynamodb.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_ebs.md b/integrations/amazon_ebs.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_ec2.md b/integrations/amazon_ec2.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_ecs.md b/integrations/amazon_ecs.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_ecs_fargate.md b/integrations/amazon_ecs_fargate.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_efs.md b/integrations/amazon_efs.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_eks.md b/integrations/amazon_eks.md
@@ -66,7 +66,7 @@ Operations for Applications uses the [Observability for Kubernetes Operator](htt
 
 VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) provides a comprehensive solution for monitoring Kubernetes. To set up the Kubernetes integration, you must install and configure our Kubernetes Metrics Collector and a Wavefront proxy. With the 2022-48.x release we introduced the Kubernetes Observability Operator which simplifies the deployment of the Kubernetes Metrics Collector and the Wavefront proxy. 
 
-The setup process varies based on the distribution type that you choose to monitor, and whether your Operations for Applications service is onboarded to the VMware Cloud services platform.
+The setup process varies based on the distribution type that you choose to monitor.
 
 
 1. Log in to your product cluster.
@@ -94,22 +94,9 @@ The setup process varies based on the distribution type that you choose to monit
       3. **HTTP Proxy Authentication** - Can be either basic (with user name and password), or CA certificate - based (with a CA certificate).
 
 1. Enter the authentication options and click **Next**.
-
-   The authentication options vary depending on whether your [Operations for Applications service is onboarded to VMware Cloud services](https://docs.wavefront.com/subscriptions-differences.html). For more details, see [Proxy Authentication Types](https://docs.wavefront.com/proxies_installing.html#proxy-authentication-types).
-
-   * If your service **is onboarded** to VMware Cloud services, choose to authenticate by using either an **OAuth App** or an **API token**. 
-
-     * **OAuth App** authentication requires you to use an existing App ID, App Secret, and Organization ID of a server to server app that has the **Proxies** service role assigned and belongs to the VMware Cloud services organization running the service.
-     * **API Token** authentication requires you to use an API token that belongs to your user account in the VMware Cloud organization running the service. Note that you must regenerate and reconfigure the API Token periodically depending on the token TTL configuration.
-
-   * If your service is **not onboarded** to VMware Cloud services, you can authenticate to the Operations for Applications REST API by using either a user account, or a service account. In both cases, the account must have an Operations for Applications API token associated with it.
+   You can authenticate to the Operations for Applications REST API using either a user account, or a service account. In both cases, the account must have an Operations for Applications API token associated with it.
 
 1. In the **Script** section, review the script and click the **Copy to clipboard** button.
-
-   * When your service **is onboarded** to VMware Cloud services:
-     * If you have selected **OAuth App** as the authentication type, replace `<CSP_APP_ID>` and `<CSP_APP_SECRET>` with your server to server app credentials and `<CSP_ORG_ID>` with the ID of the VMware Cloud organization running the service.
-     * If you have selected **API token** as the authentication type, replace `<CSP_API_TOKEN>` with your VMware Cloud services API token.
-   * When your service is **not onboarded** to VMware Cloud services, proceed to the next step.
 1. Run the script in your Kubernetes cluster.
 1. After successful installation, return back to the Operations for Applications UI, and click **Finish**.
 

diff --git a/integrations/amazon_elastic_cache.md b/integrations/amazon_elastic_cache.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_elastic_transcoder.md b/integrations/amazon_elastic_transcoder.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_elasticsearch.md b/integrations/amazon_elasticsearch.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_elb.md b/integrations/amazon_elb.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_emr.md b/integrations/amazon_emr.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_firehose.md b/integrations/amazon_firehose.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_fsx.md b/integrations/amazon_fsx.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_iot.md b/integrations/amazon_iot.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_keyage.md b/integrations/amazon_keyage.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function
 

diff --git a/integrations/amazon_kinesis.md b/integrations/amazon_kinesis.md
@@ -113,8 +113,6 @@ You can use an AWS Lambda function to ingest CloudWatch logs to Operations for A
 
 The Wavefront proxy is required to send logs from your systems to Operations for Applications. If you have not already done so, install a [Wavefront proxy](https://docs.wavefront.com/proxies_installing.html) in your AWS environment.
 
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, install  Wavefront proxy version 13.0 or later.
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, install  Wavefront proxy version 12.2 or later.
 
 #### Create an AWS Lambda Function