From a73beb505fe5676f567fcf4f5f11bad4e0ad6600 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Tue, 6 Feb 2024 03:31:09 +0000 Subject: [PATCH 01/22] Bump nokogiri from 1.14.3 to 1.16.2 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.14.3 to 1.16.2. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.14.3...v1.16.2) --- updated-dependencies: - dependency-name: nokogiri dependency-type: direct:production ... Signed-off-by: dependabot[bot] --- Gemfile | 2 +- Gemfile.lock | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/Gemfile b/Gemfile index f143e3423..c584f1572 100644 --- a/Gemfile +++ b/Gemfile @@ -1,7 +1,7 @@ source "https://rubygems.org" gem 'jekyll', '~> 4.0', '>= 4.0.1' -gem 'nokogiri', '~> 1.14.3' +gem 'nokogiri', '~> 1.16.2' group :jekyll_plugins do gem 'algoliasearch-jekyll', '~> 0.8.0' end diff --git a/Gemfile.lock b/Gemfile.lock index e5d53e492..0a6caa9de 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -66,14 +66,14 @@ GEM rb-fsevent (~> 0.10, >= 0.10.3) rb-inotify (~> 0.9, >= 0.9.10) mercenary (0.4.0) - mini_portile2 (2.8.1) - nokogiri (1.14.3) - mini_portile2 (~> 2.8.0) + mini_portile2 (2.8.5) + nokogiri (1.16.2) + mini_portile2 (~> 2.8.2) racc (~> 1.4) pathutil (0.16.2) forwardable-extended (~> 2.6) public_suffix (4.0.6) - racc (1.6.2) + racc (1.7.3) rake (13.0.1) rb-fsevent (0.10.4) rb-inotify (0.10.1) @@ -104,7 +104,7 @@ DEPENDENCIES jekyll-sitemap jekyll-target-blank kramdown-parser-gfm - nokogiri (~> 1.14.3) + nokogiri (~> 1.16.2) webrick (~> 1.7) BUNDLED WITH From 14e309947770109cfa705c9a988831990ad65450 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Fri, 5 Jan 2024 15:40:42 +0200 Subject: [PATCH 02/22] AWS int - new Service Limit Metrics setting --- pages/doc/integrations_aws_metrics.md | 4 ++-- pages/doc/integrations_aws_overview.md | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/pages/doc/integrations_aws_metrics.md b/pages/doc/integrations_aws_metrics.md index 48480854c..45043f985 100644 --- a/pages/doc/integrations_aws_metrics.md +++ b/pages/doc/integrations_aws_metrics.md @@ -301,11 +301,11 @@ Unless otherwise indicated, VMware Aria Operations for Applications sets the val - `aws.rds.capacity` - For Amazon Aurora only, RDS capacity. - `aws.rds.backtrackconsumedchangerecords` - For Amazon Aurora only, the number of change records stored for Backtrack. -- Service Limit Metrics - Capture the current resource limits and usage for your AWS account. These metrics include the point tags `Region` and `category`. +- (Optional) Service Limit Metrics - Capture the current resource limits and usage for your AWS account. These metrics include the point tags `Region` and `category`. - `aws.limits..limit` - The current limit for an AWS resource in a particular region. - `aws.limits..usage` - The current usage of an AWS resource in a particular region. - {% include note.html content="To examine these metrics, your account needs at least the Business-level AWS Support plan because the integration uses the Support API to pull service limits. You also need both ReadOnlyAccess and AWSSupportAccess. See [Giving VMware Aria Operations for Applications Read-Only Access](integrations_aws_overview.html#giving-access-to-your-aws-account) for details." %} + {% include note.html content="If you enabled the ingestion of these metrics, to examine them, your account needs at least the Business-level AWS Support plan, because the integration uses the Support API to pull service limits. You also need both ReadOnlyAccess and AWSSupportAccess. See [Giving VMware Aria Operations for Applications Read-Only Access](integrations_aws_overview.html#giving-access-to-your-aws-account) for details." %} diff --git a/pages/doc/integrations_aws_overview.md b/pages/doc/integrations_aws_overview.md index 9e9ba4704..c966b2e85 100644 --- a/pages/doc/integrations_aws_overview.md +++ b/pages/doc/integrations_aws_overview.md @@ -212,6 +212,7 @@ To set up an AWS integration, you must have a [Role ARN](#give-read-only-access- 1. Configure the integration properties: - **Name** - Name to identify the integration. - **Role ARN** - The Role ARN from your Amazon account. +1. (Optional) If you want to skip the ingestion of support service limit metrics (also known as service quotas), that is, metrics namespace `aws.limits.*`, disable **Service Limit Metrics**. 1. (Optional) If you want to configure a CloudTrail integration, click **Show Advanced Options**. - **Bucket Name** - Enter the S3 bucket containing CloudTrail logs. @@ -241,6 +242,7 @@ After you set up the AWS integration with a [Role ARN](#give-read-only-access-to 1. **Name** -- Name to identify the integration. 2. **Role ARN** -- Select the Role ARN from your Amazon account. + 3. **Service Limit Metrics** -- Disable or enable the ingestion of support service limit metrics (also known as service quotas), that is, metrics namespace `aws.limits.*`. * To register a CloudTrail service, select **Register CloudTrail**, and configure the following integration properties: From 42a2c8063662f24ec1339573da889232acccc8b4 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Fri, 5 Jan 2024 15:59:20 +0200 Subject: [PATCH 03/22] minor --- pages/doc/integrations_aws_overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/doc/integrations_aws_overview.md b/pages/doc/integrations_aws_overview.md index c966b2e85..4f5b81c57 100644 --- a/pages/doc/integrations_aws_overview.md +++ b/pages/doc/integrations_aws_overview.md @@ -212,7 +212,7 @@ To set up an AWS integration, you must have a [Role ARN](#give-read-only-access- 1. Configure the integration properties: - **Name** - Name to identify the integration. - **Role ARN** - The Role ARN from your Amazon account. -1. (Optional) If you want to skip the ingestion of support service limit metrics (also known as service quotas), that is, metrics namespace `aws.limits.*`, disable **Service Limit Metrics**. +1. (Optional) If you want to skip the ingestion of support service limit metrics (also known as service quotas), that is, metrics namespace `aws.limits.*`, disable **Service Limit Metrics**. You can later enable these metrics, if necessary. 1. (Optional) If you want to configure a CloudTrail integration, click **Show Advanced Options**. - **Bucket Name** - Enter the S3 bucket containing CloudTrail logs. @@ -242,7 +242,7 @@ After you set up the AWS integration with a [Role ARN](#give-read-only-access-to 1. **Name** -- Name to identify the integration. 2. **Role ARN** -- Select the Role ARN from your Amazon account. - 3. **Service Limit Metrics** -- Disable or enable the ingestion of support service limit metrics (also known as service quotas), that is, metrics namespace `aws.limits.*`. + 3. **Service Limit Metrics** -- Disable or enable the ingestion of support service limit metrics (also known as service quotas), that is, metrics namespace `aws.limits.*`. * To register a CloudTrail service, select **Register CloudTrail**, and configure the following integration properties: From b1dffad6aad9cb139b77200147efcfa1ada5f1c8 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Mon, 8 Jan 2024 11:13:55 +0200 Subject: [PATCH 04/22] API param for service limits --- pages/doc/integrations_aws_overview-API.md | 6 ++++-- pages/doc/integrations_aws_overview.md | 4 ++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/pages/doc/integrations_aws_overview-API.md b/pages/doc/integrations_aws_overview-API.md index a47734451..42f9e1c4d 100644 --- a/pages/doc/integrations_aws_overview-API.md +++ b/pages/doc/integrations_aws_overview-API.md @@ -107,8 +107,9 @@ You can add an AWS integration by using the REST API documentation UI. "ec2":{ "baseCredentials":{ "roleArn":"arn:aws:iam:::role/", - "externalId": "string" + "externalId": "string" }, + "customNamespaces":["LIMITS"] "metricFilterRegex":"^aws.(sqs|ec2|ebs|elb).*$", "pointTagFilterRegex":"(region|name)" }, @@ -128,9 +129,10 @@ You can add an AWS integration by using the REST API documentation UI. "cloudTrail":{ "baseCredentials":{ "roleArn":"arn:aws:iam:::role/", - "externalId":"string" + "externalId":"string" }, "filterRule":"string" + }, } ``` diff --git a/pages/doc/integrations_aws_overview.md b/pages/doc/integrations_aws_overview.md index 4f5b81c57..0ebd68f8d 100644 --- a/pages/doc/integrations_aws_overview.md +++ b/pages/doc/integrations_aws_overview.md @@ -212,7 +212,7 @@ To set up an AWS integration, you must have a [Role ARN](#give-read-only-access- 1. Configure the integration properties: - **Name** - Name to identify the integration. - **Role ARN** - The Role ARN from your Amazon account. -1. (Optional) If you want to skip the ingestion of support service limit metrics (also known as service quotas), that is, metrics namespace `aws.limits.*`, disable **Service Limit Metrics**. You can later enable these metrics, if necessary. + - **Service Limit Metrics** - Disable or enable the ingestion of support service limit metrics (also known as service quotas), that is, the metrics namespace `aws.limits.*`. You can later edit this setting, if necessary. 1. (Optional) If you want to configure a CloudTrail integration, click **Show Advanced Options**. - **Bucket Name** - Enter the S3 bucket containing CloudTrail logs. @@ -242,7 +242,7 @@ After you set up the AWS integration with a [Role ARN](#give-read-only-access-to 1. **Name** -- Name to identify the integration. 2. **Role ARN** -- Select the Role ARN from your Amazon account. - 3. **Service Limit Metrics** -- Disable or enable the ingestion of support service limit metrics (also known as service quotas), that is, metrics namespace `aws.limits.*`. + 3. **Service Limit Metrics** -- Disable or enable the ingestion of support service limit metrics (also known as service quotas), that is, the metrics namespace `aws.limits.*`. You can later edit this setting, if necessary. * To register a CloudTrail service, select **Register CloudTrail**, and configure the following integration properties: From 3c420ff86016fddf66bda7ecffdc9af96fa3221c Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Mon, 8 Jan 2024 11:18:50 +0200 Subject: [PATCH 05/22] updated API call for Metrics+ int --- pages/doc/integrations_aws_overview-API.md | 29 ++++++++++++++-------- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/pages/doc/integrations_aws_overview-API.md b/pages/doc/integrations_aws_overview-API.md index 42f9e1c4d..3b125703c 100644 --- a/pages/doc/integrations_aws_overview-API.md +++ b/pages/doc/integrations_aws_overview-API.md @@ -102,18 +102,25 @@ You can add an AWS integration by using the REST API documentation UI. ``` { - "name":"AWSMetric+ integration", - "service":"ec2", - "ec2":{ - "baseCredentials":{ - "roleArn":"arn:aws:iam:::role/", - "externalId": "string" + "name": "AWSMetric+ integration", + "service": "ec2", + "ec2": { + "baseCredentials": { + "roleArn": "arn:aws:iam:::role/", + "externalId": "string" + }, + "instanceSelectionTagsExpr": "string", + "volumeSelectionTagsExpr": "string", + "metricFilterRegex": "^aws.(sqs|ec2|ebs|elb).*$", + "pointTagFilterRegex": "(region|name)", + "hostNameTags": [ + "string" + ], + "customNamespaces": [ + "LIMITS" + ] }, - "customNamespaces":["LIMITS"] - "metricFilterRegex":"^aws.(sqs|ec2|ebs|elb).*$", - "pointTagFilterRegex":"(region|name)" - }, - "serviceRefreshRateInMins":5 + "serviceRefreshRateInMins": 5 } ``` From ef84282a31d531cbb266a38f69ac9e86f18b1053 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Mon, 8 Jan 2024 17:43:56 +0200 Subject: [PATCH 06/22] format fixes + a note about disabling service limits --- pages/doc/integrations_aws_overview-API.md | 56 +++++++++++----------- 1 file changed, 29 insertions(+), 27 deletions(-) diff --git a/pages/doc/integrations_aws_overview-API.md b/pages/doc/integrations_aws_overview-API.md index 3b125703c..50ba17d10 100644 --- a/pages/doc/integrations_aws_overview-API.md +++ b/pages/doc/integrations_aws_overview-API.md @@ -30,16 +30,16 @@ For more information, see [Giving Access to Your AWS Account](integrations_aws_o 1. Click **Execute**. 1. Copy the external ID from the response body of the request. - ``` - { - "status": { - "result": "OK", - "message": "", - "code": 200 - }, - "response": "" - } - ``` + ``` + { + "status": { + "result": "OK", + "message": "", + "code": 200 + }, + "response": "" + } + ``` ### Provide Read-Only Access to Your Amazon Account and Get the Role ARN @@ -87,13 +87,13 @@ You can add an AWS integration by using the REST API documentation UI. "name":"CloudWatch integration", "service":"CLOUDWATCH", "cloudWatch":{ - "baseCredentials":{ - "roleArn":"arn:aws:iam:::role/", - "externalId":"string" + "baseCredentials":{ + "roleArn":"arn:aws:iam:::role/", + "externalId":"string" + }, + "metricFilterRegex":"^aws.(sqs|ec2|ebs|elb).*$", + "pointTagFilterRegex":"(region|name)" }, - "metricFilterRegex":"^aws.(sqs|ec2|ebs|elb).*$", - "pointTagFilterRegex":"(region|name)" - }, "serviceRefreshRateInMins":5 } ``` @@ -124,22 +124,24 @@ You can add an AWS integration by using the REST API documentation UI. } ``` + **Note**: If you want to disable the ingestion of support service limit metrics (also known as service quotas), that is, the metrics namespace aws.limits.*, replace "customNamespaces":["LIMITS"] with "customNamespaces":[]. + * CloudTrail integration: ``` { - "name":"CloudTrail integration", - "service":"cloudTrail", - "region":"string", - "prefix": "string", - "bucketName":"string" - "cloudTrail":{ - "baseCredentials":{ - "roleArn":"arn:aws:iam:::role/", - "externalId":"string" + "name":"CloudTrail integration", + "service":"cloudTrail", + "region":"string", + "prefix": "string", + "bucketName":"string" + "cloudTrail":{ + "baseCredentials":{ + "roleArn":"arn:aws:iam:::role/", + "externalId":"string" + }, + "filterRule":"string" }, - "filterRule":"string" - }, } ``` From 99c21aa0dc6016906c7eb20310a6145cb8f48814 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Thu, 11 Jan 2024 17:28:14 +0200 Subject: [PATCH 07/22] Service limits can be disabled after initial setup of AWS integration --- pages/doc/integrations_aws_metrics.md | 17 +++++++++++++---- pages/doc/integrations_aws_overview.md | 22 +++++++++++++--------- 2 files changed, 26 insertions(+), 13 deletions(-) diff --git a/pages/doc/integrations_aws_metrics.md b/pages/doc/integrations_aws_metrics.md index 45043f985..43bd836f3 100644 --- a/pages/doc/integrations_aws_metrics.md +++ b/pages/doc/integrations_aws_metrics.md @@ -8,7 +8,7 @@ summary: Monitor CloudWatch, CloudTrail, and Metrics+ with VMware Aria Operation --- Amazon Web Services (AWS) is a collection of cloud-computing services that provide an on-demand computing platform. The Amazon Web Services integration allows you to ingest metrics directly from AWS. The Amazon Web Services built-in integration is part of the setup, but the additional steps in this document are needed to complete and customize integration setup. -{% include note.html content="You must have the [**Proxy Management** permission](permissions_overview.html) to set up an AWS integration. If you do not have permission, the UI menu selections, buttons, and links you use to perform the tasks are not visible." %} +{% include note.html content="You must have the [**Proxies** permission](permissions_overview.html) to set up an AWS integration. If you do not have permission, the UI menu selections, buttons, and links you use to perform the tasks are not visible." %} You have to set up your VMware Aria Operations for Applications account with the correct permissions. * From within the integration or explicitly, you can [Give Global Read-Only Access](integrations_aws_overview.html#give-read-only-access-to-your-amazon-account-and-get-the-role-arn). @@ -17,13 +17,14 @@ You have to set up your VMware Aria Operations for Applications account with the ## Supported AWS Integrations -The AWS integration ingests data from many products and provides dashboards for each. See any integration page for [a list of dashboards](amazon_cloudtrail.html#dashboards). The following products are of special interest to most customers: +The AWS integration ingests data from many AWS services and products including: - **[CloudWatch](http://aws.amazon.com/cloudwatch)** -- retrieves AWS [metric and dimension](http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CW_Support_For_AWS.html) data. Includes some metrics for Amazon Relational Database (RDS). - **[CloudTrail](http://aws.amazon.com/cloudtrail)** -- retrieves EC2 event information and creates System events that represent the AWS events. - **[AWS Metrics+](integrations_aws_metrics.html#aws-metrics-data)** -- retrieves additional metrics using AWS APIs other than CloudWatch. Data include EBS volume data and EC2 instance metadata like tags. You can investigate billing data and the number of reserved instances. Be sure to enable AWS+ metrics because it allows VMware Aria Operations for Applications to optimize its use of CloudWatch, and saves money on CloudWatch calls as a result. +The AWS integration provides dashboards for each supported AWS service. See any AWS integration page for [a list of dashboards](amazon_cloudtrail.html#dashboards). ## CloudWatch Integration Details @@ -33,7 +34,7 @@ VMware Aria Operations for Applications retrieves AWS metric and dimension data ### Configuring CloudWatch Data Ingestion -You can configure which instances and volumes to ingest metrics from, which metrics to ingest, and the rate at which VMware Aria Operations for Applications fetches metrics. +After you [set up an AWS integration](integrations_aws_overview.html#set-up-an-aws-integration) associated it with a Role ARN, you can configure which AWS product instances and volumes to ingest metrics from, which metrics to ingest, and the rate at which VMware Aria Operations for Applications fetches metrics. {% include tip.html content="The following examples are supported only for EC2 and EBS metrics." %} To configure CloudWatch ingestion: @@ -305,10 +306,18 @@ Unless otherwise indicated, VMware Aria Operations for Applications sets the val - `aws.limits..limit` - The current limit for an AWS resource in a particular region. - `aws.limits..usage` - The current usage of an AWS resource in a particular region. - {% include note.html content="If you enabled the ingestion of these metrics, to examine them, your account needs at least the Business-level AWS Support plan, because the integration uses the Support API to pull service limits. You also need both ReadOnlyAccess and AWSSupportAccess. See [Giving VMware Aria Operations for Applications Read-Only Access](integrations_aws_overview.html#giving-access-to-your-aws-account) for details." %} + {% include note.html content="You can [disable](#disable-service-limit-metrics-ingestion) the ingestion of these metrics. If these metrics are enabled, to examine them, your account needs at least the Business-level AWS Support plan, because the integration uses the Support API to pull service limits. You also need both ReadOnlyAccess and AWSSupportAccess. See [Giving VMware Aria Operations for Applications Read-Only Access](integrations_aws_overview.html#giving-access-to-your-aws-account) for details." %} +### Disable Service Limit Metrics Ingestion +After you [set up an AWS integration](integrations_aws_overview.html#set-up-an-aws-integration) associated it with a Role ARN, you can disable the ingestion of support service limit metrics (also known as service quotas), that is, the metrics namespace `aws.limits.*`. You can later enable these metrics again, if necessary. +1. Log in to your product cluster and click **Integrations** on the toolbar. +1. In the Featured section, click the **Amazon Web Services** tile. +1. Click the **Setup** tab. +1. In the Types column, click the **AWS Metrics+** link in the row of the integration you want to configure. +1. Deselect the **Service Limit Metrics** checkbox. +1. Click **Update**. - - - -## All 2019 - 2022 Integrations Release Notes +## All 2019 - 2023 Integrations Release Notes We have separate pages for: +* [New and Changed Integrations in 2023](integrations_new_changed_2023.html) * [New and Changed Integrations in 2022](integrations_new_changed_2022.html) * [New and Changed Integrations in 2021](integrations_new_changed_2021.html) * [New and Changed Integrations in 2019-2020](integrations_new_changed_2020.html) diff --git a/pages/doc/integrations_new_changed_2022.md b/pages/doc/integrations_new_changed_2022.md index ecf330712..beedaf291 100644 --- a/pages/doc/integrations_new_changed_2022.md +++ b/pages/doc/integrations_new_changed_2022.md @@ -8,7 +8,7 @@ summary: New and changed integrations released in 2022. --- VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) continuously adds new integrations to the existing set, and improves available integrations. -This document lists new and changed integrations for 2022. For earlier releases, see [New and Changed Integrations in 2021](integrations_new_changed_2021.html)[New and Changed Integrations in 2019-2020](integrations_new_changed_2020.html). +This document lists new and changed integrations for 2022. For earlier releases, see [New and Changed Integrations in 2021](integrations_new_changed_2021.html) and [New and Changed Integrations in 2019-2020](integrations_new_changed_2020.html). * We have a separate document for [Integrations Release Notes](integrations_new_changed.html). * We update our [list of all integrations](https://docs.wavefront.com/label_integrations%20list.html) each time we add new integrations. diff --git a/pages/doc/integrations_new_changed_2023.md b/pages/doc/integrations_new_changed_2023.md new file mode 100644 index 000000000..53c75d95c --- /dev/null +++ b/pages/doc/integrations_new_changed_2023.md @@ -0,0 +1,218 @@ +--- +title: New and Changed Integrations (2023) +keywords: integrations +tags: [integrations] +sidebar: doc_sidebar +permalink: integrations_new_changed_2023.html +summary: New and changed integrations released in 2023. +--- +VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) continuously adds new integrations to the existing set, and improves available integrations. + +This document lists new and changed integrations for 2023. For earlier releases, see [New and Changed Integrations in 2022](integrations_new_changed_2022.html), [New and Changed Integrations in 2021](integrations_new_changed_2021.html), and [New and Changed Integrations in 2019-2020](integrations_new_changed_2020.html). +* We have a separate document for [Integrations Release Notes](integrations_new_changed.html). +* We update our [list of all integrations](https://docs.wavefront.com/label_integrations%20list.html) each time we add new integrations. + +## December 2023 + +We made improvements to the following integrations in December 2023: + +* Kubernetes and related integrations -- Removed the Helm and manual installation instructions from all Kubernetes-based integrations, such as AWS Appmesh, Cassandra, Ceph, .Net Core, Envoy, etcd, Fluentd, GemFire, Istio, Kafka, NVIDIA, RabbitMQ, Redis,TSM, and Velero. + + {% include important.html content= "We deprecated the Helm and manual installation of the Kubernetes Metrics Collector, Wavefront proxy, Logs, and so on, in December 2022. Support for the legacy Collector and proxy installation methods (including bug fixes, security vulnerabilities, new functionality, etc.) was discontinued on Feb 28, 2023. You must use the Observability for Kubernetes Operator to set up the Kubernetes integration. " %} + +* Tanzu Application Service -- Fixed an issue with the **Error Rate** chart in the **Workload Monitoring** dashboard. +* VMware Tanzu Kubernetes Grid Integration -- Removed the `limit()` function from the queries in the VMware Tanzu Kubernetes Grid integration system dashboards, because this function [may return No Data](ts_limit.html#summary). + +We updated the following integrations to support VMware Cloud Services access token authentication when your Operations for Applications service **is onboarded** to VMware Cloud services. See [Integrations That Use VMware Cloud Services Access Tokens](integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens). + + * Chef Server + + This is a new Chef Server integration that supports VMware Cloud Services access token authentication. + + * Micrometer + +## October 2023 + +We **deprecated** a number of integrations in October 2023, and moved these integrations to the **Archived** section: + +* Azure Deployment Manager +* Ansible Role +* AVI Networks (NSX ALB) +* AWS Lambda Functions +* CollectD +* Data Platforms +* FreeBSD Host +* Metricproxy +* OpenBSD Host +* VMware Blockchain +* VMware tc Server +* Chef Server +* nodejs + +{% include important.html content= "The deprecated integrations will reach **end-of-life** in January, 2024 and will be removed from the product. If you are using any of these integrations and need assistance, reach out to our [Technical Support team](wavefront_support_feedback.html)." %} + +Also, we made improvements to the following integrations in October 2023: + +* Kubernetes: + + * Fixed the alert query of the **K8s node unhealthy** system alert. + * Removed the `limit()` function from the queries in the Kubernetes integration system dashboards, because this function [may return No Data](ts_limit.html#summary). + * Removed thresholds from the **K8s pod CPU usage too high** system alert. + * Updated the **Kubernetes Workloads Troubleshooting** dashboard overview with information about the Operator compatibility. +* Tanzu Application Service - Updated the **Error Rate per Minute** chart in the **Workload Monitoring** dashboard to include the 4xx and 5xx HTTP request error counts. +* Operations for Applications Usage -- Enabled the **Include Obsolete Metrics** option for all charts in the **Operations for Applications Service and Proxy Data** dashboard. +* VMware GemFire -- Updated the queries of the GemFire system alerts with new prefixes. +* Go -- Removed references of deprecated SDKs. +* C Sharp -- Removed references of deprecated libraries. + +In addition, we updated the following integrations to support VMware Cloud Services access token authentication when your Operations for Applications service **is onboarded** to VMware Cloud services. See [Integrations That Use VMware Cloud Services Access Tokens](integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens). + + * Catchpoint + * Nagios + * Uptime + +## August 2023 + +We made improvements to the following integrations in August 2023: + +* vSphere: + + * Updated a query in the **vSphere: VM Details** dashboard, which uses the `limit()` function, because this function [may return No Data](ts_limit.html#summary). The `limit ()` function is replaced by `count ()`. + + * Added a new **vSphere: VMware vSAN** dashboard that allows you to monitor detailed metrics about vSAN. + +* Tanzu Service Mesh -- Updated a query in the **Tanzu Service Mesh: Workload Summary** dashboard, which uses the `limit()` function, because this function [may return No Data](ts_limit.html#summary). The `limit ()` function is replaced by `count ()`. + +* AWS App Mesh -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. + +* Velero -- Added setup instructions to the integration. To see how to set up the Velero integration: + + 1. Log in to your service instance. + 2. Click **Integrations** on the toolbar. + 3. Search for **Velero** and click its tile. + 4. Click the **Setup** tab. + +* Tanzu Application Service -- We added support for Tanzu Application Service setup when your Operations for Applications service **is onboarded** to VMware Cloud services. See [Integrations Supported for Onboarded Subscriptions](integrations_onboarded_subscriptions.html). + +* Kubernetes: + * We added [new alerts templates](https://github.com/wavefrontHQ/observability-for-kubernetes/blob/main/docs/alerts/alerts.md). + * We added a new dashboard **Kubernetes Workloads Troubleshooting** which allows you to monitor the health of the Kubernetes workloads. To use this dashboard, maker sure that you use the Observability for Kubernetes Operator version 2.10.0 and later. + * We added support for Kubernetes setup when your Operations for Applications service **is onboarded** to VMware Cloud services. + * We now support a number of integrations on Kubernetes. The list includes: Cassandra, Ceph, Envoy Proxy, etcd, Fluentd, Kafka, NVIDIA, Rabbit MQ, and Redis. + + For the latest list of integrations, see [Integrations Supported for Onboarded Subscriptions](integrations_onboarded_subscriptions.html). + +* Operations for Applications Usage -- Made bug fixes to the **Committed Rate vs Monthly Usage (PPS P95) for Billable** and **Usage (PPS) vs Remaining Balance (PPS P95) for Burndown** dashboards. + +* Fluentd -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* Ceph -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* .NET Core -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* Docker with cAdvisor -- Updated the setup steps and instructions. +* Tanzu Service Mesh -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. + +## July 2023 + +We made improvements to the following integrations in July 2023: + +* Google Cloud Platform: + * You can select to ingest Google Cloud Platform histogram metrics and filter these metrics by their Google Cloud Platform grouping functions such as **Count**, **Mean**, and **Standard Deviation**. To do so, when you register or edit your Google Cloud Platform integration, enable **Histogram** metrics ingestion, select **Custom** and select to ingest certain histogram metrics based on the listed Google Cloud Platform grouping functions. When you select a grouping function, only the histogram metrics with the respective grouping function will be ingested. If you deselect all check boxes, all histogram metrics will be ingested. + * You can now select to ingest Google Cloud Run metrics. To do so, when you register or edit your Google Cloud Platform integration, in the **Categories to fetch** section, select **Custom** and select the **Cloud Run** check box. +* Amazon Web Services - You can now select to ingest Amazon Web Services Usage metrics. To do so, when you register or edit your CloudWatch integration, in the **Products** section, select **Custom** and select the **AWS Usage** check box. +* Kafka -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* Redis -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* etcd -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* Cassandra -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* NVIDIA -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* VMware GemFire -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. Also updated some of the dashboard queries to a new format. +* Uptime -- Updated the integration with the new Uptime logo. +* Windows Host -- The setup steps now use a URL parameter in the Wavefront proxy configuration. +* Operations for Applications Usage -- Fixed issues in the predefined dashboards. +* Terraform Provider -- Fixed a discrepancy in the Terraform `resource_alert` provider resulting in erroneous Terraform change plan. + + +## May 2023 + +We made improvements to the following integrations in May 2023: + +* Istio -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* Envoy Proxy -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* RabbitMQ -- Updated the setup steps and instructions. You can now set up the integration and the Kubernetes Metrics Collector by using the Observability for Kubernetes Operator. +* Tanzu Application Service -- Made updates to the **TAS: Nozzle Troubleshooting** and the **TAS: Workload Monitoring** dashboards, as well as to the **TAS UAA Latency is Elevated** alert. + * Updated the latency queries because now we emit latency as a histogram. + * Updated the **TAS: Nozzle Troubleshooting** dashboard to show points used by histograms. + +* Improved the documentation on how to use regular expressions for the following list of integrations: + * [Microsoft Azure](azure.html#add-a-microsoft-azure-cloud-integration) + * [Amazon Web Services](integrations_aws_metrics.html#configuring-cloudwatch-data-ingestion) + * [Google Cloud Platform](gcp.html#add-a-gcp-integration) + + +## March 2023 + + +Logs (Beta) Related Changes: + + {% include important.html content="Logs (Beta) is enabled only for selected customers. To participate, contact your VMware Aria Operations for Applications account representative or [technical support](wavefront_support_feedback.html#support)." %} + +We have made an improvement to the AWS integration: + +* Amazon Web Services –- Now contains AWS CloudWatch Logs Setup (Beta) instructions. If Logs (Beta) is enabled for you, you can set up your AWS integration to send logs to Operations for Applications. For details on our Logs (Beta) feature, see [Get Started with Logs (Beta)](logging_overview.html). For details on how to set up the integration, see [Setup for Ingesting AWS CloudWatch Logs (Beta)](integrations_aws_metrics.html#setup-for-ingesting-aws-cloudwatch-logs). + + +We added the following integration in March 2023: + +* .NET Core + + The .NET Core is a general-purpose, most versatile framework that may be used to build software applications for Windows, Linux, and MacOS. + This integration installs and configures the Kubernetes Metrics Collector to collect the .NET Core performance metrics and uses the [Wavefront proxy](https://docs.wavefront.com/proxies.html) for sending those metrics to the service. + + +We made improvements to the following integrations in March 2023: + +* Log Data -- Log Data – Updated the integration overview and setup steps to include information about the Logs (Beta) solution. +* Filebeat -- Made updates to the integration overview and the setup steps. + +* Tanzu Application Service: + + - Improved descriptions of dashboards and charts. + - Added new charts. + - Made improvements to CPU queries in dashboards for additional accuracy and consistency. + - Excluded Platform MySQL from charts on the MySQL Service dashboard, because this dashboard is only for MySQL broker and service instances. + +* Kubernetes -- Fixed validation errors in several Kubernetes system dashboards. +* Catchpoint -- Improved the Catchpoint service to validate the credentials before caching them. +* Amazon Web Services -- Made improvements to provide the dedicated thread pool to complete the AWS related tasks. +* Microsoft Azure -- Made improvements to cache the metric name properly and handle a missing data issue. +* Spring Boot -- Updated the Spring Boot integration with the steps for Spring Boot 3, and updated the doc links. + + +## February 2023 + +We made improvements to the following integration in February 2023: + +* Amazon Web Services -- With the 2023-07.x release, you can use the **Custom Namespace(s)** text box to additionally filter the list of AWS products for which you want to monitor metrics by using the CloudWatch integration. For more information about how to use this text box and monitor metrics from services that are not part of the **Products** list in the GUI, see [Configuring CloudWatch Data Ingestion](integrations_aws_metrics.html#configuring-cloudwatch-data-ingestion) and [How to Use the Metric Allow List and the Products List](integrations_aws_metrics.html#how-to-use-the-metric-allow-list-and-the-products-list). + +## January 2023 + +We made improvements to the following integrations in January 2023: + +* Amazon Web Services -- You can now ingest and monitor AWS Lambda cold start metrics. For information about how to do this, see [Ingesting AWS Lambda Cold Start Metrics into VMware Aria Operations for Applications](integrations_aws_lambda.html#ingesting-aws-lambda-cold-start-metrics-into-vmware-aria-operations-for-applications). + +* ServiceNow -- We updated the instructions on how to set up the integration to reflect the latest UI changes. + +* Microsoft SQL Server -- Updated the charts in the **SQL Server Metrics** dashboard to use the instance variables. + +* Operations for Applications Usage -- Made fixes to the integration and now dashboards are populated with data depending on your type of contract (Billable vs. Burndown). + +* Tanzu Application Service -- Made updates to the TAS system alerts and removed some of the alerts that are no longer needed, such as: + - TAS Active Locks Alerts + - TAS BOSH VM CPU Used + - TAS BOSH VM Memory Used + +* Microsoft Azure -- Added vCore charts and updated variables with common queries to the **Azure SQL Database** dashboard. + +General improvements: + +* Metrics Charts -- All charts that you see when you select a metric on the **Metrics** tab are now improved in terms of performance and are up-to-date with the latest UI. + \ No newline at end of file diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md index 984357c30..9fe07c585 100644 --- a/pages/doc/wavefront_release_notes.md +++ b/pages/doc/wavefront_release_notes.md @@ -36,6 +36,11 @@ In October, 2023, we start to incrementally [**onboard**](csp_migration.html) al {% include warning.html content="The Operations for Applications authentication and authorization will be **deprecated** in the future. Therefore, after onboarding to VMware Cloud services, **replace** [your service accounts with server to server apps](csp_migration.html#how-to-replace-a-service-account-with-a-server-to-server-app) and [your Operations for Applications API tokens with VMware Cloud Services access tokens](csp_migration.html#how-to-replace-an-operations-for-applications-api-token-with-a-vmware-cloud-services-access-token), including [the Operations for Application API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy)." %} +## 2024-03.x Release Notes + +**Amazon Web Services Integration Improvement**: You can now disable the ingestion of support service limit metrics. See the [Integrations Release Notes](integrations_new_changed.html#january-2024) for details. + + ## 2024-01.x Release Notes **Traces Security Policy**: You can block application or service information for specific users so that they don’t see the data on the Application Status page, Traces Browser, Application Map, or Operations Dashboards. To learn more, see: From 763e3cf4f4627c0e826b057ca4070cf2fc7bbbd6 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Fri, 19 Jan 2024 14:13:01 +0200 Subject: [PATCH 12/22] minor --- pages/doc/integrations_new_changed.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pages/doc/integrations_new_changed.md b/pages/doc/integrations_new_changed.md index da51b0fae..60bc3c4f3 100644 --- a/pages/doc/integrations_new_changed.md +++ b/pages/doc/integrations_new_changed.md @@ -25,7 +25,9 @@ During the process of onboarding an original Operations for Applications service ## January 2024 -Amazon Web Services - You can now disable the ingestion of support service limit metrics (also known as service quotas), that is, the metrics with the namespace `aws.limits.*`. To do so, when you register or edit your AWS Metrics+ integration, deselect the **Service Limit Metrics** check box. +We improved the following integration in January 2024: + +* Amazon Web Services - You can now disable the ingestion of support service limit metrics (also known as service quotas), that is, the metrics with the namespace `aws.limits.*`. To do so, when you register or edit your AWS Metrics+ integration, deselect the **Service Limit Metrics** check box. ## All 2019 - 2023 Integrations Release Notes From 021d4185b32aef2bb5675ec3c562ae718c3a95a2 Mon Sep 17 00:00:00 2001 From: shavidissa Date: Tue, 23 Jan 2024 15:30:02 -0800 Subject: [PATCH 13/22] Add note about 500 log alert limit --- pages/doc/logging_log_alerts.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pages/doc/logging_log_alerts.md b/pages/doc/logging_log_alerts.md index 7ee37fa71..28cd67e91 100644 --- a/pages/doc/logging_log_alerts.md +++ b/pages/doc/logging_log_alerts.md @@ -37,6 +37,8 @@ Use the Alerts Browser to create and manage your logs alerts. To see the logs al Follow these steps to create a logs alert: +{% include note.html content="You can only create 500 log alerts. If you exceed the log alert limit and need to create a new log alert, you need to delete an existing log alert so you can create a new log alert." %} + ### Go to the Alert Browser 1. Log in to your product instance as a user with the **Alerts** and **Logs** permissions. 2. On the toolbar, click **Alerting** > **All Alerts**. From dca9656e45dcbcbdda1fa89debcc3dd9bb1b05ce Mon Sep 17 00:00:00 2001 From: shavidissa Date: Thu, 25 Jan 2024 08:48:52 -0800 Subject: [PATCH 14/22] update the log alert limit note --- pages/doc/logging_log_alerts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/doc/logging_log_alerts.md b/pages/doc/logging_log_alerts.md index 28cd67e91..9adf081d8 100644 --- a/pages/doc/logging_log_alerts.md +++ b/pages/doc/logging_log_alerts.md @@ -37,7 +37,7 @@ Use the Alerts Browser to create and manage your logs alerts. To see the logs al Follow these steps to create a logs alert: -{% include note.html content="You can only create 500 log alerts. If you exceed the log alert limit and need to create a new log alert, you need to delete an existing log alert so you can create a new log alert." %} +{% include note.html content="You can only create 500 log alerts. If you reach the log alert limit and need to create a new log alert, you need to delete an existing log alert so you can create a new log alert." %} ### Go to the Alert Browser 1. Log in to your product instance as a user with the **Alerts** and **Logs** permissions. From 1bf2493b67eb90ff417bd1a653078aeb5f9296f2 Mon Sep 17 00:00:00 2001 From: shavidissa Date: Wed, 31 Jan 2024 12:40:38 -0800 Subject: [PATCH 15/22] add info on customers using micrometer-wavefront-tracing --- pages/doc/wavefront_spring_boot3.md | 89 ++++++++++++++++++++++++++++- 1 file changed, 86 insertions(+), 3 deletions(-) diff --git a/pages/doc/wavefront_spring_boot3.md b/pages/doc/wavefront_spring_boot3.md index 1032c7d3e..3a5639a95 100644 --- a/pages/doc/wavefront_spring_boot3.md +++ b/pages/doc/wavefront_spring_boot3.md @@ -93,7 +93,10 @@ Initialize a new project using the Spring Initializer or add the required depend Initialize a New Project
  • - Initialize an Existing Project + Initialize an Existing Project (Freemium) +
    • +
  • + Initialize an Existing Project (Customer)
    • @@ -132,8 +135,8 @@ Initialize a new project using the Spring Initializer or add the required depend
    -
    -

    Follow these steps:

    +
    +

    Follow these steps if you don't have an Operations for Applications account and need to use the freemium account.

    1. Add the Wavefront dependency.
    +
    +

    Follow these steps if you already have an Operations for Applications account.

    +
      +
    1. + Import the Wavefront for Spring Boot Bill of Materials (BOM) to your project. + {{site.data.alerts.tip}} +

      The Wavefront for Spring Boot dependency needs to be compatible with the Spring Boot release version. Therefore, replace $releaseVersion with the correct dependency version. See System Requirements to get the correct dependency version.

      + {{site.data.alerts.end}} + +
      +
      + 
      +
+<dependencyManagement>
+  <dependencies>
+  .....
+    <dependency>
+      <groupId>com.wavefront</groupId>
+      <artifactId>wavefront-spring-boot-bom</artifactId>
+      <version>$releaseVersion</version>
+      <type>pom</type>
+      <scope>import</scope>
+    </dependency>
+  .....
+  </dependencies>
+</dependencyManagement>
+
      +
      + +
      + 
      +dependencyManagement {
+  imports {
+    mavenBom "com.wavefront:wavefront-spring-boot-bom:$releaseVersion"
+  }
+}
+
      +
      +
      +
      2. +
    2. + If you want to send trace data to our service using Micrometer Tracing, add the following dependencies. + +
      +
      + 
      +<dependency>
+  <groupId>io.micrometer</groupId>
+  <artifactId>micrometer-tracing-bridge-brave</artifactId>
+</dependency>
+<dependency>
+  <groupId>io.micrometer</groupId>
+  <artifactId>micrometer-tracing-reporter-wavefront</artifactId>
+  <scope>runtime</scope>
+</dependency>
+
      +
      + +
      + 
      +dependencies {
+  ...
+  implementation 'io.micrometer:micrometer-tracing-bridge-brave'
+  runtimeOnly 'io.micrometer:micrometer-tracing-reporter-wavefront'
+}
+
      +
      +
      +
      3. +
    3. + You need to Specify the Operations for Applications instance, as explained in Step 2 below. Otherwise, you run into errors because the freemium account settings do not support the configurations in this section. +
      4. +
    +
    ### Step 2 (Optional): Specify Your Operations for Applications Instance From d29ed6b0edf1c38bc7697317aae88c88a39b5ab3 Mon Sep 17 00:00:00 2001 From: shavidissa Date: Thu, 1 Feb 2024 09:05:05 -0800 Subject: [PATCH 16/22] update step --- pages/doc/wavefront_spring_boot3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/doc/wavefront_spring_boot3.md b/pages/doc/wavefront_spring_boot3.md index 3a5639a95..0a1b9bce5 100644 --- a/pages/doc/wavefront_spring_boot3.md +++ b/pages/doc/wavefront_spring_boot3.md @@ -318,7 +318,7 @@ dependencies {
  • - You need to Specify the Operations for Applications instance, as explained in Step 2 below. Otherwise, you run into errors because the freemium account settings do not support the configurations in this section. + You need to Specify the VMware Cloud Services account instance or the Operations for Applications instance, as explained in Step 2 below. Otherwise, you run into errors because the freemium account settings do not support the configurations in this section.
    • From 9d99cb8d465ce78491651830960407981ff4d967 Mon Sep 17 00:00:00 2001 From: David Azatyan Date: Thu, 3 Aug 2023 12:00:37 +0400 Subject: [PATCH 17/22] MONIT-40707 - docs (webrick) --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index e5d53e492..fe61d5072 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -90,7 +90,7 @@ GEM thor (0.20.3) unicode-display_width (1.7.0) verbal_expressions (0.1.5) - webrick (1.7.0) + webrick (1.8.1) PLATFORMS x64-mingw32 From 8079d1fc7e01861c9fa1527789e64c0c1b30aa2d Mon Sep 17 00:00:00 2001 From: shavidissa Date: Mon, 26 Feb 2024 12:33:26 -0800 Subject: [PATCH 18/22] update to nokogiri1.16 --- Gemfile.lock | 81 ++++++++++++++++++++++++++++------------------------ 1 file changed, 44 insertions(+), 37 deletions(-) diff --git a/Gemfile.lock b/Gemfile.lock index 42c591ac3..e1cc59870 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -1,9 +1,9 @@ GEM remote: https://rubygems.org/ specs: - addressable (2.8.0) - public_suffix (>= 2.0.2, < 5.0) - algoliasearch (1.26.0) + addressable (2.8.6) + public_suffix (>= 2.0.2, < 6.0) + algoliasearch (1.27.5) httpclient (~> 2.8, >= 2.8.3) json (>= 1.5.1) algoliasearch-jekyll (0.8.2) @@ -19,50 +19,51 @@ GEM thor (>= 0.14.0) awesome_print (1.9.2) colorator (1.1.0) - concurrent-ruby (1.1.8) - em-websocket (0.5.2) + concurrent-ruby (1.2.3) + em-websocket (0.5.3) eventmachine (>= 0.12.9) - http_parser.rb (~> 0.6.0) + http_parser.rb (~> 0) eventmachine (1.2.7) eventmachine (1.2.7-x64-mingw32) - ffi (1.15.0) - ffi (1.15.0-x64-mingw32) + ffi (1.16.3) forwardable-extended (2.6.0) - http_parser.rb (0.6.0) + google-protobuf (3.25.3) + http_parser.rb (0.8.0) httpclient (2.8.3) - i18n (1.8.9) + i18n (1.14.1) concurrent-ruby (~> 1.0) - jekyll (4.2.0) + jekyll (4.3.3) addressable (~> 2.4) colorator (~> 1.0) em-websocket (~> 0.5) i18n (~> 1.0) - jekyll-sass-converter (~> 2.0) + jekyll-sass-converter (>= 2.0, < 4.0) jekyll-watch (~> 2.0) - kramdown (~> 2.3) + kramdown (~> 2.3, >= 2.3.1) kramdown-parser-gfm (~> 1.0) liquid (~> 4.0) - mercenary (~> 0.4.0) + mercenary (>= 0.3.6, < 0.5) pathutil (~> 0.9) - rouge (~> 3.0) + rouge (>= 3.0, < 5.0) safe_yaml (~> 1.0) - terminal-table (~> 2.0) - jekyll-sass-converter (2.1.0) - sassc (> 2.0.1, < 3.0) - jekyll-sitemap (1.3.1) + terminal-table (>= 1.8, < 4.0) + webrick (~> 1.7) + jekyll-sass-converter (3.0.0) + sass-embedded (~> 1.54) + jekyll-sitemap (1.4.0) jekyll (>= 3.7, < 5.0) - jekyll-target-blank (2.0.0) + jekyll-target-blank (2.0.2) jekyll (>= 3.0, < 5.0) nokogiri (~> 1.10) jekyll-watch (2.2.1) listen (~> 3.0) - json (2.3.1) - kramdown (2.3.1) + json (2.7.1) + kramdown (2.4.0) rexml kramdown-parser-gfm (1.1.0) kramdown (~> 2.0) - liquid (4.0.3) - listen (3.5.0) + liquid (4.0.4) + listen (3.9.0) rb-fsevent (~> 0.10, >= 0.10.3) rb-inotify (~> 0.9, >= 0.9.10) mercenary (0.4.0) @@ -72,23 +73,28 @@ GEM racc (~> 1.4) pathutil (0.16.2) forwardable-extended (~> 2.6) - public_suffix (4.0.6) + public_suffix (5.0.4) racc (1.7.3) - rake (13.0.1) - rb-fsevent (0.10.4) + rake (13.1.0) + rb-fsevent (0.11.2) rb-inotify (0.10.1) ffi (~> 1.0) - rexml (3.2.5) - rouge (3.26.0) + rexml (3.2.6) + rouge (4.2.0) safe_yaml (1.0.5) - sassc (2.4.0) - ffi (~> 1.9) - sassc (2.4.0-x64-mingw32) - ffi (~> 1.9) - terminal-table (2.0.0) - unicode-display_width (~> 1.1, >= 1.1.1) - thor (0.20.3) - unicode-display_width (1.7.0) + sass-embedded (1.71.1) + google-protobuf (~> 3.25) + rake (>= 13.0.0) + sass-embedded (1.71.1-x64-mingw32) + google-protobuf (~> 3.25) + sass-embedded (1.71.1-x86_64-darwin) + google-protobuf (~> 3.25) + sass-embedded (1.71.1-x86_64-linux-gnu) + google-protobuf (~> 3.25) + terminal-table (3.0.2) + unicode-display_width (>= 1.1.1, < 3) + thor (1.3.0) + unicode-display_width (2.5.0) verbal_expressions (0.1.5) webrick (1.8.1) @@ -96,6 +102,7 @@ PLATFORMS x64-mingw32 x64-unknown x86_64-darwin-20 + x86_64-darwin-23 x86_64-linux DEPENDENCIES From 4b66c8ce5387c5358bcf30e31ba00d506a0b3c94 Mon Sep 17 00:00:00 2001 From: shavidissa Date: Tue, 27 Feb 2024 15:34:46 -0800 Subject: [PATCH 19/22] minor change to start the build --- pages/doc/wavefront_release_notes.md | 1 - 1 file changed, 1 deletion(-) diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md index bbf720f1d..cf8159040 100644 --- a/pages/doc/wavefront_release_notes.md +++ b/pages/doc/wavefront_release_notes.md @@ -62,7 +62,6 @@ In October, 2023, we start to incrementally [**onboard**](csp_migration.html) al **Amazon Web Services Integration Improvement**: You can now disable the ingestion of support service limit metrics. See the [Integrations Release Notes](integrations_new_changed.html#january-2024) for details. - ## 2024-01.x Release Notes **Traces Security Policy**: You can block application or service information for specific users so that they don’t see the data on the Application Status page, Traces Browser, Application Map, or Operations Dashboards. To learn more, see: From 0d1844bb4a1afd7e240408b340dce33aa6065591 Mon Sep 17 00:00:00 2001 From: shavidissa Date: Tue, 27 Feb 2024 15:50:25 -0800 Subject: [PATCH 20/22] update --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index e1cc59870..495154c07 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -93,7 +93,7 @@ GEM google-protobuf (~> 3.25) terminal-table (3.0.2) unicode-display_width (>= 1.1.1, < 3) - thor (1.3.0) + thor (1.3.1) unicode-display_width (2.5.0) verbal_expressions (0.1.5) webrick (1.8.1) From 7fc3fbfd664ea2bad0ac8f2796ddb971964560c7 Mon Sep 17 00:00:00 2001 From: shavidissa Date: Wed, 28 Feb 2024 13:45:27 -0800 Subject: [PATCH 21/22] update to start the build --- pages/doc/wavefront_release_notes.md | 1 - 1 file changed, 1 deletion(-) diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md index cf8159040..108aec3d6 100644 --- a/pages/doc/wavefront_release_notes.md +++ b/pages/doc/wavefront_release_notes.md @@ -57,7 +57,6 @@ In October, 2023, we start to incrementally [**onboard**](csp_migration.html) al * Restore or permanently delete a deleted derived metric. * Select one or more derived metrics to add or remove specific tags for them, or to delete them. - ## 2024-03.x Release Notes **Amazon Web Services Integration Improvement**: You can now disable the ingestion of support service limit metrics. See the [Integrations Release Notes](integrations_new_changed.html#january-2024) for details. From 552488b9701b17cfbfeb9b6e9b7e36eedbca31ff Mon Sep 17 00:00:00 2001 From: shavidissa Date: Fri, 1 Mar 2024 13:47:00 -0800 Subject: [PATCH 22/22] jekyll 4.3.3 --- Gemfile | 2 +- Gemfile.lock | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Gemfile b/Gemfile index c584f1572..f20e18210 100644 --- a/Gemfile +++ b/Gemfile @@ -1,6 +1,6 @@ source "https://rubygems.org" -gem 'jekyll', '~> 4.0', '>= 4.0.1' +gem 'jekyll', '~> 4.3', '>= 4.3.3' gem 'nokogiri', '~> 1.16.2' group :jekyll_plugins do gem 'algoliasearch-jekyll', '~> 0.8.0' diff --git a/Gemfile.lock b/Gemfile.lock index 495154c07..f8e5b14b9 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -107,7 +107,7 @@ PLATFORMS DEPENDENCIES algoliasearch-jekyll (~> 0.8.0) - jekyll (~> 4.0, >= 4.0.1) + jekyll (~> 4.3, >= 4.3.3) jekyll-sitemap jekyll-target-blank kramdown-parser-gfm