From 0e3cdba937370703c078d6de54d51df28dab8809 Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Fri, 1 Mar 2024 16:07:26 +0200
Subject: [PATCH 01/26] Rebranding - Subscription and Commitment, RNs, Data and
Proxy, Alerts and Event, and Query Language.
---
pages/doc/2020_10.x_release_notes.md | 4 +-
pages/doc/2020_14.x_release_notes.md | 2 +-
pages/doc/2020_22.x_release_notes.md | 2 +-
pages/doc/2020_26.x_release_notes.md | 2 +-
pages/doc/2020_30.x_release_notes.md | 2 +-
pages/doc/2020_38.x_release_notes.md | 2 +-
pages/doc/2020_42.x_release_notes.md | 2 +-
pages/doc/2021-08.x_release_notes.md | 2 +-
pages/doc/2021-14.x_release_notes.md | 2 +-
pages/doc/2021-19.x_release_notes.md | 2 +-
pages/doc/2021-24.x_release_notes.md | 2 +-
pages/doc/2021-35.x_release_notes.md | 2 +-
pages/doc/2021-49.x_release_notes.md | 2 +-
pages/doc/2022-06.x_release_notes.md | 2 +-
pages/doc/2022-20.x_release_notes.md | 2 +-
pages/doc/2022-29.x_release_notes.md | 2 +-
pages/doc/2022-39.x_release_notes.md | 2 +-
pages/doc/2022-49.x_release_notes.md | 2 +-
pages/doc/2023-06.x_release_notes.md | 2 +-
pages/doc/2023-13.x_release_notes.md | 2 +-
pages/doc/2023-29.x_release_notes.md | 2 +-
pages/doc/2023-45.x_release_notes.md | 2 +-
pages/doc/alert_target_customizing.md | 6 +-
pages/doc/alerts.md | 2 +-
pages/doc/alerts_best_practices.md | 8 +-
pages/doc/alerts_delayed_data.md | 12 +-
pages/doc/alerts_dependencies.md | 2 +-
pages/doc/alerts_faq.md | 8 +-
pages/doc/alerts_manage.md | 8 +-
pages/doc/alerts_missing_data.md | 4 +-
pages/doc/alerts_notifications.md | 6 +-
pages/doc/alerts_recipes.md | 4 +-
pages/doc/alerts_states_lifecycle.md | 10 +-
pages/doc/cardinality.md | 20 +-
pages/doc/chart_builder.md | 2 +-
pages/doc/csp_area_differences.md | 192 +++++++++---------
pages/doc/csp_migration.md | 150 +++++++-------
pages/doc/csp_subscription_types.md | 12 +-
pages/doc/csp_ui_differences.md | 14 +-
pages/doc/delta_counters.md | 10 +-
pages/doc/derived_metrics.md | 12 +-
pages/doc/direct_ingestion.md | 40 ++--
pages/doc/events.md | 14 +-
pages/doc/integrations_new_changed.md | 8 +-
pages/doc/integrations_new_changed_2020.md | 4 +-
pages/doc/integrations_new_changed_2021.md | 14 +-
pages/doc/integrations_new_changed_2022.md | 16 +-
pages/doc/integrations_new_changed_2023.md | 16 +-
pages/doc/metric_types.md | 10 +-
pages/doc/metrics_managing.md | 4 +-
pages/doc/missing_data_troubleshooting.md | 18 +-
pages/doc/optimize_data_shape.md | 24 +--
pages/doc/proxies.md | 16 +-
pages/doc/proxies_configuring.md | 68 +++----
pages/doc/proxies_container.md | 20 +-
pages/doc/proxies_histograms.md | 46 ++---
pages/doc/proxies_installing.md | 18 +-
pages/doc/proxies_kube_container.md | 4 +-
pages/doc/proxies_manual_install.md | 38 ++--
pages/doc/proxies_preprocessor_rules.md | 28 +--
pages/doc/proxies_troubleshooting.md | 24 +--
pages/doc/purchase-additional-capacity.md | 14 +-
pages/doc/query_editor.md | 2 +-
.../doc/query_language_aggregate_functions.md | 2 +-
pages/doc/query_language_align_function.md | 2 +-
.../doc/query_language_discrete_continuous.md | 2 +-
pages/doc/query_language_getting_started.md | 2 +-
.../doc/query_language_metadata_functions.md | 2 +-
pages/doc/query_language_performance.md | 8 +-
pages/doc/query_language_point_tags.md | 2 +-
pages/doc/query_language_recipes.md | 6 +-
pages/doc/query_language_reference.md | 2 +-
pages/doc/query_language_series_joining.md | 2 +-
pages/doc/query_language_series_matching.md | 2 +-
pages/doc/query_language_windows_trends.md | 2 +-
pages/doc/sources_managing.md | 2 +-
pages/doc/start_trial.md | 30 +--
pages/doc/tags_overview.md | 14 +-
pages/doc/upgrade-and-purchase.md | 26 +--
pages/doc/visualize_histograms.md | 10 +-
pages/doc/wavefront_data_format.md | 16 +-
pages/doc/wavefront_data_ingestion.md | 18 +-
pages/doc/wavefront_prometheus.md | 12 +-
pages/doc/wavefront_release_notes.md | 22 +-
84 files changed, 579 insertions(+), 579 deletions(-)
diff --git a/pages/doc/2020_10.x_release_notes.md b/pages/doc/2020_10.x_release_notes.md
index 1549cff8e..a9f90c1dc 100644
--- a/pages/doc/2020_10.x_release_notes.md
+++ b/pages/doc/2020_10.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.10.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020.10 of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service. We also recently released a new version (6.1) of the Wavefront proxy. See the [Wavefront Proxy Release Notes](proxies_versions.html) for details.
+These release notes give an overview of the changes for Release 2020.10 of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service. We also recently released a new version (6.1) of the Wavefront proxy. See the [Wavefront Proxy Release Notes](proxies_versions.html) for details.
## New Histogram Functions
@@ -18,7 +18,7 @@ This release includes the following new functions for managing histograms:
## AWS Integration Changes
### Trusted Adviser Service Limit Metrics
-AWS Metrics+ Service Limit Metrics are now available in Operations for Applications.
+AWS Metrics+ Service Limit Metrics are now available in Tanzu Observability.
- Users must at least have a Business Level AWS Support plan.
- Additional permissions are required. See [Giving Global Read-Only Access](integrations_aws_overview.html#giving-access-to-your-aws-account) or [Giving Limited Access](integrations_aws_overview.html)
diff --git a/pages/doc/2020_14.x_release_notes.md b/pages/doc/2020_14.x_release_notes.md
index c9e940171..3286a3025 100644
--- a/pages/doc/2020_14.x_release_notes.md
+++ b/pages/doc/2020_14.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.14.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020.14 of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for Release 2020.14 of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Wavefront for Spring Boot
[Wavefront for Spring Boot](wavefront_springboot.html) allows you to quickly configure your environment, so Spring Boot components send metrics, histograms, and traces/spans to the Wavefront service. After you’ve completed setup, you can examine the data in preconfigured or custom Wavefront dashboards.
diff --git a/pages/doc/2020_22.x_release_notes.md b/pages/doc/2020_22.x_release_notes.md
index 1e963ba34..b52ddb1a8 100644
--- a/pages/doc/2020_22.x_release_notes.md
+++ b/pages/doc/2020_22.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.22.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020.22 of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for Release 2020.22 of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
{% include note.html content="[Tracing](tracing_basics.html) and [Histograms](proxies_histograms.html) are available by default for all customers starting with this release. Try them out and contact [support@wavefront.com](mailto:support@wavefront.com) if you have any questions." %}
diff --git a/pages/doc/2020_26.x_release_notes.md b/pages/doc/2020_26.x_release_notes.md
index 151ead5c2..6b970b80f 100644
--- a/pages/doc/2020_26.x_release_notes.md
+++ b/pages/doc/2020_26.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.26.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020.26 of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for Release 2020.26 of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## PromQL Support (Beta)
diff --git a/pages/doc/2020_30.x_release_notes.md b/pages/doc/2020_30.x_release_notes.md
index 0fb1e1d6a..35659d67b 100644
--- a/pages/doc/2020_30.x_release_notes.md
+++ b/pages/doc/2020_30.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.30.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020-30.x of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for Release 2020-30.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## OpenTelemetry Support in Wavefront
diff --git a/pages/doc/2020_38.x_release_notes.md b/pages/doc/2020_38.x_release_notes.md
index 6ff1db2b3..809954221 100644
--- a/pages/doc/2020_38.x_release_notes.md
+++ b/pages/doc/2020_38.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.38.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020-38.x of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for Release 2020-38.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Metrics Security
diff --git a/pages/doc/2020_42.x_release_notes.md b/pages/doc/2020_42.x_release_notes.md
index 808bdf66a..5fe4598a8 100644
--- a/pages/doc/2020_42.x_release_notes.md
+++ b/pages/doc/2020_42.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.42.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020-42.x of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for Release 2020-42.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Apdex Score for Services
diff --git a/pages/doc/2021-08.x_release_notes.md b/pages/doc/2021-08.x_release_notes.md
index 9970c38bd..b35c1e59c 100644
--- a/pages/doc/2021-08.x_release_notes.md
+++ b/pages/doc/2021-08.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.08.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2021-02.x to 2021-08.x of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for Release 2021-02.x to 2021-08.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Delta Counter Changes
diff --git a/pages/doc/2021-14.x_release_notes.md b/pages/doc/2021-14.x_release_notes.md
index 205641aa5..f334d7c2b 100644
--- a/pages/doc/2021-14.x_release_notes.md
+++ b/pages/doc/2021-14.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.14.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2021-09.x to 2021-14.x of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for Release 2021-09.x to 2021-14.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Partial Regex Support
diff --git a/pages/doc/2021-19.x_release_notes.md b/pages/doc/2021-19.x_release_notes.md
index 06abb58d6..48437b074 100644
--- a/pages/doc/2021-19.x_release_notes.md
+++ b/pages/doc/2021-19.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.19.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2021-15.x to 2021-19.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2021-15.x to 2021-19.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2021-19.x Release Notes
diff --git a/pages/doc/2021-24.x_release_notes.md b/pages/doc/2021-24.x_release_notes.md
index 5f5421455..6bb5755eb 100644
--- a/pages/doc/2021-24.x_release_notes.md
+++ b/pages/doc/2021-24.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.24.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2021-20.x to 2021-24.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2021-20.x to 2021-24.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2021-24.x Release Notes
diff --git a/pages/doc/2021-35.x_release_notes.md b/pages/doc/2021-35.x_release_notes.md
index a9da967a7..c8d4f0418 100644
--- a/pages/doc/2021-35.x_release_notes.md
+++ b/pages/doc/2021-35.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.35.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2021-26.x to 2021-35.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2021-26.x to 2021-35.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2021-35.x Release Notes
diff --git a/pages/doc/2021-49.x_release_notes.md b/pages/doc/2021-49.x_release_notes.md
index efb15ba51..e7a625f2c 100644
--- a/pages/doc/2021-49.x_release_notes.md
+++ b/pages/doc/2021-49.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.49.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2021-40.x to 2021-49.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2021-40.x to 2021-49.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2021-49.x Release Notes
diff --git a/pages/doc/2022-06.x_release_notes.md b/pages/doc/2022-06.x_release_notes.md
index f7e861ca5..71517a6e3 100644
--- a/pages/doc/2022-06.x_release_notes.md
+++ b/pages/doc/2022-06.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-06.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-01.x to 2022-06.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2022-01.x to 2022-06.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-06.x Release Notes
diff --git a/pages/doc/2022-20.x_release_notes.md b/pages/doc/2022-20.x_release_notes.md
index eef1dd8ad..4794d1a53 100644
--- a/pages/doc/2022-20.x_release_notes.md
+++ b/pages/doc/2022-20.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-20.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-08.x to 2022-20.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2022-08.x to 2022-20.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-20.x Release Notes
diff --git a/pages/doc/2022-29.x_release_notes.md b/pages/doc/2022-29.x_release_notes.md
index 70f7a558e..5754e5289 100644
--- a/pages/doc/2022-29.x_release_notes.md
+++ b/pages/doc/2022-29.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-29.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-22.x to 2022-29.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2022-22.x to 2022-29.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-29.x Release Notes
diff --git a/pages/doc/2022-39.x_release_notes.md b/pages/doc/2022-39.x_release_notes.md
index 26ebf7a67..cc4964d53 100644
--- a/pages/doc/2022-39.x_release_notes.md
+++ b/pages/doc/2022-39.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-39.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-32.x to 2022-39.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2022-32.x to 2022-39.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-39.x Release Notes
diff --git a/pages/doc/2022-49.x_release_notes.md b/pages/doc/2022-49.x_release_notes.md
index 37d17fec2..b23a4b600 100644
--- a/pages/doc/2022-49.x_release_notes.md
+++ b/pages/doc/2022-49.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-49.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-41.x to 2022-49.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2022-41.x to 2022-49.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-49.x Release Notes
diff --git a/pages/doc/2023-06.x_release_notes.md b/pages/doc/2023-06.x_release_notes.md
index 3cfd10e31..ac304b829 100644
--- a/pages/doc/2023-06.x_release_notes.md
+++ b/pages/doc/2023-06.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2023-06.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2023-02.x to 2023-06.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2023-02.x to 2023-06.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2023-06.x Release Notes
diff --git a/pages/doc/2023-13.x_release_notes.md b/pages/doc/2023-13.x_release_notes.md
index bf432005d..7a6eb0043 100644
--- a/pages/doc/2023-13.x_release_notes.md
+++ b/pages/doc/2023-13.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2023-13.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2023-07.x to 2023-13.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2023-07.x to 2023-13.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2023-13.x Release Notes
diff --git a/pages/doc/2023-29.x_release_notes.md b/pages/doc/2023-29.x_release_notes.md
index 79b5e8878..be5fcf27d 100644
--- a/pages/doc/2023-29.x_release_notes.md
+++ b/pages/doc/2023-29.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2023-29.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2023-18.x to 2023-29.x releases of the VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2023-18.x to 2023-29.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2023-29.x Release Notes
diff --git a/pages/doc/2023-45.x_release_notes.md b/pages/doc/2023-45.x_release_notes.md
index 5f028fa2d..0565a65e4 100644
--- a/pages/doc/2023-45.x_release_notes.md
+++ b/pages/doc/2023-45.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2023-45.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2023-31.x to 2023-45.x releases of the Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2023-31.x to 2023-45.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2023-45.x Release Notes
diff --git a/pages/doc/alert_target_customizing.md b/pages/doc/alert_target_customizing.md
index c71eb498e..320b134d2 100644
--- a/pages/doc/alert_target_customizing.md
+++ b/pages/doc/alert_target_customizing.md
@@ -7,7 +7,7 @@ permalink: alert_target_customizing.html
summary: Learn how to customize alert notifications by modifying alert target templates.
---
-An alert target provides a template that specifies how VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) extracts information from the alert, and how to assemble the notification from the alert information.
+An alert target provides a template that specifies how Tanzu Observability (formerly known as VMware Aria Operations for Applications) extracts information from the alert, and how to assemble the notification from the alert information.
You can customize the predefined template for the alert target type by making and saving changes. The template uses [Mustache syntax](https://mustache.github.io/) to combine literal text with _variables_ and _functions_ to produce the structures to be sent to the receiving messaging platform.
@@ -48,7 +48,7 @@ Here's what happens:
2. The alert template:
* Identifies the information you want to extract from the alert
* Embeds that information in a formatted structure appropriate for the target's messaging platform.
-3. Operations for Applications sends the formatted information to the target.
+3. Tanzu Observability sends the formatted information to the target.
4. The messaging platform interprets the structure and displays it as a readable notification.
For example:
@@ -74,7 +74,7 @@ The predefined Slack and VictorOps templates contain JSON attributes defined by
### Template Variables
-We define template variables for accessing [information about the alert](#obtain-information-about-the-alert) and about [the time series tested by the alert](#obtain-information-about-the-alerts-time-series). When the alert triggers a notification, Operations for Applications replaces the variables in the template with strings that represent the requested values.
+We define template variables for accessing [information about the alert](#obtain-information-about-the-alert) and about [the time series tested by the alert](#obtain-information-about-the-alerts-time-series). When the alert triggers a notification, Tanzu Observability replaces the variables in the template with strings that represent the requested values.
We support property and iterator variables, which are used differently.
diff --git a/pages/doc/alerts.md b/pages/doc/alerts.md
index 99994dce1..1df70b497 100644
--- a/pages/doc/alerts.md
+++ b/pages/doc/alerts.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: alerts.html
summary: Learn how alerts work, examine, and organize them.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports smart alerts that dynamically filter noise and capture true anomalies.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports smart alerts that dynamically filter noise and capture true anomalies.
* When the alert condition is met, an alert notifies one or more **alert targets**, which receive the alert notification(s).
* The **alert notification** includes an image and a link to see the alert in context.
* Look all alerts in the **Alert Browser** or examine a single firing alert in the **Alert Viewer**.
diff --git a/pages/doc/alerts_best_practices.md b/pages/doc/alerts_best_practices.md
index 326a597c5..cf2d03cd9 100644
--- a/pages/doc/alerts_best_practices.md
+++ b/pages/doc/alerts_best_practices.md
@@ -7,7 +7,7 @@ permalink: alerts_best_practices.html
summary: Learn about best practices for alert creation, alert settings, and alert troubleshooting.
---
-You use alerts in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) to get notified when something out of the ordinary happens. Alerts monitor your environment's behavior and send notifications based on how you configure the alert.
+You use alerts in Tanzu Observability (formerly known as VMware Aria Operations for Applications) to get notified when something out of the ordinary happens. Alerts monitor your environment's behavior and send notifications based on how you configure the alert.
This page has some best practices from our Technical Support engineers to help you set up truly useful alerts and avoid common problems with alerts.
@@ -35,7 +35,7 @@ For metrics that do not report at a fixed interval, alerts are only useful if y
* You can base the query condition on the last value reported, the sum of the values, or the average of the values depending on what nuance you want your query to capture.
-* Operations for Applications evaluates alerts once every 5 minutes by default. The **Checking Frequency** in the Alert page's **Advanced Settings** allows you to change the default (minimum is 1 minute).
+* Tanzu Observability evaluates alerts once every 5 minutes by default. The **Checking Frequency** in the Alert page's **Advanced Settings** allows you to change the default (minimum is 1 minute).
**Example 1**: Suppose you have a metric that reports the number of failures since server restart. If the metric reports 25 failures at 1:24, and 25 failures at 1:25, that could mean nothing has changed. However, it could also mean that within a minute, 10 failures resolved and 10 new failures appeared. It could even mean that within a minute, total failures dropped to 2, jumped up to 100, and came back down to 25. For this use case, your alert can't just check the number of failures once a minute. Instead, the alert has to look at a metric that captures the total number of failures that happened over time.
@@ -86,7 +86,7 @@ Don't use interpolation if metrics show deltas to avoid results like `4.5 proces
**Question:** Is this metric aligned to the minute (or any other interval)?
-By default, alert checking frequency is 5 minutes, and alert condition queries are evaluated with 1 minute granularity. If more than 1 data point comes in per minute, consider explicitly aligning your data to 1 minute using the summarization strategy appropriate for your use case (e.g., `sum`, `max`, `last` etc). If you don't specify a summarization strategy, Operations for Applications uses `avg`, which computes the mean. If your data points are coming in much less frequently than once a minute, consider adjusting the alert's checking frequency advanced option.
+By default, alert checking frequency is 5 minutes, and alert condition queries are evaluated with 1 minute granularity. If more than 1 data point comes in per minute, consider explicitly aligning your data to 1 minute using the summarization strategy appropriate for your use case (e.g., `sum`, `max`, `last` etc). If you don't specify a summarization strategy, Tanzu Observability uses `avg`, which computes the mean. If your data points are coming in much less frequently than once a minute, consider adjusting the alert's checking frequency advanced option.
### Near Real Time or Back-Filled?
@@ -104,7 +104,7 @@ For example, imagine you want to trigger an alert when the total number of error
* **Reporting intervals**: Even though each VM in this example likely has the same reporting frequency, the reporting interval may be staggered. It usually makes sense to calculate the `total number of errors reported across 10 VMs` with an aggregation function. But staggered reporting in conjunction with an aggregation function introduces interpolated values. Consider whether you want to use a raw or non-raw aggregation function. See [Aggregating Time Series](query_language_aggregate_functions.html) for background and a video.
-* **Lag in real-time data**: If the Operations for Applications service receives the error data with a 5-minute lag, then you need to consider that when setting the Alert Firing time window or constructing your query.
+* **Lag in real-time data**: If the Tanzu Observability service receives the error data with a 5-minute lag, then you need to consider that when setting the Alert Firing time window or constructing your query.
- If the alert is set to evaluate a 3-minute time window of real-time data, then there would be no reported values to evaluate during the check.
- If you look at the data 20 minutes after the fact, you see that the total number of errors were exceeded.
You can increase the **Trigger Window** or use the lag() function to get the correct behavior (alert fires).
diff --git a/pages/doc/alerts_delayed_data.md b/pages/doc/alerts_delayed_data.md
index 3efd54324..6edc0ca81 100644
--- a/pages/doc/alerts_delayed_data.md
+++ b/pages/doc/alerts_delayed_data.md
@@ -7,7 +7,7 @@ permalink: alerts_delayed_data.html
summary: Diagnose and avoid spurious alerts due to delayed data reporting.
---
-An alert fires or resolves based on the data values that are present in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) during the alert checking time window. If data reporting is delayed, an alert checking decision might be made on a temporarily incomplete set of data values. This can lead to an apparent false positive (the alert fires when you don't expect it) or false negative (the alert does not fire as expected).
+An alert fires or resolves based on the data values that are present in Tanzu Observability (formerly known as VMware Aria Operations for Applications) during the alert checking time window. If data reporting is delayed, an alert checking decision might be made on a temporarily incomplete set of data values. This can lead to an apparent false positive (the alert fires when you don't expect it) or false negative (the alert does not fire as expected).
This page can help you understand, diagnose, and prevent the impact of data delays on alerts. Buffering alerts against false positives, in particular, can help you reduce alert noise.
@@ -19,7 +19,7 @@ Suppose you need to monitor the total number of users that are sharded across 3
* At about 9:35, `app-3` finally sends its data points, and these delayed points are backfilled into the time series.
-* A few minutes later, you investigate the alert by using an Operations for Applications chart. You query for the total number of users, and adjust the custom time window so you can view the data points in the minutes around the alert check (9:28 to 9:30).
+* A few minutes later, you investigate the alert by using an Tanzu Observability chart. You query for the total number of users, and adjust the custom time window so you can view the data points in the minutes around the alert check (9:28 to 9:30).
* You are surprised to see that the chart shows a total of about 105 users during the alert check window.
@@ -35,11 +35,11 @@ If you think an alert has fired or resolved by mistake, it's possible that a dat
### What is a Data Delay?
-A data delay is a noticeable latency between the time that a source collects a data value and the time that Operations for Applications receives that value. Data delays can occur anywhere in the data pipeline. Data delays can be:
+A data delay is a noticeable latency between the time that a source collects a data value and the time that Tanzu Observability receives that value. Data delays can occur anywhere in the data pipeline. Data delays can be:
* Predictable - for example, when a source preprocesses or batches the data values before sending them.
* Unpredictable - for example, when a sudden network slowdown or outage interferes with the flow of data.
-When delayed data points arrive, Operations for Applications backfills them into their time series. Each backfilled point is stored with the timestamp that reflects when the source collected it, not when we received it.
+When delayed data points arrive, Tanzu Observability backfills them into their time series. Each backfilled point is stored with the timestamp that reflects when the source collected it, not when we received it.
diff --git a/pages/doc/chart_builder.md b/pages/doc/chart_builder.md
index 8d695f728..93ceee39b 100644
--- a/pages/doc/chart_builder.md
+++ b/pages/doc/chart_builder.md
@@ -7,7 +7,7 @@ permalink: chart_builder.html
summary: Use Chart Builder to display the data you're interested in.
---
-When you get started with VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront), Chart Builder is the fasted way to customize which metrics you see and to display them in charts.
+When you get started with Tanzu Observability (formerly known as VMware Aria Operations for Applications), Chart Builder is the fasted way to customize which metrics you see and to display them in charts.
Chart Builder has the tools for creating charts and customizing which metrics you see.
* Construct queries from building blocks
diff --git a/pages/doc/csp_area_differences.md b/pages/doc/csp_area_differences.md
index c9800637f..a4aa8a13c 100644
--- a/pages/doc/csp_area_differences.md
+++ b/pages/doc/csp_area_differences.md
@@ -4,16 +4,16 @@ keywords:
tags: [introduction]
sidebar: doc_sidebar
permalink: csp-differences-by-area.html
-summary: Learn about the functionality differences between VMware Aria Operations for Applications original subscriptions and VMware Cloud services subscriptions.
+summary: Learn about the functionality differences between Tanzu Observability original subscriptions and VMware Cloud services subscriptions.
---
-Operations for Applications subscriptions are two types: original subscriptions and VMware Cloud Services subscriptions.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) subscriptions are two types: original subscriptions and VMware Cloud Services subscriptions.
## Examples of the Functionality Differences
### Users, Roles, and Group Management
-Most of the user and account management tasks done in the Operations for Applications UI for original subscriptions, are done in the VMware Cloud services for VMware Cloud services subscriptions. For example, the following tasks related to managing users, roles, and groups can be done from the VMware Cloud Services Console.
+Most of the user and account management tasks done in the Tanzu Observability UI for original subscriptions, are done in the VMware Cloud services for VMware Cloud services subscriptions. For example, the following tasks related to managing users, roles, and groups can be done from the VMware Cloud Services Console.
* Invite new users
* Assign permissions
@@ -26,9 +26,9 @@ Most of the user and account management tasks done in the Operations for Applica
### Admin Tasks
-Some administrative tasks, done by **Super Admins** and users with the **Accounts** permission in original subscriptions, are done by VMware Cloud **Organization Owners** and VMware Cloud **Organization Administrators** in VMware Cloud services subscriptions. Others can be done by Operations for Applications **Admins** in the Operations for Applications UI.
+Some administrative tasks, done by **Super Admins** and users with the **Accounts** permission in original subscriptions, are done by VMware Cloud **Organization Owners** and VMware Cloud **Organization Administrators** in VMware Cloud services subscriptions. Others can be done by Tanzu Observability **Admins** in the Tanzu Observability UI.
-With the 2023-38 release, we introduce the **Admin** permission and service role, which partially correspond to the **Accounts** permission for original subscriptions. Users with the **Admin** service role can manage service accounts and Operations for Applications API tokens. They can also restrict access to new dashboards and alerts and set the organization settings. For example, they can restrict the access to the object creator only and set default settings, such as display settings, PromQL support, default way of building queries, and define Logs settings.
+With the 2023-38 release, we introduce the **Admin** permission and service role, which partially correspond to the **Accounts** permission for original subscriptions. Users with the **Admin** service role can manage service accounts and Tanzu Observability API tokens. They can also restrict access to new dashboards and alerts and set the organization settings. For example, they can restrict the access to the object creator only and set default settings, such as display settings, PromQL support, default way of building queries, and define Logs settings.
{% include warning.html content="Service accounts and the API tokens associated with them will be deprecated in the future. It's strongly recommended that you incrementally switch to using [server to server OAuth apps](csp_server_to_server_apps.html) which authenticate with more secure VMware Cloud services access tokens. For information on how to do this, see [How to Replace a Service Account with a Server to Server App?](csp_migration.html#how-to-replace-a-service-account-with-a-server-to-server-app)." %}
@@ -47,14 +47,14 @@ Last sentence: Тo temporarily enable service accounts for your service instance
-
Who: Operations for Applications Super Admin
-
Where: From the Operations for Applications UI
+
Who: Tanzu Observability Super Admin
+
Where: From the Tanzu Observability UI
-
Who: Users with the Operations for Applications Super Admin service role
-
Where: From the Operations for Applications UI
+
Who: Users with the Tanzu Observability Super Admin service role
+
Where: From the Tanzu Observability UI
@@ -63,14 +63,14 @@ Last sentence: Тo temporarily enable service accounts for your service instance
-
Who: Operations for Applications Super Admin
-
Where: From the Operations for Applications UI
+
Who: Tanzu Observability Super Admin
+
Where: From the Tanzu Observability UI
-
Who: Users with the Operations for Applications Super Admin service role
-
Where: From the Operations for Applications UI
+
Who: Users with the Tanzu Observability Super Admin service role
+
Where: From the Tanzu Observability UI
@@ -79,8 +79,8 @@ Last sentence: Тo temporarily enable service accounts for your service instance
-
Who: Operations for Applications Super Admin
-
Where: In the Operations for Applications UI
+
Who: Tanzu Observability Super Admin
+
Where: In the Tanzu Observability UI
@@ -91,18 +91,18 @@ Last sentence: Тo temporarily enable service accounts for your service instance
-
Create and manage service accounts and their Operations for Applications API tokens
+
Create and manage service accounts and their Tanzu Observability API tokens
-
Who: Operations for Applications users with the Accounts permission
-
Where: In the Operations for Applications UI
+
Who: Tanzu Observability users with the Accounts permission
+
Where: In the Tanzu Observability UI
-
Who: Users with the Operations for Applications Admin service role
-
Where: In the Operations for Applications UI
+
Who: Users with the Tanzu Observability Admin service role
+
Where: In the Tanzu Observability UI
@@ -111,14 +111,14 @@ Last sentence: Тo temporarily enable service accounts for your service instance
-
Who: Operations for Applications Super Admin
-
Where: In the Operations for Applications UI
+
Who: Tanzu Observability Super Admin
+
Where: In the Tanzu Observability UI
-
Who: Users with the Operations for Applications Super Admin service role
-
Where: In the Operations for Applications UI
+
Who: Users with the Tanzu Observability Super Admin service role
+
Where: In the Tanzu Observability UI
@@ -127,14 +127,14 @@ Last sentence: Тo temporarily enable service accounts for your service instance
-
Who: Operations for Applications users with the Accounts permission
-
Where: In the Operations for Applications UI
+
Who: Tanzu Observability users with the Accounts permission
+
Where: In the Tanzu Observability UI
-
Who: Users with the Operations for Applications Admin service role
-
Where: In the Operations for Applications UI
+
Who: Users with the Tanzu Observability Admin service role
+
Where: In the Tanzu Observability UI
@@ -143,14 +143,14 @@ Last sentence: Тo temporarily enable service accounts for your service instance
-
Who: Operations for Applications users with the Accounts permission
-
Where: In the Operations for Applications UI
+
Who: Tanzu Observability users with the Accounts permission
+
Where: In the Tanzu Observability UI
-
Who: Users with the Operations for Applications Admin service role
-
Where: In the Operations for Applications UI
+
Who: Users with the Tanzu Observability Admin service role
+
Where: In the Tanzu Observability UI
@@ -159,9 +159,9 @@ Last sentence: Тo temporarily enable service accounts for your service instance
### REST API Access
-For original subscriptions, using the Operations for Applications REST API requires an API token associated with a user account or a service account. To generate API tokens for your user account you need the **API Tokens** permission. To generate API tokens for service accounts and to manage the API tokens in your Operations for Applications organization, you need the **Accounts** permission.
+For original subscriptions, using the Tanzu Observability REST API requires an API token associated with a user account or a service account. To generate API tokens for your user account you need the **API Tokens** permission. To generate API tokens for service accounts and to manage the API tokens in your Tanzu Observability organization, you need the **Accounts** permission.
-When your service is onboarded to VMware Cloud services and you want to access the Operations for Applications REST API, you need a VMware Cloud services **access token**. In a few cases, when setting up a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens), authentication with an Operations for Applications API token is also supported. However, using a VMware Cloud services **access token** is the recommended way as we will deprecate the service accounts in the future. To obtain an **access token**, you can:
+When your service is onboarded to VMware Cloud services and you want to access the Tanzu Observability REST API, you need a VMware Cloud services **access token**. In a few cases, when setting up a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens), authentication with a Tanzu Observability API token is also supported. However, using a VMware Cloud services **access token** is the recommended way as we will deprecate the service accounts in the future. To obtain an **access token**, you can:
* Generate a VMware Cloud services API token associated with your user account and exchange it for an access token.
@@ -181,9 +181,9 @@ When your service is onboarded to VMware Cloud services and you want to access t
User Login
-
Users log in to their Operations for Applications service instance by using the URL of the service cluster, https://<your_instance>.wavefront.com, and their Operations for Applications accounts. If their corporate domain is configured for SAML SSO with Operations for Applications, users log in with their corporate accounts.
+
Users log in to their Tanzu Observability service instance by using the URL of the service cluster, https://<your_instance>.wavefront.com, and their Tanzu Observability accounts. If their corporate domain is configured for SAML SSO with Tanzu Observability, users log in with their corporate accounts.
-
Users log in to their Operations for Applications service instance through the VMware Cloud Services Console with their VMware Cloud services accounts. If their corporate domain is federated with VMware Cloud services, users log in with their corporate accounts. For details, see Log In from the VMware Cloud Services Console.
+
Users log in to their Tanzu Observability service instance through the VMware Cloud Services Console with their VMware Cloud services accounts. If their corporate domain is federated with VMware Cloud services, users log in with their corporate accounts. For details, see Log In from the VMware Cloud Services Console.
@@ -191,16 +191,16 @@ When your service is onboarded to VMware Cloud services and you want to access t
Who: Users with the Accounts permission.
-
Where: In the Operations for Applications user interface.
+
Where: In the Tanzu Observability user interface.
How: You can invite new users with or without assigning roles and permissions. For details, see Manage User Accounts.
Who: Users with the VMware Cloud Organization Owner or Organization Administrator role.
Where: In the VMware Cloud Services Console.
-
How: To add a user to your Operations for Applications service instance, you must assign that user:
+
How: To add a user to your Tanzu Observability service instance, you must assign that user:
An organization role for the VMware Cloud organization running the service instance. At a minimum, you must assign the VMware Cloud Organization Member role.
-
An Operations for Applications service role for your service instance. At a minimum, you must assign the Viewer service role.
-
Optionally, a custom role with one or more Operations for Applications permissions. A custom role applies to all service instances for which the user has an Operations for Applications service role.
+
A Tanzu Observability service role for your service instance. At a minimum, you must assign the Viewer service role.
+
Optionally, a custom role with one or more Tanzu Observability permissions. A custom role applies to all service instances for which the user has a Tanzu Observability service role.
Where: In the Operations for Applications user interface.
+
Where: In the Tanzu Observability user interface.
How: Service accounts authenticate with API tokens. Service accounts can be assigned with roles and permissions, as well as can be added to groups. For details, see Manage Service Accounts.
Note: Server to server OAuth apps are recommended and fully supported. Service accounts are with limited support and will be deprecated in the future.
Who:
For server to server OAuth apps, users with the VMware Cloud Organization Owner, Organization Administrator, or Organization Member with the Developer role assigned.
-
For service accounts, users with the Admin Operations for Applications service role.
+
For service accounts, users with the Admin Tanzu Observability service role.
Where:
For server to server OAuth apps, in the VMware Cloud Services Console.
-
For service accounts, in the Operations for Applications user interface.
+
For service accounts, in the Tanzu Observability user interface.
How:
Server to server OAuth apps authenticate with VMware Cloud services access tokens that can be exchanged from their OAuth credentials. Server to server OAuth app can be assigned with organization roles, service roles, and custom roles, and can belong to one or more VMware Cloud organizations. For details, see Manage Server to Server Apps.
-
Service accounts authenticate with Operations for Applications API tokens. Service accounts can be assigned with permissions only, and cannot be added to groups. For details, see Manage Service Accounts.
+
Service accounts authenticate with Tanzu Observability API tokens. Service accounts can be assigned with permissions only, and cannot be added to groups. For details, see Manage Service Accounts.
@@ -234,28 +234,28 @@ For details, see Manage User Accounts.Permissions Management
Who: Users with the Accounts permission.
-
Where: In the Operations for Applications user interface.
+
Where: In the Tanzu Observability user interface.
How: Permissions can be assigned to roles as well as to individual user accounts and service accounts.
Note: The permissions list includes the Accounts, SAML IdP Admin, and API token permissions, because they are required for all of the authorization and authentication tasks which are done in the Operations for Applications.
-
In addition, the Accounts permission grants privileges for managing the Operations for Applications organization settings.
+
Note: The permissions list includes the Accounts, SAML IdP Admin, and API token permissions, because they are required for all of the authorization and authentication tasks which are done in the Tanzu Observability.
+
In addition, the Accounts permission grants privileges for managing the Tanzu Observability organization settings.
For assigning permissions to roles, users with the VMware Cloud Organization Owner or Organization Administrator role.
-
For assigning permissions to service accounts, users with the Admin Operations for Applications service role.
+
For assigning permissions to service accounts, users with the Admin Tanzu Observability service role.
Where:
For assigning permissions to roles, in the VMware Cloud Services Console.
-
For assigning permissions to service accounts, in the Operations for Applications user interface.
+
For assigning permissions to service accounts, in the Tanzu Observability user interface.
-
How: Permissions can be assigned only to roles in the VMware Cloud services organization and service accounts - in the Operations for Applications environment.
+
How: Permissions can be assigned only to roles in the VMware Cloud services organization and service accounts - in the Tanzu Observability environment.
Note: The Accounts, SAML IdP Admin, and API token permissions don't exist, because most of the authorization and authentication tasks requiring these permissions are done in the VMware Cloud Services Console.
-
The Admin Operations for Applications permission grants privileges for managing service accounts, Operations for Applications API tokens, and the Operations for Applications organization settings.
The Admin Tanzu Observability permission grants privileges for managing service accounts, Tanzu Observability API tokens, and the Tanzu Observability organization settings.
Where: In the Operations for Applications user interface.
+
Where: In the Tanzu Observability user interface.
How: Roles can be assigned with permissions. Roles can be assigned to user accounts, service accounts, and groups. For details, see Manage Roles and Permissions.
@@ -279,7 +279,7 @@ For details, see Manage User Accounts.Where: In the VMware Cloud Services Console.
How: Roles can be assigned with permissions. Roles can be assigned to users, groups, API tokens, and server to server apps. There are:
-
Built-in Operations for Applications service roles, which are not editable. Each Operations for Applications permission is represented with a service role. In addition, the Super Admin and Viewer service roles grant full-administrative and view-only access, respectively.
+
Built-in Tanzu Observability service roles, which are not editable. Each Tanzu Observability permission is represented with a service role. In addition, the Super Admin and Viewer service roles grant full-administrative and view-only access, respectively.
Custom roles can be created and assigned with permissions for one or more services.
For details, see Manage Roles.
@@ -289,7 +289,7 @@ For details, see Manage Roles.Groups Management
Who: Users with the Accounts permission.
-
Where: In the Operations for Applications user interface.
+
Where: In the Tanzu Observability user interface.
How: A group of user and service accounts can be assigned with one or more roles. For details, see Create a Group.
@@ -302,8 +302,8 @@ For details, see Manage Roles.Self-Service SAML SSO
Who: Users with the SAML IdP Admin permission.
-
Where: In the Operations for Applications user interface.
Who: A user with the VMware Cloud Organization Owner role together with an Enterprise Administrator.
@@ -314,30 +314,30 @@ For details, see Manage Roles.
Generating API Tokens
-
Note: Only Operations for Applications API tokens are supported.
+
Note: Only Tanzu Observability API tokens are supported.
Who:
For API tokens associated with a user account, the corresponding user who must have the API Tokens permission.
For API tokens associated with service accounts, the users with the Accounts permission.
-
Where: In the Operations for Applications user interface.
+
Where: In the Tanzu Observability user interface.
How:
-
A user with the API Tokens permission can generate Operations for Applications API tokens for their own user account. The API tokens inherit all permissions that its associated user account owns.
-
Users with the Accounts permission can generate Operations for Applications API tokens for service accounts. The API tokens inherit the permissions of their associated service account.
+
A user with the API Tokens permission can generate Tanzu Observability API tokens for their own user account. The API tokens inherit all permissions that its associated user account owns.
+
Users with the Accounts permission can generate Tanzu Observability API tokens for service accounts. The API tokens inherit the permissions of their associated service account.
Note: It is recommended to use VMware Cloud services API tokens and server to server OAuth app credentials for obtaining VMware Cloud services access tokens. Operations for Applications API tokens are with limited support and will be deprecated in a future release.
+
Note: It is recommended to use VMware Cloud services API tokens and server to server OAuth app credentials for obtaining VMware Cloud services access tokens. Tanzu Observability API tokens are with limited support and will be deprecated in a future release.
Who:
For VMware Cloud services API tokens associated with a user account, the corresponding user.
-
For Operations for Applications API tokens associated with service accounts, the users with the Admin Operations for Applications service role.
+
For Tanzu Observability API tokens associated with service accounts, the users with the Admin Tanzu Observability service role.
Where:
For VMware Cloud services API tokens associated with a user account, in the VMware Cloud Services Console.
-
For Operations for Applications API tokens associated with service accounts, in the Operations for Applications user interface.
+
For Tanzu Observability API tokens associated with service accounts, in the Tanzu Observability user interface.
How:
Each user can generate VMware Cloud services API tokens for their user account. An API token can be assigned with roles from the list of roles that the user owns - organization roles, service roles, and custom roles. For details and instructions, see How do I generate API tokens in the VMware Cloud services documentation.
-
Users with the Admin service role can generate Operations for Applications API tokens for service accounts. The API tokens inherit the permissions of their associated service account. For details, see Manage Service Accounts.
+
Users with the Admin service role can generate Tanzu Observability API tokens for service accounts. The API tokens inherit the permissions of their associated service account. For details, see Manage Service Accounts.
For VMware Cloud services API tokens associated with a user account, the corresponding user.
For all VMware Cloud services API tokens in the VMware Cloud organization, the users with the VMware Cloud Organization Owner role if the organization is activated for Identity Governance and Administration (IGA).
-
For all Operations for Applications API tokens (limited support), the users with the Admin Operations for Applications service role.
+
For all Tanzu Observability API tokens (limited support), the users with the Admin Tanzu Observability service role.
Where:
For VMware Cloud services API tokens, in the Cloud Services Console.
-
For Operations for Applications API tokens (limited support), in the Operations for Applications user interface.
+
For Tanzu Observability API tokens (limited support), in the Tanzu Observability user interface.
How:
All users can view and revoke their own VMware Cloud services API tokens. For details, see How do I manage my API tokens in the VMware Cloud services documentation.
Users with the VMware Cloud Organization Owner role can monitor the API tokens created in the organization and can set constraints for idle and maximum Time to live (TTL) for all newly created tokens. For details and instructions, see How do I manage API tokens in my Organization in the VMware Cloud services documentation.
-Who: Everyone who has an Operations for Applications API token associated with a user account or a service account.
+Who: Everyone who has a Tanzu Observability API token associated with a user account or a service account.
Where: An API client.
-
How: Interacting with the Operations for Application REST API requires an Operations for Application API token.
+
How: Interacting with the Tanzu Observability REST API requires a Tanzu Observability API token.
To interact with the REST API by using a service account, you must use an API token associated with that service account. For details, see Make API Calls by Using a Service Account.
Who: Everyone who has a VMware Cloud services API token or the credentials of a server to server OAuth app.
Where: An API client.
-
How: Interacting with the Operations for Application REST API requires a VMware Cloud services access token.
+
How: Interacting with the Tanzu Observability REST API requires a VMware Cloud services access token.
To interact with the REST API on behalf of your user account, you must exchange your VMware Cloud services API token for an access token. For details, see Make API Calls by Using a User Account.
To interact with the REST API on behalf of your VMware Cloud organization, you must exchange the OAuth credentials of a server to server app for an access token. For details, see Make API Calls by Using a Server to Server App.
Note: The Wavefront proxy authenticates with an Operations for Applications API token.
+
Note: The Wavefront proxy authenticates with a Tanzu Observability API token.
Who: Users with the Proxies permission.
-
Where: In the Operations for Applications user interface.
-
How: As a user with the Proxies permission, you must configure the proxy to authenticate to Operations for Applications with an Operations for Applications API token that have the Proxies permission. For details, see Install a Proxy from the UI.
+
Where: In the Tanzu Observability user interface.
+
How: As a user with the Proxies permission, you must configure the proxy to authenticate to Tanzu Observability with a Tanzu Observability API token that have the Proxies permission. For details, see Install a Proxy from the UI.
-
Note: The Wavefront proxy authenticates with a VMware Cloud services access token obtained from server to server OAuth app credentials or from a VMware Cloud services API token. Proxy authentication with an Operations for Applications API token is still possible and supported only for a limited list of integrations.
+
Note: The Wavefront proxy authenticates with a VMware Cloud services access token obtained from server to server OAuth app credentials or from a VMware Cloud services API token. Proxy authentication with a Tanzu Observability API token is still possible and supported only for a limited list of integrations.
Who:
-
For proxy installation, users with the Proxies Operations for Applications service role.
+
For proxy installation, users with the Proxies Tanzu Observability service role.
For creating server to server OAuth apps, users with the VMware Cloud Organization Owner, Organization Administrator, or Organization Member with Developer roles.
-
For generating an Operations for Applications API token of a service account, users with the Admin Operations for Applications service role.
+
For generating a Tanzu Observability API token of a service account, users with the Admin Tanzu Observability service role.
Where:
For generating a VMware Cloud services API token or creating a server to server OAuth app, in the VMware Cloud Services Console.
-
For proxy installation and generating an Operations for Applications API token for a service account, in the Operations for Applications user interface.
+
For proxy installation and generating a Tanzu Observability API token for a service account, in the Tanzu Observability user interface.
-
How: As a user with the Proxies service role, you configure the proxy to authenticate to Operations for Applications. The proxy obtains a VMware Cloud services access token with the Proxies service role or use an Operations for Applications API token of a service account with the Proxies permission. To obtain a VMware Cloud services access token:
+
How: As a user with the Proxies service role, you configure the proxy to authenticate to Tanzu Observability. The proxy obtains a VMware Cloud services access token with the Proxies service role or use a Tanzu Observability API token of a service account with the Proxies permission. To obtain a VMware Cloud services access token:
The proxy can use the credentials of a server to server OAuth app - ID and secret, together with the VMware Cloud organization long ID.
The proxy can use the VMware Cloud services API token of an active user account.
In both ways, the access token is directly issued to the proxy. For details, see Proxy Authentication Types.
@@ -446,19 +446,19 @@ In both ways, the access token is directly issued to the proxy. For details, see
Integrations Installation
-
Note: All integrations that use a Wavefront proxy authenticate with an Operations for Applications API token.
-
Who: Users or service accounts with the Proxies permission who have an active Operations for Applications API token.
-
Where: In the Operations for Applications user interface.
+
Note: All integrations that use a Wavefront proxy authenticate with a Tanzu Observability API token.
+
Who: Users or service accounts with the Proxies permission who have an active Tanzu Observability API token.
+
Where: In the Tanzu Observability user interface.
How: Follow the instructions on the Setup tab of the integration that you want to install.
-
Note: Most of the integrations that use a Wavefront proxy authenticate with a VMware Cloud services access token. A limited list of integrations still use proxy authentication with an Operations for Applications API token.
-
Who: Users with the Proxies Operations for Applications service role who must have one of the following:
+
Note: Most of the integrations that use a Wavefront proxy authenticate with a VMware Cloud services access token. A limited list of integrations still use proxy authentication with a Tanzu Observability API token.
+
Who: Users with the Proxies Tanzu Observability service role who must have one of the following:
A valid VMware Cloud services API token with the Proxies service role assigned.
The credentials of a server to server OAuth app with the Proxies service role assigned.
-
An Operations for Applications API token associated with a service account that has the Proxies permission.
+
A Tanzu Observability API token associated with a service account that has the Proxies permission.
-
Where: In the Operations for Applications user interface.
+
Where: In the Tanzu Observability user interface.
How: Follow the instructions on the Setup tab of the integration that you want to install.
@@ -466,15 +466,15 @@ In both ways, the access token is directly issued to the proxy. For details, see
Metrics Security Policy Management
Who: Users with the Metrics permission.
-
Where: In the Operations for Applications user interface.
+
Where: In the Tanzu Observability user interface.
How: Privileged users can block or allow access to metrics for:
diff --git a/pages/doc/csp_migration.md b/pages/doc/csp_migration.md
index 35b3faf69..39d592d52 100644
--- a/pages/doc/csp_migration.md
+++ b/pages/doc/csp_migration.md
@@ -4,17 +4,17 @@ keywords: administration
tags: [administration]
sidebar: doc_sidebar
permalink: csp_migration.html
-summary: Learn about how we migrate the authorization and authentication from Operations for Applications to VMware Cloud services.
+summary: Learn about how we migrate the authorization and authentication from Tanzu Observability to VMware Cloud services.
---
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. We are in the process of incrementally onboarding all original subscriptions to VMware Cloud services.
+Starting July 3, 2023, Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. We are in the process of incrementally onboarding all original subscriptions to VMware Cloud services.
## What Should I Do Before the Onboarding?
-Currently, all original Operations for Applications subscriptions are integrated with VMware Cloud services for billing and subscription management. Therefore, you must already have a [VMware Cloud organization](csp_getting_started.html#whats-a-vmware-cloud-organization) with at least one user with the [VMware Cloud **Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role).
+Currently, all original Tanzu Observability subscriptions are integrated with VMware Cloud services for billing and subscription management. Therefore, you must already have a [VMware Cloud organization](csp_getting_started.html#whats-a-vmware-cloud-organization) with at least one user with the [VMware Cloud **Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role).
Before the onboarding:
-* Get familiar with the VMware Cloud service platform. See [Getting Started with Operations for Applications on VMware Cloud Services](csp_getting_started.html).
+* Get familiar with the VMware Cloud service platform. See [Getting Started with Tanzu Observability on VMware Cloud Services](csp_getting_started.html).
* Verify that your VMware Cloud **Organization Owner** user can log in to the [VMware Cloud Services Console](https://console.cloud.vmware.com).
- If you are the VMware Cloud **Organization Owner** user and cannot log in, try using the **Forgot Password** option.
@@ -61,23 +61,23 @@ Here's the process:
## How Are the Users Migrated to VMware Cloud Services?
-During the process of onboarding your Operations for Applications service to VMware Cloud services, we add all your current users to your VMware Cloud organization running the service.
+During the process of onboarding your Tanzu Observability service to VMware Cloud services, we add all your current users to your VMware Cloud organization running the service.
-
+
-* If a user is a **Super Admin** in Operations for Applications, we assign that user with the **Super Admin** Operations for Applications service role in VMware Cloud services.
-* If a user is assigned with individual permissions in Operations for Applications, we assign that user with the corresponding [Operations for Applications service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in) in VMware Cloud services. For example, if a user has the **Alerts** permission in Operations for Applications, we assign that user with the **Alerts** Operations for Applications service role in VMware Cloud services. There are the following exceptions:
+* If a user is a **Super Admin** in Tanzu Observability, we assign that user with the **Super Admin** Tanzu Observability service role in VMware Cloud services.
+* If a user is assigned with individual permissions in Tanzu Observability, we assign that user with the corresponding [Tanzu Observability service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in) in VMware Cloud services. For example, if a user has the **Alerts** permission in Tanzu Observability, we assign that user with the **Alerts** Tanzu Observability service role in VMware Cloud services. There are the following exceptions:
- - The **Accounts** permission is replaced by the [VMware Cloud **Organization Administrator** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) plus the **Admin** Operations for Applications service role.
+ - The **Accounts** permission is replaced by the [VMware Cloud **Organization Administrator** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) plus the **Admin** Tanzu Observability service role.
- The **API Tokens** permission is not replaced by any role, because this privilege is not needed in VMware Cloud services. Each VMware Cloud services user can manage their own VMware Cloud services API tokens.
- The **SAML IdP Admin** permission is not replaced by any role, because this privilege is not needed in VMware Cloud services. The VMware Cloud **Organization Owner** initiates enterprise federation for your corporate domain and assigns an **Enterprise Administrator**.
For details, see the [permissions differences](csp-differences-by-area.html#permissions).
-* If a user does not have any permissions and roles in Operations for Applications, we assign that user with the **Viewer** Operations for Applications service role in VMware Cloud services.
-* If a user is assigned with roles in Operations for Applications, we assign that user with the corresponding custom roles in VMware Cloud services. See [How Are the Roles Migrated to VMware Cloud Services?](#how-are-the-roles-migrated-to-vmware-cloud-services).
-* If a user belongs to a group in Operations for Applications, we add that user to the corresponding group in VMware Cloud services. See [How Are the Groups Migrated to VMware Cloud Services?](#how-are-the-groups-migrated-to-vmware-cloud-services).
+* If a user does not have any permissions and roles in Tanzu Observability, we assign that user with the **Viewer** Tanzu Observability service role in VMware Cloud services.
+* If a user is assigned with roles in Tanzu Observability, we assign that user with the corresponding custom roles in VMware Cloud services. See [How Are the Roles Migrated to VMware Cloud Services?](#how-are-the-roles-migrated-to-vmware-cloud-services).
+* If a user belongs to a group in Tanzu Observability, we add that user to the corresponding group in VMware Cloud services. See [How Are the Groups Migrated to VMware Cloud Services?](#how-are-the-groups-migrated-to-vmware-cloud-services).
-{% include tip.html content="From now on, users with the VMware Cloud **Organization Owner** and **Organization Administrator** roles can [manage the Operations for Applications users](csp_user_management.html) in the VMware Cloud Services Console."%}
+{% include tip.html content="From now on, users with the VMware Cloud **Organization Owner** and **Organization Administrator** roles can [manage the Tanzu Observability users](csp_user_management.html) in the VMware Cloud Services Console."%}
@@ -91,38 +91,38 @@ Originally, your Operation for Applications service includes the **Everyone** an
### How Are the Custom Groups Migrated?
-During the process of onboarding your Operations for Applications service to VMware Cloud services, for each group that you have created in Operations for Applications, we create a corresponding group in your VMware Cloud organization running the service.
+During the process of onboarding your Tanzu Observability service to VMware Cloud services, for each group that you have created in Tanzu Observability, we create a corresponding group in your VMware Cloud organization running the service.
-* The corresponding VMware Cloud groups are with the same names and descriptions as the original Operations for Applications custom groups.
-* All users from a custom group in Operations for Applications are added to the corresponding VMware Cloud group.
-* The service accounts from the custom groups in Operations for Applications **are not** added to any VMware Cloud group.
+* The corresponding VMware Cloud groups are with the same names and descriptions as the original Tanzu Observability custom groups.
+* All users from a custom group in Tanzu Observability are added to the corresponding VMware Cloud group.
+* The service accounts from the custom groups in Tanzu Observability **are not** added to any VMware Cloud group.
{% include important.html content="Currently, VMware Cloud services supports grouping only for user accounts."%}
-* If a custom group in Operations for Applications is assigned with roles, the corresponding VMware Cloud group is assigned with the corresponding VMware Cloud custom roles. See [How Are the Roles Migrated to VMware Cloud Services?](#how-are-the-roles-migrated-to-vmware-cloud-services).
+* If a custom group in Tanzu Observability is assigned with roles, the corresponding VMware Cloud group is assigned with the corresponding VMware Cloud custom roles. See [How Are the Roles Migrated to VMware Cloud Services?](#how-are-the-roles-migrated-to-vmware-cloud-services).
{% include tip.html content="From now on, users with the VMware Cloud **Organization Owner** and **Organization Administrator** roles can [manage the user groups](csp_users_roles.html#manage-user-groups) in the VMware Cloud Services Console."%}
### How Is the Everyone System Group Migrated?
-During the process of onboarding your Operations for Applications service to VMware Cloud services, for the **Everyone** system group in Operations for Applications, we create the corresponding **All Operations for Applications Users** group in your VMware Cloud organization running the service as follows:
+During the process of onboarding your Tanzu Observability service to VMware Cloud services, for the **Everyone** system group in Tanzu Observability, we create the corresponding **All Tanzu Observability Users** group in your VMware Cloud organization running the service as follows:
-* All current users are added to the **All Operations for Applications Users** VMware Cloud group.
+* All current users are added to the **All Tanzu Observability Users** VMware Cloud group.
{% include important.html content="New users will **no longer** be added automatically to this group."%}
-* The **All Operations for Applications Users** VMware Cloud group is assigned with the **All Operations for Applications Users** VMware Cloud custom role, which corresponds to the **Everyone** role in Operations for Applications. See [How Are the Roles Migrated to VMware Cloud Services?](#how-are-the-roles-migrated-to-vmware-cloud-services).
-* If the **Everyone** system group in Operations for Applications is assigned with custom roles, the **All Operations for Applications Users** VMware Cloud group is assigned with the corresponding VMware Cloud custom roles. See [How Are the Roles Migrated to VMware Cloud Services?](#how-are-the-roles-migrated-to-vmware-cloud-services).
-* In Operations for Applications, we continue to maintain the **Everyone** system group only as a local **internal** group that is automatically populated with all new users. This group has no roles and permissions.
+* The **All Tanzu Observability Users** VMware Cloud group is assigned with the **All Tanzu Observability Users** VMware Cloud custom role, which corresponds to the **Everyone** role in Tanzu Observability. See [How Are the Roles Migrated to VMware Cloud Services?](#how-are-the-roles-migrated-to-vmware-cloud-services).
+* If the **Everyone** system group in Tanzu Observability is assigned with custom roles, the **All Tanzu Observability Users** VMware Cloud group is assigned with the corresponding VMware Cloud custom roles. See [How Are the Roles Migrated to VMware Cloud Services?](#how-are-the-roles-migrated-to-vmware-cloud-services).
+* In Tanzu Observability, we continue to maintain the **Everyone** system group only as a local **internal** group that is automatically populated with all new users. This group has no roles and permissions.
-{% include tip.html content="From now on, it is up to you to add new users to the **All Operations for Applications Users** VMware Cloud group. The **Everyone** internal system group can be used only when managing [access to dashboards and alerts](csp_access.html), [metrics security policy rules](csp_metrics_security.html), and [ingestion policies](ingestion_policies.html)."%}
+{% include tip.html content="From now on, it is up to you to add new users to the **All Tanzu Observability Users** VMware Cloud group. The **Everyone** internal system group can be used only when managing [access to dashboards and alerts](csp_access.html), [metrics security policy rules](csp_metrics_security.html), and [ingestion policies](ingestion_policies.html)."%}
### What Happens with the Service Accounts System Group?
-During the process of onboarding your Operations for Applications service to VMware Cloud services, we **do not** migrate the **Service Accounts** system group.
+During the process of onboarding your Tanzu Observability service to VMware Cloud services, we **do not** migrate the **Service Accounts** system group.
{% include important.html content="Currently, VMware Cloud services supports grouping only for user accounts."%}
-* The permissions from the roles assigned to the **Service Accounts** system group in Operations for Applications are now directly assigned to the service accounts. See [What Happens with the Service Accounts?](#what-happens-with-the-service-accounts).
-* In Operations for Applications, we continue to maintain the **Service Accounts** system group only as a local **internal** group that is automatically populated with all [service accounts](csp_service_accounts.html) and [server to server OAuth apps](csp_server_to_server_apps.html) that have access to the service instance. This group has no roles and permissions.
+* The permissions from the roles assigned to the **Service Accounts** system group in Tanzu Observability are now directly assigned to the service accounts. See [What Happens with the Service Accounts?](#what-happens-with-the-service-accounts).
+* In Tanzu Observability, we continue to maintain the **Service Accounts** system group only as a local **internal** group that is automatically populated with all [service accounts](csp_service_accounts.html) and [server to server OAuth apps](csp_server_to_server_apps.html) that have access to the service instance. This group has no roles and permissions.
{% include tip.html content="From now on, the **Service Accounts** internal system group can be used only when managing [access to dashboards and alerts](csp_access.html), [metrics security policy rules](csp_metrics_security.html), and [ingestion policies](ingestion_policies.html)."%}
@@ -134,16 +134,16 @@ During the process of onboarding your Operations for Applications service to VMw
## How Are the Roles Migrated to VMware Cloud Services?
-During the process of onboarding your Operations for Applications service to VMware Cloud services, for each role in Operations for Applications, we create a corresponding [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) in your VMware Cloud organization running the service as follows:
+During the process of onboarding your Tanzu Observability service to VMware Cloud services, for each role in Tanzu Observability, we create a corresponding [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) in your VMware Cloud organization running the service as follows:
-* For each role that you have created in Operations for Applications, we create a corresponding VMware Cloud custom role with the same name and description.
-* For the **Everyone** role that is assigned to the **Everyone** system group in Operations for Applications, we create the **All Operations for Applications Users** VMware Cloud custom role. See [How Is the Everyone System Group Migrated?](#how-is-the-everyone-system-group-migrated).
-* For the **Service Accounts** role that is assigned to the **Service Accounts** system group in Operations for Applications, we **do not** create any VMware Cloud custom role, because this group is not migrated. See [What Happens with Service Accounts System Group?](#what-happens-with-the-service-accounts-system-group).
-* The corresponding VMware Cloud custom roles are assigned with the same [permissions](csp_permissions_overview.html) as the original roles in Operations for Applications. There are the following exceptions:
+* For each role that you have created in Tanzu Observability, we create a corresponding VMware Cloud custom role with the same name and description.
+* For the **Everyone** role that is assigned to the **Everyone** system group in Tanzu Observability, we create the **All Tanzu Observability Users** VMware Cloud custom role. See [How Is the Everyone System Group Migrated?](#how-is-the-everyone-system-group-migrated).
+* For the **Service Accounts** role that is assigned to the **Service Accounts** system group in Tanzu Observability, we **do not** create any VMware Cloud custom role, because this group is not migrated. See [What Happens with Service Accounts System Group?](#what-happens-with-the-service-accounts-system-group).
+* The corresponding VMware Cloud custom roles are assigned with the same [permissions](csp_permissions_overview.html) as the original roles in Tanzu Observability. There are the following exceptions:
- - The **Accounts** permission in Operations for Applications is replaced by the **Admin** Operations for Applications permission in VMware Cloud services. In addition, the users with that permission are assigned with the [VMware Cloud **Organization Administrator** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role).
- - The **API Tokens** permission in Operations for Applications **is not** replaced by any permission in VMware Cloud services. This permission does not exist in VMware Cloud services, because each user can manage their own VMware Cloud services API tokens.
- - The **SAML IdP Admin** permission in Operations for Applications **is not** replaced with by permission in VMware Cloud services. This permission does not exist in VMware Cloud services, because the VMware Cloud **Organization Owner** initiates enterprise federation for your corporate domain and assigns an **Enterprise Administrator**.
+ - The **Accounts** permission in Tanzu Observability is replaced by the **Admin** Tanzu Observability permission in VMware Cloud services. In addition, the users with that permission are assigned with the [VMware Cloud **Organization Administrator** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role).
+ - The **API Tokens** permission in Tanzu Observability **is not** replaced by any permission in VMware Cloud services. This permission does not exist in VMware Cloud services, because each user can manage their own VMware Cloud services API tokens.
+ - The **SAML IdP Admin** permission in Tanzu Observability **is not** replaced with by permission in VMware Cloud services. This permission does not exist in VMware Cloud services, because the VMware Cloud **Organization Owner** initiates enterprise federation for your corporate domain and assigns an **Enterprise Administrator**.
For details, see the [permissions differences](csp-differences-by-area.html#permissions).
@@ -157,26 +157,26 @@ During the process of onboarding your Operations for Applications service to VMw
## What Happens with the Service Accounts?
-During the process of onboarding your Operations for Applications service to VMware Cloud services, the service accounts **are not** migrated to VMware Cloud services, because VMware Cloud services supports [server to server OAuth apps](csp_server_to_server_apps.html), which are equivalent to the services accounts in Operations for Applications.
+During the process of onboarding your Tanzu Observability service to VMware Cloud services, the service accounts **are not** migrated to VMware Cloud services, because VMware Cloud services supports [server to server OAuth apps](csp_server_to_server_apps.html), which are equivalent to the services accounts in Tanzu Observability.
-{% include warning.html content="The usage of service accounts in Operations for Applications on VMware Cloud services is **restricted** to support only a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Operations for Applications API tokens. We are in the process of updating all of our integrations to authenticate with VMware Cloud services access tokens. Service accounts and Operations for Applications API tokens will be deprecated in the future."%}
+{% include warning.html content="The usage of service accounts in Tanzu Observability on VMware Cloud services is **restricted** to support only a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Tanzu Observability API tokens. We are in the process of updating all of our integrations to authenticate with VMware Cloud services access tokens. Service accounts and Tanzu Observability API tokens will be deprecated in the future."%}
-For backward compatibility, all of your service accounts are **preserved** in Operations for Applications as follows:
+For backward compatibility, all of your service accounts are **preserved** in Tanzu Observability as follows:
* The service accounts no longer belong to groups, because the groups management is migrated to VMware Cloud services.
* The service accounts no longer have roles, because the roles management is migrated to VMware Cloud services.
* The service accounts are assigned with their existing permissions, including the permissions that they have inherited from roles and group roles. Exceptions are the **API Tokens** and **SAML IdP Admin** permissions, which no longer exist.
- {% include note.html content="The **Accounts** permission in Operations for Applications corresponds to the [**Admin** Operations for Applications permission](csp_permissions_overview.html) in VMware Cloud services."%}
-* All service accounts still belong to the **Service Accounts** system group, which is now only an **internal** Operations for Applications group that is automatically populated with all [service accounts](csp_service_accounts.html) and [server to server OAuth apps](csp_server_to_server_apps.html) that have access to the service instance. This group has no roles and permissions.
+ {% include note.html content="The **Accounts** permission in Tanzu Observability corresponds to the [**Admin** Tanzu Observability permission](csp_permissions_overview.html) in VMware Cloud services."%}
+* All service accounts still belong to the **Service Accounts** system group, which is now only an **internal** Tanzu Observability group that is automatically populated with all [service accounts](csp_service_accounts.html) and [server to server OAuth apps](csp_server_to_server_apps.html) that have access to the service instance. This group has no roles and permissions.
-You should incrementally [replace](#how-to-replace-a-service-account-with-a-server-to-server-app) your service accounts in Operations for Applications with server to server OAuth apps in VMware Cloud services.
+You should incrementally [replace](#how-to-replace-a-service-account-with-a-server-to-server-app) your service accounts in Tanzu Observability with server to server OAuth apps in VMware Cloud services.
-{% include tip.html content="From now on, users with the VMware Cloud **Organization Owner**, **Organization Administrator**, or **Organization Member** with **Developer** roles can [manage server to server apps](csp_server_to_server_apps.html) in the VMware Cloud Services Console. Users with the **Admin** service role can [manage the service accounts](csp_service_accounts.html) in Operations for Applications. The **Service Accounts** internal system group can be used only when managing [access to dashboards and alerts](csp_access.html), [metrics security policy rules](csp_metrics_security.html), and [ingestion policies](ingestion_policies.html)."%}
+{% include tip.html content="From now on, users with the VMware Cloud **Organization Owner**, **Organization Administrator**, or **Organization Member** with **Developer** roles can [manage server to server apps](csp_server_to_server_apps.html) in the VMware Cloud Services Console. Users with the **Admin** service role can [manage the service accounts](csp_service_accounts.html) in Tanzu Observability. The **Service Accounts** internal system group can be used only when managing [access to dashboards and alerts](csp_access.html), [metrics security policy rules](csp_metrics_security.html), and [ingestion policies](ingestion_policies.html)."%}
### How to Replace a Service Account with a Server to Server App?
-Service accounts authenticate with Operations for Applications API tokens, while server to server OAuth apps authenticate with the more secure VMware Cloud services access tokens. Service accounts are supported for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) but will be deprecated in the future.
+Service accounts authenticate with Tanzu Observability API tokens, while server to server OAuth apps authenticate with the more secure VMware Cloud services access tokens. Service accounts are supported for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) but will be deprecated in the future.
@@ -188,7 +188,7 @@ Service accounts authenticate with Operations for Applications API tokens, while
-After onboarding to VMware Cloud services, you should incrementally replace your service accounts in Operations for Applications with server to server OAuth apps in VMware Cloud services.
+After onboarding to VMware Cloud services, you should incrementally replace your service accounts in Tanzu Observability with server to server OAuth apps in VMware Cloud services.
The flowchart on the right shows the overall process for creating a server to server OAuth app and replacing a service account with it.
@@ -225,14 +225,14 @@ After onboarding to VMware Cloud services, you should incrementally replace your
Required for service access. Assign the Operations for Applications service roles that correspond to the permissions of the service account that you want to replace.
-
If you already assigned a custom role, you must assign at least the Viewer Operations for Applications service role.
+
Required for service access. Assign the Tanzu Observability service roles that correspond to the permissions of the service account that you want to replace.
+
If you already assigned a custom role, you must assign at least the Viewer Tanzu Observability service role.
@@ -252,40 +252,40 @@ After onboarding to VMware Cloud services, you should incrementally replace your
-## What Happens with the Operations for Applications API Tokens?
+## What Happens with the Tanzu Observability API Tokens?
-During the process of onboarding your Operations for Applications service to VMware Cloud services, the Operations for Applications API tokens **are not** migrated to VMware Cloud services, because Operations for Applications on VMware Cloud services supports authentication with:
+During the process of onboarding your Tanzu Observability service to VMware Cloud services, the Tanzu Observability API tokens **are not** migrated to VMware Cloud services, because Tanzu Observability on VMware Cloud services supports authentication with:
* VMware Cloud services API tokens associated with user accounts.
-* Server to server OAuth apps credentials, that is, app ID and app secret. The server to server OAuth app must belong to the organization that is running the Operations for Applications service.
+* Server to server OAuth apps credentials, that is, app ID and app secret. The server to server OAuth app must belong to the organization that is running the Tanzu Observability service.
You must exchange a VMware Cloud services API token or the credentials (ID and secret) of server to server OAuth app for a VMware Cloud services **access token**.
-For backward compatibility, all of your API tokens are **preserved** in Operations for Applications as follows:
+For backward compatibility, all of your API tokens are **preserved** in Tanzu Observability as follows:
-* The Operations for Applications API tokens associated with user accounts are **no longer** editable. The users can still use, view, and revoke their Operations for Applications API tokens until they expire, but they **cannot** generate new ones.
-* The Operations for Applications API tokens associated with service accounts are editable, because we still support them for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens).
+* The Tanzu Observability API tokens associated with user accounts are **no longer** editable. The users can still use, view, and revoke their Tanzu Observability API tokens until they expire, but they **cannot** generate new ones.
+* The Tanzu Observability API tokens associated with service accounts are editable, because we still support them for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens).
-You should incrementally [replace](#how-to-replace-an-operations-for-applications-api-token-with-a-vmware-cloud-services-access-token) your Operations for Applications API tokens with VMware Cloud services API tokens and server to server OAuth apps.
+You should incrementally [replace](#how-to-replace-an-operations-for-applications-api-token-with-a-vmware-cloud-services-access-token) your Tanzu Observability API tokens with VMware Cloud services API tokens and server to server OAuth apps.
{% include tip.html content="From now on, all users must generate VMware Cloud services API tokens for their accounts and exchange them for access tokens. Users with the VMware Cloud **Organization Owner**, **Organization Administrator**, or **Organization Member** with **Developer** roles can create server to server OAuth apps and exchange the app credentials for access tokens."%}
-### How to View and Manage the Operations for Applications API Tokens?
+### How to View and Manage the Tanzu Observability API Tokens?
-Users with the **Admin** Operations for Applications service role can [manage](csp_api_tokens.html#manage-the-operations-for-applications-api-tokens-in-your-service-instance) the Operations for Applications API tokens in the service instance.
+Users with the **Admin** Tanzu Observability service role can [manage](csp_api_tokens.html#manage-the-operations-for-applications-api-tokens-in-your-service-instance) the Tanzu Observability API tokens in the service instance.
-Each user can view and revoke their own Operations for Applications API tokens:
+Each user can view and revoke their own Tanzu Observability API tokens:
1. Log in to your service instance.
1. From the gear icon on the toolbar, select your username.
-1. Click the **API Access** tab and view all your Operations for Applications API tokens.
+1. Click the **API Access** tab and view all your Tanzu Observability API tokens.
1. To revoke a token, click the **Revoke** button for the token.
If you run a script that uses a revoked token, the script returns an authorization error.
-### How to Replace an Operations for Applications API Token with a VMware Cloud Services Access Token?
+### How to Replace a Tanzu Observability API Token with a VMware Cloud Services Access Token?
-It's recommended to use Operations for Applications API tokens only for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens). We will update these integrations to authenticate with VMware Cloud services access tokens in a future release.
+It's recommended to use Tanzu Observability API tokens only for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens). We will update these integrations to authenticate with VMware Cloud services access tokens in a future release.
@@ -293,32 +293,32 @@ It's recommended to use Operations for Applications API tokens only for a [limit
-You should incrementally replace your Operations for Applications API tokens with the more secure VMware Cloud services access tokens.
+You should incrementally replace your Tanzu Observability API tokens with the more secure VMware Cloud services access tokens.
-To replace an Operations for Applications API token associated with a service account, you must replace the service account with a server to server OAuth app. See [How to Replace a Service Account with a Server to Server App?](#how-to-replace-a-service-account-with-a-server-to-server-app).
+To replace a Tanzu Observability API token associated with a service account, you must replace the service account with a server to server OAuth app. See [How to Replace a Service Account with a Server to Server App?](#how-to-replace-a-service-account-with-a-server-to-server-app).
-The flowchart on the right shows the overall process for replacing an Operations for Applications API token with a VMware Cloud services API token.
+The flowchart on the right shows the overall process for replacing a Tanzu Observability API token with a VMware Cloud services API token.
-
+
-To replace an Operations for Applications API token associated with your user account:
+To replace a Tanzu Observability API token associated with your user account:
1. Log in to the VMware Cloud Services Console.
1. Generate an API token. See [How do I generate API tokens](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-E2A3B1C1-E9AD-4B00-A6B6-88D31FCDDF7C.html) in the VMware Cloud services documentation.
- - For the name of the VMware Cloud services API token, you can enter the name of the Operations for Applications API token that you want to replace.
+ - For the name of the VMware Cloud services API token, you can enter the name of the Tanzu Observability API token that you want to replace.
- For the time to live (TTL) of the VMware Cloud services API token, you can configure a value from several minutes to several months, or never expire. This value defines the period in which the API token should be renewed.
The TTL of the access tokens that will be issued to that API token is 30 minutes and is not configurable.
- For the scopes of the API token, you must configure the minimum portion of your roles:
- {% include note.html content="Till now, the Operations for Applications API tokens inherited all your permissions and roles. Now, you can set the VMware Cloud services API token with a subset of the roles that you own."%}
+ {% include note.html content="Till now, the Tanzu Observability API tokens inherited all your permissions and roles. Now, you can set the VMware Cloud services API token with a subset of the roles that you own."%}
@@ -346,15 +346,15 @@ To replace an Operations for Applications API token associated with your user ac
Service Roles
Required for service access.
-
If you already assigned a custom role, you must assign at least the Viewer Operations for Applications service role.
+
If you already assigned a custom role, you must assign at least the Viewer Tanzu Observability service role.
-1. Reconfigure your scripts, API calls, or proxies to exchange the newly generated VMware Cloud services API token for an access token, instead of using the Operations for Applications API token.
+1. Reconfigure your scripts, API calls, or proxies to exchange the newly generated VMware Cloud services API token for an access token, instead of using the Tanzu Observability API token.
{% include important.html content="The TTL of the access tokens associated with user accounts is 30 minutes. Make sure that your script renews the access token periodically before it expires. The Wavefront proxy does this automatically. "%}
-1. [Revoke](#how-to-view-and-manage-the-operations-for-applications-api-tokens) the Operations for Applications API token that you replaced.
+1. [Revoke](#how-to-view-and-manage-the-operations-for-applications-api-tokens) the Tanzu Observability API token that you replaced.
@@ -364,11 +364,11 @@ To replace an Operations for Applications API token associated with your user ac
## What Happens with the Wavefront Proxies?
-During the process of onboarding your Operations for Applications service to VMware Cloud services, all of the existing Wavefront proxies are **preserved** with their existing Operations for Applications API tokens.
+During the process of onboarding your Tanzu Observability service to VMware Cloud services, all of the existing Wavefront proxies are **preserved** with their existing Tanzu Observability API tokens.
You should incrementally [replace](#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy) the tokens of your proxies to authenticate with the more secure VMware Cloud services access tokens.
-{% include tip.html content="From now on, the users with the **Proxies** service role can create and manage the proxies in your Operations for Applications service. New proxies must authenticate with VMware Cloud services access tokens unless used for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Operations for Applications API tokens."%}
+{% include tip.html content="From now on, the users with the **Proxies** service role can create and manage the proxies in your Tanzu Observability service. New proxies must authenticate with VMware Cloud services access tokens unless used for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Tanzu Observability API tokens."%}
### How to Replace the Operations for Application API Token of a Wavefront Proxy?
@@ -395,7 +395,7 @@ You should incrementally [replace](#how-to-replace-the-operations-for-applicatio
```
cspAPIToken=
```
-1. [Revoke](#how-to-view-and-manage-the-operations-for-applications-api-tokens) the Operations for Applications API token that you replaced.
+1. [Revoke](#how-to-view-and-manage-the-operations-for-applications-api-tokens) the Tanzu Observability API token that you replaced.
@@ -405,11 +405,11 @@ You should incrementally [replace](#how-to-replace-the-operations-for-applicatio
## What Happens with the Integrations?
-During the process of onboarding your Operations for Applications service to VMware Cloud services, all of the existing integrations are **preserved** and continue to operate using proxy authentication with Operations for Applications API tokens.
+During the process of onboarding your Tanzu Observability service to VMware Cloud services, all of the existing integrations are **preserved** and continue to operate using proxy authentication with Tanzu Observability API tokens.
You should incrementally [replace](#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy) the proxy tokens of your [integrations](integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens) that are updated to use proxy authentication with the more secure VMware Cloud services access token.
-{% include tip.html content="From now on, the users with the **Proxies** and **Integrations** service roles can set up integrations in your Operations for Applications service. New integrations must use proxy authentication with VMware Cloud services access tokens except for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Operations for Applications API tokens."%}
+{% include tip.html content="From now on, the users with the **Proxies** and **Integrations** service roles can set up integrations in your Tanzu Observability service. New integrations must use proxy authentication with VMware Cloud services access tokens except for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Tanzu Observability API tokens."%}
diff --git a/pages/doc/csp_subscription_types.md b/pages/doc/csp_subscription_types.md
index 600123cca..828e5572b 100644
--- a/pages/doc/csp_subscription_types.md
+++ b/pages/doc/csp_subscription_types.md
@@ -4,20 +4,20 @@ keywords:
tags: [introduction]
sidebar: doc_sidebar
permalink: subscriptions-differences.html
-summary: Learn about the VMware Aria Operations for Applications subscription types and the advantages of VMware Cloud services subscriptions over original subscriptions.
+summary: Learn about the Tanzu Observability subscription types and the advantages of VMware Cloud services subscriptions over original subscriptions.
---
-Operations for Applications subscriptions are two types: original subscriptions and VMware Cloud services subscriptions.
+Tanzu Observability subscriptions are two types: original subscriptions and VMware Cloud services subscriptions.
## Why the Two Subscription Types Differ?
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Operations for Applications subscriptions **onboarded** to the [VMware Cloud services platform](https://console.cloud.vmware.com/) and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services.
+Starting July 3, 2023, Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the [VMware Cloud services platform](https://console.cloud.vmware.com/) and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services.
-Starting September 20, 2023, all [**new trial**](start_trial.html) instances of Operations for Applications are **onboarded** to VMware Cloud services.
+Starting September 20, 2023, all [**new trial**](start_trial.html) instances of Tanzu Observability are **onboarded** to VMware Cloud services.
{% include note.html content="We will support both **original** and **onboarded** subscriptions until all original subscriptions are onboarded to VMware Cloud services." %}
-VMware Cloud services provides single sign-on (SSO) and identity access management (IAM) to your entire VMware Cloud services portfolio across hybrid and native public clouds, including Operations for Applications. Therefore, there are differences in the experience for VMware Cloud services subscribers and original subscribers.
+VMware Cloud services provides single sign-on (SSO) and identity access management (IAM) to your entire VMware Cloud services portfolio across hybrid and native public clouds, including Tanzu Observability. Therefore, there are differences in the experience for VMware Cloud services subscribers and original subscribers.
## Advantages of VMware Cloud Services Subscriptions Over Original Subscriptions
@@ -33,7 +33,7 @@ VMware Cloud services provides single sign-on (SSO) and identity access manageme
You can also configure any other SAML 2.0 compliant third-party IdP that is not part of the list above. See [Configure the identity provider](https://docs.vmware.com/en/VMware-Cloud-services/services/setting-up-enterprise-federation-cloud-services/GUID-320CDE08-FD8F-4540-BB19-BE9647F31075.html) in the VMware Cloud services documentation.
* **Enterprise Groups Synchronization**: The enterprise groups from your federated corporate domain are available for you to assign them roles, including default roles. In addition, you can nest an enterprise group into a custom group.
-* **Centralized Authorization with Role-Based Access Control**: The VMware Cloud Services Console provides access management for your entire VMware Cloud services portfolio. It includes organization roles, service-specific roles, and custom roles, which can be assigned to users, API tokens, and sever to server apps (which correspond to service accounts in Operations for Applications).
+* **Centralized Authorization with Role-Based Access Control**: The VMware Cloud Services Console provides access management for your entire VMware Cloud services portfolio. It includes organization roles, service-specific roles, and custom roles, which can be assigned to users, API tokens, and sever to server apps (which correspond to service accounts in Tanzu Observability).
* **Improved Security**:
* VMware Cloud services supports authentication polices for user access, such as multi-factor authentication, IP authentication preferences, and user access at domain level.
* An API token can be assigned with a subset of the roles that its associated user owns.
diff --git a/pages/doc/csp_ui_differences.md b/pages/doc/csp_ui_differences.md
index 06f6efbe6..ab9fd73f6 100644
--- a/pages/doc/csp_ui_differences.md
+++ b/pages/doc/csp_ui_differences.md
@@ -4,10 +4,10 @@ keywords:
tags: [introduction]
sidebar: doc_sidebar
permalink: csp-ui-differences.html
-summary: Learn about the differences in the UI of VMware Aria Operations for Applications original subscriptions and VMware Cloud services subscriptions.
+summary: Learn about the differences in the UI of Tanzu Observability original subscriptions and VMware Cloud services subscriptions.
---
-Operations for Applications subscriptions are two types: original subscriptions and VMware Cloud services subscriptions.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) subscriptions are two types: original subscriptions and VMware Cloud services subscriptions.
## Menu Bar
@@ -17,14 +17,14 @@ The menu bar differs, because the VMware Cloud services toolbar is added to the
From the VMware Cloud services toolbar, you can:
- 1. Switch between tenants (service instances) in a multi-tenant Operations for Applications environment.
+ 1. Switch between tenants (service instances) in a multi-tenant Tanzu Observability environment.
1. See notifications from VMware Cloud services.
1. Manage your VMware Cloud services account and switch to other organizations.
1. Go to the VMware Cloud Services Console and switch to other service subscriptions.
## Own User Account Settings
-When viewing their own user account settings in the Operations for Applications UI, VMware Cloud services subscribers do not have the **Groups, Roles & Permissions** and the **API Access** tabs (1) and can no longer change their password from the Operations for Applications UI (2), because this is done from the VMware Cloud Services Console.
+When viewing their own user account settings in the Tanzu Observability UI, VMware Cloud services subscribers do not have the **Groups, Roles & Permissions** and the **API Access** tabs (1) and can no longer change their password from the Tanzu Observability UI (2), because this is done from the VMware Cloud Services Console.
@@ -54,8 +54,8 @@ Most of the identity and access management tasks for VMware Cloud services subsc
- 1. The **User Accounts**, **Groups**, and **Roles** tabs are missing, because the management of users, groups, and roles is done from the VMware Cloud Services Console. By using the **Accounts** menu item, the VMware Cloud services subscribers can manage only service accounts and the Operations for Applications API tokens associated with them.
- 1. VMware Cloud services subscribers cannot assign roles to service accounts and also can’t add them to groups. For VMware Cloud services subscriptions, service accounts are local entities in Operations for Applications, while roles and groups management is centralized in VMware Cloud services. VMware Cloud services subscribers can grant only permissions to service accounts.
+ 1. The **User Accounts**, **Groups**, and **Roles** tabs are missing, because the management of users, groups, and roles is done from the VMware Cloud Services Console. By using the **Accounts** menu item, the VMware Cloud services subscribers can manage only service accounts and the Tanzu Observability API tokens associated with them.
+ 1. VMware Cloud services subscribers cannot assign roles to service accounts and also can’t add them to groups. For VMware Cloud services subscriptions, service accounts are local entities in Tanzu Observability, while roles and groups management is centralized in VMware Cloud services. VMware Cloud services subscribers can grant only permissions to service accounts.
1. Filtering the service accounts can be done only by permissions, because they don’t have roles and don’t belong to groups.
## Super Admin Page
@@ -66,7 +66,7 @@ The **Super Admin** page is replaced with **Orphaned Objects**, because Super Ad
## Add New Wavefront Proxy Page
-When adding a Wavefront proxy, VMware Cloud services subscribers have two options for the proxy authorization to Operations for Applications. They can configure the proxy with server to server OAuth app credentials or with a VMware Cloud services API token.
+When adding a Wavefront proxy, VMware Cloud services subscribers have two options for the proxy authorization to Tanzu Observability. They can configure the proxy with server to server OAuth app credentials or with a VMware Cloud services API token.
diff --git a/pages/doc/delta_counters.md b/pages/doc/delta_counters.md
index 37f8a9e27..b18e68887 100644
--- a/pages/doc/delta_counters.md
+++ b/pages/doc/delta_counters.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: delta_counters.html
summary: Learn when and how to use cumulative counters and delta counters.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports [several types of metrics](metric_types.html), including 2 kinds of counters.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports [several types of metrics](metric_types.html), including 2 kinds of counters.
* **Cumulative counters** (usually called **counters** in this doc set) monotonically increasing counters. They're useful for aggregating metric information such as the number of hits on a web page, how many users log into a portal, etc. They're usually used with `rate()` or a similar function.
* **Delta counters** (sometimes called periodic counters) measure the **change** since a metric was last recorded. For example, metrics for request count could be delta counters. Each value records how many requests were received since the last data point was recorded.
@@ -44,7 +44,7 @@ It often makes sense to collect both counter metrics and delta counter metrics -
The following illustration contrasts cumulative counters and delta counters with a simple example:
-* Error data are being sent to Operations for Applications. 5 errors in the first minute, 17 in the second, and 8 in the third.
+* Error data are being sent to Tanzu Observability. 5 errors in the first minute, 17 in the second, and 8 in the third.
* The top row shows cumulative counter behavior. In many cases, the data actually come in as cumulative counters:
- The running total of the errors (5, 22, 30) is ingested and stored.
- The `ts()` query shows a chart with values increasing over time.
@@ -78,7 +78,7 @@ For more on delta counter use cases, see the blog [Monitoring Apps in the Server
AWS Lambda allows you to specify functions that you want to run -- and then you can stop worrying about the function execution. For example, assume that you want to generate a thumbnail each time any of your users uploads images to a folder. You can write a Lambda function that monitors the folders and takes care of thumbnail generation for you. AWS runs as many of the functions as necessary to handle the current workload, and you don't have to worry about scaling up or down.
-Delta counters make monitoring easy for this use case. Operations for Applications aggregates the metrics that come from different invocations of the same function. The AWS Lambda Functions integration comes preconfigured with several delta counters and a gauge for standard metrics. In addition, you can monitor custom business metrics by using our SDK to define a wrapper for your AWS Lambda function. See the [AWS Lambda Functions Integration](aws-lambda-functions.html) for setup instructions.
+Delta counters make monitoring easy for this use case. Tanzu Observability aggregates the metrics that come from different invocations of the same function. The AWS Lambda Functions integration comes preconfigured with several delta counters and a gauge for standard metrics. In addition, you can monitor custom business metrics by using our SDK to define a wrapper for your AWS Lambda function. See the [AWS Lambda Functions Integration](aws-lambda-functions.html) for setup instructions.
## Using Delta Counters
@@ -141,11 +141,11 @@ You can use our SDKs to make your metric a delta counter.
We support the following [proxy configuration properties](proxies_configuring.html#configuration-properties) with delta counters.
- **deltaCounterPorts**: Comma-separated list of ports that accept only delta counter data.
-- **deltaCounterAggregationInterval**: Time that the proxy spends aggregating data before sending them to Operations for Applications. Default is 30 seconds.
+- **deltaCounterAggregationInterval**: Time that the proxy spends aggregating data before sending them to Tanzu Observability. Default is 30 seconds.
### Delta Prefix
-If you want to send metrics as delta counters to the Wavefront proxy or directly to Operations for Applications, prefix each metric with a delta (∆) character, as shown in the following [sample code snippet](https://github.com/wavefrontHQ/wavefront-pyformance/blob/master/wavefront_pyformance/delta.py).
+If you want to send metrics as delta counters to the Wavefront proxy or directly to Tanzu Observability, prefix each metric with a delta (∆) character, as shown in the following [sample code snippet](https://github.com/wavefrontHQ/wavefront-pyformance/blob/master/wavefront_pyformance/delta.py).
```
DELTA_PREFIX = u"\u2206"
diff --git a/pages/doc/derived_metrics.md b/pages/doc/derived_metrics.md
index aa938225b..682355fa0 100644
--- a/pages/doc/derived_metrics.md
+++ b/pages/doc/derived_metrics.md
@@ -7,7 +7,7 @@ permalink: derived_metrics.html
summary: Learn how to save a query so it runs once a minute, and how to use the derived metric elsewhere.
---
-Use derived metrics to run a query and ingest it back into VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront). All users can then use the result of the query, that is, the derived metric, in their queries.
+Use derived metrics to run a query and ingest it back into Tanzu Observability (formerly known as VMware Aria Operations for Applications). All users can then use the result of the query, that is, the derived metric, in their queries.
You can create a derived metric from a time series metric or a histogram.
@@ -19,7 +19,7 @@ Derived metrics created and metrics points scanned apply to your data ingestion
{{site.data.alerts.note}}
- The minimum reporting interval for a derived metric is 1 minute. If the query that is used in the derived metric reports data points more than once within a minute, Operations for Applications summarizes it using the mean() aggregation and aligns it to 1 minute time buckets.
+ The minimum reporting interval for a derived metric is 1 minute. If the query that is used in the derived metric reports data points more than once within a minute, Tanzu Observability summarizes it using the mean() aggregation and aligns it to 1 minute time buckets.
Obsolete metrics are removed from derived metrics.
@@ -69,10 +69,10 @@ You can reduce the data scan rate in a similar way using derived metrics.
You can customize how often the derived metric executes, and how many minutes of results we include.
-* **Execute the query every N minutes**: By default, Operations for Applications executes the derived metric query every 1 minute. Use this setting to adjust the execution interval.
+* **Execute the query every N minutes**: By default, Tanzu Observability executes the derived metric query every 1 minute. Use this setting to adjust the execution interval.
-* **Include results in the last N minutes**: By default, Operations for Applications uses the last 5 minutes as the time window for the derived metrics query to account for possible delays in the upstream metric pipeline. The results of the query:
- - Are ingested back into Operations for Applications,
+* **Include results in the last N minutes**: By default, Tanzu Observability uses the last 5 minutes as the time window for the derived metrics query to account for possible delays in the upstream metric pipeline. The results of the query:
+ - Are ingested back into Tanzu Observability,
- Overwrite existing data in the last N minutes for the derived metric. You can adjust the time window of the query with this setting.
{% include note.html content="We recommend that the **Includes...** setting is always larger than the **Execute** setting." %}
@@ -92,4 +92,4 @@ To create a derived metric:
## Learn More
-See the KB article [Migrating Objects or Data Between Environments](https://vmwaoa.zendesk.com/hc/en-us/articles/21153594484493-Migrating-Objects-or-Data-Between-VMware-Aria-Operations-for-Applications-Environments) if your company has several Operations for Applications service instances.
+See the KB article [Migrating Objects or Data Between Environments](https://vmwaoa.zendesk.com/hc/en-us/articles/21153594484493-Migrating-Objects-or-Data-Between-VMware-Aria-Operations-for-Applications-Environments) if your company has several Tanzu Observability service instances.
diff --git a/pages/doc/direct_ingestion.md b/pages/doc/direct_ingestion.md
index 076d74953..92598013d 100644
--- a/pages/doc/direct_ingestion.md
+++ b/pages/doc/direct_ingestion.md
@@ -7,19 +7,19 @@ permalink: direct_ingestion.html
summary: Learn how to send data directly to your service instance.
---
-You can send data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) directly (by using direct ingestion) or by using the Wavefront proxy.
+You can send data to Tanzu Observability (formerly known as VMware Aria Operations for Applications) directly (by using direct ingestion) or by using the Wavefront proxy.
* **Direct data ingestion** can be the best approach at the beginning only for testing purposes and during a POC. In production environments, the best way to send data is by using a Wavefront proxy.
{% include note.html content="You must have the [**Direct Data Ingestion** permission](permissions_overview.html) to perform direct data ingestion." %}
-* In larger environments, send data to the Operations for Applications service by taking advantage of **proxy benefits**:
+* In larger environments, send data to the Tanzu Observability service by taking advantage of **proxy benefits**:
- {% include note.html content="In production environments, you must send data to the Operations for Applications service by installing a Wavefront proxy. Direct data ingestion is suitable only for test, trial, and POC environments and is not supported for production environments." %}
+ {% include note.html content="In production environments, you must send data to the Tanzu Observability service by installing a Wavefront proxy. Direct data ingestion is suitable only for test, trial, and POC environments and is not supported for production environments." %}
* **Prevent data loss, optimize network bandwidth** – The proxy buffers and manages data traffic. Even if there’s a connectivity problem, you don’t lose data points.
- * **Simple firewall configuration** – The proxy receives metrics from many agents on different hosts and forwards those metrics to the Operations for Applications service. You don’t need to open internet access for each of the agents.
- * **Enrich or filter data** – You can set up the proxy preprocessor to filter data before it’s sent to the Operations for Applications service.
+ * **Simple firewall configuration** – The proxy receives metrics from many agents on different hosts and forwards those metrics to the Tanzu Observability service. You don’t need to open internet access for each of the agents.
+ * **Enrich or filter data** – You can set up the proxy preprocessor to filter data before it’s sent to the Tanzu Observability service.
* **Examine bottlenecks** – Each proxy generates its own metrics. You can [learn about incoming and outgoing data](monitoring_proxies.html) in the individual proxy dashboards and the **Operations for Applications Service and Proxy Data** dashboard.
@@ -27,26 +27,26 @@ You can send data to VMware Aria Operations for Applications (formerly known as
## Background
-Most customers set up their environment so that the host, application, or custom code sends metrics to a [Wavefront proxy](proxies.html) installed in their environment. The proxy forwards metrics to the Operations for Applications service. In production environments, two proxies behind a load balancer guarantee availability and prevent data loss.
+Most customers set up their environment so that the host, application, or custom code sends metrics to a [Wavefront proxy](proxies.html) installed in their environment. The proxy forwards metrics to the Tanzu Observability service. In production environments, two proxies behind a load balancer guarantee availability and prevent data loss.
-Because some customers wanted to send data directly to the Operations for Applications service, we made this functionality available.
+Because some customers wanted to send data directly to the Tanzu Observability service, we made this functionality available.
## Direct Ingestion Example Commands
-The following examples illustrate how to send data directly to the Operations for Applications service.
+The following examples illustrate how to send data directly to the Tanzu Observability service.
* A token is required. Referred to as `` in the examples. Depends on your [subscription type](subscriptions-differences.html):
- For VMware Cloud services subscriptions, a VMware Cloud services access token is required. You can retrieve an access token by exchanging your [user API token](csp_users_account_managing.html#generate-an-api-token) or [server to server OAuth credentials](csp_server_to_server_apps.html#how-server-to-server-apps-work).
- For original subscriptions, an [API token](api_tokens.html) is required. The API token can be associated to a user account or service account.
-* You must know your Operations for Applications service instance name. This doc page uses `mydomain.wavefront.com`.
-* Currently, direct ingestion supports only [Operations for Applications Data Format](wavefront_data_format.html), which is named `wavefront`. If you don't specify `f=wavefront`, we still use that format.
+* You must know your Tanzu Observability service instance name. This doc page uses `mydomain.wavefront.com`.
+* Currently, direct ingestion supports only [Tanzu Observability Data Format](wavefront_data_format.html), which is named `wavefront`. If you don't specify `f=wavefront`, we still use that format.
### Multiple Data Points
-Assume `wavefront.txt` contains 1 or more lines in the Operations for Applications data format. You can send the data to the Operations for Applications service like this:
+Assume `wavefront.txt` contains 1 or more lines in the Tanzu Observability data format. You can send the data to the Tanzu Observability service like this:
```
cat wavefront.txt | curl -H "Authorization: Bearer " -F file=@- https://mydomain.wavefront.com/report
@@ -61,7 +61,7 @@ echo "hello.world 1 source=" | curl -H "Authorization: Bearer " -
### Histogram Distribution
-You can perform direct ingestion of [histogram distributions](proxies_histograms.html#sending-histogram-distributions) in histogram data format. You cannot perform direct ingestion of histogram data in Operations for Applications data format.
+You can perform direct ingestion of [histogram distributions](proxies_histograms.html#sending-histogram-distributions) in histogram data format. You cannot perform direct ingestion of histogram data in Tanzu Observability data format.
Here's a simple example:
```
@@ -74,7 +74,7 @@ Notes:
* Include `f=histogram` at the end of the `--data` argument to ensure the input is treated as a histogram distribution.
### Trace Data (Spans)
-You can perform direct ingestion of trace data in Operations for Applications [span format](trace_data_details.html#spans).
+You can perform direct ingestion of trace data in Tanzu Observability [span format](trace_data_details.html#spans).
Here's a simple example:
```
@@ -83,7 +83,7 @@ echo "getAllUsers source=localhost traceId=7b3bf470-9456-11e8-9eb6-529269fb1459
Notes:
* In the example, you:
- - Specify the span using [Operations for Applications span format](trace_data_details.html#operations-for-applications-span-format).
+ - Specify the span using [Tanzu Observability span format](trace_data_details.html#tanzu-observability-span-format).
- Include `f=trace` at the end of the `--data` argument to ensure the input is treated as trace data.
- Include `cluster=none` and `shard=none` for a span that does not have values for the `cluster` and `shard` span tags.
- Replace `` and `` with numbers indicating the span's start time and duration.
@@ -98,19 +98,19 @@ Direct ingestion has some benefits, but also some limitations:
* No rate limiting
* No block list or allow list
* No preprocessor
-* Only Operations for Applications data format is currently supported. No support for OpenTSB, JSON, and Pickle
+* Only Tanzu Observability data format is currently supported. No support for OpenTSB, JSON, and Pickle
* No support for log ingestion
-When you use direct ingestion, you might see 406 responses, which means that the Operations for Applications service pushed back the data. Direct ingestion drops this data -- and if you code your client to retry, you're actually starting to rebuild the proxy.
+When you use direct ingestion, you might see 406 responses, which means that the Tanzu Observability service pushed back the data. Direct ingestion drops this data -- and if you code your client to retry, you're actually starting to rebuild the proxy.
-{% include note.html content="If you're using Operations for Applications as part of a free trial or Freemium offering, there are limits on how much data you can send to the service using direct ingestion. Contact support@wavefront.com if you need a higher limit. For production environments, you must install a Wavefront proxy and ingest the data through the proxy. Direct data ingestion is suitable only for test, trial, and POC environments and is not supported for production environments." %}
+{% include note.html content="If you're using Tanzu Observability as part of a free trial or Freemium offering, there are limits on how much data you can send to the service using direct ingestion. Contact support@wavefront.com if you need a higher limit. For production environments, you must install a Wavefront proxy and ingest the data through the proxy. Direct data ingestion is suitable only for test, trial, and POC environments and is not supported for production environments." %}
-It's typical that the Operations for Applications service doesn't accept a small amount of data. This pushback doesn't cause any issues with proxies. Consider this example:
+It's typical that the Tanzu Observability service doesn't accept a small amount of data. This pushback doesn't cause any issues with proxies. Consider this example:
* The data rate smoothed out over a minute is 100k PPS.
-* The Operations for Applications cluster is sized to 150k PPS (plenty of headroom).
+* The Tanzu Observability cluster is sized to 150k PPS (plenty of headroom).
* However, the client (customer) sends all the data for each minute on the minute. The client might send 6M PPS in 1 second, then nothing for 59 seconds, then repeat.
-Operations for Applications doesn't size your cluster for 6M PPS when the smoothed-out traffic is really 100k PPS. Instead, the Operations for Applications service relies on the proxy to smooth out the traffic over the minute. Proxies retry queued points, so even with just one proxy you won't see dropped points.
+Tanzu Observability doesn't size your cluster for 6M PPS when the smoothed-out traffic is really 100k PPS. Instead, the Tanzu Observability service relies on the proxy to smooth out the traffic over the minute. Proxies retry queued points, so even with just one proxy you won't see dropped points.
With direct ingestion you might lose data. In most cases, using a proxy will therefore give you more reliable results.
diff --git a/pages/doc/events.md b/pages/doc/events.md
index 60f1cbb77..1df7dc017 100644
--- a/pages/doc/events.md
+++ b/pages/doc/events.md
@@ -4,7 +4,7 @@ keywords: events
tags: [events, alerts]
sidebar: doc_sidebar
permalink: events.html
-summary: Learn about events and how to view, create, and close events in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn about events and how to view, create, and close events in Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
An event is a record that something of interest has happened. For example, the event might show that an alert has changed state, AWS instances have started or stopped, and so on. To view the list of all events, select **Browse > Events**.
@@ -34,7 +34,7 @@ Watch these videos to get you started! Note that these videos were created in 20
-Operations for Applications creates System events and Alert events for you. You can create User events via the UI or API to signal that something of interest has happened. Jason demos how to create an event from a chart and shows how it immediately appears in the UI.
+Tanzu Observability creates System events and Alert events for you. You can create User events via the UI or API to signal that something of interest has happened. Jason demos how to create an event from a chart and shows how it immediately appears in the UI.
@@ -61,7 +61,7 @@ An event can have one of the following sources.
- The CloudTrail integration retrieves EC2 event information and creates System events that represent the EC2 events. See [CloudTrail Integration](integrations_aws_metrics.html#cloudtrail-events-metrics-and-point-tags).
- For Microsoft Azure, some information from the Azure Activity Log integration is available as events.
-- **User** -- You can [manually create events](events.html#creating-a-user-event) with source **User** to identify user actions. For example, you can create an event for code pushes that affect Operations for Applications metrics but that occur outside Operations for Applications. The event is then available on charts that display the metrics.
+- **User** -- You can [manually create events](events.html#creating-a-user-event) with source **User** to identify user actions. For example, you can create an event for code pushes that affect Tanzu Observability metrics but that occur outside Tanzu Observability. The event is then available on charts that display the metrics.
Events have types and subtypes, which are typically used in [events queries](events_queries.html). Types include **alert** or **alert-detail** You can see types in the Type column of the **Events** page.
@@ -89,7 +89,7 @@ The example does not include an event that's in the Pending state.
-To improve event performance, Operations for Applications ends events that have been ongoing for 60 days (based on start time). We also don't return events for certain ongoing `events()` queries. See [When Does an Event Query Return Events](events_queries.html#when-does-an-event-query-return-events).
+To improve event performance, Tanzu Observability ends events that have been ongoing for 60 days (based on start time). We also don't return events for certain ongoing `events()` queries. See [When Does an Event Query Return Events](events_queries.html#when-does-an-event-query-return-events).
{% include note.html content="You cannot have more than 1000 ongoing events on your cluster. Use the `~events.num-ongoing-events` internal metric to monitor the number of ongoing events." %}
@@ -116,7 +116,7 @@ The chart includes information about the alert associated with the event, and ab
## Creating a User Event
-Operations for Applications creates many events for you, but you can also create an event explicitly:
+Tanzu Observability creates many events for you, but you can also create an event explicitly:
1. Do one of the following:
- Select **Browse > Events** and click the Create Event button on top.
@@ -148,7 +148,7 @@ Operations for Applications creates many events for you, but you can also create
The end time of the event:
Instantaneous - End the event instantaneously with the start time. The exact interval is indeterminate. The Events page can report that the event starts and ends at exactly the same time or that it lasts a few seconds.
-
Ongoing - The event does not have a specified end time. You can manually end (close) the event from the Events page. Operations for Applications closes events that are older than 60 days.
+
Ongoing - The event does not have a specified end time. You can manually end (close) the event from the Events page. Tanzu Observability closes events that are older than 60 days.
- End the event at the specified day and time. Click the text field to select the end time.
Note: If you can create an event with an end time, you cannot make changes to the event name or other event properties later.
@@ -174,7 +174,7 @@ Operations for Applications creates many events for you, but you can also create
## Event Closure and Deletion
-Operations for Applications closes any event that is older than 60 days, based on start time. You can explicitly close events and delete user events if you have the right permissions.
+Tanzu Observability closes any event that is older than 60 days, based on start time. You can explicitly close events and delete user events if you have the right permissions.
### Closing an Event
diff --git a/pages/doc/integrations_new_changed.md b/pages/doc/integrations_new_changed.md
index 60bc3c4f3..704d73ad2 100644
--- a/pages/doc/integrations_new_changed.md
+++ b/pages/doc/integrations_new_changed.md
@@ -6,20 +6,20 @@ sidebar: doc_sidebar
permalink: integrations_new_changed.html
summary: New and changed integrations.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) continuously adds new integrations to the existing set, and improves available integrations. We update our [**complete list of all integrations**](https://docs.wavefront.com/label_integrations%20list.html) each time we add new integrations.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations. We update our [**complete list of all integrations**](https://docs.wavefront.com/label_integrations%20list.html) each time we add new integrations.
## Announcement
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Operations for Applications subscriptions **onboarded** to the [VMware Cloud services platform](https://console.cloud.vmware.com/) and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services. We are in the process of incrementally [onboarding](csp_migration.html) all original subscriptions to VMware Cloud services.
+Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the [VMware Cloud services platform](https://console.cloud.vmware.com/) and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services. We are in the process of incrementally [onboarding](csp_migration.html) all original subscriptions to VMware Cloud services.
For details about the two subscription types and how they differ, see [Subscription Types](subscriptions-differences.html).
-If your Operations for Applications service **is onboarded** to VMware Cloud services, most of the integrations authenticate with VMware Cloud services **access tokens**. Only a limited list of integrations still authenticate with Operations for Applications API tokens. For details, see [How Integration Authentication Works](integrations_onboarded_subscriptions.html).
+If your Tanzu Observability service **is onboarded** to VMware Cloud services, most of the integrations authenticate with VMware Cloud services **access tokens**. Only a limited list of integrations still authenticate with Tanzu Observability API tokens. For details, see [How Integration Authentication Works](integrations_onboarded_subscriptions.html).
{% include note.html content= "The integrations in the **Archived** section are approaching their end-of-life. For that reason, we will not update these integrations to authenticate with VMware Cloud services access tokens." %}
-During the process of onboarding an original Operations for Applications service to VMware Cloud services, all of the existing integrations are preserved and continue to operate using Operations for Applications API tokens. You should incrementally switch to integration authentication with the more secure VMware Cloud services access tokens. See [What Happens with the Integrations?](csp_migration.html#what-happens-with-the-integrations).
+During the process of onboarding an original Tanzu Observability service to VMware Cloud services, all of the existing integrations are preserved and continue to operate using Tanzu Observability API tokens. You should incrementally switch to integration authentication with the more secure VMware Cloud services access tokens. See [What Happens with the Integrations?](csp_migration.html#what-happens-with-the-integrations).
{% include note.html content= "Currently, if your service **is onboarded** to VMware Cloud services, direct ingestion by using the Wavefront Output Plugin for Telegraf is not supported. For best performance, use a Wavefront proxy. " %}
diff --git a/pages/doc/integrations_new_changed_2020.md b/pages/doc/integrations_new_changed_2020.md
index 02abbdca0..3f580644e 100644
--- a/pages/doc/integrations_new_changed_2020.md
+++ b/pages/doc/integrations_new_changed_2020.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_new_changed_2020.html
summary: New and changed integrations released in 2019-2020
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) continuously adds new integrations to the existing set, and improves available integrations.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations.
This document lists new and changed integrations for 2019 and 2020.
* We have a separate document for [Integrations Release Notes](integrations_new_changed.html).
@@ -28,7 +28,7 @@ Made improvements to the following integrations in October 2020 - December 2020:
* Slack -- URL unfurler
* Operations for Applications Usage new dashboards:
- **Operations for Applications Ingestion Policy Explorer** In environments where [ingestion policies](ingestion_policies.html) have been configured, shows usage for each user and ingestion policy.
- - **Committed Rate and Monthly Usage (PPS P95)** dashboard shows Operations for Applications monthly usage against committed rate.
+ - **Committed Rate and Monthly Usage (PPS P95)** dashboard shows Tanzu Observability monthly usage against committed rate.
- **Operations for Applications Namespace Usage Explorer**: Tracks the number of metrics received for the first 3 levels of your metric namespace.
* Google Cloud Platform (GCP) -- Fixed dashboard queries in Google Kubernetes Engine (GKE) dashboard
* Azure Storage -- Preconfigured dashboard now supports monitoring of the Classic storage type
diff --git a/pages/doc/integrations_new_changed_2021.md b/pages/doc/integrations_new_changed_2021.md
index e0425feb5..8ac8d05fc 100644
--- a/pages/doc/integrations_new_changed_2021.md
+++ b/pages/doc/integrations_new_changed_2021.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_new_changed_2021.html
summary: New and changed integrations released in 2021
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) continuously adds new integrations to the existing set, and improves available integrations.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations.
This document lists new and changed integrations for 2021. For earlier releases, see [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).
@@ -38,7 +38,7 @@ We added the following integration in November 2021:
* AVI Networks
- Now, NSX Advance Load Balancer (AVI Networks) can be monitored by using out-of-the-box dashboards provided in the AVI Networks (NSX ALB) integration tile. This integration is developed and created by the community and falls into to the new **Community Integrations** section of the **Integrations** page. This is the first integration in this category. We do not validate the community integrations and they are not fully supported by the VMware Aria Operations for Applications team.
+ Now, NSX Advance Load Balancer (AVI Networks) can be monitored by using out-of-the-box dashboards provided in the AVI Networks (NSX ALB) integration tile. This integration is developed and created by the community and falls into to the new **Community Integrations** section of the **Integrations** page. This is the first integration in this category. We do not validate the community integrations and they are not fully supported by the Tanzu Observability team.
Made improvements to the following integrations and dashboards in November 2021:
@@ -112,7 +112,7 @@ Made improvements to the following integrations and dashboards in July 2021:
* Project Pacific -- Renamed the integration from Project Pacific Integration to vSphere with Tanzu Integration.
* VMware Cloud PKS -- Removed the VMware Cloud PKS integration.
-* OpenTelemetry -- Updated the steps for configuring the application to send trace data to VMware Aria Operations for Applications using the trace exporter.
+* OpenTelemetry -- Updated the steps for configuring the application to send trace data to Tanzu Observability using the trace exporter.
* Operations for Applications Usage -- Added new charts to **Proxies Overview** section in the **Operations for Applications Service and Proxy Data** dashboard to show **Spans Sampled By Policies**.
* Azure AD -- Added steps to configure Azure AD using Self-Service SAML.
* Data Platforms -- Added a new dashboard **Data Platform Blueprint2 - Kafka-Spark-Elasticsearch**.
@@ -187,7 +187,7 @@ Made improvements to the following integrations and dashboards in April 2021:
* Pivotal Cloud Foundry:
* Fixed charts in the **PCF: MySQL** dashboard.
* Added the **VMware Tanzu Application Services** tile to the Pivotal Cloud Foundry integration.
-* Istio -- Deprecated the VMware Operations for Applications Istio adapter and added support to monitor Istio 1.8.
+* Istio -- Deprecated the Tanzu Observability Istio adapter and added support to monitor Istio 1.8.
* Jaeger -- Updates to the integration setup instructions to send data to the Wavefront proxy through gRPC.
* HipChat -- Removed the HipChat integration.
* OpenTelemetry -- Updates to the integration setup instructions.
@@ -198,8 +198,8 @@ Made improvements to the following integrations and dashboards in April 2021:
Made improvements to the following integrations in March 2021:
* Catchpoint:
- * Labels in Catchpoint are available as point tags in VMware Aria Operations for Applications.
- * Insight Settings in Catchpoint, such as tracepoints and indicators, are available as metrics in Operations for Applications.
+ * Labels in Catchpoint are available as point tags in Tanzu Observability.
+ * Insight Settings in Catchpoint, such as tracepoints and indicators, are available as metrics in Tanzu Observability.
* OpenTelemetry -- Fixed broken links in the setup instructions
* Istio -- Fixed broken links in the setup instructions
* Kubernetes:
@@ -210,7 +210,7 @@ Made improvements to the following integrations in March 2021:
* OneLogin -- Updates to the integration setup instructions
* vSphere -- Fixes to the out of the box dashboards
* RabbitMQ -- Fixes to the out of the box dashboards
-* Operations for Applications Usage -- Added new alerts to the Operations for Applications usage integration
+* Operations for Applications Usage -- Added new alerts to the integration
## December 2020 - February 2021
diff --git a/pages/doc/integrations_new_changed_2022.md b/pages/doc/integrations_new_changed_2022.md
index beedaf291..90b694bce 100644
--- a/pages/doc/integrations_new_changed_2022.md
+++ b/pages/doc/integrations_new_changed_2022.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_new_changed_2022.html
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.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) 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) 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).
@@ -91,7 +91,7 @@ We made improvements to the following integrations in November 2022:
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)." %}
+{% include important.html content="Logs (Beta) is enabled only for selected customers. To participate, contact your Tanzu Observability account representative or [technical support](wavefront_support_feedback.html#support)." %}
With the Initial Availability of our Logs (Beta) feature, we have made improvements to the following integrations:
@@ -106,7 +106,7 @@ We made improvements and bug fixes to the following integrations in October 2022
- Made a minor fix to the **Operations for Applications Service and Proxy Data** dashboard.
* Terraform Provider:
- We added data source support for alerts, dashboards, events, derived metrics, maintenance windows, and external links.
- - Added support for checking frequency of Terraform Operations for Applications Alert.
+ - Added support for checking frequency of Terraform Tanzu Observability Alert.
- User groups and roles can be now fetched by ID.
- We added a data source example to the sample Terraform Provider script.
* Tanzu Application Service:
@@ -145,7 +145,7 @@ We added the following integration in August 2022:
* VMware Tanzu Greenplum:
- VMware Tanzu Greenplum is a massively parallel processing (MPP) database server that supports next generation data warehousing and large-scale analytics processing. This integration installs and configures Telegraf to send system and query metrics into VMware Aria Operations for Applications.
+ VMware Tanzu Greenplum is a massively parallel processing (MPP) database server that supports next generation data warehousing and large-scale analytics processing. This integration installs and configures Telegraf to send system and query metrics into Tanzu Observability.
We made improvements to the following integrations in August 2022:
@@ -201,7 +201,7 @@ We made improvements to the following integrations in June 2022:
* Snowflake:
* To enhance authentication security, we updated the setup steps of the integration. Now, to register Snowflake, you have to provide a private key.
- * We improved the setup instructions with information on how to generate the public and private keys and give Operations for Applications access to your Snowflake account.
+ * We improved the setup instructions with information on how to generate the public and private keys and give Tanzu Observability access to your Snowflake account.
* Improved the **Snowflake Summary** dashboard and included charts for warehouse load monitoring.
* Jenkins:
@@ -260,7 +260,7 @@ We added the following integration in March 2022:
* VMware Blockchain
- VMware Blockchain is an enterprise-grade blockchain platform that enables multi-party workflows. This integration is developed and created by the community and falls into to the **Community Integrations** section of the VMware Aria Operations for Applications **Integrations** page. We do not validate the community integrations and they are not fully supported by the VMware Aria Operations for Applications team.
+ VMware Blockchain is an enterprise-grade blockchain platform that enables multi-party workflows. This integration is developed and created by the community and falls into to the **Community Integrations** section of the Tanzu Observability **Integrations** page. We do not validate the community integrations and they are not fully supported by the Tanzu Observability team.
We made improvements to the following integrations in March 2022:
@@ -297,7 +297,7 @@ We added the following integrations in February 2022:
* Dynatrace SaaS
- This integration collects the metrics from a Dynatrace SaaS environment and sends them to VMware Aria Operations for Applications. The on-premises Dynatrace integration is moved to the **Archived** section.
+ This integration collects the metrics from a Dynatrace SaaS environment and sends them to Tanzu Observability. The on-premises Dynatrace integration is moved to the **Archived** section.
Made improvements to the following integrations and dashboards in February 2022:
@@ -322,7 +322,7 @@ We added the following integrations in January 2022:
* Velero
- You can monitor the Velero backup and restore solution. This integration is developed and created by the community and falls into to the **Community Integrations** section of the VMware Aria Operations for Applications **Integrations** page. We do not validate the community integrations and they are not fully supported by the VMware Aria Operations for Applications team.
+ You can monitor the Velero backup and restore solution. This integration is developed and created by the community and falls into to the **Community Integrations** section of the Tanzu Observability **Integrations** page. We do not validate the community integrations and they are not fully supported by the Tanzu Observability team.
Made improvements to the following integrations and dashboards in January 2022:
diff --git a/pages/doc/integrations_new_changed_2023.md b/pages/doc/integrations_new_changed_2023.md
index 53c75d95c..e415081b9 100644
--- a/pages/doc/integrations_new_changed_2023.md
+++ b/pages/doc/integrations_new_changed_2023.md
@@ -6,7 +6,7 @@ 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.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) 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).
@@ -23,7 +23,7 @@ We made improvements to the following integrations in December 2023:
* 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).
+We updated the following integrations to support VMware Cloud Services access token authentication when your Tanzu Observability 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
@@ -65,7 +65,7 @@ Also, we made improvements to the following integrations in October 2023:
* 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).
+In addition, we updated the following integrations to support VMware Cloud Services access token authentication when your Tanzu Observability 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
@@ -92,12 +92,12 @@ We made improvements to the following integrations in August 2023:
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).
+* Tanzu Application Service -- We added support for Tanzu Application Service setup when your Tanzu Observability 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 added support for Kubernetes setup when your Tanzu Observability 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).
@@ -152,11 +152,11 @@ We made improvements to the following integrations in May 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)." %}
+ {% include important.html content="Logs (Beta) is enabled only for selected customers. To participate, contact your Tanzu Observability 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).
+* 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 Tanzu Observability. 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:
@@ -196,7 +196,7 @@ We made improvements to the following integration in February 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).
+* 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 Tanzu Observability](integrations_aws_lambda.html#ingesting-aws-lambda-cold-start-metrics-into-tanzu-observability).
* ServiceNow -- We updated the instructions on how to set up the integration to reflect the latest UI changes.
diff --git a/pages/doc/metric_types.md b/pages/doc/metric_types.md
index 43821cbd6..966fc836c 100644
--- a/pages/doc/metric_types.md
+++ b/pages/doc/metric_types.md
@@ -7,9 +7,9 @@ permalink: metric_types.html
summary: Learn about gauges, counters, delta counters, histograms, and spans.
---
- VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports monitoring time series, histograms, and traces.
+ Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports monitoring time series, histograms, and traces.
* Each **time series** consists of numeric data points for a metric, for example, CPU load or failed network connections. Time series can use one of the [supported data formats](wavefront_data_format.html#supported-data-formats-for-metrics).
- The type of data that you’re collecting determines the type of metric. Operations for Applications supports gauges, counters, delta counters, and more.
+ The type of data that you’re collecting determines the type of metric. Tanzu Observability supports gauges, counters, delta counters, and more.
* **[Histograms](proxies_histograms.html)** let you compute, store, and use distributions of metrics rather than single metrics. Histograms are useful for high-velocity metrics about your applications and infrastructure–-particularly metrics that are gathered across many distributed sources.
* **[Distributed tracing](tracing_basics.html)** enables you to track the flow of work that is performed by an application as it processes a user request. We support the OpenTracing standard. You can either visualize and examine traces coming from a 3rd-party system such as Jaeger or Zipkin, or instrument your application for tracing using one of our SDKs.
@@ -77,9 +77,9 @@ For example, `~metric.new_host_ids` and `~query.requests` are internal metrics t
[Delta counters](delta_counters.html) bin to a minute timestamp and treat write operations to the same bin as deltas. They are well suited for the kind of bursty traffic you typically get in a Function-as-a-Service environment. Many functions execute simultaneously and it's not possible to monitor bursty traffic like that without losing metric points to collision.
-For example, instead of one person with a counter standing at a single concert entrance, several people count, each at one entrance gate. Eventually the results from the counters can be added for total attendance. In the same way, Operations for Applications can aggregate delta counter information.
+For example, instead of one person with a counter standing at a single concert entrance, several people count, each at one entrance gate. Eventually the results from the counters can be added for total attendance. In the same way, Tanzu Observability can aggregate delta counter information.
-To have the Operations for Applications service treat a metric as a delta counter, you have several choices:
+To have the Tanzu Observability service treat a metric as a delta counter, you have several choices:
* Use the `cs()` instead of the `ts()` function.
* Add a delta character prefix to the metric.
@@ -89,7 +89,7 @@ To have the Operations for Applications service treat a metric as a delta counte
## Histograms
-Operations for Applications can receive and store metrics at 1 point per second per unique source. However, some scenarios generate metrics even more frequently. Suppose you are measuring the latency of web requests. If you have a lot of traffic at multiple servers, you may have multiple distinct measurements for a given metric, timestamp, and source. Using "normal” metrics, we can’t measure this.
+Tanzu Observability can receive and store metrics at 1 point per second per unique source. However, some scenarios generate metrics even more frequently. Suppose you are measuring the latency of web requests. If you have a lot of traffic at multiple servers, you may have multiple distinct measurements for a given metric, timestamp, and source. Using "normal” metrics, we can’t measure this.
To address high frequency data, we supports histograms – a mechanism to compute, store, and use distributions of metrics. A histogram is a distribution of metrics collected and computed by the Wavefront proxy. [Sending Histogram Distributions](proxies_histograms.html) describes the histogram format, histogram ports, and some examples.
diff --git a/pages/doc/metrics_managing.md b/pages/doc/metrics_managing.md
index 7f47dfa87..f5031b6be 100644
--- a/pages/doc/metrics_managing.md
+++ b/pages/doc/metrics_managing.md
@@ -7,7 +7,7 @@ permalink: metrics_managing.html
summary: Understand metrics structure and how to explore metrics in the Metrics Browser
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) provides observability for several different [metric types](metric_types.html) including time series metrics, delta counters, histograms, and traces/spans. This page looks at the anatomy of a time series metric and shows you how to explore it in the Metrics Browser.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) provides observability for several different [metric types](metric_types.html) including time series metrics, delta counters, histograms, and traces/spans. This page looks at the anatomy of a time series metric and shows you how to explore it in the Metrics Browser.
## Videos
@@ -177,4 +177,4 @@ The selected metrics and metric prefixes appear again as long as they are not ob
## Learn More!
* [Optimizing the Data Shape to Improve Performance](optimize_data_shape.html)
-* See the KB article [Migrating Objects or Data Between Operations for Applications Environments](https://vmwaoa.zendesk.com/hc/en-us/articles/21153594484493-Migrating-Objects-or-Data-Between-VMware-Aria-Operations-for-Applications-Environments) if your company has several service instances.
+* See the KB article [Migrating Objects or Data Between Environments](https://vmwaoa.zendesk.com/hc/en-us/articles/21153594484493-Migrating-Objects-or-Data-Between-VMware-Aria-Operations-for-Applications-Environments) if your company has several service instances.
diff --git a/pages/doc/missing_data_troubleshooting.md b/pages/doc/missing_data_troubleshooting.md
index 36584684f..bb5ffa8d3 100644
--- a/pages/doc/missing_data_troubleshooting.md
+++ b/pages/doc/missing_data_troubleshooting.md
@@ -7,7 +7,7 @@ permalink: missing_data_troubleshooting.html
summary: Learn how to troubleshoot when you expect to see data but it doesn't appear in charts.
---
-Sometimes you expect to see certain data in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) but, for some reason, it doesn't show up! This can be a frustrating and confusing experience, especially when you urgently need the data. Operations for Applications does not delete data, and retains [metric data for 18 months](terms_of_service.html#data-retention). What could be the problem?
+Sometimes you expect to see certain data in Tanzu Observability (formerly known as VMware Aria Operations for Applications) but, for some reason, it doesn't show up! This can be a frustrating and confusing experience, especially when you urgently need the data. Tanzu Observability does not delete data, and retains [metric data for 18 months](terms_of_service.html#data-retention). What could be the problem?
This doc page, based on the extensive experience of our customer success team, helps you investigate, understand, and remedy possible causes. In addition to manually investigating and troubleshooting your issues, you can use the [Query Analyzer](query_language_performance.html#use-the-query-analyzer) which helps you identify where exactly the problem is.
@@ -26,7 +26,7 @@ It might sound surprising, but many **No Data** problems are the result of a typ
### Step 2: Quote
-Because of character limitations imposed by the Operations for Applications Data Format, it's possible that your queries cannot recognize source names or tag names unless they are surrounded by double quotes. See [Data Format Best Practices](wavefront_data_format.html#operations-for-applications-data-format-best-practices).
+Because of character limitations imposed by the Tanzu Observability Data Format, it's possible that your queries cannot recognize source names or tag names unless they are surrounded by double quotes. See [Taznu Observability Data Format Best Practices](wavefront_data_format.html#tanzu-observability-data-format-best-practices).
### Step 3: Untangle
@@ -264,7 +264,7 @@ As the proxy processes data in the memory buffers, space is freed up for new inc
#### Proxy Queue Reasons: Network Issues
-If network issues prevent or slow down requests from the proxy to the Operations for Applications service, then the proxy queue fills up because data arrives at the proxy faster than data can be sent to the service.
+If network issues prevent or slow down requests from the proxy to the Tanzu Observability service, then the proxy queue fills up because data arrives at the proxy faster than data can be sent to the service.
**Troubleshooting & Further Investigation:**
@@ -286,7 +286,7 @@ The proxy configuration property `memGuardFlushThreshold` is meant to protect ag
### Step 2: Understand Data Delays Inherent to Your Data Pipeline
-If your data travels through a pipeline before reaching the Wavefront proxy or before being direct ingested to the Operations for Applications service, the pipeline itself can introduce delays to the ingestion process.
+If your data travels through a pipeline before reaching the Wavefront proxy or before being direct ingested to the Tanzu Observability service, the pipeline itself can introduce delays to the ingestion process.
**Troubleshooting & Further Investigation**
@@ -300,7 +300,7 @@ Every pipeline inherently has its own latencies. Understanding the latencies hel
### Step 3: Find Data Delays Caused by High Rate of New IDs
-Components of each data point are converted into IDs at the backend (Operations for Applications service) before the points are stored. These components include metric name, source name, and the point tag key and value combination.
+Components of each data point are converted into IDs at the backend (Tanzu Observability service) before the points are stored. These components include metric name, source name, and the point tag key and value combination.
Each time the service detects a new name, it generates a new ID. ID generation adds to the ingestion time. When the rate of new IDs is low, this is negligible. However, when you send a large amount of new data at the same time and the ID generation rate is high, a backlog of items that need an ID can result. This backlog results in delays in ingestion.
@@ -309,8 +309,8 @@ Each time the service detects a new name, it generates a new ID. ID generation a
The **Operations for Applications Usage** integration includes several alerts that you can customize to be alerted when there is a high rate of new IDs.
-* A high rate of new IDs can happen when you start sending new data to Operations for Applications.
-* A high rate of new IDs could also indicate a **cardinality issue** with the data shape of the data you're sending to Operations for Applications. For instance, if a timestamp was included as a point tag, a high number of unique point tags results. This can be a problem when you send the data to Operations for Applications, but also causes problems later when you query the data. See [Data Naming Best Practices](wavefront_data_naming.html) for best practices.
+* A high rate of new IDs can happen when you start sending new data to Tanzu Observability.
+* A high rate of new IDs could also indicate a **cardinality issue** with the data shape of the data you're sending to Tanzu Observability. For instance, if a timestamp was included as a point tag, a high number of unique point tags results. This can be a problem when you send the data to Tanzu Observability, but also causes problems later when you query the data. See [Data Naming Best Practices](wavefront_data_naming.html) for best practices.
## Problem: Blocked Data
@@ -325,14 +325,14 @@ By default, the proxy and the service allow data points that are timestamped bet
* 8760 hours (1 year) ago
* 24 hours (1 day) ahead of the current time
-This functionality supports back-fill of old data or pre-fill future data. Make sure that the timestamp of your data points is in this range. Data with a timestamp outside this range will be rejected at the proxy or not ingested by the Operations for Applications service. If you have a use case for ingesting data outside this time range, update the proxy configuration and [contact Support](wavefront_support_feedback.html#support) to have the backend configuration for your environment updated.
+This functionality supports back-fill of old data or pre-fill future data. Make sure that the timestamp of your data points is in this range. Data with a timestamp outside this range will be rejected at the proxy or not ingested by the Tanzu Observability service. If you have a use case for ingesting data outside this time range, update the proxy configuration and [contact Support](wavefront_support_feedback.html#support) to have the backend configuration for your environment updated.
### Step 2: Do Invalid Data Format Block Data?
The proxy supports a variety of data formats. Most environments are set up to use different ports for different formats. Ensure that data is being sent to the proper port.
-For data that is in the Operations for Applications data format, see [this page](wavefront_data_format.html) for information on what is and is not valid and on the [limits that are in place](wavefront_limits.html).
+For data that is in the Tanzu Observability data format, see [this page](wavefront_data_format.html) for information on what is and is not valid and on the [limits that are in place](wavefront_limits.html).
* Each component of the data point has a set of allowed characters and length limits.
* There is also, for example, a default limit of 20 points tags per data point.
diff --git a/pages/doc/optimize_data_shape.md b/pages/doc/optimize_data_shape.md
index eaa46d879..2bae3153e 100644
--- a/pages/doc/optimize_data_shape.md
+++ b/pages/doc/optimize_data_shape.md
@@ -6,15 +6,15 @@ sidebar: doc_sidebar
permalink: optimize_data_shape.html
summary: Learn how to optimize your data in high-cardinality environments.
---
-Data shape refers to how each component of a time series is designed and formatted. Your data shapes in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) are important regardless of how you use the service and where you are in your work with the platform.
+Data shape refers to how each component of a time series is designed and formatted. Your data shapes in Tanzu Observability (formerly known as VMware Aria Operations for Applications) are important regardless of how you use the service and where you are in your work with the platform.
-* **New users** who plan on sending data into Operations for Applications need to understand the most efficient ways of sending data in.
+* **New users** who plan on sending data into Tanzu Observability need to understand the most efficient ways of sending data in.
* **Existing users** who explore data in dashboards and chart can investigate data shape and use that information to optimize data exploration. If they see that the data shape is not optimal, they might even request changes to how data are ingested.
In this doc page, we:
* Discuss how **all users** can examine data that are already being ingested.
-* Look at best practices for **users who send data to Operations for Applications** so they can use the optimal data shape and cardinality, and, as a result, optimize performance.
+* Look at best practices for **users who send data to Tanzu Observability** so they can use the optimal data shape and cardinality, and, as a result, optimize performance.
## Video
@@ -26,7 +26,7 @@ In the following video, Wavefront co-founder Clement Pang explains cardinality a
## Examine Ingested Data: Lag, Backfill, and Metric Type
-If data are already flowing into Operations for Applications, some aspects of how data are being ingested can significantly change what you see in your chart and whether your alerts work correctly. You can often fix problems using missing data function or using the correct metric type.
+If data are already flowing into Tanzu Observability, some aspects of how data are being ingested can significantly change what you see in your chart and whether your alerts work correctly. You can often fix problems using missing data function or using the correct metric type.
Ask yourself these questions:
@@ -57,7 +57,7 @@ The reporting window is easy to see in your Point Plot with 10-minute time windo
* Hover over each point to determine the time and the associated gap between the metrics.
* Look at the metric without advanced functions applied to the query (if possible) For example, if your query is `align(5m, sum(ts("my.metric")))`, use just `ts("my.metric")`.
-In most use cases and by default, Operations for Applications expects that a metric comes in each minute -- your *reporting interval* is 60 seconds. In the point plot, the points are 1 minute apart. In some cases metrics are separated by more than a minute and the 10 min live view of point plot reflects that.
+In most use cases and by default, Tanzu Observability expects that a metric comes in each minute -- your *reporting interval* is 60 seconds. In the point plot, the points are 1 minute apart. In some cases metrics are separated by more than a minute and the 10 min live view of point plot reflects that.
Here are the common reporting interval scenarios:
@@ -103,19 +103,19 @@ After considering the reporting interval and any potential delays in the metrics
With counter metrics, it is often useful to use functions such as `rate()`, `ratediff()` or `mdiff()` because those functions calculate the change over time.
-* **Delta Counter**: Delta counters are different from traditional counters. The delta counter value represents the change in value over time. In Operations for Applications, delta counters bin to a minute timestamp and write operations to the same bin are treated as deltas. Delta counters are helpful for calculating bursts of events because collisions can result if a traditional gauge or counter metrics tries to represent something that changes so rapidly.
+* **Delta Counter**: Delta counters are different from traditional counters. The delta counter value represents the change in value over time. In Tanzu Observability, delta counters bin to a minute timestamp and write operations to the same bin are treated as deltas. Delta counters are helpful for calculating bursts of events because collisions can result if a traditional gauge or counter metrics tries to represent something that changes so rapidly.
See [Cumulative Counters and Delta Counters](delta_counters.html) for background
## Fine-Tune How Data Are Ingested
-If you're responsible for sending data into Operations for Applications, you can significantly improve performance and get the results you need by following the best practices in this section.
+If you're responsible for sending data into Tanzu Observability, you can significantly improve performance and get the results you need by following the best practices in this section.
### Step 1: Ensure You Send Time Series Data
-Operations for Applications supports time series data. Time series track behavior over time. Each data point is a measurement at a particular point in time. We can connect and graph data points because they measure the same behavior at different moments in time. For example, you can measure the CPU load for one data source over time and can then graph those data to show increase, decrease, etc.
+Tanzu Observability supports time series data. Time series track behavior over time. Each data point is a measurement at a particular point in time. We can connect and graph data points because they measure the same behavior at different moments in time. For example, you can measure the CPU load for one data source over time and can then graph those data to show increase, decrease, etc.
Check if your data is time series data. If your data is tracking very unique behavior and the metric/source combination is unique for each data point, it's difficult to graph that time series.
@@ -139,16 +139,16 @@ Fewer time series means faster data retrieval, so reducing the number of series
### Step 3: Be Smart about Data Point Components
-Operations for Applications uses several indexes for retrieving data.
+Tanzu Observability uses several indexes for retrieving data.
* One index uses the metric name and source name combination.
* Another index allows retrieval of data based on the point tag key and values combination.
-If you are smart about data shaping to optimize how Operations for Applications uses these indexes so that the query engine can return results faster. See [Ask How Data Will Be Queried and Optimize](#step-5-ask-how-data-will-be-queried-and-optimize).
+If you are smart about data shaping to optimize how Tanzu Observability uses these indexes so that the query engine can return results faster. See [Ask How Data Will Be Queried and Optimize](#step-5-ask-how-data-will-be-queried-and-optimize).
-Operations for Applications identifies data points that measure the same behavior by looking at the **components of each data point** (metric name, source name, and point tag name/value). The unique combination of these components describes what a time series is.
+Tanzu Observability identifies data points that measure the same behavior by looking at the **components of each data point** (metric name, source name, and point tag name/value). The unique combination of these components describes what a time series is.
-For example, Operations for Applications sees that the CPU load for source-1 is different from the CPU load for source-2 and shows 2 time series in the chart. Operations for Applications can also access point tags to display different Kubernetes pods as different time series or to show different time series for different availability zones. See [Fine Tune Queries with Point Tags](query_language_point_tags.html) to understand how point tags work.
+For example, Tanzu Observability sees that the CPU load for source-1 is different from the CPU load for source-2 and shows 2 time series in the chart. Tanzu Observability can also access point tags to display different Kubernetes pods as different time series or to show different time series for different availability zones. See [Fine Tune Queries with Point Tags](query_language_point_tags.html) to understand how point tags work.
### Step 4: Investigate Lags, Backfills, and Metric Type
diff --git a/pages/doc/proxies.md b/pages/doc/proxies.md
index ebc04a377..25cbdb2ac 100644
--- a/pages/doc/proxies.md
+++ b/pages/doc/proxies.md
@@ -6,20 +6,20 @@ sidebar: doc_sidebar
permalink: proxies.html
summary: Learn about Wavefront proxies.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) enables you to:
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) enables you to:
* Send data through Wavefront proxies. Most customers and our DevOps team use proxies.
* Send data directly using [direct ingestions](direct_ingestion.html).
-A Wavefront proxy ingests metrics and forwards them to Operations for Applications in a secure, fast, and reliable manner. After you install a proxy in your environment, it can handle thousands of simultaneous clients. Your data collection agents or custom code send data to the proxy, which consolidates points into configurable batches and sends the data to your Operations for Applications service.
+A Wavefront proxy ingests metrics and forwards them to Tanzu Observability in a secure, fast, and reliable manner. After you install a proxy in your environment, it can handle thousands of simultaneous clients. Your data collection agents or custom code send data to the proxy, which consolidates points into configurable batches and sends the data to your Tanzu Observability service.
## Proxy Benefits
Having a proxy be part of the architecture has benefits:
- **Prevent data loss, optimize network bandwidth** -- The proxy buffers and manages data traffic. Even if there's a connectivity problem, you don't lose data points.
-- **Simple firewall configuration** -- The proxy receives metrics from many agents on different hosts and forwards those metrics to Operations for Applications. You don't need to open internet access for each of the agents.
-- **Enrich or filter data** -- You can set up the preprocessor to filter data before it's sent to your Operations for Applications service.
-- **Examine bottlenecks** -- Each proxy generates its own metrics, so you can check whether data comes in and whether data is sent to your Operations for Applications service.
+- **Simple firewall configuration** -- The proxy receives metrics from many agents on different hosts and forwards those metrics to Tanzu Observability. You don't need to open internet access for each of the agents.
+- **Enrich or filter data** -- You can set up the preprocessor to filter data before it's sent to your Tanzu Observability service.
+- **Examine bottlenecks** -- Each proxy generates its own metrics, so you can check whether data comes in and whether data is sent to your Tanzu Observability service.
In this video, Clement contrasts using a Wavefront proxy with using direct ingestion, discusses proxy benefits, and goes over the architecture of most production systems, which includes a fleet of proxies behind a load balancer. The result is more resilience and a better user experience. Note that this video was created in 2019 and some of the information in it might have changed.
@@ -30,8 +30,8 @@ In this video, Clement contrasts using a Wavefront proxy with using direct inges
## Proxy Deployment Options
You have a choice of proxy deployment option:
-* Initially, as part of the in-product Getting Started workflow, trial users install their first integration - often an integration with the local host. In that case, the data source, the agent, and the proxy all run on the same host and the proxy forwards metrics to the Operations for Applications service.
-* As your environment grows, you place the proxy on a dedicated host. Different agents and other data sources can send metrics to the proxy, and the proxy forwards the metrics to your Operations for Applications service. Agents can run either on the same host as the data source or on a different host.
+* Initially, as part of the in-product Getting Started workflow, trial users install their first integration - often an integration with the local host. In that case, the data source, the agent, and the proxy all run on the same host and the proxy forwards metrics to the Tanzu Observability service.
+* As your environment grows, you place the proxy on a dedicated host. Different agents and other data sources can send metrics to the proxy, and the proxy forwards the metrics to your Tanzu Observability service. Agents can run either on the same host as the data source or on a different host.
* In production environments, you can place two proxies or a fleet of proxies behind a load balancer for optimal performance and high availability. In that case, each proxy must have a unique name. Your fleet of proxies does not run on the same host as your data sources.
{% include note.html content="It's not a good idea to install a proxy on each host you're monitoring. First, you lose the benefit of protection against data loss -- the proxy can buffer your metrics. Second, you only need a small number of proxies even in production environments." %}
@@ -50,7 +50,7 @@ When you set up an integration, the Setup page lets you pick a proxy –- or off
### Development Environment: Shared Proxy Deployment
-A proxy can accept metrics from multiple collector agents and forward those metrics to Operations for Applications. Having just one proxy means that you don't need to open multiple firewall ports: The proxy is the only component that needs a firewall port opened, simplifying configuration.
+A proxy can accept metrics from multiple collector agents and forward those metrics to Tanzu Observability. Having just one proxy means that you don't need to open multiple firewall ports: The proxy is the only component that needs a firewall port opened, simplifying configuration.
diff --git a/pages/doc/proxies_configuring.md b/pages/doc/proxies_configuring.md
index f793efcb6..eac808dbc 100644
--- a/pages/doc/proxies_configuring.md
+++ b/pages/doc/proxies_configuring.md
@@ -8,7 +8,7 @@ summary: Proxy files, logs, and configuration properties
---
-Even without additional customization, the Wavefront proxy ingests metrics and forwards them to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) in a secure, fast, and reliable manner. If needed, you can customize your proxy.
+Even without additional customization, the Wavefront proxy ingests metrics and forwards them to Tanzu Observability (formerly known as VMware Aria Operations for Applications) in a secure, fast, and reliable manner. If needed, you can customize your proxy.
* **[Proxy configuration properties](#configuration-properties)** allow you to change how the proxy processes your data. For example, you can change ports or perform other advanced installation management.
@@ -41,13 +41,13 @@ By default, proxy files are installed in the following locations.
## Data Buffering
-If the Wavefront proxy is unable to post received data to the Operations for Applications servers, it buffers the data to disk across a number of buffer files, and then tries to resend the points once the connection to the Operations for Applications servers is available again. If this buffering occurs, you'll see lines like this in `wavefront.log`:
+If the Wavefront proxy is unable to post received data to the Tanzu Observability servers, it buffers the data to disk across a number of buffer files, and then tries to resend the points once the connection to the Tanzu Observability servers is available again. If this buffering occurs, you'll see lines like this in `wavefront.log`:
```
2013-11-18 18:02:35,061 WARN [com.wavefront.daemon.QueuedSshDaemonService] current retry queue sizes: [1/0/0/0]
```
-By default, there are 4 threads (and 4 buffer files) waiting to retry points once the connections are up; this line shows how many blocks of points have been stored by each thread (in this case, the first thread has 1 block of queued points, while the second, third, and fourth threads all have 0 blocks). These lines are only printed when there are points in the queue; you'll never see a line with all 0's in the queue sizes. Once the connection to the Operations for Applications servers has been established, and all the threads have sent the past data to us, you'll see a single line like this in `wavefront.log`:
+By default, there are 4 threads (and 4 buffer files) waiting to retry points once the connections are up; this line shows how many blocks of points have been stored by each thread (in this case, the first thread has 1 block of queued points, while the second, third, and fourth threads all have 0 blocks). These lines are only printed when there are points in the queue; you'll never see a line with all 0's in the queue sizes. Once the connection to the Tanzu Observability servers has been established, and all the threads have sent the past data to us, you'll see a single line like this in `wavefront.log`:
```
2013-11-18 18:59:46,665 WARN [com.wavefront.daemon.QueuedSshDaemonService] retry queue has been cleared
@@ -219,7 +219,7 @@ Ex: 12878
deltaCountersAggregationIntervalSeconds
-
Interval between flushing aggregating delta counters to the Operations for Applications service. Use this property in conjunction with deltaCountersAggregationListenerPorts to send points to the port(s) in batches, thereby limiting the number of points per second. Default: 30
+
Interval between flushing aggregating delta counters to the Tanzu Observability service. Use this property in conjunction with deltaCountersAggregationListenerPorts to send points to the port(s) in batches, thereby limiting the number of points per second. Default: 30
Number of seconds.
Ex: 45
6.0
@@ -240,7 +240,7 @@ Ex: 5044
flushThreads
-
Number of threads that flush data to the server. Setting this value too high results in sending batches that are too small to the Operations for Applications service and wasting connections. Values between 6 and 16 are a good starting point. This setting is per listening port. Default: The number of available processors (min 4).
+
Number of threads that flush data to the server. Setting this value too high results in sending batches that are too small to the Tanzu Observability service and wasting connections. Values between 6 and 16 are a good starting point. This setting is per listening port. Default: The number of available processors (min 4).
Positive integer.
Ex: 16
3.14
@@ -269,14 +269,14 @@ Ex: 2003,2004
gzipCompression
-
If set to true, metric traffic from the proxy to the Operations for Applications endpoint is gzip-compressed. Default: true
+
If set to true, metric traffic from the proxy to the Tanzu Observability endpoint is gzip-compressed. Default: true
Boolean.
Ex: true
gzipCompressionLevel
-
Sets the gzip compression level if gzipCompression is enabled. Higher compression levels slightly reduces the volume of traffic between the proxy and the Operations for Applications service, but uses more CPU. Default: 4
+
Sets the gzip compression level if gzipCompression is enabled. Higher compression levels slightly reduces the volume of traffic between the proxy and the Tanzu Observability service, but uses more CPU. Default: 4
String to prepend before every metric name. For example, if you set prefix to production, a metric that is sent to the proxy as cpu.loadavg.1m is sent from the proxy to the Operations for Applications service as production.cpu.loadavg.1m. Default: none
+
String to prepend before every metric name. For example, if you set prefix to production, a metric that is sent to the proxy as cpu.loadavg.1m is sent from the proxy to the Tanzu Observability service as production.cpu.loadavg.1m. Default: none
A lowercase alphanumeric string, with periods separating segments. You do not need to include a trailing period.
HTTP proxy host to be used in configurations when direct HTTP connections to Operations for Applications instances are not possible. Must be used with proxyPort.
+
HTTP proxy host to be used in configurations when direct HTTP connections to Tanzu Observability instances are not possible. Must be used with proxyPort.
HTTP proxy port to be used in configurations when direct HTTP connections to Operations for Applications instances are not possible. Must be used with proxyHost.
+
HTTP proxy port to be used in configurations when direct HTTP connections to Tanzu Observability instances are not possible. Must be used with proxyHost.
Maximum number of points to send to the Operations for Applications service during each flush. Default: 40000
+
Maximum number of points to send to the Tanzu Observability service during each flush. Default: 40000
Positive integer.
Ex: 40000
pushFlushMaxHistograms
-
Maximum number of histograms to send to the Operations for Applications service during each flush. Default: 10000
+
Maximum number of histograms to send to the Tanzu Observability service during each flush. Default: 10000
Positive integer.
Ex: 10000
6.0
pushFlushMaxSpans
-
Maximum number of spans to send to the Operations for Applications service during each flush. Default: 5000
+
Maximum number of spans to send to the Tanzu Observability service during each flush. Default: 5000
Positive integer.
Ex: 5000
6.0
pushFlushMaxSpanLogs
-
Maximum number of span logs to send to the Operations for Applications service during each flush. Default: 1000
+
Maximum number of span logs to send to the Tanzu Observability service during each flush. Default: 1000
Positive integer.
Ex: 1000
6.0
pushListenerHttpBufferSize
-
Maximum allowed request size (in bytes) for incoming HTTP requests on Operations for Applications, OpenTSDB, or Graphite ports. Default: 16777216 (16MB).
+
Maximum allowed request size (in bytes) for incoming HTTP requests on Tanzu Observability, OpenTSDB, or Graphite ports. Default: 16777216 (16MB).
Ex: 8388608
4.31
pushListenerMaxReceivedLength
-
Maximum line length for received points in plaintext format on Operations for Applications, OpenTSDB, or Graphite ports. Default: 32KB
+
Maximum line length for received points in plaintext format on Tanzu Observability, OpenTSDB, or Graphite ports. Default: 32KB
Ports to receive the data sent to the relay. In environments where direct outbound connections to the Operations for Applications instance are not possible, you can use another Wavefront proxy that has outbound access to act as a relay and forward all the data received on that endpoint (from direct data ingestion clients and/or other proxies) to your Operations for Applications instance. Default: none
+
Ports to receive the data sent to the relay. In environments where direct outbound connections to the Tanzu Observability instance are not possible, you can use another Wavefront proxy that has outbound access to act as a relay and forward all the data received on that endpoint (from direct data ingestion clients and/or other proxies) to your Tanzu Observability instance. Default: none
Comma-separated list of available port numbers. Can be a single port.
Ex: 2978
Ex: 2978,2979
@@ -568,7 +568,7 @@ Ex: 2978,2979
pushValidationLevel
-
Level of validation to perform on incoming data before sending the data to the Operations for Applications service. If NO_VALIDATION, all data is sent forward. If NUMERIC_ONLY, data is checked to make sure that it is numerical and dropped locally if it is not.
+
Level of validation to perform on incoming data before sending the data to the Tanzu Observability service. If NO_VALIDATION, all data is sent forward. If NUMERIC_ONLY, data is checked to make sure that it is numerical and dropped locally if it is not.
NUMERIC_ONLY or NO_VALIDATION
Ex: NUMERIC_ONLY
@@ -605,7 +605,7 @@ Ex: 2978,2979
server
-
The API URL of the Operations for Applications instance in the format https://<your_instance>.wavefront.com/api/.
+
The API URL of the Tanzu Observability instance in the format https://<your_instance>.wavefront.com/api/.
@@ -712,7 +712,7 @@ Sets the headroom multiplier for traffic shaping when there's backlog.
Because the proxy is running in your local network by default, communication **to** the proxy is un-authenticated. If you want to authenticate inbound traffic to the proxy, use the settings in this section.
-The Wavefront proxy must authenticate outbound traffic to the Operations for Applications service. See [Authenticate Incoming HTTP Requests at the Proxy](proxies_configuring.html#authenticate-incoming-http-requests-at-the-proxy) for step-by-step instructions.
+The Wavefront proxy must authenticate outbound traffic to the Tanzu Observability service. See [Authenticate Incoming HTTP Requests at the Proxy](proxies_configuring.html#authenticate-incoming-http-requests-at-the-proxy) for step-by-step instructions.
@@ -836,14 +836,14 @@ Ex: token1234abcd
traceJaegerHttpListenerPorts
-
TCP ports to receive Jaeger Thrift formatted data via HTTP. The data is then sent to the Operations for Applications service in [Operations for Applications span format](trace_data_details.html#operations-for-applications-span-format).
+
TCP ports to receive Jaeger Thrift formatted data via HTTP. The data is then sent to the Tanzu Observability service in [Tanzu Observability span format](trace_data_details.html#tanzu-observability-span-format).
Default: none
Version: Since 6.0
Comma-separated list of available port numbers. Can be a single port.
traceJaegerListenerPorts
-
TCP ports to receive Jaeger Thrift formatted data via TChannel. The data is then sent to the Operations for Applications service in Operations for Applications span format. Default: none
+
TCP ports to receive Jaeger Thrift formatted data via TChannel. The data is then sent to the Tanzu Observability service in Tanzu Observability span format. Default: none
{% include warning.html content=" Sending data via TChannel has been deprecated in Jaeger 1.16. Therefore, we recommend using traceJaegerHttpListenerPorts to receive Jaeger Thrift formatted data via HTTP." %}
Comma-separated list of available port numbers. Can be a single port.
TCP ports to receive spans and derive RED metrics from the SDKs that send raw data to the Tanzu Observability service.
Default: None.
Version: Since 6.0
{% include note.html content=" The application name and service name tags are required to generate RED metrics. If these tags are not sent with your span, the application name defaults to wfProxy, and the service name defaults to defaultService."%}
@@ -874,20 +874,20 @@ Ex: token1234abcd
Ex: 1048576
traceListenerPorts
-
TCP ports that listen to incoming [spans](tracing_basics.html) from the Operations for Applications SDKs that [collect metrics and histograms](wavefront_sdks.html#sdks-for-collecting-metrics-and-histograms), and [SDKs for sending raw data](wavefront_sdks.html#sdks-for-sending-raw-data). Default: none
+
TCP ports that listen to incoming [spans](tracing_basics.html) from the Tanzu Observability SDKs that [collect metrics and histograms](wavefront_sdks.html#sdks-for-collecting-metrics-and-histograms), and [SDKs for sending raw data](wavefront_sdks.html#sdks-for-sending-raw-data). Default: none
Comma-separated list of available port numbers. Can be a single port.
Ex: 2878
Ex: 2878,2879
traceSamplingDuration
-
Minimum duration of the tracing spans that can be sent to the Operations for Applications service for [trace data sampling](trace_data_sampling.html). Default: 0 (send all generated spans).
+
Minimum duration of the tracing spans that can be sent to the Tanzu Observability service for [trace data sampling](trace_data_sampling.html). Default: 0 (send all generated spans).
Number of milliseconds.
Ex: 45
traceSamplingRate
-
Percentage of all generated spans to send to the Operations for Applications service for [trace data sampling](trace_data_sampling.html). Default: `1.0` (send all generated spans).
+
Percentage of all generated spans to send to the Tanzu Observability service for [trace data sampling](trace_data_sampling.html). Default: `1.0` (send all generated spans).
Number from 0.0 to 1.0.
Ex: .1
@@ -941,7 +941,7 @@ Ex: token1234abcd
### Histogram Configuration Properties
-Operations for Applications supports additional histogram configuration properties, shown in the following table. The **requirements** on the state directory and the effect of the two `persist` properties listed at the bottom of the table.
+Tanzu Observability supports additional histogram configuration properties, shown in the following table. The **requirements** on the state directory and the effect of the two `persist` properties listed at the bottom of the table.
Interval in milliseconds to check for histograms to be sent to a Operations for Applications service according to their histogramMinuteFlushSecs settings. Default: 1000
+
Interval in milliseconds to check for histograms to be sent to a Tanzu Observability service according to their histogramMinuteFlushSecs settings. Default: 1000
Time-to-live, in seconds, for a day granularity accumulation on the proxy (before the intermediary is sent to the Operations for Applications service). Default: 18000 (5 hours).
+
Time-to-live, in seconds, for a day granularity accumulation on the proxy (before the intermediary is sent to the Tanzu Observability service). Default: 18000 (5 hours).
Number of seconds to keep a new distribution bin open for new samples, before the intermediary is sent to the Operations for Applications service. Default: 70
+
Number of seconds to keep a new distribution bin open for new samples, before the intermediary is sent to the Tanzu Observability service. Default: 70
Time-to-live, in seconds, for an hour granularity accumulation on the proxy (before the intermediary is sent to the Operations for Applications service). Default: 4200
+
Time-to-live, in seconds, for an hour granularity accumulation on the proxy (before the intermediary is sent to the Tanzu Observability service). Default: 4200
Time-to-live, in seconds, for a minute granularity accumulation on the proxy (before the intermediary is sent to the Operations for Applications service). Default: 70
+
Time-to-live, in seconds, for a minute granularity accumulation on the proxy (before the intermediary is sent to the Tanzu Observability service). Default: 70
Directory for persistent proxy state, must be writable. Before being flushed to the Operations for Applications service, histogram data is persisted on the filesystem where the Wavefront proxy runs. If the files are corrupted or the files in the directory can't be accessed, the proxy reports the problem in its log and fails back to using in-memory structures. In this mode, samples can be lost if the proxy terminates without draining its queues. Default: /var/spool/wavefront-proxy.
+
Directory for persistent proxy state, must be writable. Before being flushed to the Tanzu Observability service, histogram data is persisted on the filesystem where the Wavefront proxy runs. If the files are corrupted or the files in the directory can't be accessed, the proxy reports the problem in its log and fails back to using in-memory structures. In this mode, samples can be lost if the proxy terminates without draining its queues. Default: /var/spool/wavefront-proxy.
A valid path on the local file system. {% include note.html content="A high PPS requires that the machine that the proxy is on has an appropriate amount of IOPS. We recommend about 1K IOPS with at least 8GB RAM on the machine that the proxy writes histogram data to. Recommended machine type: m4.xlarge." %}
@@ -1206,7 +1206,7 @@ Ex: 40
pushRelayHistogramAggregatorFlushSecs
-
Since 6.0. Interval in milliseconds to check for histograms that have accumulated at the relay ports before sending data to the Operations for Applications service. Only applicable if the pushRelayHistogramAggregator is set to true. Default: 70
+
Since 6.0. Interval in milliseconds to check for histograms that have accumulated at the relay ports before sending data to the Tanzu Observability service. Only applicable if the pushRelayHistogramAggregator is set to true. Default: 70
Number of milliseconds. Ex: 80
diff --git a/pages/doc/proxies_container.md b/pages/doc/proxies_container.md
index b67fb2551..15e2ad026 100644
--- a/pages/doc/proxies_container.md
+++ b/pages/doc/proxies_container.md
@@ -6,15 +6,15 @@ sidebar: doc_sidebar
permalink: proxies_container.html
summary: Configure Wavefront proxy and Telegraf in a Docker container
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports container proxy setup. This page discusses running a proxy and Telegraf agent as Docker containers, but the guidance (though not some specifics) applies to other container solutions as well.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports container proxy setup. This page discusses running a proxy and Telegraf agent as Docker containers, but the guidance (though not some specifics) applies to other container solutions as well.
## Run a Proxy in a Docker Container
You can run a proxy in a Docker container by running one of the following commands:
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The [proxy authentication](proxies_installing.html#proxy-authentication-types) to Operations for Applications differs for VMware Cloud services subscriptions and original subscriptions. For details, see [Subscription Types](subscriptions-differences.html).
-- For VMware Cloud services subscriptions, starting with version 13.0, the Wavefront proxy supports authentication to Operations for Applications with a VMware Cloud services API token or OAuth app.
-- For original Operations for Applications subscriptions, the Wavefront proxy 13.0 still supports authentication with Operations for Applications tokens. "%}
+{% include note.html content="Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. The [proxy authentication](proxies_installing.html#proxy-authentication-types) to Tanzu Observability differs for VMware Cloud services subscriptions and original subscriptions. For details, see [Subscription Types](subscriptions-differences.html).
+- For VMware Cloud services subscriptions, starting with version 13.0, the Wavefront proxy supports authentication to Tanzu Observability with a VMware Cloud services API token or OAuth app.
+- For original Tanzu Observability subscriptions, the Wavefront proxy 13.0 still supports authentication with Tanzu Observability tokens. "%}
**dockerhub:**
@@ -141,9 +141,9 @@ Options:
For VMware Cloud services subscriptions and proxy authentication with a server to server OAuth app, CSP_APP_ID and CSP_APP_SECRET are the server to server app credentials (ID and secret). The server to server app must be assigned with the Proxies service role and must be added to the VMware Cloud organization running the Operations for Applications service instance. CSP_ORG_ID is the ID of the VMware Cloud organization.
+
For VMware Cloud services subscriptions and proxy authentication with a server to server OAuth app, CSP_APP_ID and CSP_APP_SECRET are the server to server app credentials (ID and secret). The server to server app must be assigned with the Proxies service role and must be added to the VMware Cloud organization running the Tanzu Observability service instance. CSP_ORG_ID is the ID of the VMware Cloud organization.
For VMware Cloud services subscriptions and proxy authentication with an API token, CSP_API_TOKEN is the VMware Cloud services API token. The API token and its associated user account must be assigned with the Proxies service role.
-
For original subscriptions, WAVEFRONT_TOKEN is the Operations for Applications API token. The user account or service account associated with the API token must be assigned with the Proxies permission.
+
For original subscriptions, WAVEFRONT_TOKEN is the Tanzu Observability API token. The user account or service account associated with the API token must be assigned with the Proxies permission.
@@ -152,7 +152,7 @@ Options:
Service instance
-
<myinstance> is the URL of your Operations for Applications service, for example, https://example.wavefront.com
+
<myinstance> is the URL of your Tanzu Observability service, for example, https://example.wavefront.com
Port
@@ -294,9 +294,9 @@ Example: Run a command like the following for testing (see the Docker documentat
```
You must specify:
-* WAVEFRONT_URL: The URL of your Operations for Applications service (e.g., https://example.wavefront.com)
+* WAVEFRONT_URL: The URL of your Tanzu Observability service (e.g., https://example.wavefront.com)
* Authentication parameters for your [subscription type](subscriptions-differences.html) and authentication type:
- * For VMware Cloud services subscriptions and authentication with a [server to server OAuth app](csp_server_to_server_apps.html), CSP_APP_ID and CSP_APP_SECRET are the server to server app credentials (ID and secret). The server to server app must be assigned with the **Proxies** service role and must be added to the VMware Cloud organization running the Operations for Applications service instance. CSP_ORG_ID is the ID of the VMware Cloud organization.
+ * For VMware Cloud services subscriptions and authentication with a [server to server OAuth app](csp_server_to_server_apps.html), CSP_APP_ID and CSP_APP_SECRET are the server to server app credentials (ID and secret). The server to server app must be assigned with the **Proxies** service role and must be added to the VMware Cloud organization running the Tanzu Observability service instance. CSP_ORG_ID is the ID of the VMware Cloud organization.
* For VMware Cloud services subscriptions and authentication with an [API token](csp_users_account_managing.html#generate-an-api-token), CSP_API_TOKEN is the VMware Cloud services API token. The API token and its associated user account must be assigned with the **Proxies** service role.
- * For original subscriptions, WAVEFRONT_TOKEN is the [Operations for Applications API token](api_tokens.html). The user account or service account associated with the API token must be assigned with the **Proxies** permission.
+ * For original subscriptions, WAVEFRONT_TOKEN is the [Tanzu Observability API token](api_tokens.html). The user account or service account associated with the API token must be assigned with the **Proxies** permission.
* The port that the proxy is using; 2878 by default.
\ No newline at end of file
diff --git a/pages/doc/proxies_histograms.md b/pages/doc/proxies_histograms.md
index 512b776da..c8242b65c 100644
--- a/pages/doc/proxies_histograms.md
+++ b/pages/doc/proxies_histograms.md
@@ -7,7 +7,7 @@ published: true
permalink: proxies_histograms.html
summary: Learn how to use histograms.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports histograms for computing, storing, and using **distributions of metrics** rather than single metrics. Histograms are useful for high-velocity metrics about your applications and infrastructure – particularly those gathered across many distributed sources. You can send histograms to a Wavefront proxy or use direct ingestion.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports histograms for computing, storing, and using **distributions of metrics** rather than single metrics. Histograms are useful for high-velocity metrics about your applications and infrastructure – particularly those gathered across many distributed sources. You can send histograms to a Wavefront proxy or use direct ingestion.
This page explain how to send histogram distributions. After the data is available, you can [visualize histogram distributions](visualize_histograms.html) using Histogram charts or Heatmap charts.
@@ -26,7 +26,7 @@ The following blog posts give some background information:
## Why Use Histograms?
-Operations for Applications can receive and store highly granular metrics at 1 point per second per unique source. However, some scenarios generate even higher frequency data.
+Tanzu Observability can receive and store highly granular metrics at 1 point per second per unique source. However, some scenarios generate even higher frequency data.
Suppose you are measuring the latency of web requests. If you have a lot of traffic at multiple servers, you may have multiple distinct measurements for a given metric,
timestamp, and source. Using "normal" metrics, we can't measure this because, rather than metric-timestamp-source mapping to a single value, the composite key maps to a [multiset](https://en.wikipedia.org/wiki/Multiset) (multiple and possibly duplicate values).
@@ -34,13 +34,13 @@ timestamp, and source. Using "normal" metrics, we can't measure this because, ra
One approach to dealing with high frequency data is to calculate an aggregate statistic, such as a percentile, at each source and send only that data. The problem with this approach is that performing an aggregate of a percentile (such as
a 95th percentile from a variety of sources) does not yield an accurate and valid percentile with high velocity metrics. That might mean that even though you have an outlier in some of the source data, it becomes obscured by all the other data.
-### Operations for Applications Histograms Overview
+### Tanzu Observability Histograms Overview
-To address high frequency data, Operations for Applications supports histograms -- a mechanism to compute, store, and use distributions of metrics. You have several options:
-* Send metrics in Operations for Applications data format to a histogram proxy port. The Operations for Applications service:
+To address high frequency data, Tanzu Observability supports histograms -- a mechanism to compute, store, and use distributions of metrics. You have several options:
+* Send metrics in Tanzu Observability data format to a histogram proxy port. The Tanzu Observability service:
- Converts the metrics to histogram distributions
- Adds the extension `.m`, `.h`, or `.d` (for minute, hour, or day distributions).
-* Convert the metric to histogram format on your side and send them in Operations for Applications histogram format (prefix `M!`, `H!`, or `D!`, discussed below)
+* Convert the metric to histogram format on your side and send them in Tanzu Observability histogram format (prefix `M!`, `H!`, or `D!`, discussed below)
* Specify `f=histogram` as part of the [direct ingestion command](direct_ingestion.html#histogram-distribution).
You can query histograms with a set of [functions](query_language_reference.html#histogram-functions) and display them using a histogram charts or heatmap or other chart types.
@@ -60,9 +60,9 @@ In addition to these PPS savings, you will also get all the benefits of histogra
A histogram distribution allows you to combine multiple points into a complex value that has a single timestamp. You can either send metrics data to a specialized histogram port, or send histogram data to a proxy port that accepts histogram data.
-### Send Data in Operations for Applications Histogram Format
+### Send Data in Tanzu Observability Histogram Format
-You can send data in Operations for Applications **histogram** format, which includes the aggregation interval, to a proxy port that is accepting histogram data. The ports are defined by `pushListenerPorts` (default: 2878) or `histogramDistListenerPorts` (default: 40000) in the proxy configuration file.
+You can send data in Tanzu Observability **histogram** format, which includes the aggregation interval, to a proxy port that is accepting histogram data. The ports are defined by `pushListenerPorts` (default: 2878) or `histogramDistListenerPorts` (default: 40000) in the proxy configuration file.
Here's the syntax:
@@ -85,13 +85,13 @@ Here's the syntax:
is a distribution that sends 20 points of the metric `request.latency` with value 30, and 10 points with value 5, that have been aggregated into minute intervals.
- {% include note.html content="Unlike the Operations for Applications data format, which is ``, histogram data format inverts the ordering of components in a data point: ` #`." %}
+ {% include note.html content="Unlike the Tanzu Observability data format, which is ``, histogram data format inverts the ordering of components in a data point: ` #`." %}
You can also send a histogram distribution using [direct ingestion](direct_ingestion.html#histogram-distribution). In that case, you must include `f=histogram` or your data are treated as metrics even if you use histogram data format.
-### Send Data in Operations for Applications Data Format
+### Send Data in Tanzu Observability Data Format
-You can send metric data in Operations for Applications **data** format to one of the **histogram aggregation ports**. Different ports are for different aggregation intervals. Here are the defaults, see [Histogram Aggregation Ports](#histogram-aggregation-ports) for details.
+You can send metric data in Tanzu Observability **data** format to one of the **histogram aggregation ports**. Different ports are for different aggregation intervals. Here are the defaults, see [Histogram Aggregation Ports](#histogram-aggregation-ports) for details.
* minute - 40001
* hour - 40002
@@ -127,7 +127,7 @@ Histogram data format includes:
### Option 2: Convert Metrics to Histogram by Using Histogram Proxy Port
-You can send the data in [Operations for Applications data format](wavefront_data_format.html) to one of the histogram aggregation proxy ports (for this example, we use the hour port, which defaults to 40002). Here are the requirements:
+You can send the data in [Tanzu Observability data format](wavefront_data_format.html) to one of the histogram aggregation proxy ports (for this example, we use the hour port, which defaults to 40002). Here are the requirements:
* You have to send each point separately and include a timestamp
* All points have to arrive within the time interval (in this example, within the hour).
@@ -141,11 +141,11 @@ my.metric 100
my.metric 100
```
-The proxy aggregates the points and sends only the histogram distribution to the Operations for Applications service. The Operations for Applications service knows only what each bin is and how many points are in each bin. The service doesn't store the value of each single histogram point, it computes and stores the distribution.
+The proxy aggregates the points and sends only the histogram distribution to the Tanzu Observability service. The Tanzu Observability service knows only what each bin is and how many points are in each bin. The service doesn't store the value of each single histogram point, it computes and stores the distribution.
## Histogram Functions
-After the histogram have been sent to the Operations for Applications service, you can manipulate the data with [histogram functions](query_language_reference.html#histogram-functions).
+After the histogram have been sent to the Tanzu Observability service, you can manipulate the data with [histogram functions](query_language_reference.html#histogram-functions).
For example, you can try to find out what the 85th percentile of the histogram is by writing a query like this:
@@ -190,19 +190,19 @@ The port you use depends on your intention.
@@ -210,13 +210,13 @@ The port you use depends on your intention.
Send [**distribution data format**](#sending-histogram-distributions) histogram data only to the distribution port. If you send histogram distribution data format to `min`, `hour`, or `day` ports, the points are rejected as invalid input format and logged.
-Send [**Operations for Applications data format**](wavefront_data_format.html) histogram data only to a minute, hour, or day port.
-* If you send Operations for Applications data format histogram data to the distribution port, the points are rejected as invalid input format and logged.
-* If you send Operations for Applications data format histogram data to port 2878 (instead of a min, hour, or day port), the data is not ingested as histogram data but as regular Operations for Applications data format metrics.
+Send [**Tanzu Observability data format**](wavefront_data_format.html) histogram data only to a minute, hour, or day port.
+* If you send Tanzu Observability data format histogram data to the distribution port, the points are rejected as invalid input format and logged.
+* If you send Tanzu Observability data format histogram data to port 2878 (instead of a min, hour, or day port), the data is not ingested as histogram data but as regular Tanzu Observability data format metrics.
-## How the Operations for Applications Service Creates Histogram Distributions
+## How the Tanzu Observability Service Creates Histogram Distributions
-The Operations for Applications service creates distributions by aggregating metrics into bins. The following figure illustrates a distribution of 205 points that range in value from 0 to 120 at t = 1 minute, into bins of size 10.
+The Tanzu Observability service creates distributions by aggregating metrics into bins. The following figure illustrates a distribution of 205 points that range in value from 0 to 120 at t = 1 minute, into bins of size 10.
@@ -259,7 +259,7 @@ Histograms do not store each actual data point value that is fed to it. Instead,
### Histogram Metric Aggregation Intervals
-Operations for Applications supports aggregating metrics by the minute, hour, or day. Intervals start and end on the minute, hour, or day, depending on the granularity that you choose. For example, day-long intervals start at the beginning of each day, UTC time zone.
+Tanzu Observability supports aggregating metrics by the minute, hour, or day. Intervals start and end on the minute, hour, or day, depending on the granularity that you choose. For example, day-long intervals start at the beginning of each day, UTC time zone.
The aggregation intervals do not overlap. If you are aggregating by the minute, a value reported at 13:58:37 is assigned to the interval `[13:58:00;13:59:00]`. If no metrics are sent during an interval, no histogram points are recorded.
diff --git a/pages/doc/proxies_installing.md b/pages/doc/proxies_installing.md
index 80a096bf8..d42a215eb 100644
--- a/pages/doc/proxies_installing.md
+++ b/pages/doc/proxies_installing.md
@@ -5,15 +5,15 @@ sidebar: doc_sidebar
permalink: proxies_installing.html
summary: Learn how to install and manage Wavefront proxies.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) offers several [deployment options](proxies.html#proxy-deployment-options). During development, a single proxy is often sufficient for all data sources. In production, place a team of proxies behind a load balancer.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) offers several [deployment options](proxies.html#proxy-deployment-options). During development, a single proxy is often sufficient for all data sources. In production, place a team of proxies behind a load balancer.
-In most cases, a Wavefront proxy must be running in your environment before metrics begin streaming to your Operations for Applications service from a host or application.
+In most cases, a Wavefront proxy must be running in your environment before metrics begin streaming to your Tanzu Observability service from a host or application.
{% include note.html content="You must have the [**Proxies** permission](permissions_overview.html) to install and manage Wavefront proxies." %}
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
-- For VMware Cloud services subscriptions, starting with version 13.0, the Wavefront proxy supports authentication to Operations for Applications with a VMware Cloud services access token.
-- For original Operations for Applications subscriptions, the Wavefront proxy 13.0 still supports authentication with an Operations for Applications API token."%}
+{% include note.html content="Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
+- For VMware Cloud services subscriptions, starting with version 13.0, the Wavefront proxy supports authentication to Tanzu Observability with a VMware Cloud services access token.
+- For original Tanzu Observability subscriptions, the Wavefront proxy 13.0 still supports authentication with a Tanzu Observability API token."%}
## Proxy Host Requirements
@@ -35,10 +35,10 @@ In most cases, a Wavefront proxy must be running in your environment before metr
## Proxy Authentication Types
-* If your Operations for Applications service instance **is** onboarded to VMware Cloud services, the proxy requires a VMware Cloud services access token with the **Proxies** [service role](csp_users_roles.html#operations-for-applications-service-roles-built-in). There are two options for the proxy to retrieve an access token. You can configure the proxy with:
+* If your Tanzu Observability service instance **is** onboarded to VMware Cloud services, the proxy requires a VMware Cloud services access token with the **Proxies** [service role](csp_users_roles.html#tanzu-observability-service-roles-built-in). There are two options for the proxy to retrieve an access token. You can configure the proxy with:
* The credentials (ID and secret) of a VMware Cloud services server to server **OAuth app** and the ID of the VMware Cloud organization running the service.
- Before you add a proxy with an OAuth app, you must retrieve the credentials (ID and secret) of a server to server app that is assigned with the **Proxies** Operations for Applications service role and added to the VMware Cloud organization running the service. See [How to use OAuth 2.0 for server to server apps](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-327AE12A-85DB-474B-89B2-86651DF91C77.html?hWord=N4IgpgHiBcIMpgE4DckAIAuB7NBnJqiaAhgA6kgC+QA) in the VMware Cloud services documentation.
+ Before you add a proxy with an OAuth app, you must retrieve the credentials (ID and secret) of a server to server app that is assigned with the **Proxies** Tanzu Observability service role and added to the VMware Cloud organization running the service. See [How to use OAuth 2.0 for server to server apps](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-327AE12A-85DB-474B-89B2-86651DF91C77.html?hWord=N4IgpgHiBcIMpgE4DckAIAuB7NBnJqiaAhgA6kgC+QA) in the VMware Cloud services documentation.
Also, you must retrieve the VMware Cloud organization long ID. See [View the Organization ID](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-CF9E9318-B811-48CF-8499-9419997DC1F8.html#view-the-organization-id-1) in the VMware Cloud services documentation.
@@ -50,7 +50,7 @@ In most cases, a Wavefront proxy must be running in your environment before metr
{% include important.html content="You might need to regenerate and reconfigure the API token periodically depending on its TTL configuration."%}
-* If your Operations for Applications service instance **isn't** onboarded to VMware Cloud services, the proxy requires an Operations for Applications **API token**.
+* If your Tanzu Observability service instance **isn't** onboarded to VMware Cloud services, the proxy requires a Tanzu Observability **API token**.
Before you add a proxy, you must have an API token associated with your user account or a service account with the **Proxies** permission. See [Manage API Tokens](api_tokens.html) for details.
@@ -58,7 +58,7 @@ In most cases, a Wavefront proxy must be running in your environment before metr
Many users install a proxy when they set up an integration. You can also install a proxy from the UI or perform a scripted installation manually.
-{% include note.html content="In development, many customers use only one proxy that receives data from many applications and sends those data to Operations for Applications. In production, consider using two proxies behind a load balancer. See [Proxy Deployment Options](proxies.html#proxy-deployment-options)." %}
+{% include note.html content="In development, many customers use only one proxy that receives data from many applications and sends those data to Tanzu Observability. In production, consider using two proxies behind a load balancer. See [Proxy Deployment Options](proxies.html#proxy-deployment-options)." %}
### Install a Proxy from the UI
diff --git a/pages/doc/proxies_kube_container.md b/pages/doc/proxies_kube_container.md
index 2ee6355bc..aaa906750 100644
--- a/pages/doc/proxies_kube_container.md
+++ b/pages/doc/proxies_kube_container.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: proxies_kube_container.html
summary: Run a Wavefront proxy in a Kubernetes container and customize it.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports setting up the Wavefront proxy to run [in a Kubernetes container](kubernetes.html#kubernetes-manual-install). However, you cannot rely on a single `wavefront.conf` file. Instead, a ConfigMap file governs deployment.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports setting up the Wavefront proxy to run [in a Kubernetes container](kubernetes.html#kubernetes-manual-install). However, you cannot rely on a single `wavefront.conf` file. Instead, a ConfigMap file governs deployment.
1. Create a custom ConfigMap file that contains the custom setup, for example preprocessing rules, for your proxy configuration. This doc page creates a `00_proxy-preprocessor-config.yaml` file.
2. Edit `wavefront.yaml` so it points to the ConfigMap file.
@@ -16,7 +16,7 @@ VMware Aria Operations for Applications (formerly known as Tanzu Observability b
This section illustrates how to use a custom ConfigMap to block traffic for some metrics via preprocessor rules. You can use the same approach to, for example, have the Wavefront proxy use an HTTPS proxy.
-In this section, we first create a custom ConfigMap (`00_proxy-preprocessor-config.yaml`) that includes preprocessor rules to block metrics. Then we customize the `wavefront.yaml` so it points to our Operations for Applications service instance, includes the proxy authentication, and points to the ConfigMap file.
+In this section, we first create a custom ConfigMap (`00_proxy-preprocessor-config.yaml`) that includes preprocessor rules to block metrics. Then we customize the `wavefront.yaml` so it points to our Tanzu Observability service instance, includes the proxy authentication, and points to the ConfigMap file.
**1.** Create a file called `00_proxy-preprocessor-config.yaml` with content like the following. This sample file includes some examples of preprocessor rules that block certain metrics.
diff --git a/pages/doc/proxies_manual_install.md b/pages/doc/proxies_manual_install.md
index ec002782e..fe5e1b46d 100644
--- a/pages/doc/proxies_manual_install.md
+++ b/pages/doc/proxies_manual_install.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: proxies_manual_install.html
summary: Learn how to manually install a Wavefront proxy and Telegraf agent.
---
-Most VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) customers use an automated proxy install:
+Most Tanzu Observability (formerly known as VMware Aria Operations for Applications) customers use an automated proxy install:
* Option 1: Install the Wavefront proxy and the Telegraf agent when the set up an integration.
* Option 2: Perform a [scripted installation](proxies_installing.html#scripted-proxy-installation) of the Wavefront proxy and Telegraf agent.
@@ -20,7 +20,7 @@ Follow these steps to install a proxy on a host with full network access (incomi
### Prerequisites
-- **Networking:** [Test connectivity](proxies_manual_install.html#testing-proxy-host-connectivity) between the target proxy host and your Operations for Applications service.
+- **Networking:** [Test connectivity](proxies_manual_install.html#testing-proxy-host-connectivity) between the target proxy host and your Tanzu Observability service.
{% include important.html content="For VMware Cloud services subscriptions, to retrieve a VMware Cloud services access token, the Wavefront proxy calls the VMware Cloud services API. For that reason, you must also test connectivity between the target proxy host and the VMware Cloud services platform (`https://console.cloud.vmware.com/`). For details about original and VMware Cloud services subscriptions, see [Subscription Types](subscriptions-differences.html)."%}
@@ -48,24 +48,24 @@ Before you can customize the proxy configuration, you have to find the values fo
**server**
-
URL of your Operations for Applications service instance.
+
URL of your Tanzu Observability service instance.
https://try.wavefront.com/api/
token
-
A valid Operations for Applications token associated with an active user or service account. The account must have the Proxies permission.
Note: Applies only to original Operations for Applications subscriptions that are not onboarded to VMware Cloud services, i.e. when the proxy authenticates to Operations for Applications with an Operations for Applications API token.
+
A valid Tanzu Observability token associated with an active user or service account. The account must have the Proxies permission.
Note: Applies only to original Tanzu Observability subscriptions that are not onboarded to VMware Cloud services, i.e. when the proxy authenticates to Tanzu Observability with a Tanzu Observability API token.
cspAppId
cspAppSecret
cspOrgId
-
Server to server OAuth app credentials - ID and secret (cspAppId and cspAppSecret), and the VMware Cloud organization ID (cspOrgId) running the Operations for Applications service instance. The server to server app must have the Proxies service role and must belong to the VMware Cloud organization running the Operations for Applications service instance.
-
Note: Applies only to Operations for Applications subscriptions on VMware Cloud services if the proxy authenticates to Operations for Applications with a VMware Cloud services OAuth app.
+
Server to server OAuth app credentials - ID and secret (cspAppId and cspAppSecret), and the VMware Cloud organization ID (cspOrgId) running the Tanzu Observability service instance. The server to server app must have the Proxies service role and must belong to the VMware Cloud organization running the Tanzu Observability service instance.
+
Note: Applies only to Tanzu Observability subscriptions on VMware Cloud services if the proxy authenticates to Tanzu Observability with a VMware Cloud services OAuth app.
cspAPIToken
A valid VMware Cloud services API token associated with an active user account. The user and the token must have the Proxies service role.
-
Note: Applies only to Operations for Applications subscriptions on VMware Cloud services if the proxy authenticates to Operations for Applications with a VMware Cloud services token.
+
Note: Applies only to Tanzu Observability subscriptions on VMware Cloud services if the proxy authenticates to Tanzu Observability with a VMware Cloud services token.
@@ -145,7 +145,7 @@ In some cases, you might need to run the proxy on a host with limited network ac
### Prerequisites
-- **Networking:** The minimum requirement is an outbound HTTPS connection to your Operations for Applications service, so the proxy can send metrics to the service. For metrics, by default the proxy uses port 2878. You can change this port and you can configure [separate proxy ports](proxies_configuring.html#configuration-properties) for histograms and traces.
+- **Networking:** The minimum requirement is an outbound HTTPS connection to your Tanzu Observability service, so the proxy can send metrics to the service. For metrics, by default the proxy uses port 2878. You can change this port and you can configure [separate proxy ports](proxies_configuring.html#configuration-properties) for histograms and traces.
{% include important.html content="For VMware Cloud services subscriptions, to retrieve a VMware Cloud services access token, the Wavefront proxy calls the VMware Cloud services API. For that reason, your environment must also allow an outbound HTTPS connection to the VMware Cloud services platform (`https://console.cloud.vmware.com/`). For details about original and VMware Cloud services subscriptions, see [Subscription Types](subscriptions-differences.html)."%}
@@ -159,7 +159,7 @@ In some cases, you might need to run the proxy on a host with limited network ac
Installation and configuration is similar to environments with full network access but might require additional work.
-1. Make sure all prerequisites are met, including an open outgoing HTTPS connection to your Operations for Applications service and JRE.
+1. Make sure all prerequisites are met, including an open outgoing HTTPS connection to your Tanzu Observability service and JRE.
2. Install the .rpm or .deb file.
3. Update the settings, either by editing the configuration file or by running the autoconf script, as explained above.
4. You may need to update the Wavefront proxy control file `/etc/init.d/wavefront.proxy` to the following settings:
@@ -266,7 +266,7 @@ You can test your proxy using `curl`. Documentation for the following `curl` com
You can run the commands [directly from the API documentation](https://tanzu.vmware.com/content/vmware-aria-operations-for-applications-blog/did-you-know-that-our-api-docs-are-alive). This is less error prone than copy/paste of the token.
-For this task, you first get the list of proxies for your Operations for Applications service, then you display information for just the proxy you installed.
+For this task, you first get the list of proxies for your Tanzu Observability service, then you display information for just the proxy you installed.
Step 1: Get the list of proxies for your service instance:
```
@@ -315,9 +315,9 @@ Sample output for single proxy:
## Configure Wavefront Proxy with an HTTP/HTTPS Proxy
-The Wavefront proxy initiates an HTTPS connection to your Operations for Applications service. The connection is made over the default HTTPS port 443.
+The Wavefront proxy initiates an HTTPS connection to your Tanzu Observability service. The connection is made over the default HTTPS port 443.
-Instead of sending traffic directly, you can send traffic from the Wavefront proxy to an HTTP or HTTPS proxy, which forwards to the Operations for Applications service. You set the connection parameters in the `wavefront.conf` file (`/etc/wavefront/wavefront-proxy/wavefront.conf` by default). See
+Instead of sending traffic directly, you can send traffic from the Wavefront proxy to an HTTP or HTTPS proxy, which forwards to the Tanzu Observability service. You set the connection parameters in the `wavefront.conf` file (`/etc/wavefront/wavefront-proxy/wavefront.conf` by default). See
* [the sample conf file on Github](https://github.com/wavefrontHQ/wavefront-proxy/blob/master/pkg/etc/wavefront/wavefront-proxy/wavefront.conf.default)
* Some detail on [configuration options](proxies_configuring.html).
@@ -329,7 +329,7 @@ Instead of sending traffic directly, you can send traffic from the Wavefront pro
By default, the HTTP/HTTPS proxy section is commented out. Uncomment the section in `wavefront.conf` if you want to use an HTTP/HTTPS proxy, and specify the following information:
```
-## The following settings are used to connect to an Operations for Applications service instance through a HTTP proxy:
+## The following settings are used to connect to a Tanzu Observability service instance through a HTTP proxy:
#proxyHost=
#proxyPort=
## Optional: if http/https proxy supports username/password authentication
@@ -409,14 +409,14 @@ Sometimes, the output from one Wavefront proxy needs to be sent to another Wavef
Common use cases include:
-* **Restrictions on outbound connections**: In environments where no direct outbound connections to Operations for Applications are possible, you can use a Wavefront proxy that has outbound access to act as a relay and forward data received on its endpoint to the Operations for Applications service.
-* **Log data filtering**: If you use a proxy to parse log data, you might need to perform filtering or tagging with proxy preprocessor rules. One proxy in a chain can have the job of altering or dropping certain strings before data is sent to Operations for Applications.
+* **Restrictions on outbound connections**: In environments where no direct outbound connections to Tanzu Observability are possible, you can use a Wavefront proxy that has outbound access to act as a relay and forward data received on its endpoint to the Tanzu Observability service.
+* **Log data filtering**: If you use a proxy to parse log data, you might need to perform filtering or tagging with proxy preprocessor rules. One proxy in a chain can have the job of altering or dropping certain strings before data is sent to Tanzu Observability.
* **Preprocessor rule consolidation**: Proxy chaining can consolidate preprocessing rules to a central proxy. For example, proxies running in containers on a Kubernetes cluster could relay metrics to the chained proxy which has all required defined preprocessor rules.
### Set Up the Configuration Files for Chaining
-Let's set up proxy chaining. Proxy A sends data to the relay proxy (Proxy B). Proxy B then sends data to the Operations for Applications service. Follow these steps:
+Let's set up proxy chaining. Proxy A sends data to the relay proxy (Proxy B). Proxy B then sends data to the Tanzu Observability service. Follow these steps:
1. On the proxy which will act as the relay (Proxy B) open the proxy configuration file (`wavefront.conf`) for edit. See [Proxy File Paths](proxies_configuring.html#proxy-file-paths) for the default location.
2. Uncomment the `pushRelayListenerPorts` line so the proxy will listen for any relay messages.
@@ -429,11 +429,11 @@ Let's set up proxy chaining. Proxy A sends data to the relay proxy (Proxy B). Pr
4. Change the server address to the address of relay (Proxy B). Here's an example:
```
- # The server should be either the primary Operations for Applications cloud server, or your custom VPC address.
- # This will be provided to you by the Operations for Applications team.
+ # The server should be either the primary Tanzu Observability cloud server, or your custom VPC address.
+ # This will be provided to you by the Tanzu Observability team.
server=http://192.168.xxx.xxx:2978/api/
```
- The authentication token that is specified in the `wavefront.conf` of the relay proxy (Proxy B) will be used to send the metrics to the Operations for Applications instances. An authentication token for Proxy A is not needed.
+ The authentication token that is specified in the `wavefront.conf` of the relay proxy (Proxy B) will be used to send the metrics to the Tanzu Observability instances. An authentication token for Proxy A is not needed.
5. After making the changes, restart both proxies and examine the `wavefront.log` file from the relay proxy (Proxy B). Look for points that are delivered on the relay listener port, as in the following example:
diff --git a/pages/doc/proxies_preprocessor_rules.md b/pages/doc/proxies_preprocessor_rules.md
index 54b222705..494ab38b9 100644
--- a/pages/doc/proxies_preprocessor_rules.md
+++ b/pages/doc/proxies_preprocessor_rules.md
@@ -7,7 +7,7 @@ permalink: proxies_preprocessor_rules.html
summary: Learn how to write proxy preprocessor rules.
---
-For fine-grained control before data are sent to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront), the Wavefront proxy supports:
+For fine-grained control before data are sent to Tanzu Observability (formerly known as VMware Aria Operations for Applications), the Wavefront proxy supports:
* Point filtering and point altering rules
* Span filtering and span altering rules
@@ -19,7 +19,7 @@ This page explains how to write these preprocessor rules, and includes many exam
## Overview
-The Wavefront proxy includes a preprocessor that applies rules before data is sent to Operations for Applications. The rules make it possible to address data quality issues in the data flow when it's not possible to fix the problem at the source. For example, you could have a rule "before the point line is parsed, replace invalid characters with underscores" to allow points that would be rejected to get to Operations for Applications.
+The Wavefront proxy includes a preprocessor that applies rules before data is sent to Tanzu Observability. The rules make it possible to address data quality issues in the data flow when it's not possible to fix the problem at the source. For example, you could have a rule "before the point line is parsed, replace invalid characters with underscores" to allow points that would be rejected to get to Tanzu Observability.
You can limit when a rule applies using the `if` parameter (proxy 7.0 and later). See [Preprocessor Rule Conditions](proxies_preprocessor_rule_conditions.html) for details.
@@ -131,7 +131,7 @@ For earlier versions of the proxy, you have to [restart the proxy](proxies_insta
### Interactive Testing of Preprocessor Rules
-You can test a preprocessor rule before sending data to your Operations for Applications service using `-testPreprocessorForPort `.
+You can test a preprocessor rule before sending data to your Tanzu Observability service using `-testPreprocessorForPort `.
How you run the proxy in test mode depends on whether you're using the JVM bundled with the Wavefront proxy. In that case, if the proxy installer detects that java v8, 9, 10 or, 11 already exists in the users path that version of Java is used.
@@ -180,7 +180,7 @@ Defines a regex that points must match to be filtered out.
scope
Any of the following:
-
pointLine—Rule applies to the whole point line before it's parsed (can be used with Operations for Applications and Graphite data formats only).
+
pointLine—Rule applies to the whole point line before it's parsed (can be used with Tanzu Observability and Graphite data formats only).
metricName—Rule applies only to the metric name after the point is parsed.
sourceName—Rule applies only to the source name after the point is parsed.
<point tag>—Rule applies to the value of the specified point tag key after the point is parsed.
@@ -237,7 +237,7 @@ Points must match the `allow` list to be accepted. Multiple `allow` rules are al
scope
Any of the following:
-
pointLine—Rule applies to the whole point line before it's parsed (can be used with Operations for Applications and Graphite data formats only).
+
pointLine—Rule applies to the whole point line before it's parsed (can be used with Tanzu Observability and Graphite data formats only).
metricName—Rule applies only to the metric name after the point is parsed.
sourceName—Rule applies only to the source name after the point is parsed.
<point tag>—Rule applies to the value of the specified point tag key after the point is parsed.
@@ -296,12 +296,12 @@ Enables you to pass only metrics that are provided in a `preprocessor_rules.yaml
function
-
allow -- Sends only metrics that match one of the entries listed in names to the Operations for Applications service. All other metrics are dropped.
-
drop -- Drops all metrics that match one of the entries listed in names. All other metrics are sent on to the Operations for Applications service.
+
allow -- Sends only metrics that match one of the entries listed in names to the Tanzu Observability service. All other metrics are dropped.
+
drop -- Drops all metrics that match one of the entries listed in names. All other metrics are sent on to the Tanzu Observability service.
names
-
List of exact metric names or regular expressions. The list specifies which metrics are sent to the Operations for Applications service or which are dropped. Regular expressions must start and end with `/`.
+
List of exact metric names or regular expressions. The list specifies which metrics are sent to the Tanzu Observability service or which are dropped. Regular expressions must start and end with `/`.
@@ -336,7 +336,7 @@ The example:
Point altering rules allow you to:
-* Replace text in the point line. The point line uses the Operations for Applications data format input format:
+* Replace text in the point line. The point line uses the Tanzu Observability data format input format:
` [] source= [pointTags]`
* Add, remove, or update point tags.
@@ -367,7 +367,7 @@ Replaces arbitrary text in the point line or any of its components:
scope
Any of the following:
-
pointLine—Rule applies to the whole point line before it's parsed (can be used with Operations for Applications and Graphite data formats only).
+
pointLine—Rule applies to the whole point line before it's parsed (can be used with Tanzu Observability and Graphite data formats only).
metricName—Rule applies only to the metric name after the point is parsed.
sourceName—Rule applies only to the source name after the point is parsed.
<point tag>—Rule applies to the value of the specified point tag key after the point is parsed.
@@ -544,7 +544,7 @@ extractTagIfNotExists
source
Any of the following:
-
pointLine—Rule applies to the whole point line before it's parsed (can be used with Operations for Applications and Graphite data formats only).
+
pointLine—Rule applies to the whole point line before it's parsed (can be used with Tanzu Observability and Graphite data formats only).
metricName—Rule applies only to the metric name after the point is parsed.
sourceName—Rule applies only to the source name after the point is parsed.
<point tag>—Rule applies to the value of the specified point tag key after the point is parsed.
@@ -664,7 +664,7 @@ Converts metric name, source name, or point tag value to lowercase.
scope
Any of the following:
-
pointLine—Rule applies to the whole point line before it's parsed (can be used with Operations for Applications and Graphite data formats only).
+
pointLine—Rule applies to the whole point line before it's parsed (can be used with Tanzu Observability and Graphite data formats only).
metricName—Rule applies only to the metric name after the point is parsed.
sourceName—Rule applies only to the source name after the point is parsed.
<point tag>—Rule applies to the value of the specified point tag key after the point is parsed.
@@ -714,7 +714,7 @@ Enforces string length limits for a metric name, source name, or point tag value
scope
Any of the following:
-
pointLine—Rule applies to the whole point line before it's parsed (can be used with Operations for Applications and Graphite data formats only).
+
pointLine—Rule applies to the whole point line before it's parsed (can be used with Tanzu Observability and Graphite data formats only).
metricName—Rule applies only to the metric name after the point is parsed.
sourceName—Rule applies only to the source name after the point is parsed.
<point tag>—Rule applies to the value of the specified point tag key after the point is parsed.
@@ -769,7 +769,7 @@ The following example illustrates using a `limitLength` for a point tag. The lim
## Span Filtering Rules
-[Operations for Applications distributed tracing](tracing_basics.html) gives you end-to-end visibility into an entire request across application services by allowing you to examine traces and spans. Span filtering rules allow you to specify a block list or allow list that determines which spans the proxy sends to Operations for Applications.
+[Tanzu Observability distributed tracing](tracing_basics.html) gives you end-to-end visibility into an entire request across application services by allowing you to examine traces and spans. Span filtering rules allow you to specify a block list or allow list that determines which spans the proxy sends to Tanzu Observability.
{% include tip.html content="The span filtering rules and span altering rules apply to data coming from any supported source, including Jaeger and Zipkin." %}
diff --git a/pages/doc/proxies_troubleshooting.md b/pages/doc/proxies_troubleshooting.md
index f3de61442..e23e7126d 100644
--- a/pages/doc/proxies_troubleshooting.md
+++ b/pages/doc/proxies_troubleshooting.md
@@ -7,13 +7,13 @@ permalink: proxies_troubleshooting.html
summary: Troubleshoot proxy problems.
---
-Wavefront proxies give you a lot of flexibility and control over proxies in your VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) environment. But with flexibility comes the potential for problems, so it's a best practice to [monitor you proxies](monitoring_proxies.html). For example, on the Proxies Browser page, you can see the account used to set up a specific proxy.
+Wavefront proxies give you a lot of flexibility and control in your Tanzu Observability (formerly known as VMware Aria Operations for Applications) environment. But with flexibility comes the potential for problems, so it's a best practice to [monitor you proxies](monitoring_proxies.html). For example, on the Proxies Browser page, you can see the account used to set up a specific proxy.
In addition, our SaaS Value Engineering team has put together the following troubleshooting advice.
## Validate Metrics Received at the Proxy
-As part of troubleshooting, it's often useful to check if metrics are received at the proxy in the intended format. See [Operations for Applications data format best practices](wavefront_data_format.html#operations-for-applications-data-format-best-practices) for background.
+As part of troubleshooting, it's often useful to check if metrics are received at the proxy in the intended format. See [Tanzu Observability data format best practices](wavefront_data_format.html#tanzu-observability-data-format-best-practices) for background.
### Step 1: Enable Valid Point Logging and Examine Valid Points
@@ -140,7 +140,7 @@ This section describes commonly seen messages Wavefront proxy logs, organized by
```
* Explanation:
- The proxy has been configured to listen for metrics using the Operations for Applications Data Format on port 2878. If tracing or histograms are configured, you should see a corresponding message. For example:
+ The proxy has been configured to listen for metrics using the Tanzu Observability Data Format on port 2878. If tracing or histograms are configured, you should see a corresponding message. For example:
```
INFO [proxy:startTraceListener] listening on port: 30000 for trace data
@@ -175,7 +175,7 @@ This section describes commonly seen messages Wavefront proxy logs, organized by
```
* Explanation:
- The proxy successfully checked in with the Operations for Applications backend. A message like this should appear at 1 minute intervals (approximately).
+ The proxy successfully checked in with the Tanzu Observability backend. A message like this should appear at 1 minute intervals (approximately).
**Processed Since Start INFO Message**
@@ -213,7 +213,7 @@ INFO [AbstractReportableEntityHandler:reject] [] blocked input: [WF-300 Ca
Confirm that the data point conforms to the format configured for the specified port. The proxy can handle various different data formats. Ensure that the data format you've configured for the port matches the format of data arriving at that port.
- If the port is configured for standard [Operations for Applications data format](wavefront_data_format.html), check the format of the data point mentioned in the log message.
+ If the port is configured for standard [Tanzu Observability data format](wavefront_data_format.html), check the format of the data point mentioned in the log message.
### Proxy WARN Messages
@@ -279,7 +279,7 @@ INFO [AbstractReportableEntityHandler:reject] [] blocked input: [WF-300 Ca
```
* Explanation: The proxy cannot connect using the token provided.
- {% include important.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The [proxy authentication](proxies_installing.html#proxy-authentication-types) to Operations for Applications differs for VMware Cloud services subscriptions and original subscriptions."%}
+ {% include important.html content="Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. The [proxy authentication](proxies_installing.html#proxy-authentication-types) to Tanzu Observability differs for VMware Cloud services subscriptions and original subscriptions."%}
@@ -501,26 +501,26 @@ The example test output might look like this.
The `curl` command checks for status, and the status 200 is returned.
-## Cannot Modify the Proxy (Operations for Applications Installed Through Tanzu Mission Control)
+## Cannot Modify the Proxy (Tanzu Observability Installed Through Tanzu Mission Control)
**Symptom**
-You're monitoring your Kubernetes cluster with Operations for Applications. You installed Operations for Applications from Tanzu Mission Control. Now you're having problems making a change to the Wavefront proxy.
+You're monitoring your Kubernetes cluster with Tanzu Observability. You installed Tanzu Observability from Tanzu Mission Control. Now you're having problems making a change to the Wavefront proxy.
**Cause**
-If you installed Operations for Applications from Tanzu Mission Control, you cannot make changes to the Wavefront proxy.
+If you installed Tanzu Observability from Tanzu Mission Control, you cannot make changes to the Wavefront proxy.
**Resolution**
-If your environment has a standalone Operations for Applications instance, use that instance. We are working on resolving the issue.
+If your environment has a standalone Tanzu Observability instance, use that instance. We are working on resolving the issue.
## Proxies FAQ
This section gives answers to some frequently asked questions. We expect to add more questions and answers as we hear from customers.
-### Can You Explain wavefront-proxy timestamps and Operations for Applications timestamps?
+### Can You Explain wavefront-proxy timestamps and Tanzu Observability timestamps?
-The Wavefront proxy sends metric timestamps as milliseconds, but the ingestion layer of the Operations for Applications service converts and stores the information as seconds.
+The Wavefront proxy sends metric timestamps as milliseconds, but the ingestion layer of the Tanzu Observability service converts and stores the information as seconds.
diff --git a/pages/doc/purchase-additional-capacity.md b/pages/doc/purchase-additional-capacity.md
index fcf9b0d1d..c8b1fae8a 100644
--- a/pages/doc/purchase-additional-capacity.md
+++ b/pages/doc/purchase-additional-capacity.md
@@ -4,21 +4,21 @@ keywords: administration
tags: [administration]
sidebar: doc_sidebar
permalink: purchase_additional_capacity.html
-summary: Learn how to add capacity to your current VMware Aria Operations for Applications subscription.
+summary: Learn how to add capacity to your current Tanzu Observability (formerly known as VMware Aria Operations for Applications) subscription.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
-- For VMware Cloud services subscriptions, to purchase additional capacity, you must hold the [**Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) in the VMware Cloud organization running the service as well as at least one [Operations for Applications service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance. If your enterprise domain is federated, to access the organization billing account, you must have a VMware account linked to your corporate account.
-- For original Operations for Applications subscriptions, to purchase additional capacity, you must be a **Super Admin** user."%}
+{% include note.html content="Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
+- For VMware Cloud services subscriptions, to purchase additional capacity, you must hold the [**Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) in the VMware Cloud organization running the service as well as at least one [Tanzu Observability service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance. If your enterprise domain is federated, to access the organization billing account, you must have a VMware account linked to your corporate account.
+- For original Tanzu Observability subscriptions, to purchase additional capacity, you must be a **Super Admin** user."%}
## Supported Contracts
-Currently, you can buy additional capacity only if you have a billable commit contract and your Operations for Applications service is connected to a VMware Cloud Services organization. If your Operations for Applications service is not connected to a VMware Cloud Services organization, or if you have a burndown commit contract, contact the Operations for Applications sales team to add more capacity to your subscription.
+Currently, you can buy additional capacity only if you have a billable commit contract and your Tanzu Observability service is connected to a VMware Cloud Services organization. If your Tanzu Observability service is not connected to a VMware Cloud Services organization, or if you have a burndown commit contract, contact the Tanzu Observability sales team to add more capacity to your subscription.
## How to Purchase Additional Capacity
1. Log in to your service instance.
-1. If you are a Super Admin user in an original Operations for Applications subscription, [enable Super Admin mode](users_account_managing.html#enable-or-disable-super-admin-mode).
+1. If you are a Super Admin user in an original Tanzu Observability subscription, [enable Super Admin mode](users_account_managing.html#enable-or-disable-super-admin-mode).
1. From the gear icon on the toolbar, select **Usage and Subscriptions**.
1. Click the **Subscriptions** tab.
@@ -32,4 +32,4 @@ Currently, you can buy additional capacity only if you have a billable commit co
After checking out, you will see an order confirmation message. Typically, it takes 24 hours to fulfil an order. Once your additional capacity becomes available, you'll receive an email notification.
-In case of urgency, you can contact the Operations for Applications team by sending an email to `tanzu_saas_ops@vmware.com` with your contact details and someone from our team will help you.
+In case of urgency, you can contact the Tanzu Observability team by sending an email to `tanzu_saas_ops@vmware.com` with your contact details and someone from our team will help you.
diff --git a/pages/doc/query_editor.md b/pages/doc/query_editor.md
index 2d2391718..245d39ef1 100644
--- a/pages/doc/query_editor.md
+++ b/pages/doc/query_editor.md
@@ -7,7 +7,7 @@ permalink: query_editor.html
summary: Query your metrics with query language functions and variables.
---
-VMware Aria Operations for Application (formerly known as Tanzu Observability by Wavefront) supports two tools for working with queries:
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports two tools for working with queries:
* [Chart Builder](chart_builder.html) is the fasted way to customize which metrics you see and to display them in charts.
* Query Editor, discussed on this page, allows advanced users to extract exactly the metrics they need from ingested data. If a chart uses functions that are not supported in Chart Builder, or if the chart has been opened in Query Editor before, we show Query editor when you open the chart for edit.
diff --git a/pages/doc/query_language_aggregate_functions.md b/pages/doc/query_language_aggregate_functions.md
index d072ffc82..ae90c2d08 100644
--- a/pages/doc/query_language_aggregate_functions.md
+++ b/pages/doc/query_language_aggregate_functions.md
@@ -7,7 +7,7 @@ permalink: query_language_aggregate_functions.html
summary: How to aggregate points from multiple time series with or without interpolation.
---
-You can combine points from multiple time series using an [**aggregation function**](query_language_reference.html#aggregation-functions) such as `sum()`, `avg()`, `min()`, `count()`, `percentile()` etc. An aggregation function returns a series of points whose values are calculated from corresponding points in two or more input time series. VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) supports aggregation with interpolation or without interpolation:
+You can combine points from multiple time series using an [**aggregation function**](query_language_reference.html#aggregation-functions) such as `sum()`, `avg()`, `min()`, `count()`, `percentile()` etc. An aggregation function returns a series of points whose values are calculated from corresponding points in two or more input time series. Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports aggregation with interpolation or without interpolation:
* Standard aggregation functions (e.g. `sum()`, `avg()`, or `max()`) first interpolate the points of the underlying set of series, and then apply the aggregation function to the interpolated series. These functions aggregate multiple series down, usually to a single series.
* Raw aggregation functions (e.g. `rawsum()`, `rawavg()`) do **not** interpolate the underlying series before aggregation.
diff --git a/pages/doc/query_language_align_function.md b/pages/doc/query_language_align_function.md
index ef09c8c6e..1de069a31 100644
--- a/pages/doc/query_language_align_function.md
+++ b/pages/doc/query_language_align_function.md
@@ -7,7 +7,7 @@ permalink: query_language_align_function.html
summary: Learn where to use the align() function and why the query engine does pre-alignment.
---
-In VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) charts, point buckets represent data that has been summarized over a certain length of time.
+In Tanzu Observability (formerly known as VMware Aria Operations for Applications) charts, point buckets represent data that has been summarized over a certain length of time.
Both the **Summarize By** chart option and the [`align()` function](ts_align.html) group points into buckets and allow you to specify how those points are aggregated (e.g., averaged, counted, summed, etc.). The `align()` function allows you to specify the desired bucket size. By default, the summarization method that aggregation functions use is based on the bucket size of the [chart resolution](ui_charts.html#chart-resolution).
diff --git a/pages/doc/query_language_discrete_continuous.md b/pages/doc/query_language_discrete_continuous.md
index 7abe8820f..7712f78fc 100644
--- a/pages/doc/query_language_discrete_continuous.md
+++ b/pages/doc/query_language_discrete_continuous.md
@@ -7,7 +7,7 @@ permalink: query_language_discrete_continuous.html
summary: Understand discrete and continuous time series and when the query engine performs interpolation.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports both discrete and continuous time series. Understanding how to work with them is important for best performance.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports both discrete and continuous time series. Understanding how to work with them is important for best performance.
## Basics
diff --git a/pages/doc/query_language_getting_started.md b/pages/doc/query_language_getting_started.md
index 3547f7ddb..2ce7fd12c 100644
--- a/pages/doc/query_language_getting_started.md
+++ b/pages/doc/query_language_getting_started.md
@@ -7,7 +7,7 @@ permalink: query_language_getting_started.html
summary: Watch some videos, run a query, apply filters and functions, and more.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes the Wavefront Query Language (WQL), which lets you retrieve and display data that has been ingested.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Wavefront Query Language (WQL), which lets you retrieve and display data that has been ingested.
* **Time series data** The query language is particularly well suited to time series data because it accommodates the periodicity, potential irregularity, and streaming nature of that data type.
* **Histograms** The query language includes functions for [manipulating histograms](query_language_reference.html#histogram-functions).
* **Traces and spans** Use the [tracing UI](tracing_traces_browser.html) to query traces and spans.
diff --git a/pages/doc/query_language_metadata_functions.md b/pages/doc/query_language_metadata_functions.md
index d7d3e779a..70d24ea64 100644
--- a/pages/doc/query_language_metadata_functions.md
+++ b/pages/doc/query_language_metadata_functions.md
@@ -7,7 +7,7 @@ permalink: query_language_metadata_functions.html
summary: Learn how to rename metrics and sources and create point tags with aliasSource, aliasMetric, and taggify.
---
-VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) includes metadata (label manipulation) functions that enable users to temporarily rename a source, rename a metric or create a synthetic point tag. Dashboards and charts display the changed name or aggregated point tag. We support:
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes metadata (label manipulation) functions that enable users to temporarily rename a source, rename a metric or create a synthetic point tag. Dashboards and charts display the changed name or aggregated point tag. We support:
* [`aliasSource`](ts_aliasSource.html) - Manipulate a source name
* [`aliasMetric`](ts_aliasMetric.html) - Manipulate a metric name
* [`taggify`](ts_taggify.html) - Manipulate a point tag name
diff --git a/pages/doc/query_language_performance.md b/pages/doc/query_language_performance.md
index 5065ac8c6..ec7686483 100644
--- a/pages/doc/query_language_performance.md
+++ b/pages/doc/query_language_performance.md
@@ -7,7 +7,7 @@ permalink: query_language_performance.html
summary: Tricks for improving the query language performance.
---
-The Wavefront Query Language (WQL) lets you retrieve and display the data that has been ingested into VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) and create alerts that use this data.
+The Wavefront Query Language (WQL) lets you retrieve and display the data that has been ingested into Tanzu Observability (formerly known as VMware Aria Operations for Applications) and create alerts that use this data.
@@ -82,7 +82,7 @@ To see the performance statistics for a particular query of a chart or alert:
## Use Performance Improvement Suggestions
-If the query uses certain functions in ways that often cause performance degradation, Operations for Applications shows actionable suggestions for improving the query performance. The suggestions also include links to documentation and videos for details.
+If the query uses certain functions in ways that often cause performance degradation, Tanzu Observability shows actionable suggestions for improving the query performance. The suggestions also include links to documentation and videos for details.
@@ -108,7 +108,7 @@ To see and, optionally, apply the performance improvement suggestions for a quer
## Use the Query Analyzer
-Sometimes, when you expect to see certain data in Operations for Applications, it doesn’t show up for some reason. By default, in such cases, charts display a **No Data** message (unless you have [overridden this setting and have set up charts to show another message](ui_charts.html#override-the-no-data-message-on-a-chart)). When you see **No Data** on a chart, you can use the Query Analyzer to analyze your queries and subqueries. The Query Analyzer helps you identify potential issues, so that you can easily [troubleshoot missing data](missing_data_troubleshooting.html), and also shows performance statistics for the queries and subqueries that result in **No Data**.
+Sometimes, when you expect to see certain data in Tanzu Observability, it doesn’t show up for some reason. By default, in such cases, charts display a **No Data** message (unless you have [overridden this setting and have set up charts to show another message](ui_charts.html#override-the-no-data-message-on-a-chart)). When you see **No Data** on a chart, you can use the Query Analyzer to analyze your queries and subqueries. The Query Analyzer helps you identify potential issues, so that you can easily [troubleshoot missing data](missing_data_troubleshooting.html), and also shows performance statistics for the queries and subqueries that result in **No Data**.
{% include tip.html content="If you use variables in your queries, in the Query Analyzer the variables are replaced by their actual (static) values. See the example below."%}
@@ -130,7 +130,7 @@ The subquery that causes the **No Data** issue is highlighted.
-- **Example 2**: No data is present in Operations for Applications.
+- **Example 2**: No data is present in Tanzu Observability.
diff --git a/pages/doc/query_language_point_tags.md b/pages/doc/query_language_point_tags.md
index 39584f664..82ce9a167 100644
--- a/pages/doc/query_language_point_tags.md
+++ b/pages/doc/query_language_point_tags.md
@@ -20,7 +20,7 @@ Many of our cloud integrations generate point tags automatically to help you fil
### Point Tag Maximum
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports up 20 point tags per time series. A larger number of point tags does not improve the user experience and can lead to performance problems.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports up 20 point tags per time series. A larger number of point tags does not improve the user experience and can lead to performance problems.
{% include note.html content="If the number of point tags exceeds 20, then we drop the metrics that have those point tags." %}
diff --git a/pages/doc/query_language_recipes.md b/pages/doc/query_language_recipes.md
index 3dfb68029..25bbd58b4 100644
--- a/pages/doc/query_language_recipes.md
+++ b/pages/doc/query_language_recipes.md
@@ -115,7 +115,7 @@ For more details, see [Display Daily Average](query_language_windows_trends.html
## Data Pipeline Queries
-Data pipeline queries allow you to determine whether data is flowing to the proxies or to the VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) service. You can also examine the point rate and potentially set an alert if data is larger than a threshold.
+Data pipeline queries allow you to determine whether data is flowing to the proxies or to the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service. You can also examine the point rate and potentially set an alert if data is larger than a threshold.
### Point Rate for All Proxies
@@ -135,7 +135,7 @@ Point rate blocked across all Wavefront proxies. Points might be blocked due to
`sum(rate(ts(~proxy.points.*.blocked)))`
-Total points that are collected by the Operations for Applications service. The `~collector` service acts as an entry point to the Operations for Applications service, and these metrics monitor the data processed at the collector.
+Total points that are collected by the Tanzu Observability service. The `~collector` service acts as an entry point to the Tanzu Observability service, and these metrics monitor the data processed at the collector.
`sum(rate(ts(~collector.points.reported)))`
@@ -145,7 +145,7 @@ Point rate received at each Wavefront proxy:
`sum(rate(ts(~proxy.points.*.received)),sources)`
-Point rate sent to Operations for Applications service by each Wavefront proxy:
+Point rate sent to Tanzu Observability service by each Wavefront proxy:
`sum(rate(ts(~proxy.points.*.sent)),sources)`
diff --git a/pages/doc/query_language_reference.md b/pages/doc/query_language_reference.md
index bb72b7c74..a2f48b8fd 100644
--- a/pages/doc/query_language_reference.md
+++ b/pages/doc/query_language_reference.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: query_language_reference.html
summary: Learn about the query syntax, operators, and functions supported by Wavefront Query Language (WQL).
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes the Wavefront Query Language, which allows you to extract the information you need from your data. You use the query language for queries that display in charts and for alerts. This page is a complete reference to all query language elements and functions. You can click most functions for a page with details and examples.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Wavefront Query Language, which allows you to extract the information you need from your data. You use the query language for queries that display in charts and for alerts. This page is a complete reference to all query language elements and functions. You can click most functions for a page with details and examples.
## Query Expressions
diff --git a/pages/doc/query_language_series_joining.md b/pages/doc/query_language_series_joining.md
index 53c4aa670..d035ee777 100644
--- a/pages/doc/query_language_series_joining.md
+++ b/pages/doc/query_language_series_joining.md
@@ -7,7 +7,7 @@ permalink: query_language_series_joining.html
summary: Use relationships among your time series to build full stack correlations.
---
-VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) supports a `join()` function that lets you:
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports a `join()` function that lets you:
* Compare two or more time series and find matches, or, conversely, find the time series that do not match.
* Combine the data points from any matching time series to form a new synthetic time series with point tags from one or both of the input series.
diff --git a/pages/doc/query_language_series_matching.md b/pages/doc/query_language_series_matching.md
index 8d6aed476..0a64bae7f 100644
--- a/pages/doc/query_language_series_matching.md
+++ b/pages/doc/query_language_series_matching.md
@@ -7,7 +7,7 @@ permalink: query_language_series_matching.html
summary: Learn how implicit series matching operates on pairs of time series that have corresponding sources and point tags.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) performs **series matching** to identify meaningful pairs of individual time series to operate on. For example, because of implicit series matching in the following operation, the query engine compares metrics for disk reads and disk writes only when they come from the same source and have common point tag values:
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) performs **series matching** to identify meaningful pairs of individual time series to operate on. For example, because of implicit series matching in the following operation, the query engine compares metrics for disk reads and disk writes only when they come from the same source and have common point tag values:
```
ts(~sample.disk.bytes.read) > ts(~sample.disk.bytes.written)
diff --git a/pages/doc/query_language_windows_trends.md b/pages/doc/query_language_windows_trends.md
index e54503a36..258c480c6 100644
--- a/pages/doc/query_language_windows_trends.md
+++ b/pages/doc/query_language_windows_trends.md
@@ -7,7 +7,7 @@ permalink: query_language_windows_trends.html
summary: Highlight trends with moving and tumbling windows.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports moving time window functions for calculating continuous aggregation over a sliding time window. [Moving time window functions](query_language_reference.html#moving-window-time-functions) are useful if, for example, you want to calculate the moving average over the past 24 hours.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports moving time window functions for calculating continuous aggregation over a sliding time window. [Moving time window functions](query_language_reference.html#moving-window-time-functions) are useful if, for example, you want to calculate the moving average over the past 24 hours.
But if you want to look at the daily average for each day, you have to create fixed-size time window. This page explains how use moving and fixed-sized time windows.
diff --git a/pages/doc/sources_managing.md b/pages/doc/sources_managing.md
index e9d2e2cf2..a8d0af3e4 100644
--- a/pages/doc/sources_managing.md
+++ b/pages/doc/sources_managing.md
@@ -7,7 +7,7 @@ permalink: sources_managing.html
summary: Learn about sources and how to manage them.
---
-In VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront), a **source** is a unique application, host, container, or instance that emits metrics. The source is explicitly set in the `source` field of an [Operations for Applications data format](wavefront_data_format.html) metric. For AWS integrations, the source is extracted from the [AWS CloudWatch service properties or dimensions](integrations_aws_metrics.html#aws_sources).
+In Tanzu Observability (formerly known as VMware Aria Operations for Applications), a **source** is a unique application, host, container, or instance that emits metrics. The source is explicitly set in the `source` field of an [Tanzu Observability data format](wavefront_data_format.html) metric. For AWS integrations, the source is extracted from the [AWS CloudWatch service properties or dimensions](integrations_aws_metrics.html#aws_sources).
* To view and manage sources, click **Browse > Sources** on the toolbar.
* To filter and group in charts, use the Wavefront Query Language. You can filter by source and [filter and group by source tags](tags_overview.html#source-tags).
diff --git a/pages/doc/start_trial.md b/pages/doc/start_trial.md
index 1436860cf..d60ad5684 100644
--- a/pages/doc/start_trial.md
+++ b/pages/doc/start_trial.md
@@ -1,23 +1,23 @@
----
-title: Start an Operations for Applications Free Trial
+---Console
+title: Start a Tanzu Observability Free Trial
keywords: administration
tags: [administration]
sidebar: doc_sidebar
permalink: start_trial.html
-summary: VMware offers a free trial of the VMware Aria Operations for Applications service where you can explore all of the service capabilities.
+summary: VMware offers a free trial of the Tanzu Observability service where you can explore all of the service capabilities.
---
-You can start a 30-day free trial of the Operations for Applications service from the VMware Cloud Services Console.
+You can start a 30-day free trial of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service from the VMware Cloud Services Console.
-## Operations for Applications and VMware Cloud Services
+## Tanzu Observability and VMware Cloud Services
-Starting July 3, 2023, VMware Aria Operations for Applications is a service in the VMware Cloud services platform.
+Starting July 3, 2023, Tanzu Observability is a service in the VMware Cloud services platform.
-Starting September 20, 2023, all **new trial** instances of Operations for Applications are **onboarded** to VMware Cloud services.
+Starting September 20, 2023, all **new trial** instances of Tanzu Observability are **onboarded** to VMware Cloud services.
-VMware Cloud services provides provides single sign-on (SSO) and identity access management (IAM) to your entire VMware Cloud services portfolio across hybrid and native public clouds, including Operations for Applications. See [Getting Started with Operations for Applications on VMware Cloud Services](csp_getting_started.html) for details.
+VMware Cloud services provides provides single sign-on (SSO) and identity access management (IAM) to your entire VMware Cloud services portfolio across hybrid and native public clouds, including Tanzu Observability. See [Getting Started with Tanzu Observability on VMware Cloud Services](csp_getting_started.html) for details.
## Start Your Free Trial
@@ -26,10 +26,10 @@ VMware Cloud services provides provides single sign-on (SSO) and identity access
{% include tip.html content="If you don't have a VMware account, you must create one." %}
1. From the navigation bar on the left, click **Services**.
-1. Click the **All** tab and search for VMware Aria Operations for Applications.
-1. In the **VMware Aria Operations for Applications** tile, click **Access**.
+1. Click the **All** tab and search for Tanzu Observability.
+1. In the **Tanzu Observability** tile, click **Access**.
- You are redirected to the Operations for Applications marketing website.
+ You are redirected to the Tanzu Observability marketing website.
1. Click **Start Free Trial**, enter your contact information and company details, review the Terms of Service, and click **Sign Up Now**.
@@ -53,12 +53,12 @@ VMware Cloud services provides provides single sign-on (SSO) and identity access
6. Click **Continue**.
- You are redirected to the Operations for Applications GUI. You are logged with your VMware account.
+ You are redirected to the Tanzu Observability GUI. You are logged with your VMware account.
- {% include note.html content="Initially, you have only the [**Viewer** Operations for Applications service role](csp_users_roles.html#operations-for-applications-service-roles-built-in). As a VMware Cloud **Organization Owner**, you can [change your roles](csp_users_roles.html#manage-roles). It's recommended that when you start your free trial, you change your role to **Super Admin**. You can also add users to your service. See [Manage User Accounts](csp_user_management.html) for details." %}
+ {% include note.html content="Initially, you have only the [**Viewer** Tanzu Observability service role](csp_users_roles.html#operations-for-applications-service-roles-built-in). As a VMware Cloud **Organization Owner**, you can [change your roles](csp_users_roles.html#manage-roles). It's recommended that when you start your free trial, you change your role to **Super Admin**. You can also add users to your service. See [Manage User Accounts](csp_user_management.html) for details." %}
## Learn More!
-* [Get Started with Operations for Applications on VMware Cloud Services](csp_getting_started.html).
-* See the list of [integrations supported for Operations for Applications subscriptions on VMware Cloud services](integrations_onboarded_subscriptions.html).
+* [Get Started with Tanzu Observability on VMware Cloud Services](csp_getting_started.html).
+* See the list of [integrations supported for Tanzu Observability subscriptions on VMware Cloud services](integrations_onboarded_subscriptions.html).
* Try out the [Windows Host Integration Tutorial](windows_host_tutorial.html).
* Find more [learning resources](tutorial_overview.html).
\ No newline at end of file
diff --git a/pages/doc/tags_overview.md b/pages/doc/tags_overview.md
index 920316512..df61ed5b3 100644
--- a/pages/doc/tags_overview.md
+++ b/pages/doc/tags_overview.md
@@ -5,7 +5,7 @@ sidebar: doc_sidebar
permalink: tags_overview.html
summary: Learn how to use tags to focus and speed up queries display and to unclutter the UI.
---
-In VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports tags for adding application-specific metadata to objects such alerts, dashboards, events, sources, and metrics.
+In Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports tags for adding application-specific metadata to objects such alerts, dashboards, events, sources, and metrics.
## Videos
@@ -46,7 +46,7 @@ You use tags in several ways:
* **Object tags** -- Limit the number of objects (e.g. dashboards) and metrics. For example, you might display only dashboards with a certain tag.
* **[Span tags](trace_data_details.html#span-tags)** -- Tags that are associated with a span. Certain span tags are required for a span to be valid. In addition, you can instrument an application with custom span tags.
-You can use tags to filter alerts, dashboards, events, and sources from the Operations for Applications UI or with the REST API.
+You can use tags to filter alerts, dashboards, events, and sources from the Tanzu Observability UI or with the REST API.
### How to Use Different Tag Types
@@ -106,7 +106,7 @@ When you construct a query, you can use a colon (:) in a tag key, only if the ta
### Tags in the UI
-In the Operations for Applications UI:
+In the Tanzu Observability UI:
* Tags display when you hover your mouse over a line, point, etc. in a chart.
* Tags display as gray labeled icons  in the filter bar and below each object in the browser for that object (e.g. dashboard or alerts browse).
* Tags on the left of the object browser allow you to filter your display.
@@ -128,7 +128,7 @@ All tag types support the ability to organize tags in a hierarchy. The hierarchy
In dashboards, internal tags start with a tilde, for example, `~welcome.`, `~integration.`, and `~system.`. To improve readability, tags retain case for display but they are treated as case-insensitive for searching, sorting, etc.
In the UI you operate on tag paths by selecting a component at a specific node in the hierarchy. For example:
-* Select all Operations for Applications dashboards by clicking **wavefront**.
+* Select all Tanzu Observability dashboards by clicking **wavefront**.
* Select only tutorial dashboards by expanding the **wavefront** node and then selecting **tutorial**.
In queries, you achieve the same effect by specifying a tag path with trailing wildcards `".*"`. For example, enter `alertTagPath.*` to match alerts named `alertTagPath.tpc1`, `alertTagPath.tpc1.tpc11`, and so on.
@@ -184,11 +184,11 @@ To filter by a tag, click a tag icon. You can click the icon in the filter bar o
## Source Tags
-A metric in Operations for Applications Data Format includes a source name. If source names change frequently or if you want to filter sources, a source tag can help. Source tags are just strings--in contrast, point tags are key-value pairs.
+A metric in Tanzu Observability Data Format includes a source name. If source names change frequently or if you want to filter sources, a source tag can help. Source tags are just strings--in contrast, point tags are key-value pairs.
You can add source tags from the UI or API, or you can inject source tags and source descriptions directly at the proxy.
-{% include note.html content="You must have **Source Tags** permission to manage sources and source tags. If you don't have **Source Tags** permission, Operations for Applications rejects source tags with a 403 error." %}
+{% include note.html content="You must have **Source Tags** permission to manage sources and source tags. If you don't have **Source Tags** permission, Tanzu Observability rejects source tags with a 403 error." %}
### Why Source Tags?
@@ -291,6 +291,6 @@ The syntax is the same for both the SourceTag and the SourceDescription property
## Learn More!
-* See [Data Naming](wavefront_data_format.html#operations-for-applications-data-format-best-practices) for examples of tags and tag naming.
+* See [Data Naming](wavefront_data_format.html#tanzu-observability-data-format-best-practices) for examples of tags and tag naming.
* Read the blog post [Skyline Resolves Production Incidents Faster with Alert-Based Health Dashboards](https://tanzu.vmware.com/content/blog/skyline-resolves-production-incidents-faster-with-alert-based-health-dashboards) for a discussion of a real-world example that uses alert tags.
diff --git a/pages/doc/upgrade-and-purchase.md b/pages/doc/upgrade-and-purchase.md
index 01549ff61..33b16d6d7 100644
--- a/pages/doc/upgrade-and-purchase.md
+++ b/pages/doc/upgrade-and-purchase.md
@@ -7,28 +7,28 @@ permalink: upgrade_and_purchase.html
summary: Learn how to upgrade from a trial version and purchase the service.
---
-When you register for the trial version of VMware Aria Operations for Applications, your trial expires after 30 days. One of the options that we offer is to purchase the service by using our self-service workflow. Another option is to contact the Operations for Applications sales team, so that they guide you through the purchase process. For large commitments and more PPS, we strongly recommend the latter option.
+When you register for the trial version of Tanzu Observability (formerly known as VMware Aria Operations for Applications), your trial expires after 30 days. One of the options that we offer is to purchase the service by using our self-service workflow. Another option is to contact the Tanzu Observability sales team, so that they guide you through the purchase process. For large commitments and more PPS, we strongly recommend the latter option.
-{% include note.html content="Starting September 20, 2023, all [**new trial**](start_trial.html) instances of Operations for Applications are **onboarded** to VMware Cloud services. Trial service instances before this date are considered **original**. The upgrade procedure is slightly different for a [trial service instance on VMware Cloud services](upgrade_and_purchase.html#upgrade-a-trial-service-instance-on-vmware-cloud-services) and for an [original trial service instance](upgrade_and_purchase.html#upgrade-an-original-trial-service-instance)." %}
+{% include note.html content="Starting September 20, 2023, all [**new trial**](start_trial.html) instances of Tanzu Observability are **onboarded** to VMware Cloud services. Trial service instances before this date are considered **original**. The upgrade procedure is slightly different for a [trial service instance on VMware Cloud services](upgrade_and_purchase.html#upgrade-a-trial-service-instance-on-vmware-cloud-services) and for an [original trial service instance](upgrade_and_purchase.html#upgrade-an-original-trial-service-instance)." %}
After the upgrade, you will be able to sign up for a free trial of our logs feature. See [Get Started with Logs](logging_overview.html).
## Commit Contracts
-Operations for Applications commit contracts are two types:
+Tanzu Observability commit contracts are two types:
* Billable -- You pay for certain amount of ingested points per second (PPS) per billing period. If there's an overage, you will be charged for the number of PPS above your committed rate.
* Burndown -- You pay for certain amount of ingested PPS for the contract period. We extract your P95 PPS usage for each billing period from your burndown commitment and calculate your remaining balance till the end of the contract period.
## Supported Upgrades
-{% include important.html content="The self-service upgrade from a trial version currently provides offers only for billable commit contracts. If you're interested in burndown commit offers, contact the Operations for Applications sales team. " %}
+{% include important.html content="The self-service upgrade from a trial version currently provides offers only for billable commit contracts. If you're interested in burndown commit offers, contact the Tanzu Observability sales team. " %}
-Billing depends on the amount of data, measured in points per second (PPS), that you send to Operations for Applications per [billing period](glossary.html#b). If you exceed the contracted rate for more than 5% of the hours of a given billing period, you will be charged for the usage above it (the overage). In any case, you do not lose any of your data.
+Billing depends on the amount of data, measured in points per second (PPS), that you send to Tanzu Observability per [billing period](glossary.html#b). If you exceed the contracted rate for more than 5% of the hours of a given billing period, you will be charged for the usage above it (the overage). In any case, you do not lose any of your data.
## Upgrade a Trial Service Instance on VMware Cloud Services
-{% include note.html content="To upgrade from a trial version, you must hold the [**Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) in the VMware Cloud organization running the service as well as at least one [Operations for Applications service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance. If your enterprise domain is federated, to access the organization billing account, you must have a VMware account linked to your corporate account." %}
+{% include note.html content="To upgrade from a trial version, you must hold the [**Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) in the VMware Cloud organization running the service as well as at least one [Tanzu Observability service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance. If your enterprise domain is federated, to access the organization billing account, you must have a VMware account linked to your corporate account." %}
1. Log in to your service instance.
1. On the banner showing you how many days have left from your trial period, click **Upgrade**.
@@ -39,10 +39,10 @@ Billing depends on the amount of data, measured in points per second (PPS), that
You are redirected to the VMware Cloud Services Console to complete your organization profile. See [Getting started with VMware Cloud Services billing and subscriptions](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-F772AF05-AA85-40A0-B9B5-D98C7D83D713.html) in the VMware Cloud services documentation.
- After you complete your organization profile in the VMware Cloud Service Console, you are redirected back to the purchase wizard in Operations for Applications.
+ After you complete your organization profile in the VMware Cloud Service Console, you are redirected back to the purchase wizard in Tanzu Observability.
* If your VMware Cloud organization already has a billing account, optionally, review the billing details by clicking **View Organization Profile**, which opens the VMware Cloud Services Console in a new tab.
- To proceed with the purchase, in Operations for Applications, click **Next**.
+ To proceed with the purchase, in Tanzu Observability, click **Next**.
1. On the **Create Subscription** page, enter the number of PPS (in kilo points per second) to purchase and click **Next**.
@@ -50,11 +50,11 @@ Billing depends on the amount of data, measured in points per second (PPS), that
1. Choose the billing terms and conditions, and click **Place Order**.
- You can choose to subscribe to Operations for Applications for one, three, or five years and pay in full, on a monthly basis (when you subscribe for one year), or on an annual basis (when you subscribe for three or five years).
+ You can choose to subscribe to Tanzu Observability for one, three, or five years and pay in full, on a monthly basis (when you subscribe for one year), or on an annual basis (when you subscribe for three or five years).
After you place your order, you will see a purchase confirmation page. Typically, it takes 24 hours to fulfil an order. Once your subscription becomes active, you'll receive an email notification.
-In case of urgency, you can contact the Operations for Applications team by sending an email to `tanzu_saas_ops@vmware.com` with your service ID and someone from our team will help you.
+In case of urgency, you can contact the Tanzu Observability team by sending an email to `tanzu_saas_ops@vmware.com` with your service ID and someone from our team will help you.
## Upgrade an Original Trial Service Instance
@@ -83,7 +83,7 @@ In case of urgency, you can contact the Operations for Applications team by send
6. Click **Continue**.
- After you successfully connect to your VMware account and organization, you are redirected back to the Operations for Applications purchase wizard.
+ After you successfully connect to your VMware account and organization, you are redirected back to the Tanzu Observability purchase wizard.
7. Verify that you are connected to the correct organization and click **Next**.
@@ -93,8 +93,8 @@ In case of urgency, you can contact the Operations for Applications team by send
9. Choose the billing terms and conditions, and click **Place Order**.
- You can choose to subscribe to Operations for Applications for one, three, or five years and pay in full, on a monthly basis (when you subscribe for one year), or on an annual basis (when you subscribe for three or five years). The purchase will be charged to the default payment method for your organization as set in the [VMware Cloud Services Console](https://console.cloud.vmware.com).
+ You can choose to subscribe to Tanzu Observability for one, three, or five years and pay in full, on a monthly basis (when you subscribe for one year), or on an annual basis (when you subscribe for three or five years). The purchase will be charged to the default payment method for your organization as set in the [VMware Cloud Services Console](https://console.cloud.vmware.com).
After you place your order, you will see a purchase confirmation page. Typically, it takes 24 hours to fulfil an order. Once your subscription becomes active, you'll receive an email notification.
-
+
diff --git a/pages/doc/visualize_histograms.md b/pages/doc/visualize_histograms.md
index c48539621..27f526028 100644
--- a/pages/doc/visualize_histograms.md
+++ b/pages/doc/visualize_histograms.md
@@ -7,7 +7,7 @@ published: true
permalink: visualize_histograms.html
summary: Learn how to visualize histograms.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports histograms for computing, storing, and using distributions of metrics rather than single metrics. You can [send histograms](proxies_histograms.html#sending-histogram-distributions) to a Wavefront proxy or use direct ingestion.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports histograms for computing, storing, and using distributions of metrics rather than single metrics. You can [send histograms](proxies_histograms.html#sending-histogram-distributions) to a Wavefront proxy or use direct ingestion.
You can find histogram metrics in the histogram browser and query for them using an `hs()` query. You can also visualize histograms different chart types.
@@ -18,7 +18,7 @@ You can find histogram metrics in the histogram browser and query for them using
You can view histograms in the Histogram browser.
1. Click **Browse > Histograms** and start typing the histogram metric name.
- Each histogram metric has an extension .d, .h, or .m. If you sent a metric in histogram data format, the extension corresponds to the interval you specified (`!M`, `!H`, or `!D`). If you sent a metric using Operations for Applications data format, the extension depends on the histogram port that you used.
+ Each histogram metric has an extension .d, .h, or .m. If you sent a metric in histogram data format, the extension corresponds to the interval you specified (`!M`, `!H`, or `!D`). If you sent a metric using Tanzu Observability data format, the extension depends on the histogram port that you used.
2. Select the metric you're interested in.
@@ -36,7 +36,7 @@ You can display histogram information in any chart.
You use the [`hs()` function](hs_function.html) with the name of a histogram metric to access the histogram distributions for that metric. A histogram metric name has an extension `.m`, `.h`, or `.d`:
* If you sent distributions in histogram data format, the histogram metric extension corresponds to the interval you specified (`!M`, `!H`, or `!D`).
-* If you sent metrics using Operations for Applications data format, the histogram metric extension corresponds to the histogram port that you used.
+* If you sent metrics using Tanzu Observability data format, the histogram metric extension corresponds to the histogram port that you used.
When you run an `hs()` query, you can optionally use it with one of the [histogram to histogram functions](query_language_reference.html#histogram-to-histogram-functions).
@@ -83,7 +83,7 @@ Histogram charts are designed especially for histogram visualization:
Histogram charts are interactive. Hover legends give details, and you can go from the ellipsis in the top right to the trace browser for the histogram:
* Add histogram queries in Chart Builder or Query Editor.
- - Use an `hs()` query to visualize data that were ingested as Operations for Applications histograms.
+ - Use an `hs()` query to visualize data that were ingested as Tanzu Observability histograms.
- Use a `ts()` query to visualize **any data** as histograms.
* Set the Y axis dimensions and X axis minimum, maximum, and units.
* Select percentile markers to display.
@@ -106,7 +106,7 @@ The following diagram uses the same query as the histogram chart above.
The heatmap is interactive and lets you examine the histogram in detail.
* Add histogram queries in Chart Builder or Query Editor.
- - Use an `hs()` query to visualize data that were ingested as Operations for Applications histograms.
+ - Use an `hs()` query to visualize data that were ingested as Tanzu Observability histograms.
- Use a `ts()` query to visualize any data as histograms.
* Hover over any field to bring up a legend. The legend:
- Shows how this histogram bar fits in with the rest of the histogram using a contrasting color.
diff --git a/pages/doc/wavefront_data_format.md b/pages/doc/wavefront_data_format.md
index b0830c106..4e693a37a 100644
--- a/pages/doc/wavefront_data_format.md
+++ b/pages/doc/wavefront_data_format.md
@@ -6,18 +6,18 @@ sidebar: doc_sidebar
permalink: wavefront_data_format.html
summary: Learn about the data format syntax and parameters.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports the same native data format with Wavefront proxies and with direct ingestion. This page is a reference to the data format and includes best practices.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports the same native data format with Wavefront proxies and with direct ingestion. This page is a reference to the data format and includes best practices.
## Metrics
### Supported Data Formats for Metrics
-[Direct ingestion](direct_ingestion.html) supports only the Operations for Applications data format.
+[Direct ingestion](direct_ingestion.html) supports only the Tanzu Observability data format.
[Wavefront proxies](proxies.html) support:
-- Operations for Applications data format
+- Tanzu Observability data format
- [Graphite data format (plaintext and pickle)](https://graphite.readthedocs.io/en/latest/feeding-carbon.html)
- [OpenTSDB data format (Telnet interface and HTTP API (JSON))](http://opentsdb.net/docs/build/html/user_guide/writing/)
@@ -31,7 +31,7 @@ Here's the data format for metrics.
Fields must be space separated and each line must be terminated with the newline character (\\n or ASCII hex 0A). See the **Data Format Fields** table below for details about each parameter.
-### Operations for Applications Data Format Fields
+### Tanzu Observability Data Format Fields
@@ -71,7 +71,7 @@ Maximum length for metricName is 256.
timestamp
No
Timestamp of the metric.
-
Number that reflects the epoch seconds of the metric (e.g. 1382754475). When this field is omitted, the timestamp is set to the current time at the Wavefront proxy when the metric arrives. Note that even if the timestamp at the proxy is in milliseconds, the Operations for Applications backend converts to seconds.
+
Number that reflects the epoch seconds of the metric (e.g. 1382754475). When this field is omitted, the timestamp is set to the current time at the Wavefront proxy when the metric arrives. Note that even if the timestamp at the proxy is in milliseconds, the Tanzu Observability backend converts to seconds.
source
@@ -155,12 +155,12 @@ Most of our discussion of the histogram and span data formats is on the pages li
source=
```
-## Operations for Applications Data Format Best Practices
+## Tanzu Observability Data Format Best Practices
Follow best practices for improved query execution speed and meaningful results.
* Make the metrics the most stable part of your data:
- - Do not include source names in the metric name. Operations for Applications captures sources separately.
+ - Do not include source names in the metric name. Tanzu Observability captures sources separately.
- Do not include data or timestamps in the metric name. Each point has an associated timestamp.
* Aim for a metric hierarchy:
- Partition the top level of the metric hierarchy by including at least one dot.
@@ -179,7 +179,7 @@ Metric names should reflect a class of comparable data across different sources
### Source Names Best Practices
-Operations for Applications assumes that source names are unique. Source names should reflect a unique source that is emitting metrics. For example, consider prefixing the source names with the datacenter name or making source names unique in other ways.
+Tanzu Observability assumes that source names are unique. Source names should reflect a unique source that is emitting metrics. For example, consider prefixing the source names with the datacenter name or making source names unique in other ways.
For example, if you have the same machine name in different data centers, and don't separate the two machines when sending data, you can get confusing query results. Time series might oscillate between different values seemingly randomly, or you might see unexpected averaging of points between multiple sources.
diff --git a/pages/doc/wavefront_data_ingestion.md b/pages/doc/wavefront_data_ingestion.md
index 48080e61f..64a6c9c62 100644
--- a/pages/doc/wavefront_data_ingestion.md
+++ b/pages/doc/wavefront_data_ingestion.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: wavefront_data_ingestion.html
summary: Learn how to set up the data ingestion pipeline.
---
-How you get your data into VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) depends on your use case, but you have many options. You can use one of the supported integrations, or you can instrument your application and send data directly.
+How you get your data into Tanzu Observability (formerly known as VMware Aria Operations for Applications) depends on your use case, but you have many options. You can use one of the supported integrations, or you can instrument your application and send data directly.
Watch this video to listen to the Wavefront co-founder Clement Pang's talk about data ingestion. Note that this video was created in 2018 and some of the information in it might have changed.
@@ -25,15 +25,15 @@ The data flow is like this:
1. The metrics originate with your infrastructure or application. They could come from Telegraf, or a cloud service, or you might collect metrics with a custom metrics pipeline.
2. You set up the data ingestion pipeline:
* For cloud services, you use one of the Cloud integrations -- you don't have to install or set up a Wavefront proxy.
- * To monitor hosts, infrastructure, or applications, set up an integration. The integration Setup tab has instructions for getting the data flowing. For many integrations, you set up Telegraf to collect the metrics and create a Wavefront proxy (or select an existing proxy). The proxy forwards metrics from many sources to the Operations for Applications service.
- * If no built-in integration for your data source exists, you can set up one of the collector integrations (such as a Telegraf integration) or you can stream your data to the Wavefront proxy. The proxy accepts metrics in OpenTSB, Grafana, and [Operations for Applications data format](wavefront_data_format.html).
- * Another option is direct ingestion. In that case, you send data directly to the Operations for Applications service. Most customers and our SRE team prefer using a proxy -- there are [many benefits](proxies.html#proxy-benefits).
+ * To monitor hosts, infrastructure, or applications, set up an integration. The integration Setup tab has instructions for getting the data flowing. For many integrations, you set up Telegraf to collect the metrics and create a Wavefront proxy (or select an existing proxy). The proxy forwards metrics from many sources to the Tanzu Observability service.
+ * If no built-in integration for your data source exists, you can set up one of the collector integrations (such as a Telegraf integration) or you can stream your data to the Wavefront proxy. The proxy accepts metrics in OpenTSB, Grafana, and [Tanzu Observability data format](wavefront_data_format.html).
+ * Another option is direct ingestion. In that case, you send data directly to the Tanzu Observability service. Most customers and our SRE team prefer using a proxy -- there are [many benefits](proxies.html#proxy-benefits).
-
+
## Step 1: Understand Your Use Case
-Operations for Applications can help you get insight into the telemetry at all levels of your application stack. Here are the levels, and the associated use cases -- for details on each use case see Step 2.
+Tanzu Observability can help you get insight into the telemetry at all levels of your application stack. Here are the levels, and the associated use cases -- for details on each use case see Step 2.
@@ -60,7 +60,7 @@ The simplest path for any use case is to use a [pre-built integration](label_int
### Get Metrics from a Cloud Provider
-Cloud integrations use a different setup process than other integrations. You log in to the cloud service, and give the Operations for Applications service read access to the metrics that you're interested in. There's no need to install or set up a Wavefront proxy.
+Cloud integrations use a different setup process than other integrations. You log in to the cloud service, and give the Tanzu Observability service read access to the metrics that you're interested in. There's no need to install or set up a Wavefront proxy.
We support integrations for the most popular cloud services. This doc set has customization information for example, for [AWS Metrics Integration](integrations_aws_metrics.html), [AWS ECS Integration](integrations_aws_ecs.html), [AWS Lambda Functions](integrations_aws_lambda.html), and [Pivotal Container Service](integrations_pks.html).
@@ -76,7 +76,7 @@ For use cases that center around infrastructure data like CPU, memory, or databa
3. If no built-in integration exists, set up a collector agent such as Telegraf or collectd to collect your metrics.
We support integrations for many custom collector agents. The collector agent can send your data to the Wavefront proxy.
- Some collector agents, such as Telegraf, include an output plug-in for Operations for Applications. You add a configuration file to Telegraf that specifies which data you want to get from which host, and select the proxy to send the data to.
+ Some collector agents, such as Telegraf, include an output plug-in for Tanzu Observability. You add a configuration file to Telegraf that specifies which data you want to get from which host, and select the proxy to send the data to.
@@ -97,7 +97,7 @@ For use cases that involve metrics from proprietary applications, you can instru
If your company already has a **custom metrics pipeline**, follow these steps:
-1. Convert your data into one of the [supported data formats](proxies.html#supported-data-formats). You can send data in [Operations for Applications data format](wavefront_data_format.html), Graphite data format, and OpenTSDB data format.
+1. Convert your data into one of the [supported data formats](proxies.html#supported-data-formats). You can send data in [Tanzu Observability data format](wavefront_data_format.html), Graphite data format, and OpenTSDB data format.
2. Set up a Wavefront proxy. If you have a proxy installed in your environment, consider using that - or you can install a new proxy. See [Installing and Managing Proxies](proxies_installing.html)
2. Send the metrics you're interested in to the Wavefront proxy at port 2878. In production environments, customers use 2 proxies behind a load balancer. Otherwise, 1 proxy is usually enough.
diff --git a/pages/doc/wavefront_prometheus.md b/pages/doc/wavefront_prometheus.md
index 2ae002251..c79408743 100644
--- a/pages/doc/wavefront_prometheus.md
+++ b/pages/doc/wavefront_prometheus.md
@@ -6,13 +6,13 @@ permalink: wavefront_prometheus.html
summary: Run PromQL queries in the Query Editor
---
-VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) supports both PromQL and Wavefront Query Language (WQL) queries. The Query Editor includes admin-level organization settings for enabling PromQL and a query line GUI that includes a translation option.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports both PromQL and Wavefront Query Language (WQL) queries. The Query Editor includes admin-level organization settings for enabling PromQL and a query line GUI that includes a translation option.
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
+{% include note.html content="Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
- For VMware Cloud services subscriptions, users with the **Super Admin** service role (in Super Admin mode) and users with the **Admin** service role can enable the PromQL support.
-- For original Operations for Applications subscriptions, users with the **Accounts** permission can enable the PromQL support."%}
+- For original Tanzu Observability subscriptions, users with the **Accounts** permission can enable the PromQL support."%}
-* Users with an administrative role in Operations for Applications have control over user defaults:
+* Users with an administrative role in Tanzu Observability have control over user defaults:
- On the **Organization Settings** page (New User Defaults) they can enable users to write queries in PromQL.
- If queries in PromQL are enabled, they can also set other options.
* Users can then type PromQL or WQL queries into the Query Editor.
@@ -48,7 +48,7 @@ To set PromQL settings for your organization:
If an administrator has enabled PromQL support (discussed above), each user can control some aspects of PromQL.
-{% include note.html content="If you can only choose between Query Editor and Chart Builder, then PromQL is not supported on your Operations for Applications instance." %}
+{% include note.html content="If you can only choose between Query Editor and Chart Builder, then PromQL is not supported on your Tanzu Observability instance." %}
1. From the gear icon, select your username.
2. Under **Query Settings**, select:
@@ -101,7 +101,7 @@ Next, you can make changes to the visualization.
## Frequently Asked Questions
-Operations for Applications supports most PromQL functions and operators out of the box. There are a small number of differences.
+Tanzu Observability supports most PromQL functions and operators out of the box. There are a small number of differences.
### FAQ: Do You Have Best Practices?
diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md
index bbf720f1d..ee7da3ccd 100644
--- a/pages/doc/wavefront_release_notes.md
+++ b/pages/doc/wavefront_release_notes.md
@@ -4,10 +4,10 @@ keywords:
tags:
sidebar: doc_sidebar
permalink: wavefront_release_notes.html
-summary: Announcements and new and updated features in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Announcements and new and updated features in Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-This page lists new and updated features for the VMware Aria Operations for Applications service.
+This page lists new and updated features for the Tanzu Observability service.
* For **Wavefront Proxy**, your go-to place is the [Wavefront proxy GitHub page](https://GitHub.com/wavefrontHQ/java/releases). On that page, you can see releases in progress and GA versions. If proxy changes are important for the service, we update this doc set, for example, with new configuration parameters, ports, etc.
* For the latest changes and releases of our **Integrations**, see the [Integrations Release Notes](integrations_new_changed.html).
@@ -15,30 +15,30 @@ This page lists new and updated features for the VMware Aria Operations for Appl
## Announcements
-### VMware Aria Operations for Applications on VMware Cloud Services
+### Tanzu Observability on VMware Cloud Services
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the [VMware Cloud services platform](https://console.cloud.vmware.com/). After this date, we support two types of subscriptions:
+Starting July 3, 2023, Tanzu Observability is a service on the [VMware Cloud services platform](https://console.cloud.vmware.com/). After this date, we support two types of subscriptions:
-* **Onboarded Subscriptions**: Operations for Applications subscriptions that are onboarded to the VMware Cloud services platform.
+* **Onboarded Subscriptions**: Tanzu Observability subscriptions that are onboarded to the VMware Cloud services platform.
* **Original Subscriptions**: Existing subscriptions which remain as is until onboarded to VMware Cloud services.
For information about the two subscription types and how they differ, see [Subscription Types](subscriptions-differences.html).
{% include note.html content="We will support both original and onboarded subscriptions until all original subscriptions are onboarded to VMware Cloud services."%}
-### Free Trial of VMware Aria Operations for Applications on VMware Cloud Services
+### Free Trial of Tanzu Observability on VMware Cloud Services
-Starting September 20, 2023, all **new trial** instances of Operations for Applications are **onboarded** to VMware Cloud services. You can [start a free trial](start_trial.html) directly from the VMware Cloud Services Console.
+Starting September 20, 2023, all **new trial** instances of Tanzu Observability are **onboarded** to VMware Cloud services. You can [start a free trial](start_trial.html) directly from the VMware Cloud Services Console.
-### Onboarding Original VMware Aria Operations for Applications to VMware Cloud Services
+### Onboarding Original Tanzu Observability to VMware Cloud Services
-In October, 2023, we start to incrementally [**onboard**](csp_migration.html) all original subscriptions to VMware Cloud services. You will receive a notification in your Operations for Applications UI with the date scheduled for your service onboarding to VMware Cloud services. Make sure that you get familiar with the VMware Cloud services platform and prepare for the onboarding. See [What Should I Do Before the Onboarding?](csp_migration.html#what-should-i-do-before-the-onboarding).
+In October, 2023, we start to incrementally [**onboard**](csp_migration.html) all original subscriptions to VMware Cloud services. You will receive a notification in your Tanzu Observability UI with the date scheduled for your service onboarding to VMware Cloud services. Make sure that you get familiar with the VMware Cloud services platform and prepare for the onboarding. See [What Should I Do Before the Onboarding?](csp_migration.html#what-should-i-do-before-the-onboarding).
-{% 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)." %}
+{% include warning.html content="The Tanzu Observability 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 Tanzu Observability 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-05.x Release Notes
-* **Updated Support Link**: The link for contacting our Technical Support team from within the Operations for Applications user interface is now updated. To open a support ticket, click the gear icon on the toolbar and select **Support**.
+* **Updated Support Link**: The link for contacting our Technical Support team from within the Tanzu Observability user interface is now updated. To open a support ticket, click the gear icon on the toolbar and select **Support**.
* **Derived Metrics Browser Improvements**: We improved the user experience of the **Derived Metrics Browser**. To navigate to this page, select **Browse > Derived Metrics**.
From b82b7333c3333c021c8ac5360220982232c5e352 Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Tue, 5 Mar 2024 15:44:10 +0200
Subject: [PATCH 02/26] Rebranding - Integrations section
---
.../doc/cloud_integrations_troubleshooting.md | 8 ++---
pages/doc/csp_supported_integrations.md | 24 +++++++-------
pages/doc/integrations.md | 14 ++++----
pages/doc/integrations_aws_ecs.md | 10 +++---
pages/doc/integrations_aws_key_age.md | 6 ++--
pages/doc/integrations_aws_lambda.md | 12 +++----
pages/doc/integrations_aws_metrics.md | 32 +++++++++----------
pages/doc/integrations_aws_overview-API.md | 8 ++---
pages/doc/integrations_aws_overview.md | 16 +++++-----
.../doc/integrations_bigpanda_troubleshoot.md | 10 +++---
pages/doc/integrations_cloudhealth.md | 26 +++++++--------
pages/doc/integrations_collectd.md | 2 +-
pages/doc/integrations_collectd_apache.md | 4 +--
pages/doc/integrations_collectd_cassandra.md | 4 +--
pages/doc/integrations_collectd_memcached.md | 4 +--
pages/doc/integrations_collectd_mysql.md | 4 +--
pages/doc/integrations_collectd_ngnix.md | 4 +--
pages/doc/integrations_collectd_redis.md | 4 +--
pages/doc/integrations_collectd_zookeeper.md | 4 +--
pages/doc/integrations_gcp_API.md | 10 +++---
pages/doc/integrations_gcp_overview.md | 6 ++--
pages/doc/integrations_grafana.md | 28 ++++++++--------
pages/doc/integrations_log_data.md | 10 +++---
pages/doc/integrations_pks.md | 6 ++--
pages/doc/integrations_vrops.md | 17 +++++-----
pages/labels/label_integrations%20list.md | 6 ++--
26 files changed, 139 insertions(+), 140 deletions(-)
diff --git a/pages/doc/cloud_integrations_troubleshooting.md b/pages/doc/cloud_integrations_troubleshooting.md
index 259efba97..e5efc4295 100644
--- a/pages/doc/cloud_integrations_troubleshooting.md
+++ b/pages/doc/cloud_integrations_troubleshooting.md
@@ -7,7 +7,7 @@ permalink: integrations-troubleshooting.html
summary: Learn how to troubleshoot the setup of our Cloud Services integrations.
---
-Integrations are one easy way to get data from external systems into VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront). You can use one of the [built-in integrations](label_integrations%20list.html) and customize it as needed.
+Integrations are one easy way to get data from external systems into Tanzu Observability (formerly known as VMware Aria Operations for Applications). You can use one of the [built-in integrations](label_integrations%20list.html) and customize it as needed.
## Cloud Services Integrations
@@ -24,7 +24,7 @@ Our Cloud Services integrations are:
## Troubleshooting Snowflake Integration Setup
-If you give Operations for Applications access to a Snowflake account which is additionally secured, for example, if it has network policies attached, you can perform certain prechecks and thus ensure the successful authentication during the [Snowflake integration setup](snowflake.html).
+If you give Tanzu Observability access to a Snowflake account which is additionally secured, for example, if it has network policies attached, you can perform certain prechecks and thus ensure the successful authentication during the [Snowflake integration setup](snowflake.html).
The following precheck steps use SnowSQL.
@@ -44,7 +44,7 @@ The following precheck steps use SnowSQL.
In this example:
* `` is the Snowflake account identifier with the account name, `-`.
- * `` is the user that you have created for Operations for Applications by following the setup steps for the Snowflake integration in the Operations for Applications UI. For example, `My_AoA_Integration`.
+ * `` is the user that you have created for Tanzu Observability by following the setup steps for the Snowflake integration in the Tanzu Observability UI. For example, `My_AoA_Integration`.
2. Provide your password when prompted.
3. To quit the connection, enter `!quit`.
@@ -59,7 +59,7 @@ The following precheck steps use SnowSQL.
* `` is the path to your private `rsa_key.p8` key. For example, `~/.ssh/rsa_key.p8`
* `` is the Snowflake account identifier with the account name, `-`.
- * `` is the user that you have created for Operations for Applications by following the setup steps for the Snowflake integration in the Operations for Applications UI. . For example, `My_AoA_Integration`.
+ * `` is the user that you have created for Tanzu Observability by following the setup steps for the Snowflake integration in the Tanzu Observability UI. For example, `My_AoA_Integration`.
2. Provide the passphrase for the private key when prompted.
3. Copy the generated JWT token.
diff --git a/pages/doc/csp_supported_integrations.md b/pages/doc/csp_supported_integrations.md
index 1d80a1bc3..1adb694f6 100644
--- a/pages/doc/csp_supported_integrations.md
+++ b/pages/doc/csp_supported_integrations.md
@@ -4,18 +4,18 @@ keywords: integrations
tags:
sidebar: doc_sidebar
permalink: integrations_onboarded_subscriptions.html
-summary: Learn how integration authentication happens, which integrations work with VMware Cloud services access tokens and which integrations still work with Operations for Applications API tokens.
+summary: Learn how integration authentication happens, which integrations work with VMware Cloud services access tokens and which integrations still work with Tanzu Observability API tokens.
---
## Subscription Types
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Operations for Applications subscriptions **onboarded** to the VMware Cloud services platform and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until [onboarded](csp_migration.html) to VMware Cloud services.
+Starting July 3, 2023, Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the VMware Cloud services platform and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until [onboarded](csp_migration.html) to VMware Cloud services.
-For best performance, when you set up most of our integrations, it is recommended to use the Wavefront proxy. The Wavefront proxy ingests metrics and forwards them to Operations for Applications in a secure, fast, and reliable manner.
+For best performance, when you set up most of our integrations, it is recommended to use the Wavefront proxy. The Wavefront proxy ingests metrics and forwards them to Tanzu Observability in a secure, fast, and reliable manner.
### VMware Cloud Services Subscriptions
-When your Operations for Applications service **is onboarded** to the VMware Cloud services platform you have the following choices for the [Wavefront proxy](proxies_installing.html) authentication:
+When your Tanzu Observability service **is onboarded** to the VMware Cloud services platform you have the following choices for the [Wavefront proxy](proxies_installing.html) authentication:
**VMware Cloud Services Access Token**
@@ -35,22 +35,22 @@ The Wavefront proxy requires a VMware Cloud services access token with the **Pro
You might need to regenerate and reconfigure the API token periodically depending on the TTL configuration.
-**Operations for Applications API token**
+**Tanzu Observability API token**
-For a limited number of integrations, you must still use an Operations for Applications API token, associated with a [service account](csp_service_accounts.html) that has the **Proxies** permission. As a user with the **Admin** service role, you can create a service account with the **Proxies** permission and generate an API token for it. Then, you can install the Wavefront proxy and set up your integration to pass the API token of the service account.
+For a limited number of integrations, you must still use a Tanzu Observability API token, associated with a [service account](csp_service_accounts.html) that has the **Proxies** permission. As a user with the **Admin** service role, you can create a service account with the **Proxies** permission and generate an API token for it. Then, you can install the Wavefront proxy and set up your integration to pass the API token of the service account.
-{% include warning.html content=" It is strongly recommended that you gradually [switch to using server to server OAuth apps](csp_migration.html#how-to-replace-a-service-account-with-a-server-to-server-app) which authenticate with more secure VMware Cloud services access tokens. Service accounts and Operations for Applications API tokens will be deprecated in the future." %}
+{% include warning.html content=" It is strongly recommended that you gradually [switch to using server to server OAuth apps](csp_migration.html#how-to-replace-a-service-account-with-a-server-to-server-app) which authenticate with more secure VMware Cloud services access tokens. Service accounts and Tanzu Observability API tokens will be deprecated in the future." %}
-To understand how you can manage the API tokens for service accounts, see [Managing the Operations for Applications API Tokens for a Service Account](csp_api_tokens.html#manage-the-operations-for-applications-api-tokens-for-a-service-account).
+To understand how you can manage the API tokens for service accounts, see [Managing the Tanzu Observability API Tokens for a Service Account](csp_api_tokens.html#manage-the-tanzu-observability-api-tokens-for-a-service-account).
### Original Subscriptions
-When your Operations for Applications service instance **is not onboarded** to VMware Cloud services, the proxy requires an Operations for Applications **API token**.
+When your Tanzu Observability service instance **is not onboarded** to VMware Cloud services, the proxy requires a Tanzu Observability **API token**.
Before you add a proxy, you must have an API token associated with your user account or a service account with the **Proxies** permission. See [Manage API Tokens](api_tokens.html) for details.
@@ -61,7 +61,7 @@ We're in the process of incrementally updating our integrations so that you can
{% include note.html content= "The integrations in the **Archived** section are approaching their end-of-life. For that reason, we will not update these integrations to authenticate with VMware Cloud services access tokens." %}
-When your Operations for Applications service **is onboarded** to the VMware Cloud services platform, the list of the integrations that are updated as of today is in the table below. This list grows with each release. If you urgently need an integration to become available and configurable with a VMware Cloud services access token, please contact [technical support](wavefront_support_feedback.html).
+When your Tanzu Observability service **is onboarded** to the VMware Cloud services platform, the list of the integrations that are updated as of today is in the table below. This list grows with each release. If you urgently need an integration to become available and configurable with a VMware Cloud services access token, please contact [technical support](wavefront_support_feedback.html).
@@ -439,7 +439,7 @@ When your Operations for Applications service **is onboarded** to the VMware Clo
-## Integrations That Use Operations for Applications API Tokens
+## Integrations That Use Tanzu Observability API Tokens
Here's the list of the integrations that still use API tokens. Currently, if your service **is onboarded** to VMware Cloud services, direct ingestion by using the Wavefront Output Plugin for Telegraf is supported only when you use a service account.
@@ -456,7 +456,7 @@ Here's the list of the integrations that still use API tokens. Currently, if you
## List of Unaffected Integrations
-The following integrations do not depend on the subscription type and work as expected, no matter whether your Operations for Applications service is onboarded to VMware Cloud services platform or not.
+The following integrations do not depend on the subscription type and work as expected, no matter whether your Tanzu Observability service is onboarded to VMware Cloud services platform or not.
### Cloud Integrations
diff --git a/pages/doc/integrations.md b/pages/doc/integrations.md
index d7b452af9..6deebef89 100644
--- a/pages/doc/integrations.md
+++ b/pages/doc/integrations.md
@@ -7,11 +7,11 @@ permalink: integrations.html
summary: Learn how to customize a built-in integration and how to set up a custom integration.
---
-Integrations are one easy way to get data from external systems into VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront). Use one of the [built-in integrations](label_integrations%20list.html) and customize it as needed.
+Integrations are one easy way to get data from external systems into Tanzu Observability (formerly known as VMware Aria Operations for Applications). Use one of the [built-in integrations](label_integrations%20list.html) and customize it as needed.
We update our [integrations release notes](integrations_new_changed.html) frequently.
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Operations for Applications subscriptions **onboarded** to the [VMware Cloud services platform](https://console.cloud.vmware.com/) and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until they migrate to VMware Cloud services. For information about the subscription types and how they differ, see [Subscription Types](subscriptions-differences.html).
+Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the [VMware Cloud services platform](https://console.cloud.vmware.com/) and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until they migrate to VMware Cloud services. For information about the subscription types and how they differ, see [Subscription Types](subscriptions-differences.html).
## Watch a Video
@@ -27,7 +27,7 @@ Sign up for a trial version to try our integrations. Detailed setup steps for ea
When the integration setup requires a token for the proxy authentication, the setup instructions of some integrations (such as all integrations for Linux distributions, Windows host integration, MacOS integration, Prometheus, and so on) vary depending on whether your service is onboarded to VMware Cloud services or not. For details, see [Integrations Supported for Onboarded Subscriptions](integrations_onboarded_subscriptions.html). For the latest and most recent instructions on how to set up an integration, see the steps on the **Setup** tab of the integration that you're interested in.
-* If your Operations for Applications service **is** onboarded to VMware Cloud services, you have two choices:
+* If your Tanzu Observability service **is** onboarded to VMware Cloud services, you have two choices:
* Use OAuth App authentication (recommended):
@@ -41,7 +41,7 @@ When the integration setup requires a token for the proxy authentication, the se
The API token must be generated in the VMware Cloud Services Console by an active user account. It also must have the **Proxies** service role assigned. For more information, see [How do I generate API tokens](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-E2A3B1C1-E9AD-4B00-A6B6-88D31FCDDF7C.html).
-* If your Operations for Applications service is **not** onboarded to VMware Cloud services, generate the API token in the Operations for Applications UI. It is recommended that you use a service account API token. For more information, see [Manage API tokens](api_tokens.html).
+* If your Tanzu Observability service is **not** onboarded to VMware Cloud services, generate the API token in the Tanzu Observability UI. It is recommended that you use a service account API token. For more information, see [Manage API tokens](api_tokens.html).
Here's a sample of what you see when you select one of our integrations:
* The **Overview** tab explains how the integration works and what's included, often a sample dashboard with commonly used charts.
@@ -58,7 +58,7 @@ Here's a screenshot that shows the different tabs of the Apache Solr integration
## Built-In and Custom Integrations
-VMware Aria Operations for Applications lets you set up many integrations directly from the product. For other integrations, we give step-by-step instructions -- or you can send your data in other ways, for example, using the Telegraf output plug-in.
+Tanzu Observability lets you set up many integrations directly from the product. For other integrations, we give step-by-step instructions -- or you can send your data in other ways, for example, using the Telegraf output plug-in.
- **Built-in integrations** provide assisted installation and configuration. Many integrations also install a dashboard for you. Access the integration by clicking **Integrations** on the toolbar and clicking the **Setup** tab.
@@ -94,7 +94,7 @@ This table provides links to the documentation pages for many of the custom and
Our customers have started to make open-source integrations available on GitHub.
-Our first external integration sends AlertSite monitoring results to VMware Aria Operations for Applications and is available at [https://github.com/secureworks/AlertSite2Wavefront](https://github.com/secureworks/AlertSite2Wavefront).
+Our first external integration sends AlertSite monitoring results to Tanzu Observability and is available at [https://github.com/secureworks/AlertSite2Wavefront](https://github.com/secureworks/AlertSite2Wavefront).
We're excited about this contribution and hope to see more soon!
@@ -235,7 +235,7 @@ When you hover over an integration, the integration border in the UI changes and
## More Info
* Don't see the integration you are looking for? Have a look at [Set Up Data Ingestion](wavefront_data_ingestion.html) and at [Data Format](wavefront_data_format.html).
-* On our [VMware Aria Operations for Applications](https://tanzu.vmware.com/observability) pages we have several blog posts with use cases and background info:
+* On our [Tanzu Observability](https://tanzu.vmware.com/observability) pages we have several blog posts with use cases and background info:
- [Google Cloud Monitoring Using Wavefront Metrics-Driven Analytics](https://tanzu.vmware.com/content/vmware-tanzu-observability-blog/google-cloud-monitoring-using-wavefront-metrics-driven-analytics)
- [Monitor MongoDB Metrics for Better Scaling and Optimized Database Performance](https://tanzu.vmware.com/content/vmware-tanzu-observability-blog/monitor-mongodb-metrics-for-better-scaling-and-optimized-database-performance)
- [Monitoring Apache HTTP Server with Wavefront Metrics-Driven Analytics](https://tanzu.vmware.com/content/vmware-tanzu-observability-blog/monitoring-apache-http-server-with-wavefront-metrics-driven-analytics)
diff --git a/pages/doc/integrations_aws_ecs.md b/pages/doc/integrations_aws_ecs.md
index ccd419acf..0a24ba870 100644
--- a/pages/doc/integrations_aws_ecs.md
+++ b/pages/doc/integrations_aws_ecs.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_aws_ecs.html
-summary: Send AWS ECS data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) using Telegraf agent or AWS Fargate.
+summary: Send AWS ECS data to Tanzu Observability (formerly known as VMware Aria Operations for Applications) using Telegraf agent or AWS Fargate.
---
[Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) is Amazon's Docker container orchestration system. From the Amazon ECS website:
@@ -36,9 +36,9 @@ Set up the [AWS integration](integrations_aws_metrics.html). This allows us to c
**Note:** To ensure that dashboards display correctly, use only the default EC2 instance name for the ECS cluster.
-## Create AWS ECS Fargate Task Definition for VMware Aria Operations for Applications
+## Create AWS ECS Fargate Task Definition for Tanzu Observability
-You can set up VMware Aria Operations for Applications to collect the data from AWS Fargate containers. These steps create an ECS task definition that ensures the VMware Aria Operations for Applications Collector automatically runs on each Fargate instance in your ECS cluster.
+You can set up Tanzu Observability to collect the data from AWS Fargate containers. These steps create an ECS task definition that ensures the Tanzu Observability Collector automatically runs on each Fargate instance in your ECS cluster.
After you've performed the setup, you can view and examine the data in our AWS Fargate dashboard in your product instance. See the screenshot at the bottom of this page.
@@ -107,9 +107,9 @@ After you've performed the setup, you can view and examine the data in our AWS F
9. Click **Run Task**.
-## Create an AWS ECS EC2 Task Definition for VMware Aria Operations for Applications
+## Create an AWS ECS EC2 Task Definition for Tanzu Observability
-A Telegraf (telegraf-ecs) image enables VMware Aria Operations for Applications to monitor Amazon ECS service. The Telegraf container must run in the same Task as the workload it is inspecting. Below are the steps to create an example ECS task definition and run the Telegraf container along with other containers in the task. In the Telegraf container, the ECS input plugin is enabled to gather stats on running containers in a Task and the output plugin is enabled to send ECS metrics to VMware Aria Operations for Applications.
+A Telegraf (telegraf-ecs) image enables Tanzu Observability to monitor Amazon ECS service. The Telegraf container must run in the same Task as the workload it is inspecting. Below are the steps to create an example ECS task definition and run the Telegraf container along with other containers in the task. In the Telegraf container, the ECS input plugin is enabled to gather stats on running containers in a Task and the output plugin is enabled to send ECS metrics to Tanzu Observability.
After you perform the setup, you can view and examine the data in the AWS ECS dashboard of your product instance. The screenshots at the bottom of this page show the AWS ECS dashboard.
diff --git a/pages/doc/integrations_aws_key_age.md b/pages/doc/integrations_aws_key_age.md
index 7cbcd38f8..5d0038a48 100644
--- a/pages/doc/integrations_aws_key_age.md
+++ b/pages/doc/integrations_aws_key_age.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_aws_key_age.html
-summary: Send AWS Key Age data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Send AWS Key Age data to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
AWS Identity and Access Management (IAM) allows administrators of different AWS services to manage access to those AWS services and resources securely.
@@ -13,7 +13,7 @@ AWS Identity and Access Management (IAM) allows administrators of different AWS
An AWS Identity and Access Management (IAM) user represents a person or application that interacts with AWS. The user has a name and an access key. The access key consists of an access key ID and a secret key and can be used when accessing AWS programmatically.
-VMware Aria Operations for Applications supports a built-in integration that allows us to collect metrics about the access key age of all IAM users in an AWS profile. If you establish a trust relationship with an AWS integration and follow the setup steps in this guide you can:
+Tanzu Observability supports a built-in integration that allows us to collect metrics about the access key age of all IAM users in an AWS profile. If you establish a trust relationship with an AWS integration and follow the setup steps in this guide you can:
* Monitor access key age metric related to IAM users by a profile.
* Set up alerts so you know when access keys are about to expire. For example, you can configure an alert target to notify when the access key age of user is about to reach the MAX_KEY_AGE (180 days).
@@ -28,7 +28,7 @@ To perform the AWS IAM Access Key Age service integration setup, your environmen
## Sending IAM Access Key Age Data
-After you've set up your environment to meet the prerequisites, follow these steps to send the access key age data to VMware Aria Operations for Applications:
+After you've set up your environment to meet the prerequisites, follow these steps to send the access key age data to Tanzu Observability:
1. Connect to the EC2 instance through SSH.
2. Update the `~/.aws/credentials` file with an `access_key_id` and `secret_key` for each profile. The following example illustrates this:
diff --git a/pages/doc/integrations_aws_lambda.md b/pages/doc/integrations_aws_lambda.md
index 66259ad8b..b0572bcca 100644
--- a/pages/doc/integrations_aws_lambda.md
+++ b/pages/doc/integrations_aws_lambda.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations, dashboards]
sidebar: doc_sidebar
permalink: integrations_aws_lambda.html
-summary: Learn about AWS Lambda and VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn about AWS Lambda and Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
The [AWS Lambda Functions integration](aws-lambda-functions.html) includes:
* Setup instructions
@@ -13,20 +13,20 @@ The [AWS Lambda Functions integration](aws-lambda-functions.html) includes:
On this page, we give some background and details not available on the integration page.
-## VMware Aria Operations for Applications and AWS Lambda
+## Tanzu Observability and AWS Lambda
AWS Lambda is ideal for situations when you want to run a function in response to an event. Use cases include generating thumbnails whenever users upload images to a website or similar scenarios. You define the function in one of the languages that AWS Lambda supports, and the function runs whenever a triggering event occurs. This model is called Function-as-a-Service or serverless.
While it's convenient to stop worrying about function execution, you might want to monitor the function. We offer these choices to monitor your AWS Lambda function:
-* Use the Amazon CloudWatch integration. Using the CloudWatch integration allows access to the full set of standard metrics, but polling CloudWatch and send the data to VMware Aria Operations for Applications introduces some lag.
+* Use the Amazon CloudWatch integration. Using the CloudWatch integration allows access to the full set of standard metrics, but polling CloudWatch and send the data to Tanzu Observability introduces some lag.
* Use the [AWS Lambda Functions integration](aws-lambda-functions.html). The integration collects standard metrics available through the public API. It also allows you to monitor business metrics by using a wrapper in Python, Go, or Node.js.
- [Go SDK for AWS Lambda](https://github.com/wavefrontHQ/wavefront-lambda-go)
- [Node.js SDK for AWS Lambda](https://github.com/wavefrontHQ/wavefront-lambda-nodejs)
- [Python SDK for AWS Lambda](https://github.com/wavefrontHQ/wavefront-lambda-python)
-## How to Use Operations for Applications to Monitor AWS Lambda
+## How to Use Tanzu Observability to Monitor AWS Lambda
-To support monitoring serverless environments, we include a metric type called [delta counter](delta_counters.html). With delta counters, VMware Aria Operations for Applications points are aggregated to the minute bucket. That avoids point collisions.
+To support monitoring serverless environments, we include a metric type called [delta counter](delta_counters.html). With delta counters, Tanzu Observability points are aggregated to the minute bucket. That avoids point collisions.
The AWS Lambda Function integration and the SDKs listed above make it easy to collect standard metrics and custom metrics.
@@ -47,7 +47,7 @@ Some metrics are counters, others are delta counters.
-## Ingesting AWS Lambda Cold Start Metrics into VMware Aria Operations for Applications
+## Ingesting AWS Lambda Cold Start Metrics into Tanzu Observability
An AWS Lambda "cold start" is the first request that a new AWS Lambda instance handles. Once the request is complete, the instance stays up-and-running, so that it can handle the subsequent requests. There is no defined time when this first instance will be removed. If an instance has been accidentally removed, "cold start" will happen again. As a result, the response time increases, because "cold start" will keep happening and you won't be able to find the cause behind this.
diff --git a/pages/doc/integrations_aws_metrics.md b/pages/doc/integrations_aws_metrics.md
index a25fe71cb..25e721a3c 100644
--- a/pages/doc/integrations_aws_metrics.md
+++ b/pages/doc/integrations_aws_metrics.md
@@ -4,13 +4,13 @@ keywords:
tags: [integrations, dashboards]
sidebar: doc_sidebar
permalink: integrations_aws_metrics.html
-summary: Monitor CloudWatch, CloudTrail, and Metrics+ with VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Monitor CloudWatch, CloudTrail, and Metrics+ with Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
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 [**Proxies** permission](permissions_overview.html) to set up an AWS integration. If you do not have this 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.
+You have to set up your Tanzu Observability 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).
* As an alternative, you can [Create an IAM Policy to Specify Limited Access](integrations_aws_overview.html#create-iam-policy-to-specify-limited-access).
@@ -22,19 +22,19 @@ 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.
+- **[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 Tanzu Observability 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
-VMware Aria Operations for Applications retrieves AWS metric and dimension data from AWS services using the AWS CloudWatch API. The complete list of metrics and dimensions that can be retrieved from AWS CloudWatch is available at [Amazon CloudWatch Metrics and Dimensions Reference](http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CW_Support_For_AWS.html). In addition, you can publish [custom AWS metrics](http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html) that can also be ingested by the CloudWatch integration.
+Tanzu Observability retrieves AWS metric and dimension data from AWS services using the AWS CloudWatch API. The complete list of metrics and dimensions that can be retrieved from AWS CloudWatch is available at [Amazon CloudWatch Metrics and Dimensions Reference](http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CW_Support_For_AWS.html). In addition, you can publish [custom AWS metrics](http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html) that can also be ingested by the CloudWatch integration.
### Configuring CloudWatch Data Ingestion
-After you [set up an AWS integration](integrations_aws_overview.html#set-up-an-aws-integration) associated 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.
+After you [set up an AWS integration](integrations_aws_overview.html#set-up-an-aws-integration) associated 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 Tanzu Observability fetches metrics.
{% include tip.html content="The following examples are supported only for EC2 and EBS metrics." %}
To configure CloudWatch ingestion:
@@ -59,7 +59,7 @@ To configure CloudWatch ingestion:
Here, the actual metric name is `aws.dynamodb.successfulrequestlatency`, while `average`, `maximum`, `minimum`, `samplecount`, and `sum` are the aggregation types. When you create the regular expression, you must use only `aws.dynamodb.successfulrequestlatency`. For example, `^aws.dynamodb.successfulrequestlatency$`.
- - **Bucket Allow List** – Enter a regular expression with the names of the buckets that contain the objects you want to request metrics for. This way, you add the bucket names to an allow list and only the S3 metrics that are in the matching buckets will be sent to VMware Aria Operations for Applications.
+ - **Bucket Allow List** – Enter a regular expression with the names of the buckets that contain the objects you want to request metrics for. This way, you add the bucket names to an allow list and only the S3 metrics that are in the matching buckets will be sent to Tanzu Observability.
- **Point Tag Allow List** – Add custom AWS point tags to an allow list by specifying a regular expression. If you do not specify a regular expression, no point tags are added to metrics.
Currently, custom point tags only for AWS EC2 instances and volumes are supported. To ingest the custom tags, you must first add the custom tags to the supported resources, and then add the tag keys in the **Point Tag Allow List** as a regular expression.
- **Service Refresh Rate** -- Number of minutes between requesting metrics. Default is `5`.
@@ -127,11 +127,11 @@ If you are ingesting metrics for a service, which is not part of the products li
### CloudWatch Sources and Source Tags
-VMware Aria Operations for Applications automatically sets each metric's source field and adds source tags to each AWS source, as follows:
+Tanzu Observability automatically sets each metric's source field and adds source tags to each AWS source, as follows:
**Metric Source Field**
-VMware Aria Operations for Applications sets the value of the AWS metric [`source`](wavefront_data_format.html) field by service:
+Tanzu Observability sets the value of the AWS metric [`source`](wavefront_data_format.html) field by service:
- **EC2** - the value of the **hostname**, **host**, or **name** [EC2 tags](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html), if the tags exist and you have an EC2 integration. Otherwise, the source is set to the Amazon instance ID.
- **EBS** - the Amazon instance ID of the EC2 instance the volume is attached to.
@@ -143,7 +143,7 @@ AWS sources are assigned source tags that identify their originating service fol
### CloudWatch Point Tags
-VMware Aria Operations for Applications adds the following point tags to CloudWatch metrics:
+Tanzu Observability adds the following point tags to CloudWatch metrics:
- `accountId` - the Amazon account that reported the metric.
- `Region` - The region in which the service is running. Added to EC2 and EBS metrics only.
@@ -151,7 +151,7 @@ VMware Aria Operations for Applications adds the following point tags to CloudWa
### CloudWatch Pricing
-Standard AWS CloudWatch pricing applies each time VMware Aria Operations for Applications requests metrics using the CloudWatch API. For pricing information, see [AWS \| Amazon CloudWatch \| Pricing](http://aws.amazon.com/cloudwatch/pricing). After selecting a region, you can find the current expected price under **Amazon CloudWatch API Requests**. In addition, custom metrics have a premium price; see the **Amazon CloudWatch Custom Metrics** section of the pricing page. To limit cost, by default VMware Aria Operations for Applications queries the API every 5 minutes. However, you can [change the refresh rate](#configuring-cloudwatch-data-ingestion), which will change the cost.
+Standard AWS CloudWatch pricing applies each time Tanzu Observability requests metrics using the CloudWatch API. For pricing information, see [AWS \| Amazon CloudWatch \| Pricing](http://aws.amazon.com/cloudwatch/pricing). After selecting a region, you can find the current expected price under **Amazon CloudWatch API Requests**. In addition, custom metrics have a premium price; see the **Amazon CloudWatch Custom Metrics** section of the pricing page. To limit cost, by default Tanzu Observability queries the API every 5 minutes. However, you can [change the refresh rate](#configuring-cloudwatch-data-ingestion), which will change the cost.
As an alternative to using the CloudWatch API for EC2 metrics, you can collect these metrics using [a Telegraf collector](telegraf.html) on each AWS instance. In this case, to prevent CloudWatch from requesting those metrics, you should set the **Metric Allow List** property to allow all metrics except EC2. For example:
@@ -167,7 +167,7 @@ The AWS Billing and Cost Management service sends [billing metrics](http://docs.
-VMware Aria Operations for Applications reports the single metric `aws.billing.estimatedcharges`. The `source` field and `ServiceName` point tag identify the AWS services. For the total estimated charge metric, `source` is set to `usd` and `ServiceName` is empty. VMware Aria Operations for Applications also provides the point tags `accountId`, `Currency`, `LinkedAccount`, and `Region`. Billing metrics are typically reported every 4 hours.
+Tanzu Observability reports the single metric `aws.billing.estimatedcharges`. The `source` field and `ServiceName` point tag identify the AWS services. For the total estimated charge metric, `source` is set to `usd` and `ServiceName` is empty. Tanzu Observability also provides the point tags `accountId`, `Currency`, `LinkedAccount`, and `Region`. Billing metrics are typically reported every 4 hours.
### AWS Usage Metrics
@@ -178,14 +178,14 @@ As part of CloudWatch we collect metrics that let you check if throttling is hap
### Setup for Ingesting AWS CloudWatch Logs
-You can ingest CloudWatch logs to Operations for Applications. You can use CloudWatch to detect anomalous behavior in your environments, set alarms, visualize logs and metrics side by side, take automated actions, troubleshoot issues, and discover insights to keep applications running smoothly. To understand more about CloudWatch, see the [Amazon CloudWatch documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html).
+You can ingest CloudWatch logs to Tanzu Observability. You can use CloudWatch to detect anomalous behavior in your environments, set alarms, visualize logs and metrics side by side, take automated actions, troubleshoot issues, and discover insights to keep applications running smoothly. To understand more about CloudWatch, see the [Amazon CloudWatch documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html).
#### Install the Wavefront Proxy
-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](proxies_installing.html) in your AWS environment.
+The Wavefront proxy is required to send logs from your systems to Tanzu Observability. If you have not already done so, install a [Wavefront proxy](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.
+* If your Tanzu Observability service **is** onboarded to VMware Cloud services, install Wavefront proxy version 13.0 or later.
+* If your Tanzu Observability service is **not** onboarded to VMware Cloud services, install Wavefront proxy version 12.2 or later.
{% include note.html content="For optimal performance, install a standalone proxy cluster that receives only logs payload. Typically two proxy instances behind a load balancer are sufficient." %}
@@ -282,7 +282,7 @@ You can use the following point tags to filter the metrics.
## AWS Metrics+ Data
AWS Metrics+ are metrics retrieved using AWS metrics API calls other than CloudWatch.
-Unless otherwise indicated, VMware Aria Operations for Applications sets the value of the AWS Metrics+ `source` field to the AWS instance ID. If an EBS volume is detached, its source field is set to the volume ID. The metrics include:
+Unless otherwise indicated, Tanzu Observability sets the value of the AWS Metrics+ `source` field to the AWS instance ID. If an EBS volume is detached, its source field is set to the volume ID. The metrics include:
- `aws.instance.price` - EC2 instances and how much they cost per hour. This metric includes the point tags `availabilityZone`, `instanceID`, `instanceLifecycle`, `instanceType`, and `operatingSystem`.
- `aws.reservedinstance.count` - Number of reserved instances in each availability zone by each instance type. This metric includes the point tags `availabilityZone`, `instanceID`, `instanceType`, and `operatingSystem`. This metric appears only if your account has reserved instances.
diff --git a/pages/doc/integrations_aws_overview-API.md b/pages/doc/integrations_aws_overview-API.md
index 3b6716e1b..44363be00 100644
--- a/pages/doc/integrations_aws_overview-API.md
+++ b/pages/doc/integrations_aws_overview-API.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_aws_overview_API.html
summary: Understand how to set up and manage the AWS integration by using our REST API.
---
-The Amazon Web Services integration allows you to ingest metrics directly from AWS. In addition to setting up and managing the AWS integration through the UI, you can also use the REST API for setting up and managing the AWS integration. This doc page provides some basic steps and examples on how to do this.
+The Amazon Web Services integration allows you to ingest metrics directly from AWS to Tanzu Observability (formerly known as VMware Aria Operations for Applications). In addition to setting up and managing the AWS integration through the UI, you can also use the REST API for setting up and managing the AWS integration. This doc page provides some basic steps and examples on how to do this.
{% include note.html content="You must have the [**Proxy Management** permission](permissions_overview.html) to set up an AWS integration." %}
@@ -14,7 +14,7 @@ In these examples, you access the REST API through the interface, so that you do
## Before You Start
-To set up the Amazon Web Services integration, you must provide VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) with read-only access to your Amazon account. To do that, you need to provide an account ID and external ID. While the account ID is a constant value - the ID to which you want to grant access to your resources, the external ID is not a constant value. The external ID is a secret identifier that is known by you and VMware Aria Operations for Applications (the third-party). The external ID is time-sensitive and regenerated each time you reopen the AWS Integration setup page, and you cannot reuse it.
+To set up the Amazon Web Services integration, you must provide Tanzu Observability with read-only access to your Amazon account. To do that, you need to provide an account ID and external ID. While the account ID is a constant value - the ID to which you want to grant access to your resources, the external ID is not a constant value. The external ID is a secret identifier that is known by you and Tanzu Observability (the third-party). The external ID is time-sensitive and regenerated each time you reopen the AWS Integration setup page, and you cannot reuse it.
For information about external IDs and how they are used in AWS, see [How to Use External ID When Granting Access to Your AWS Resources](https://aws.amazon.com/blogs/security/how-to-use-external-id-when-granting-access-to-your-aws-resources/).
@@ -58,7 +58,7 @@ For more information, see [Giving Access to Your AWS Account](integrations_aws_o
- Select the **Require external ID** check box and provide the [external ID that you have copied](integrations_aws_overview_API.html#create-an-external-id).
- You can also copy and paste the **External ID** displayed in the instructions on the **Amazon Web Services** integration **Setup** page (in the VMware Aria Operations for Applications GUI).
+ You can also copy and paste the **External ID** displayed in the instructions on the **Amazon Web Services** integration **Setup** page (in the Tanzu Observability GUI).
1. Click **Next**.
1. On the **Add permissions** screen, search for, and select the **ReadOnlyAccess** check box.
@@ -286,7 +286,7 @@ We also add the metrics for these services to a metric allow list by using a reg
## Enable and Disable an AWS Integration
-VMware Aria Operations for Applications automatically disables integrations that are experiencing errors due to invalid credentials. To enable an integration after the credential has been corrected or to manually disable an integration, you need the integration ID.
+Tanzu Observability automatically disables integrations that are experiencing errors due to invalid credentials. To enable an integration after the credential has been corrected or to manually disable an integration, you need the integration ID.
1. In the REST API documentation UI, click the `GET/api/v2/cloudintegration` request.
1. Click **Execute**.
diff --git a/pages/doc/integrations_aws_overview.md b/pages/doc/integrations_aws_overview.md
index bfaad4164..fbdf4ca08 100644
--- a/pages/doc/integrations_aws_overview.md
+++ b/pages/doc/integrations_aws_overview.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_aws_overview.html
summary: Understand setup and services in the AWS integration.
---
-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.
+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 to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
You can use the Amazon Web Services integration for initial setup, but additional steps might be needed for some of the services. This page gives an overview.
@@ -18,19 +18,19 @@ 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 VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) 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.
+- **[CloudTrail](http://aws.amazon.com/cloudtrail)** -- retrieves EC2 event information and creates Tanzu Observability 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 Tanzu Observability to optimize its use of CloudWatch, and saves money on CloudWatch calls as a result.
{% include tip.html content="See [AWS CloudWatch, CloudTrail, and Metrics+ Integrations](integrations_aws_metrics.html)" %}
### Establish a Trust Relationship
-Adding an AWS integration requires establishing a trust relationship between Amazon and VMware Aria Operations for Applications by specifying account information. You have to do that only once, and you have 2 options:
+Adding an AWS integration requires establishing a trust relationship between Amazon and Tanzu Observability by specifying account information. You have to do that only once, and you have 2 options:
* [Give Global Read-Only Access](#give-read-only-access-to-your-amazon-account-and-get-the-role-arn)
* [Give Limited Access](#giving-limited-access)
-After you've set up the integration, you can examine metrics from all AWS services that you subscribe to from the VMware Aria Operations for Applications GUI. The integration includes a predefined dashboard for each service. You can clone and modify the system dashboards, or create your own custom dashboard.
+After you've set up the integration, you can examine metrics from all AWS services that you subscribe to from the Tanzu Observability GUI. The integration includes a predefined dashboard for each service. You can clone and modify the system dashboards, or create your own custom dashboard.
-The API token must be a [valid Operations for Applications API token](api_tokens.html) of a user account or a service account that has access to the Operations for Applications sources that you want to ingest in CloudHealth.
+The API token must be a [valid Tanzu Observability API token](api_tokens.html) of a user account or a service account that has access to the Tanzu Observability sources that you want to ingest in CloudHealth.
{% include tip.html content="Creating a service account is often the right approach." %}
-## Create a VMware Aria Operations for Applications (Wavefront) Account in CloudHealth
+## Create a Tanzu Observability (Wavefront) Account in CloudHealth
Follow these steps to create a Wavefront account in CloudHealth:
@@ -60,13 +60,13 @@ Follow these steps to create a Wavefront account in CloudHealth:
1. Click **New Account** and configure the integration:
1. Enter an account name.
- 1. Retrieve the VMware Aria Operations for Applications API token (see Prerequisites) and paste it in the **API Token** field.
- 1. If you are using a metric prefix in VMware Aria Operations for Applications, enter its value in the **Metric Prefix** field.
+ 1. Retrieve the Tanzu Observability API token (see Prerequisites) and paste it in the **API Token** field.
+ 1. If you are using a metric prefix in Tanzu Observability, enter its value in the **Metric Prefix** field.
1. To import tags from a legacy Servers account, enable **Import Tags**.
CloudHealth then actively collects tags, and you will see an additional field to accept the tags that you want to import into CloudHealth.
1. Click **Save Account**.
-CloudHealth begins collecting VMware Aria Operations for Applications Sources within 15 minutes of account setup, and continues collecting these Sources every 15 min. CloudHealth fetches up to one day's worth of time-series data from the date when you add the Wavefront account.
+CloudHealth begins collecting Tanzu Observability Sources within 15 minutes of account setup, and continues collecting these Sources every 15 min. CloudHealth fetches up to one day's worth of time-series data from the date when you add the Wavefront account.
## Data Gathered by CloudHealth
diff --git a/pages/doc/integrations_collectd.md b/pages/doc/integrations_collectd.md
index 4600616a5..64f1b6176 100644
--- a/pages/doc/integrations_collectd.md
+++ b/pages/doc/integrations_collectd.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd.html
-summary: Learn how to send data collected by collectd to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn how to send data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
To set up collectd to collect metrics, follow the in-product instructions on the Setup tab of the **collectd (Archived)** integration.
diff --git a/pages/doc/integrations_collectd_apache.md b/pages/doc/integrations_collectd_apache.md
index 0ff449dce..558799f9a 100644
--- a/pages/doc/integrations_collectd_apache.md
+++ b/pages/doc/integrations_collectd_apache.md
@@ -4,12 +4,12 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_apache.html
-summary: Learn how to send Apache data collected by collectd to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn how to send Apache data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[Apache](https://httpd.apache.org/) is a popular open-source web server. To collect Apache data with collectd, use the collectd Apache plugin documentation found at [Plugin:Apache - collectd Wiki](https://collectd.org/wiki/index.php/Plugin:Apache).
-VMware Aria Operations for Applications supports a built-in integration that gets data from Apache using Telegraf. If you want to use collectd instead, follow the instructions on this page.
+Tanzu Observability supports a built-in integration that gets data from Apache using Telegraf. If you want to use collectd instead, follow the instructions on this page.
## Apache Setup
diff --git a/pages/doc/integrations_collectd_cassandra.md b/pages/doc/integrations_collectd_cassandra.md
index bf43695e5..5b465facd 100644
--- a/pages/doc/integrations_collectd_cassandra.md
+++ b/pages/doc/integrations_collectd_cassandra.md
@@ -4,13 +4,13 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_cassandra.html
-summary: Learn how to send Cassandra data collected by collectd to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn how to send Cassandra data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[Apache Cassandra](http://cassandra.apache.org/) is a popular, distributed, NoSQL database system.
Since Cassandra uses JMX to export metrics, collectd depends on the [Java](https://collectd.org/wiki/index.php/Plugin:Java) and [GenericJMX](https://collectd.org/wiki/index.php/Plugin:GenericJMX) plugins in order to collect metrics from Cassandra.
-VMware Aria Operations for Applications supports a built-in integration that gets data from Cassandra using Telegraf. If you want to use collectd instead, follow the instructions on this page.
+Tanzu Observability supports a built-in integration that gets data from Cassandra using Telegraf. If you want to use collectd instead, follow the instructions on this page.
## Cassandra Set Up
diff --git a/pages/doc/integrations_collectd_memcached.md b/pages/doc/integrations_collectd_memcached.md
index 7695aae87..cc2db10da 100644
--- a/pages/doc/integrations_collectd_memcached.md
+++ b/pages/doc/integrations_collectd_memcached.md
@@ -4,12 +4,12 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_memcached.html
-summary: Learn how to send memcached data collected by collectd to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn how to send memcached data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[memcached](https://memcached.org/) is a popular memory object cache system. See [collectd memcached plugin documentation](https://collectd.org/wiki/index.php/Plugin:memcached).
-VMware Aria Operations for Applications supports a built-in integration that gets data from memcached using Telegraf. If you want to use collectd instead, follow the instructions on this page.
+Tanzu Observability supports a built-in integration that gets data from memcached using Telegraf. If you want to use collectd instead, follow the instructions on this page.
## Installation
diff --git a/pages/doc/integrations_collectd_mysql.md b/pages/doc/integrations_collectd_mysql.md
index b659702be..4231e23b8 100644
--- a/pages/doc/integrations_collectd_mysql.md
+++ b/pages/doc/integrations_collectd_mysql.md
@@ -4,12 +4,12 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_mysql.html
-summary: Learn how to send MySQL data collected by collectd to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn how to send MySQL data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[MySQL](https://www.mysql.com/) is a popular open-source relational database. See [collectd MySQL plugin documentation](https://collectd.org/wiki/index.php/Plugin:MySQL).
-VMware Aria Operations for Applications supports a built-in integration that gets data from MySQL using Telegraf. If you want to use collectd instead, follow the instructions on this page.
+Tanzu Observability supports a built-in integration that gets data from MySQL using Telegraf. If you want to use collectd instead, follow the instructions on this page.
## Installation
diff --git a/pages/doc/integrations_collectd_ngnix.md b/pages/doc/integrations_collectd_ngnix.md
index d87e49721..ada29bf8a 100644
--- a/pages/doc/integrations_collectd_ngnix.md
+++ b/pages/doc/integrations_collectd_ngnix.md
@@ -4,12 +4,12 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_nginx.html
-summary: Learn how to send NGiNX data collected by collectd to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn how to send NGiNX data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[NGiNX](https://www.nginx.com/) is a popular web and proxy server. To collect NGiNX data with collectd, use the collectd NGiNX plugin documentation found at [Plugin:NGiNX - collectd Wiki](https://collectd.org/wiki/index.php/Plugin:nginx).
-VMware Aria Operations for Applications supports a built-in integration that gets data from NGiNX using Telegraf. If you want to use collectd instead, follow the instructions on this page.
+Tanzu Observability supports a built-in integration that gets data from NGiNX using Telegraf. If you want to use collectd instead, follow the instructions on this page.
## NGiNX Setup
diff --git a/pages/doc/integrations_collectd_redis.md b/pages/doc/integrations_collectd_redis.md
index e8670a872..19c83646c 100644
--- a/pages/doc/integrations_collectd_redis.md
+++ b/pages/doc/integrations_collectd_redis.md
@@ -4,10 +4,10 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_redis.html
-summary: Learn how to send Redis data collected by collectd to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn how to send Redis data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-[Redis](https://redis.io/) is an in-memory data structure store, often used as a database, cache and message broker. VMware Aria Operations for Applications supports a built-in integration that gets data from Redis using Telegraf. If you want to use collectd instead, follow the instructions on this page.
+[Redis](https://redis.io/) is an in-memory data structure store, often used as a database, cache and message broker. Tanzu Observability supports a built-in integration that gets data from Redis using Telegraf. If you want to use collectd instead, follow the instructions on this page.
We recommend the collectd Redis Python plugin. See [collectd Redis plugin documentation](https://github.com/powdahound/redis-collectd-plugin). There are 2 types of Redis nodes that can be monitored with collectd: Masters and Slaves.
diff --git a/pages/doc/integrations_collectd_zookeeper.md b/pages/doc/integrations_collectd_zookeeper.md
index ed8645a49..91f97b5e5 100644
--- a/pages/doc/integrations_collectd_zookeeper.md
+++ b/pages/doc/integrations_collectd_zookeeper.md
@@ -4,10 +4,10 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_zookeeper.html
-summary: Learn how to send ZooKeeper data collected by collectd to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn how to send ZooKeeper data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-[Apache ZooKeeper](https://zookeeper.apache.org/) is a popular service for maintaining configuration and coordinating distributed systems. ZooKeeper is used by technologies like Hadoop and Apache Solr to coordinate clusters and help them run reliably. VMware Aria Operations for Applications supports a built-in integration that gets data from ZooKeeper using Telegraf. If you want to use collectd instead, follow the instructions on this page.
+[Apache ZooKeeper](https://zookeeper.apache.org/) is a popular service for maintaining configuration and coordinating distributed systems. ZooKeeper is used by technologies like Hadoop and Apache Solr to coordinate clusters and help them run reliably. Tanzu Observability supports a built-in integration that gets data from ZooKeeper using Telegraf. If you want to use collectd instead, follow the instructions on this page.
The collectd ZooKeeper plugin documentation can be found at [collectd.conf(5) – collectd – The system statistics collection daemon](https://collectd.org/documentation/manpages/collectd.conf.5.shtml#plugin_zookeeper).
diff --git a/pages/doc/integrations_gcp_API.md b/pages/doc/integrations_gcp_API.md
index 764c21bb7..cad9cd88e 100644
--- a/pages/doc/integrations_gcp_API.md
+++ b/pages/doc/integrations_gcp_API.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_gcp_api.html
summary: Understand how to set up and manage the GCP integration by using our REST API.
---
-The Google Cloud Platform integration allows you to ingest metrics directly from GCP. In addition to setting up and managing the GCP integration through the UI, you can also use the REST API for setting up and managing the GCP integration. This doc page provides some basic steps and examples on how to do this.
+The Google Cloud Platform integration allows you to ingest metrics directly from GCP to Tanzu Observability (formerly known as VMware Aria Operations for Applications). In addition to setting up and managing the GCP integration through the UI, you can also use the REST API for setting up and managing the GCP integration. This doc page provides some basic steps and examples on how to do this.
{% include note.html content="You must have the [**Proxy Management** permission](permissions_overview.html) to set up an GCP integration." %}
@@ -14,7 +14,7 @@ In these examples, you access the REST API through the interface, so that you do
## Before You Start
-When you set up a Google Cloud Platform integration, you have to give the VMware Aria Operations for Applications service permissions to access the data you want to visualize and analyze.
+When you set up a Google Cloud Platform integration, you have to give the Tanzu Observability service permissions to access the data you want to visualize and analyze.
For information, see [Google Cloud Platform Overview and Permissions](integrations_gcp_overview.html).
@@ -132,7 +132,7 @@ We also change the service refresh rate from `5` to `10` minutes.
- {% include note.html content="The values that we pass as `categoriesToFetch` are not the same as the ones displayed in the Operations for Applications UI." %}
+ {% include note.html content="The values that we pass as `categoriesToFetch` are not the same as the ones displayed in the Tanzu Observability UI." %}
1. To change the service refresh rate to 10 minutes, update the `"serviceRefreshRateInMins"` value:
@@ -165,7 +165,7 @@ We also change the service refresh rate from `5` to `10` minutes.
```
- {% include note.html content="The values that we pass as `categoriesToFetch` are not the same as the ones displayed in the Operations for Applications UI." %}
+ {% include note.html content="The values that we pass as `categoriesToFetch` are not the same as the ones displayed in the Tanzu Observability UI." %}
1. In the REST API documentation UI, click the `PUT /api/v2/cloudintegration/{id}` request.
1. Under **Parameters**, in the **id** text box enter the ID of the integration that you want to update.
@@ -175,7 +175,7 @@ We also change the service refresh rate from `5` to `10` minutes.
## Enable and Disable a GCP Integration
-VMware Aria Operations for Applications automatically disables integrations that are experiencing errors due to invalid credentials. To enable an integration after the credential has been corrected or to manually disable an integration, you need the integration ID.
+Tanzu Observability automatically disables integrations that are experiencing errors due to invalid credentials. To enable an integration after the credential has been corrected or to manually disable an integration, you need the integration ID.
1. In the REST API documentation UI, click the `GET/api/v2/cloudintegration` request.
1. Click **Execute**.
diff --git a/pages/doc/integrations_gcp_overview.md b/pages/doc/integrations_gcp_overview.md
index 453636718..d7f459cab 100644
--- a/pages/doc/integrations_gcp_overview.md
+++ b/pages/doc/integrations_gcp_overview.md
@@ -7,12 +7,12 @@ permalink: integrations_gcp_overview.html
summary: Minimum permissions for Google Cloud Platform.
---
-When you set up a Google Cloud Platform integration, you have to give the VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) service permissions to access the data you want to visualize and analyze.
+When you set up a Google Cloud Platform integration, you have to give the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service permissions to access the data you want to visualize and analyze.
## Access Options
-Data flows from GCP to VMware Aria Operations for Applications only if the account has the required access. You have several options, discussed in detail below
+Data flows from GCP to Tanzu Observability only if the account has the required access. You have several options, discussed in detail below
@@ -22,7 +22,7 @@ Data flows from GCP to VMware Aria Operations for Applications only if the accou
Assign predefined roles
-
In most cases, it makes sense to give the Aria Operations for Applications account a small set of predefined roles.
+
In most cases, it makes sense to give the Tanzu Observability account a small set of predefined roles.
Create IAM policy to specify limited access
Explicitly specify the access settings in a custom IAM policy.
diff --git a/pages/doc/integrations_grafana.md b/pages/doc/integrations_grafana.md
index 318feca07..ff3d26605 100644
--- a/pages/doc/integrations_grafana.md
+++ b/pages/doc/integrations_grafana.md
@@ -1,23 +1,23 @@
---
-title: Set Up VMware Aria Operations for Applications as a PromQL Data Source in Grafana
+title: Set Up Tanzu Observability as a PromQL Data Source in Grafana
keywords:
tags: [integrations, grafana]
sidebar: doc_sidebar
permalink: integrations_grafana.html
-summary: Learn how you can set up VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) as a Prometheus data source in Grafana.
+summary: Learn how you can set up Tanzu Observability (formerly known as VMware Aria Operations for Applications) as a Prometheus data source in Grafana.
---
-In addition to [setting up and using VMware Aria Operations for Applications as a Wavefront Query Language data source in Grafana](grafana.html), you can also use VMware Aria Operations for Applications as a Prometheus data source in Grafana.
+In addition to [setting up and using Tanzu Observability as a Wavefront Query Language data source in Grafana](grafana.html), you can also use Tanzu Observability as a Prometheus data source in Grafana.
-When you set up VMware Aria Operations for Applications as a data source in Grafana, you can view the data stored in VMware Aria Operations for Applications by using the Grafana GUI.
+When you set up Tanzu Observability as a data source in Grafana, you can view the data stored in Tanzu Observability by using the Grafana GUI.
-## Set Up VMware Aria Operations for Applications as a Prometheus Data Source
+## Set Up Tanzu Observability as a Prometheus Data Source
-To set up VMware Aria Operations for Applications as a PromQL data source in Grafana, you must provide an API Token.
+To set up Tanzu Observability as a PromQL data source in Grafana, you must provide an API Token.
-
+If your Tanzu Observability service is **not** onboarded to VMware Cloud services, the API token must be a [valid Tanzu Observability API token](api_tokens.html) of a user account or a service account that can run queries. -->
1. Log in to your Grafana instance.
2. In the Navigation bar on the left, click **Configuration**.
@@ -39,19 +39,19 @@ If your Operations for Applications service is **not** onboarded to VMware Cloud
8. Click **Save and Test**.
-## How to Use VMware Aria Operations for Applications as a Prometheus Data Source
+## How to Use Tanzu Observability as a Prometheus Data Source
-To use VMware Aria Operations for Applications as a PromQL data source, make sure that [PromQL support is enabled on your cluster](https://docs.wavefront.com/wavefront_prometheus.html#set-promql-organization-settings-administrator-only).
+To use Tanzu Observability as a PromQL data source, make sure that [PromQL support is enabled on your cluster](https://docs.wavefront.com/wavefront_prometheus.html#set-promql-organization-settings-administrator-only).
-{% include important.html content="After the setup, the behavior of the PromQL queries that you run in Grafana will be the same as the behavior of the same queries that you run in our GUI. All limitations and best practices for using PromQL in VMware Aria Operations for Applications apply. For information, see [Using PromQL in VMware Aria Operations for Applications](https://docs.wavefront.com/wavefront_prometheus.html)." %}
+{% include important.html content="After the setup, the behavior of the PromQL queries that you run in Grafana will be the same as the behavior of the same queries that you run in our GUI. All limitations and best practices for using PromQL in Tanzu Observability apply. For information, see [Using PromQL in Tanzu Observability](https://docs.wavefront.com/wavefront_prometheus.html)." %}
-You can now test and see that a PromQL query in VMware Aria Operations for Applications returns the same result as a PromQL query in Grafana when the data source is the VMware Aria Operations for Applications cluster that you have configured.
+You can now test and see that a PromQL query in Tanzu Observability returns the same result as a PromQL query in Grafana when the data source is the Tanzu Observability cluster that you have configured.
-* A PromQL query in VMware Aria Operations for Applications:
+* A PromQL query in Tanzu Observability:
-* Same PromQL query in Grafana when the data source is the VMware Aria Operations for Applications cluster that you have just set up.
+* Same PromQL query in Grafana when the data source is the Tanzu Observability cluster that you have just set up.
diff --git a/pages/doc/integrations_log_data.md b/pages/doc/integrations_log_data.md
index 584e9321e..0847c74af 100644
--- a/pages/doc/integrations_log_data.md
+++ b/pages/doc/integrations_log_data.md
@@ -4,13 +4,13 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_log_data.html
-summary: Learn how to send log data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) by setting up a proxy and configuring Filebeat or TCP.
+summary: Learn how to send log data to Tanzu Observability (formerly known as VMware Aria Operations for Applications) by setting up a proxy and configuring Filebeat or TCP.
---
-VMware Aria Operations for Applications supports two methods for sending log data metrics to a Wavefront proxy: Filebeat and TCP. Wavefront proxy 4.4 and later supports these methods.
+Tanzu Observability supports two methods for sending log data metrics to a Wavefront proxy: Filebeat and TCP. Wavefront proxy 4.4 and later supports these methods.
**Warning** Log ingestion functionality does not work well if you use a load balancer in your environment.
-* When traffic is split between nodes, each node tracks its own counter. The counters collide when they are sent to VMware Aria Operations for Applications.
+* When traffic is split between nodes, each node tracks its own counter. The counters collide when they are sent to Tanzu Observability.
* Information about the actual source (host) is lost.
The [Create Metrics from Logs for Real-Time Cloud Application Monitoring](https://tanzu.vmware.com/content/vmware-tanzu-observability-blog/engineering-tips-series-create-metrics-from-logs-for-real-time-cloud-application-monitoring-without-breaking-your-bank) blog post discusses a real example and complements this page.
@@ -25,7 +25,7 @@ The built-in Log Data integration guides you through installing a Wavefront prox
## Configuring the Wavefront Proxy to Ingest Log Data
-In this example, we configure VMware Aria Operations for Applications to parse [Combined Apache Logs](http://httpd.apache.org/docs/2.4/logs.html#combined), which is a common logging format for many web services (for example, NGiNX). The example is merely a starting point— so you understand how to ingest metrics from any log format.
+In this example, we configure Tanzu Observability to parse [Combined Apache Logs](http://httpd.apache.org/docs/2.4/logs.html#combined), which is a common logging format for many web services (for example, NGiNX). The example is merely a starting point— so you understand how to ingest metrics from any log format.
### Configuring the Wavefront Proxy to Listen for Log Data
@@ -143,7 +143,7 @@ The Wavefront proxy automatically assigns metrics a **source** according to the
### Instructions
-1. Install [Filebeat](http://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation.html) on any production node that has log data to send to Operations for Applications:
+1. Install [Filebeat](http://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation.html) on any production node that has log data to send to Tanzu Observability:
- **Ubuntu**:
$ curl -L -O https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-5.0.1-amd64.deb
diff --git a/pages/doc/integrations_pks.md b/pages/doc/integrations_pks.md
index 19b6fc165..d3158d615 100644
--- a/pages/doc/integrations_pks.md
+++ b/pages/doc/integrations_pks.md
@@ -12,7 +12,7 @@ On this page, we list predefined alerts and give other details about the integra
## Predefined Alerts for the Integration
-The Tanzu Kubernetes Grid integration provides the following monitoring alerts for PKS. These alerts are predefined, no additional setup is required. You can [create additional alerts](alerts_manage.html) from the **Alerts** browser or from charts in the VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) GUI.
+The Tanzu Kubernetes Grid integration provides the following monitoring alerts for PKS. These alerts are predefined, no additional setup is required. You can [create additional alerts](alerts_manage.html) from the **Alerts** browser or from charts in the Tanzu Observability (formerly known as VMware Aria Operations for Applications) GUI.
@@ -57,7 +57,7 @@ The Tanzu Kubernetes Grid integration provides the following monitoring alerts f
## Tanzu Kubernetes Grid Monitoring Dashboards
-VMware Aria Operations for Applications includes several predefined dashboards for monitoring Tanzu Kubernetes Grid. You can use these dashboards as is, or [clone and customize them](ui_dashboards.html).
+Tanzu Observability includes several predefined dashboards for monitoring Tanzu Kubernetes Grid. You can use these dashboards as is, or [clone and customize them](ui_dashboards.html).
We support dashboards for major functionality including:
* Home dashboard
@@ -79,7 +79,7 @@ The Wavefront proxy pod includes four containers.
-VMware Aria Operations for Applications runs a Wavefront proxy pod inside each Kubernetes cluster created by Tanzu Kubernetes Grid. There are four containers within the Wavefront proxy pod.
+Tanzu Observability runs a Wavefront proxy pod inside each Kubernetes cluster created by Tanzu Kubernetes Grid. There are four containers within the Wavefront proxy pod.
## Troubleshooting the Tanzu Kubernetes Grid Integration
diff --git a/pages/doc/integrations_vrops.md b/pages/doc/integrations_vrops.md
index 5e5b272f4..980383498 100644
--- a/pages/doc/integrations_vrops.md
+++ b/pages/doc/integrations_vrops.md
@@ -4,22 +4,21 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_vrops.html
-summary: Understand the setup and the VMware Aria Operations (SaaS)integration v1 limitations and caveats.
+summary: Understand the setup and the VMware Aria Operations (SaaS) integration v1 limitations and caveats.
---
[VMware Aria Operations (SaaS)](https://www.vmware.com/products/aria-operations.html) (formerly vRealize Operations Cloud) delivers intelligent operations management with application-to-storage visibility across physical, virtual, and cloud infrastructures. Using policy-based automation, operations teams automate key processes and improve the IT efficiency.
-
-The VMware Aria Operations (SaaS) integration is a full-featured native integration that offers agentless data ingestion of VMware Aria Operations (SaaS) metric data, as well as a predefined dashboard.
+The VMware Aria Operations (SaaS) integration is a full-featured native integration that offers agentless data ingestion of VMware Aria Operations (SaaS) metric data into Tanzu Observability (formerly known as VMware Aria Operations for Applications), as well as a predefined dashboard.
{% include important.html content="The VMware Aria Operations (SaaS) integration v1 is the first version of this integration and currently fetches only vCenter Server adapter resources, such as Cluster Compute Resource and Datastore. We will add more features to this integration in future releases." %}
## How to Register a VMware Aria Operations (SaaS) Integration
-To register a new VMware Aria Operations (SaaS) instance, you need a Cloud Services console API token and a VMware Aria Operations (SaaS) endpoint URL.
+To register a new VMware Aria Operations (SaaS) instance, you need a VMware Cloud services API token and a VMware Aria Operations (SaaS) endpoint URL.
### Obtain an API Token
-The API token will give read-only access to VMware Aria Operations (SaaS) and enable VMware Aria Operations for Applications (formerly Tanzu Observability by Wavefront) to continually load metrics from various resource categories. The minimum role required for the integration is the **Operations ReadOnly** role. Make sure that the role assigned to the API token is also assigned to the user generating the API token.
+The API token will give read-only access to VMware Aria Operations (SaaS) and enable Tanzu Observability to continually load metrics from various resource categories. The minimum role required for the integration is the **Operations ReadOnly** role. Make sure that the role assigned to the API token is also assigned to the user generating the API token.
1. Navigate to the [VMware Cloud Services Console](https://console.cloud.vmware.com/csp/gateway/discovery) page.
1. Click your user name on the right of the toolbar, and select **My Account**.
@@ -41,7 +40,7 @@ The API token will give read-only access to VMware Aria Operations (SaaS) and en
### Set Up the VMware Aria Operations (SaaS) Integration
-1. Log in to your Operations for Applications instance.
+1. Log in to your Tanzu Observability instance.
1. Click **Integrations** on the toolbar.
1. In the VMware section, click the **VMware Aria Operations (SaaS)** tile.
1. Click **Add Integration**.
@@ -85,7 +84,7 @@ With this initial, v1 release of the VMware Aria Operations (SaaS) integration,
You can see the full list of the collected metrics on the **Metrics Browser** page.
-1. In your VMware Aria Operations for Applications cluster, click **Browse > Metrics**.
+1. In the Tanzu Observability UI, click **Browse > Metrics**.
2. On the **Metrics Browser** page, in the **Metrics** text box, enter `vrops.vmware.`.
3. Click the folder icons to drill down to the individual metrics.
@@ -95,7 +94,7 @@ This initial release of the VMware Aria Operations (SaaS) integration has the fo
* For supermetrics, such as `Cost Drivers - Facilities (US $/Month)`, `Total Server Purchase Cost`, and so on, the metric names are not fetched and in our UI, these metrics are displayed with the super metric ID.
* The VMware Aria Operations (SaaS) metrics have a point tag, which represents the organization ID. This is the UUIF of the organization. Currently, we collect the Organization ID as a point tag, instead of the Organization name.
-* Along with the summary for a resource, in VMware Aria Operations (SaaS) there might be other properties. In Operations for Applications, currently we do not collect such properties. The VMware VMware Aria Operations (SaaS) integration only collects properties under the summary section as point tags.
+* Along with the summary for a resource, in VMware Aria Operations (SaaS) there might be other properties. In Tanzu Observability, currently we do not collect such properties. The VMware VMware Aria Operations (SaaS) integration only collects properties under the summary section as point tags.
* In this release, you will see all the vCenter Server instances that you have configured in VMware Aria Operations (SaaS). To shortlist the vCenter Server instances you want to monitor, apply a filter by using the REST API.
1. In your cluster, click the gear icon in the top right corner, and select **API Documentation**.
2. Expand **Cloud Integration** and click the `GET /api/v2/cloudintegration` request.
@@ -130,4 +129,4 @@ This initial release of the VMware Aria Operations (SaaS) integration has the fo
9. In the **Edit Value** text box, enter the contents of the JSON file that you created in Step 6.
10. Click **Execute**.
- You get a `200` response and in the Operations for Applications UI, you can see that the vCenter Server instances are filtered out.
+ You get a `200` response and in the Tanzu Observability UI, you can see that the vCenter Server instances are filtered out.
diff --git a/pages/labels/label_integrations%20list.md b/pages/labels/label_integrations%20list.md
index c7fa88456..aee969632 100644
--- a/pages/labels/label_integrations%20list.md
+++ b/pages/labels/label_integrations%20list.md
@@ -7,14 +7,14 @@ sidebar: doc_sidebar
folder: labels
---
-
If your Operations for Applications service is onboarded to VMware Cloud services, you still can see, but cannot configure some of our integrations. For the list of integrations that we support when your Operations for Applications service is onboarded to VMware Cloud services, see Integrations Supported for Onboarded Subscriptions.
+
If your Tanzu Observability (formerly known as VMware Aria Operations for Applications) service is onboarded to VMware Cloud services, you still can see, but cannot configure some of our integrations. For the list of integrations that we support when your Tanzu Observability service is onboarded to VMware Cloud services, see Integrations Supported for Onboarded Subscriptions.
The documentation pages only for a limited number of integrations contain the setup steps and instructions. If you do not see the setup steps on a certain integration doc page:
-
Navigate to the Operations for Applications GUI and click Integrations on the toolbar.
+
Navigate to the Tanzu Observability GUI and click Integrations on the toolbar.
Search for the integration that you want to set up and click its tile.
The detailed instructions for setting up and configuring the integration are on the Setup tab.
-
Here's how to learn about the VMware Aria Operations for Applications integrations:
+
Here's how to learn about the Tanzu Observability integrations:
From b5ee16520be1b2d7d401739b4c94f551b3b71986 Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Tue, 5 Mar 2024 16:17:15 +0200
Subject: [PATCH 03/26] Rebranding - Logs section
---
pages/doc/logging_log_alerts.md | 4 ++--
pages/doc/logging_logs_settings.md | 6 +++---
pages/doc/logging_overview.md | 6 +++---
pages/doc/logging_proxy_configurations.md | 6 +++---
pages/doc/logging_send_logs.md | 2 +-
5 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/pages/doc/logging_log_alerts.md b/pages/doc/logging_log_alerts.md
index 9adf081d8..98e5a0259 100644
--- a/pages/doc/logging_log_alerts.md
+++ b/pages/doc/logging_log_alerts.md
@@ -6,7 +6,7 @@ permalink: logging_log_alerts.html
summary: Learn how you can create, snooze and delete a logs alert.
---
-{% include important.html content="Our service retains logs for 30 days during the Logs free trial or retains logs for 7 days when on the freemium subscription! To retain logs for a longer period, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
+{% include important.html content="Tanzu Observability (formerly known as VMware Aria Operations for Applications) retains logs for 30 days during the Logs free trial or retains logs for 7 days when on the freemium subscription! To retain logs for a longer period, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
You can create alerts for your logs data and see the firing events of an alert.
@@ -358,4 +358,4 @@ Follow these steps to delete a logs alert you no longer need:
### What are the logs alert limits?
-Operations for Applications uses VMware Aria Operations for logs. See the limitations listed on the [Operations for logs documentation (scroll to Limits)](https://developer.vmware.com/apis/vmware-aria-operations-for-logs/latest/) when creating and managing logs alerts.
+Tanzu Observability uses VMware Aria Operations for Logs (SaaS). See the limitations listed on the [Operations for logs documentation (scroll to Limits)](https://developer.vmware.com/apis/vmware-aria-operations-for-logs/latest/) when creating and managing logs alerts.
diff --git a/pages/doc/logging_logs_settings.md b/pages/doc/logging_logs_settings.md
index 1899b5f4d..3f98d9e96 100644
--- a/pages/doc/logging_logs_settings.md
+++ b/pages/doc/logging_logs_settings.md
@@ -3,14 +3,14 @@ title: Customize Logs Settings
tags: [logs]
sidebar: doc_sidebar
permalink: logging_logs_settings.html
-summary: Learn how you can customize logs settings from the Organization Settings page.
+summary: Learn how you can customize logs settings in Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
Users with access to the logs settings can map metrics tags to logs tags, traces tags to logs tags, and customize the time window you see on a chart or Traces Browser when you drill into logs from a chart and trace.
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
+{% include note.html content="Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
- For VMware Cloud services subscriptions, only users with the **Super Admin** service role in Super Admin mode can customize the logs settings.
-- For original Operations for Applications subscriptions, users with the **Accounts** permission can customize the logs settings."%}
+- For original Tanzu Observability subscriptions, users with the **Accounts** permission can customize the logs settings."%}
## Map Tags
diff --git a/pages/doc/logging_overview.md b/pages/doc/logging_overview.md
index 3ca4ee6f5..b7493c1e0 100644
--- a/pages/doc/logging_overview.md
+++ b/pages/doc/logging_overview.md
@@ -3,7 +3,7 @@ title: Get Started with Logs
tags: [getting started, logs]
sidebar: doc_sidebar
permalink: logging_overview.html
-summary: Learn about VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) metrics, logs, and traces.
+summary: Learn about Tanzu Observability (formerly known as VMware Aria Operations for Applications) metrics, logs, and traces.
---
{% include important.html content="The Logs feature is enabled only for selected customers. To participate, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
@@ -12,7 +12,7 @@ summary: Learn about VMware Aria Operations for Applications (formerly known as
- VMware Aria Operations for Applications helps you monitor your application using metrics, traces, and logs.
+ Tanzu Observability helps you monitor your application using metrics, traces, and logs.
For example, you can:
@@ -27,7 +27,7 @@ summary: Learn about VMware Aria Operations for Applications (formerly known as
- 
+ 
diff --git a/pages/doc/logging_proxy_configurations.md b/pages/doc/logging_proxy_configurations.md
index afef7d064..5c55b6269 100644
--- a/pages/doc/logging_proxy_configurations.md
+++ b/pages/doc/logging_proxy_configurations.md
@@ -3,7 +3,7 @@ title: Logs Proxy Configurations and Preprocessor Rules
tags: [getting started, logs]
sidebar: doc_sidebar
permalink: logging_proxy_configurations.html
-summary: Proxy configuration properties and preprocessor rules for logging.
+summary: Proxy configuration properties and preprocessor rules for ingesting logs into Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
{% include important.html content="The Logs feature is enabled only for selected customers. To participate, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
@@ -164,9 +164,9 @@ We've added the following configuration properties for logs to the already exist
### Properties for VMware Cloud Services Subscriptions
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Operations for Applications subscriptions **onboarded** to the VMware Cloud services platform and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until they migrate to VMware Cloud services. The content in this section is valid for **onboarded** subscribers. For information about original and new subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html)." %}
+{% include note.html content="Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the VMware Cloud services platform and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until they migrate to VMware Cloud services. The content in this section is valid for **onboarded** subscribers. For information about original and new subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html)." %}
-VMware Cloud services provides access to both VMware Aria Operations for Logs and VMware Aria Operations for Applications. Therefore, to send logs data and see the data on the Operations for Applications Logs Browser, you must configure the proxy with the Operations for Logs URL and token.
+VMware Cloud services provides access to both VMware Aria Operations for Logs (SaaS) and Tanzu Observability. Therefore, to send logs data and see the data on the Tanzu Observability Logs Browser, you must configure the proxy with the Operations for Logs URL and token.
diff --git a/pages/doc/logging_send_logs.md b/pages/doc/logging_send_logs.md
index fa07357a2..407d5234b 100644
--- a/pages/doc/logging_send_logs.md
+++ b/pages/doc/logging_send_logs.md
@@ -4,7 +4,7 @@ keywords: data, logs
tags: [getting started, logs]
sidebar: doc_sidebar
permalink: logging_send_logs.html
-summary: Learn about sending logs to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn about sending logs to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
{% include important.html content="The Logs feature is enabled only for selected customers. To participate, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
From 38308b938a6bd3747e7adf1397949065528be188 Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Tue, 12 Mar 2024 18:57:39 +0200
Subject: [PATCH 04/26] Product long name on 1st mentions
---
pages/doc/2020_10.x_release_notes.md | 2 +-
pages/doc/2020_14.x_release_notes.md | 2 +-
pages/doc/2020_22.x_release_notes.md | 2 +-
pages/doc/2020_26.x_release_notes.md | 2 +-
pages/doc/2020_30.x_release_notes.md | 2 +-
pages/doc/2020_38.x_release_notes.md | 2 +-
pages/doc/2020_42.x_release_notes.md | 2 +-
pages/doc/2021-08.x_release_notes.md | 2 +-
pages/doc/2021-14.x_release_notes.md | 2 +-
pages/doc/2021-19.x_release_notes.md | 2 +-
pages/doc/2021-24.x_release_notes.md | 2 +-
pages/doc/2021-35.x_release_notes.md | 2 +-
pages/doc/2021-49.x_release_notes.md | 2 +-
pages/doc/2022-06.x_release_notes.md | 2 +-
pages/doc/2022-20.x_release_notes.md | 2 +-
pages/doc/2022-29.x_release_notes.md | 2 +-
pages/doc/2022-39.x_release_notes.md | 2 +-
pages/doc/2022-49.x_release_notes.md | 2 +-
pages/doc/2023-06.x_release_notes.md | 2 +-
pages/doc/2023-13.x_release_notes.md | 2 +-
pages/doc/2023-29.x_release_notes.md | 2 +-
pages/doc/2023-45.x_release_notes.md | 2 +-
pages/doc/alert_target_customizing.md | 2 +-
pages/doc/alerts.md | 2 +-
pages/doc/alerts_best_practices.md | 2 +-
pages/doc/alerts_delayed_data.md | 2 +-
pages/doc/alerts_dependencies.md | 2 +-
pages/doc/alerts_faq.md | 2 +-
pages/doc/alerts_manage.md | 2 +-
pages/doc/alerts_missing_data.md | 2 +-
pages/doc/alerts_notifications.md | 2 +-
pages/doc/alerts_recipes.md | 2 +-
pages/doc/alerts_states_lifecycle.md | 2 +-
pages/doc/cardinality.md | 2 +-
pages/doc/chart_builder.md | 2 +-
pages/doc/cloud_integrations_troubleshooting.md | 2 +-
pages/doc/csp_area_differences.md | 2 +-
pages/doc/csp_migration.md | 2 +-
pages/doc/csp_subscription_types.md | 2 +-
pages/doc/csp_supported_integrations.md | 2 +-
pages/doc/csp_ui_differences.md | 2 +-
pages/doc/delta_counters.md | 2 +-
pages/doc/derived_metrics.md | 2 +-
pages/doc/direct_ingestion.md | 2 +-
pages/doc/events.md | 2 +-
pages/doc/integrations_aws_ecs.md | 2 +-
pages/doc/integrations_aws_key_age.md | 2 +-
pages/doc/integrations_aws_lambda.md | 2 +-
pages/doc/integrations_aws_metrics.md | 2 +-
pages/doc/integrations_aws_overview-API.md | 2 +-
pages/doc/integrations_aws_overview.md | 2 +-
pages/doc/integrations_bigpanda_troubleshoot.md | 2 +-
pages/doc/integrations_cloudhealth.md | 2 +-
pages/doc/integrations_collectd.md | 2 +-
pages/doc/integrations_collectd_apache.md | 2 +-
pages/doc/integrations_collectd_cassandra.md | 2 +-
pages/doc/integrations_collectd_memcached.md | 2 +-
pages/doc/integrations_collectd_mysql.md | 2 +-
pages/doc/integrations_collectd_ngnix.md | 2 +-
pages/doc/integrations_collectd_redis.md | 2 +-
pages/doc/integrations_collectd_zookeeper.md | 2 +-
pages/doc/integrations_gcp_API.md | 2 +-
pages/doc/integrations_gcp_overview.md | 2 +-
pages/doc/integrations_grafana.md | 2 +-
pages/doc/integrations_log_data.md | 2 +-
pages/doc/integrations_new_changed.md | 2 +-
pages/doc/integrations_new_changed_2020.md | 2 +-
pages/doc/integrations_new_changed_2021.md | 2 +-
pages/doc/integrations_new_changed_2022.md | 2 +-
pages/doc/integrations_new_changed_2023.md | 2 +-
pages/doc/integrations_pks.md | 2 +-
pages/doc/integrations_vrops.md | 2 +-
pages/doc/logging_log_alerts.md | 2 +-
pages/doc/logging_logs_settings.md | 2 +-
pages/doc/logging_overview.md | 2 +-
pages/doc/logging_proxy_configurations.md | 2 +-
pages/doc/logging_send_logs.md | 2 +-
pages/doc/metric_types.md | 2 +-
pages/doc/metrics_managing.md | 2 +-
pages/doc/missing_data_troubleshooting.md | 2 +-
pages/doc/optimize_data_shape.md | 2 +-
pages/doc/proxies.md | 2 +-
pages/doc/proxies_configuring.md | 2 +-
pages/doc/proxies_container.md | 2 +-
pages/doc/proxies_histograms.md | 2 +-
pages/doc/proxies_installing.md | 2 +-
pages/doc/proxies_kube_container.md | 2 +-
pages/doc/proxies_manual_install.md | 2 +-
pages/doc/proxies_preprocessor_rules.md | 2 +-
pages/doc/proxies_troubleshooting.md | 2 +-
pages/doc/purchase-additional-capacity.md | 2 +-
pages/doc/query_editor.md | 2 +-
pages/doc/query_language_aggregate_functions.md | 2 +-
pages/doc/query_language_align_function.md | 2 +-
pages/doc/query_language_discrete_continuous.md | 2 +-
pages/doc/query_language_getting_started.md | 2 +-
pages/doc/query_language_metadata_functions.md | 2 +-
pages/doc/query_language_performance.md | 2 +-
pages/doc/query_language_point_tags.md | 2 +-
pages/doc/query_language_recipes.md | 2 +-
pages/doc/query_language_reference.md | 2 +-
pages/doc/query_language_series_joining.md | 2 +-
pages/doc/query_language_series_matching.md | 2 +-
pages/doc/query_language_windows_trends.md | 2 +-
pages/doc/sources_managing.md | 2 +-
pages/doc/start_trial.md | 6 +++---
pages/doc/tags_overview.md | 2 +-
pages/doc/upgrade-and-purchase.md | 2 +-
pages/doc/visualize_histograms.md | 2 +-
pages/doc/wavefront_data_format.md | 2 +-
pages/doc/wavefront_data_ingestion.md | 2 +-
pages/doc/wavefront_prometheus.md | 2 +-
pages/doc/wavefront_release_notes.md | 2 +-
pages/labels/label_integrations%20list.md | 2 +-
114 files changed, 116 insertions(+), 116 deletions(-)
diff --git a/pages/doc/2020_10.x_release_notes.md b/pages/doc/2020_10.x_release_notes.md
index a9f90c1dc..2b753b47c 100644
--- a/pages/doc/2020_10.x_release_notes.md
+++ b/pages/doc/2020_10.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.10.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020.10 of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service. We also recently released a new version (6.1) of the Wavefront proxy. See the [Wavefront Proxy Release Notes](proxies_versions.html) for details.
+These release notes give an overview of the changes for Release 2020.10 of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service. We also recently released a new version (6.1) of the Wavefront proxy. See the [Wavefront Proxy Release Notes](proxies_versions.html) for details.
## New Histogram Functions
diff --git a/pages/doc/2020_14.x_release_notes.md b/pages/doc/2020_14.x_release_notes.md
index 3286a3025..731b01f90 100644
--- a/pages/doc/2020_14.x_release_notes.md
+++ b/pages/doc/2020_14.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.14.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020.14 of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for Release 2020.14 of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Wavefront for Spring Boot
[Wavefront for Spring Boot](wavefront_springboot.html) allows you to quickly configure your environment, so Spring Boot components send metrics, histograms, and traces/spans to the Wavefront service. After you’ve completed setup, you can examine the data in preconfigured or custom Wavefront dashboards.
diff --git a/pages/doc/2020_22.x_release_notes.md b/pages/doc/2020_22.x_release_notes.md
index b52ddb1a8..7ddefa992 100644
--- a/pages/doc/2020_22.x_release_notes.md
+++ b/pages/doc/2020_22.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.22.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020.22 of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for Release 2020.22 of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
{% include note.html content="[Tracing](tracing_basics.html) and [Histograms](proxies_histograms.html) are available by default for all customers starting with this release. Try them out and contact [support@wavefront.com](mailto:support@wavefront.com) if you have any questions." %}
diff --git a/pages/doc/2020_26.x_release_notes.md b/pages/doc/2020_26.x_release_notes.md
index 6b970b80f..350a5f07f 100644
--- a/pages/doc/2020_26.x_release_notes.md
+++ b/pages/doc/2020_26.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.26.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020.26 of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for Release 2020.26 of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## PromQL Support (Beta)
diff --git a/pages/doc/2020_30.x_release_notes.md b/pages/doc/2020_30.x_release_notes.md
index 35659d67b..8381a5754 100644
--- a/pages/doc/2020_30.x_release_notes.md
+++ b/pages/doc/2020_30.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.30.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020-30.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for Release 2020-30.x of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## OpenTelemetry Support in Wavefront
diff --git a/pages/doc/2020_38.x_release_notes.md b/pages/doc/2020_38.x_release_notes.md
index 809954221..15bd4d5a4 100644
--- a/pages/doc/2020_38.x_release_notes.md
+++ b/pages/doc/2020_38.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.38.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020-38.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for Release 2020-38.x of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Metrics Security
diff --git a/pages/doc/2020_42.x_release_notes.md b/pages/doc/2020_42.x_release_notes.md
index 5fe4598a8..ee0a59a99 100644
--- a/pages/doc/2020_42.x_release_notes.md
+++ b/pages/doc/2020_42.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2020.42.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2020-42.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for Release 2020-42.x of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Apdex Score for Services
diff --git a/pages/doc/2021-08.x_release_notes.md b/pages/doc/2021-08.x_release_notes.md
index b35c1e59c..5d0f94eb2 100644
--- a/pages/doc/2021-08.x_release_notes.md
+++ b/pages/doc/2021-08.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.08.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2021-02.x to 2021-08.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for Release 2021-02.x to 2021-08.x of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Delta Counter Changes
diff --git a/pages/doc/2021-14.x_release_notes.md b/pages/doc/2021-14.x_release_notes.md
index f334d7c2b..7bc9140f7 100644
--- a/pages/doc/2021-14.x_release_notes.md
+++ b/pages/doc/2021-14.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.14.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for Release 2021-09.x to 2021-14.x of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for Release 2021-09.x to 2021-14.x of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## Partial Regex Support
diff --git a/pages/doc/2021-19.x_release_notes.md b/pages/doc/2021-19.x_release_notes.md
index 48437b074..09486f568 100644
--- a/pages/doc/2021-19.x_release_notes.md
+++ b/pages/doc/2021-19.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.19.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2021-15.x to 2021-19.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2021-15.x to 2021-19.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2021-19.x Release Notes
diff --git a/pages/doc/2021-24.x_release_notes.md b/pages/doc/2021-24.x_release_notes.md
index 6bb5755eb..136f7ff0b 100644
--- a/pages/doc/2021-24.x_release_notes.md
+++ b/pages/doc/2021-24.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.24.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2021-20.x to 2021-24.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2021-20.x to 2021-24.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2021-24.x Release Notes
diff --git a/pages/doc/2021-35.x_release_notes.md b/pages/doc/2021-35.x_release_notes.md
index c8d4f0418..00f695bd3 100644
--- a/pages/doc/2021-35.x_release_notes.md
+++ b/pages/doc/2021-35.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.35.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2021-26.x to 2021-35.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2021-26.x to 2021-35.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2021-35.x Release Notes
diff --git a/pages/doc/2021-49.x_release_notes.md b/pages/doc/2021-49.x_release_notes.md
index e7a625f2c..2a2135557 100644
--- a/pages/doc/2021-49.x_release_notes.md
+++ b/pages/doc/2021-49.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2021.49.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2021-40.x to 2021-49.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2021-40.x to 2021-49.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2021-49.x Release Notes
diff --git a/pages/doc/2022-06.x_release_notes.md b/pages/doc/2022-06.x_release_notes.md
index 71517a6e3..dd998fceb 100644
--- a/pages/doc/2022-06.x_release_notes.md
+++ b/pages/doc/2022-06.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-06.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-01.x to 2022-06.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2022-01.x to 2022-06.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-06.x Release Notes
diff --git a/pages/doc/2022-20.x_release_notes.md b/pages/doc/2022-20.x_release_notes.md
index 4794d1a53..0c68e617b 100644
--- a/pages/doc/2022-20.x_release_notes.md
+++ b/pages/doc/2022-20.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-20.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-08.x to 2022-20.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2022-08.x to 2022-20.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-20.x Release Notes
diff --git a/pages/doc/2022-29.x_release_notes.md b/pages/doc/2022-29.x_release_notes.md
index 5754e5289..bc9e273e9 100644
--- a/pages/doc/2022-29.x_release_notes.md
+++ b/pages/doc/2022-29.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-29.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-22.x to 2022-29.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2022-22.x to 2022-29.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-29.x Release Notes
diff --git a/pages/doc/2022-39.x_release_notes.md b/pages/doc/2022-39.x_release_notes.md
index cc4964d53..cd0142549 100644
--- a/pages/doc/2022-39.x_release_notes.md
+++ b/pages/doc/2022-39.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-39.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-32.x to 2022-39.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2022-32.x to 2022-39.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-39.x Release Notes
diff --git a/pages/doc/2022-49.x_release_notes.md b/pages/doc/2022-49.x_release_notes.md
index b23a4b600..d9e79fc36 100644
--- a/pages/doc/2022-49.x_release_notes.md
+++ b/pages/doc/2022-49.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2022-49.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2022-41.x to 2022-49.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2022-41.x to 2022-49.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2022-49.x Release Notes
diff --git a/pages/doc/2023-06.x_release_notes.md b/pages/doc/2023-06.x_release_notes.md
index ac304b829..325861cce 100644
--- a/pages/doc/2023-06.x_release_notes.md
+++ b/pages/doc/2023-06.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2023-06.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2023-02.x to 2023-06.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2023-02.x to 2023-06.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2023-06.x Release Notes
diff --git a/pages/doc/2023-13.x_release_notes.md b/pages/doc/2023-13.x_release_notes.md
index 7a6eb0043..d4b676923 100644
--- a/pages/doc/2023-13.x_release_notes.md
+++ b/pages/doc/2023-13.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2023-13.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2023-07.x to 2023-13.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2023-07.x to 2023-13.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2023-13.x Release Notes
diff --git a/pages/doc/2023-29.x_release_notes.md b/pages/doc/2023-29.x_release_notes.md
index be5fcf27d..b3ed5af48 100644
--- a/pages/doc/2023-29.x_release_notes.md
+++ b/pages/doc/2023-29.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2023-29.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2023-18.x to 2023-29.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2023-18.x to 2023-29.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2023-29.x Release Notes
diff --git a/pages/doc/2023-45.x_release_notes.md b/pages/doc/2023-45.x_release_notes.md
index 0565a65e4..37b36617d 100644
--- a/pages/doc/2023-45.x_release_notes.md
+++ b/pages/doc/2023-45.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2023-45.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2023-31.x to 2023-45.x releases of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
+These release notes give an overview of the changes for the 2023-31.x to 2023-45.x releases of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service.
## 2023-45.x Release Notes
diff --git a/pages/doc/alert_target_customizing.md b/pages/doc/alert_target_customizing.md
index 320b134d2..931df0ad8 100644
--- a/pages/doc/alert_target_customizing.md
+++ b/pages/doc/alert_target_customizing.md
@@ -7,7 +7,7 @@ permalink: alert_target_customizing.html
summary: Learn how to customize alert notifications by modifying alert target templates.
---
-An alert target provides a template that specifies how Tanzu Observability (formerly known as VMware Aria Operations for Applications) extracts information from the alert, and how to assemble the notification from the alert information.
+An alert target provides a template that specifies how VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) extracts information from the alert, and how to assemble the notification from the alert information.
You can customize the predefined template for the alert target type by making and saving changes. The template uses [Mustache syntax](https://mustache.github.io/) to combine literal text with _variables_ and _functions_ to produce the structures to be sent to the receiving messaging platform.
diff --git a/pages/doc/alerts.md b/pages/doc/alerts.md
index 1df70b497..ce694f327 100644
--- a/pages/doc/alerts.md
+++ b/pages/doc/alerts.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: alerts.html
summary: Learn how alerts work, examine, and organize them.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports smart alerts that dynamically filter noise and capture true anomalies.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports smart alerts that dynamically filter noise and capture true anomalies.
* When the alert condition is met, an alert notifies one or more **alert targets**, which receive the alert notification(s).
* The **alert notification** includes an image and a link to see the alert in context.
* Look all alerts in the **Alert Browser** or examine a single firing alert in the **Alert Viewer**.
diff --git a/pages/doc/alerts_best_practices.md b/pages/doc/alerts_best_practices.md
index cf2d03cd9..9271be58d 100644
--- a/pages/doc/alerts_best_practices.md
+++ b/pages/doc/alerts_best_practices.md
@@ -7,7 +7,7 @@ permalink: alerts_best_practices.html
summary: Learn about best practices for alert creation, alert settings, and alert troubleshooting.
---
-You use alerts in Tanzu Observability (formerly known as VMware Aria Operations for Applications) to get notified when something out of the ordinary happens. Alerts monitor your environment's behavior and send notifications based on how you configure the alert.
+You use alerts in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) to get notified when something out of the ordinary happens. Alerts monitor your environment's behavior and send notifications based on how you configure the alert.
This page has some best practices from our Technical Support engineers to help you set up truly useful alerts and avoid common problems with alerts.
diff --git a/pages/doc/alerts_delayed_data.md b/pages/doc/alerts_delayed_data.md
index 6edc0ca81..aa875dd2d 100644
--- a/pages/doc/alerts_delayed_data.md
+++ b/pages/doc/alerts_delayed_data.md
@@ -7,7 +7,7 @@ permalink: alerts_delayed_data.html
summary: Diagnose and avoid spurious alerts due to delayed data reporting.
---
-An alert fires or resolves based on the data values that are present in Tanzu Observability (formerly known as VMware Aria Operations for Applications) during the alert checking time window. If data reporting is delayed, an alert checking decision might be made on a temporarily incomplete set of data values. This can lead to an apparent false positive (the alert fires when you don't expect it) or false negative (the alert does not fire as expected).
+An alert fires or resolves based on the data values that are present in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) during the alert checking time window. If data reporting is delayed, an alert checking decision might be made on a temporarily incomplete set of data values. This can lead to an apparent false positive (the alert fires when you don't expect it) or false negative (the alert does not fire as expected).
This page can help you understand, diagnose, and prevent the impact of data delays on alerts. Buffering alerts against false positives, in particular, can help you reduce alert noise.
diff --git a/pages/doc/alerts_dependencies.md b/pages/doc/alerts_dependencies.md
index ce6fcdd01..e7b57443f 100644
--- a/pages/doc/alerts_dependencies.md
+++ b/pages/doc/alerts_dependencies.md
@@ -9,7 +9,7 @@ summary: Use alert metrics to build alerts that depend on other alerts.
Metrics can be related in a dependency hierarchy. For example, a login application service is dependent on a user database, and that database is dependent on a hardware host.
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) generates _alert metrics_ for any alert. You can pass the metrics from one alert to the next in the dependency hierarchy.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) generates _alert metrics_ for any alert. You can pass the metrics from one alert to the next in the dependency hierarchy.
## Alert Metrics
diff --git a/pages/doc/alerts_faq.md b/pages/doc/alerts_faq.md
index 364221982..70165180f 100644
--- a/pages/doc/alerts_faq.md
+++ b/pages/doc/alerts_faq.md
@@ -8,7 +8,7 @@ summary: Learn alert customization from our experts.
---
## Why Can't I View and Edit This Alert?
-By default, all users in Tanzu Observability (formerly known as VMware Aria Operations for Applications) can view all alerts. But permissions and access control affect this default.
+By default, all users in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) can view all alerts. But permissions and access control affect this default.
* You must have the **Alerts** permission to edit alerts. The [Alerts](permissions_overview.html) permission applies to all alerts **except** [ingestion policy](ingestion_policies.html) alerts.
- Users with the **Alerts** permission can view, create, and modify alerts except ingestion policy alerts.
diff --git a/pages/doc/alerts_manage.md b/pages/doc/alerts_manage.md
index 6062e3119..86ccddc78 100644
--- a/pages/doc/alerts_manage.md
+++ b/pages/doc/alerts_manage.md
@@ -7,7 +7,7 @@ permalink: alerts_manage.html
summary: Learn how to create and manage alerts.
---
-All users in Tanzu Observability (formerly known as VMware Aria Operations for Applications) can [examine alerts and drill down to find the problem](alerts.html).
+All users in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) can [examine alerts and drill down to find the problem](alerts.html).
{% include note.html content="You need the [**Alerts**](permissions_overview.html) permission to create and manage alerts. If some of the alerts in your environment are under [access control](access.html), you can view or view and modify those alerts only if they've been shared with you." %}
diff --git a/pages/doc/alerts_missing_data.md b/pages/doc/alerts_missing_data.md
index 45586e37a..54dc61279 100644
--- a/pages/doc/alerts_missing_data.md
+++ b/pages/doc/alerts_missing_data.md
@@ -7,7 +7,7 @@ permalink: alerts_missing_data.html
summary: Configure an alert to fire when a time series stops reporting.
---
-Operations for Applications enables you to configure alerts that inform you about machine or application faults. When a machine or application crashes, it stops reporting data to Tanzu Observability -- the data from that source is missing.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) enables you to configure alerts that inform you about machine or application faults. When a machine or application crashes, it stops reporting data to Tanzu Observability -- the data from that source is missing.
This explains how to configure alerts that detect missing data, so you can identify potential failures and resolve them.
diff --git a/pages/doc/alerts_notifications.md b/pages/doc/alerts_notifications.md
index 60d0a6eee..a83f07d85 100644
--- a/pages/doc/alerts_notifications.md
+++ b/pages/doc/alerts_notifications.md
@@ -7,7 +7,7 @@ permalink: alerts_notifications.html
summary: Learn about alert notifications and some special notification use cases.
---
-When an alert in Tanzu Observability (formerly known as VMware Aria Operations for Applications) changes state, it sends notifications to one or more alert targets. Each notification contains information extracted from the alert about its state change. By default, the notification includes a static alert image and a link to the alert chart in Alert Viewer.
+When an alert in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) changes state, it sends notifications to one or more alert targets. Each notification contains information extracted from the alert about its state change. By default, the notification includes a static alert image and a link to the alert chart in Alert Viewer.
## Where and When Notifications Are Sent
diff --git a/pages/doc/alerts_recipes.md b/pages/doc/alerts_recipes.md
index 935a10cb7..b95fb611f 100644
--- a/pages/doc/alerts_recipes.md
+++ b/pages/doc/alerts_recipes.md
@@ -4,7 +4,7 @@ keywords: alerts
tags: [alerts, best practice]
sidebar: doc_sidebar
permalink: alerts_recipes.html
-summary: Queries for common alert scenarios in VTanzu Observability (formerly known as VMware Aria Operations for Applications)
+summary: Queries for common alert scenarios in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications)
---
Our Customer Success team has found that customers use certain alerts frequently. For example, customers want to alert on point rate drops or on between specific times.
diff --git a/pages/doc/alerts_states_lifecycle.md b/pages/doc/alerts_states_lifecycle.md
index d58b49e21..148292551 100644
--- a/pages/doc/alerts_states_lifecycle.md
+++ b/pages/doc/alerts_states_lifecycle.md
@@ -6,7 +6,7 @@ permalink: alerts_states_lifecycle.html
summary: Learn about alert conditions and states, when alerts fire, and how alerts resolve.
---
-Here's a video to get you started with the alerts lifecycle in Tanzu Observability (formerly known as VMware Aria Operations for Applications). Note that this video was created in 2017 and some of the information in it might have changed. It also uses the 2017 version of the UI.
+Here's a video to get you started with the alerts lifecycle in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications). Note that this video was created in 2017 and some of the information in it might have changed. It also uses the 2017 version of the UI.
diff --git a/pages/doc/cardinality.md b/pages/doc/cardinality.md
index 0b087ffdf..0806aa07c 100644
--- a/pages/doc/cardinality.md
+++ b/pages/doc/cardinality.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: cardinality.html
summary: Learn about how the service deals with cardinality.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports high cardinality when dealing with timeseries data and infinite cardinality in its distributed tracing offering. Tanzu Observability can handle more than 200,000 concurrently running containers per Kubernetes cluster. In certain situations, however, high cardinality can cause system slowdown and metrics retrieval issues.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports high cardinality when dealing with timeseries data and infinite cardinality in its distributed tracing offering. Tanzu Observability can handle more than 200,000 concurrently running containers per Kubernetes cluster. In certain situations, however, high cardinality can cause system slowdown and metrics retrieval issues.
## Video
diff --git a/pages/doc/chart_builder.md b/pages/doc/chart_builder.md
index 93ceee39b..ce4341e08 100644
--- a/pages/doc/chart_builder.md
+++ b/pages/doc/chart_builder.md
@@ -7,7 +7,7 @@ permalink: chart_builder.html
summary: Use Chart Builder to display the data you're interested in.
---
-When you get started with Tanzu Observability (formerly known as VMware Aria Operations for Applications), Chart Builder is the fasted way to customize which metrics you see and to display them in charts.
+When you get started with VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications), Chart Builder is the fasted way to customize which metrics you see and to display them in charts.
Chart Builder has the tools for creating charts and customizing which metrics you see.
* Construct queries from building blocks
diff --git a/pages/doc/cloud_integrations_troubleshooting.md b/pages/doc/cloud_integrations_troubleshooting.md
index e5efc4295..504698a3c 100644
--- a/pages/doc/cloud_integrations_troubleshooting.md
+++ b/pages/doc/cloud_integrations_troubleshooting.md
@@ -7,7 +7,7 @@ permalink: integrations-troubleshooting.html
summary: Learn how to troubleshoot the setup of our Cloud Services integrations.
---
-Integrations are one easy way to get data from external systems into Tanzu Observability (formerly known as VMware Aria Operations for Applications). You can use one of the [built-in integrations](label_integrations%20list.html) and customize it as needed.
+Integrations are one easy way to get data from external systems into VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications). You can use one of the [built-in integrations](label_integrations%20list.html) and customize it as needed.
## Cloud Services Integrations
diff --git a/pages/doc/csp_area_differences.md b/pages/doc/csp_area_differences.md
index a4aa8a13c..6b8ae6ccb 100644
--- a/pages/doc/csp_area_differences.md
+++ b/pages/doc/csp_area_differences.md
@@ -7,7 +7,7 @@ permalink: csp-differences-by-area.html
summary: Learn about the functionality differences between Tanzu Observability original subscriptions and VMware Cloud services subscriptions.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) subscriptions are two types: original subscriptions and VMware Cloud Services subscriptions.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) subscriptions are two types: original subscriptions and VMware Cloud Services subscriptions.
## Examples of the Functionality Differences
diff --git a/pages/doc/csp_migration.md b/pages/doc/csp_migration.md
index 39d592d52..ae07fc5cc 100644
--- a/pages/doc/csp_migration.md
+++ b/pages/doc/csp_migration.md
@@ -7,7 +7,7 @@ permalink: csp_migration.html
summary: Learn about how we migrate the authorization and authentication from Tanzu Observability to VMware Cloud services.
---
-Starting July 3, 2023, Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. We are in the process of incrementally onboarding all original subscriptions to VMware Cloud services.
+Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. We are in the process of incrementally onboarding all original subscriptions to VMware Cloud services.
## What Should I Do Before the Onboarding?
diff --git a/pages/doc/csp_subscription_types.md b/pages/doc/csp_subscription_types.md
index 828e5572b..70695198e 100644
--- a/pages/doc/csp_subscription_types.md
+++ b/pages/doc/csp_subscription_types.md
@@ -11,7 +11,7 @@ Tanzu Observability subscriptions are two types: original subscriptions and VMwa
## Why the Two Subscription Types Differ?
-Starting July 3, 2023, Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the [VMware Cloud services platform](https://console.cloud.vmware.com/) and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services.
+Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the [VMware Cloud services platform](https://console.cloud.vmware.com/) and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services.
Starting September 20, 2023, all [**new trial**](start_trial.html) instances of Tanzu Observability are **onboarded** to VMware Cloud services.
diff --git a/pages/doc/csp_supported_integrations.md b/pages/doc/csp_supported_integrations.md
index 1adb694f6..1e51b1f02 100644
--- a/pages/doc/csp_supported_integrations.md
+++ b/pages/doc/csp_supported_integrations.md
@@ -9,7 +9,7 @@ summary: Learn how integration authentication happens, which integrations work w
## Subscription Types
-Starting July 3, 2023, Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the VMware Cloud services platform and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until [onboarded](csp_migration.html) to VMware Cloud services.
+Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the VMware Cloud services platform and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until [onboarded](csp_migration.html) to VMware Cloud services.
For best performance, when you set up most of our integrations, it is recommended to use the Wavefront proxy. The Wavefront proxy ingests metrics and forwards them to Tanzu Observability in a secure, fast, and reliable manner.
diff --git a/pages/doc/csp_ui_differences.md b/pages/doc/csp_ui_differences.md
index ab9fd73f6..fecc6204d 100644
--- a/pages/doc/csp_ui_differences.md
+++ b/pages/doc/csp_ui_differences.md
@@ -7,7 +7,7 @@ permalink: csp-ui-differences.html
summary: Learn about the differences in the UI of Tanzu Observability original subscriptions and VMware Cloud services subscriptions.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) subscriptions are two types: original subscriptions and VMware Cloud services subscriptions.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) subscriptions are two types: original subscriptions and VMware Cloud services subscriptions.
## Menu Bar
diff --git a/pages/doc/delta_counters.md b/pages/doc/delta_counters.md
index b18e68887..833148ac1 100644
--- a/pages/doc/delta_counters.md
+++ b/pages/doc/delta_counters.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: delta_counters.html
summary: Learn when and how to use cumulative counters and delta counters.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports [several types of metrics](metric_types.html), including 2 kinds of counters.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports [several types of metrics](metric_types.html), including 2 kinds of counters.
* **Cumulative counters** (usually called **counters** in this doc set) monotonically increasing counters. They're useful for aggregating metric information such as the number of hits on a web page, how many users log into a portal, etc. They're usually used with `rate()` or a similar function.
* **Delta counters** (sometimes called periodic counters) measure the **change** since a metric was last recorded. For example, metrics for request count could be delta counters. Each value records how many requests were received since the last data point was recorded.
diff --git a/pages/doc/derived_metrics.md b/pages/doc/derived_metrics.md
index 682355fa0..ef9364774 100644
--- a/pages/doc/derived_metrics.md
+++ b/pages/doc/derived_metrics.md
@@ -7,7 +7,7 @@ permalink: derived_metrics.html
summary: Learn how to save a query so it runs once a minute, and how to use the derived metric elsewhere.
---
-Use derived metrics to run a query and ingest it back into Tanzu Observability (formerly known as VMware Aria Operations for Applications). All users can then use the result of the query, that is, the derived metric, in their queries.
+Use derived metrics to run a query and ingest it back into VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications). All users can then use the result of the query, that is, the derived metric, in their queries.
You can create a derived metric from a time series metric or a histogram.
diff --git a/pages/doc/direct_ingestion.md b/pages/doc/direct_ingestion.md
index 92598013d..f0b37ce72 100644
--- a/pages/doc/direct_ingestion.md
+++ b/pages/doc/direct_ingestion.md
@@ -7,7 +7,7 @@ permalink: direct_ingestion.html
summary: Learn how to send data directly to your service instance.
---
-You can send data to Tanzu Observability (formerly known as VMware Aria Operations for Applications) directly (by using direct ingestion) or by using the Wavefront proxy.
+You can send data to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) directly (by using direct ingestion) or by using the Wavefront proxy.
* **Direct data ingestion** can be the best approach at the beginning only for testing purposes and during a POC. In production environments, the best way to send data is by using a Wavefront proxy.
diff --git a/pages/doc/events.md b/pages/doc/events.md
index 1df7dc017..1e277269d 100644
--- a/pages/doc/events.md
+++ b/pages/doc/events.md
@@ -4,7 +4,7 @@ keywords: events
tags: [events, alerts]
sidebar: doc_sidebar
permalink: events.html
-summary: Learn about events and how to view, create, and close events in Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn about events and how to view, create, and close events in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
An event is a record that something of interest has happened. For example, the event might show that an alert has changed state, AWS instances have started or stopped, and so on. To view the list of all events, select **Browse > Events**.
diff --git a/pages/doc/integrations_aws_ecs.md b/pages/doc/integrations_aws_ecs.md
index 0a24ba870..8a1e9eb31 100644
--- a/pages/doc/integrations_aws_ecs.md
+++ b/pages/doc/integrations_aws_ecs.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_aws_ecs.html
-summary: Send AWS ECS data to Tanzu Observability (formerly known as VMware Aria Operations for Applications) using Telegraf agent or AWS Fargate.
+summary: Send AWS ECS data to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) using Telegraf agent or AWS Fargate.
---
[Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) is Amazon's Docker container orchestration system. From the Amazon ECS website:
diff --git a/pages/doc/integrations_aws_key_age.md b/pages/doc/integrations_aws_key_age.md
index 5d0038a48..c77d00086 100644
--- a/pages/doc/integrations_aws_key_age.md
+++ b/pages/doc/integrations_aws_key_age.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_aws_key_age.html
-summary: Send AWS Key Age data to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Send AWS Key Age data to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
AWS Identity and Access Management (IAM) allows administrators of different AWS services to manage access to those AWS services and resources securely.
diff --git a/pages/doc/integrations_aws_lambda.md b/pages/doc/integrations_aws_lambda.md
index b0572bcca..9879c089b 100644
--- a/pages/doc/integrations_aws_lambda.md
+++ b/pages/doc/integrations_aws_lambda.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations, dashboards]
sidebar: doc_sidebar
permalink: integrations_aws_lambda.html
-summary: Learn about AWS Lambda and Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn about AWS Lambda and VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
The [AWS Lambda Functions integration](aws-lambda-functions.html) includes:
* Setup instructions
diff --git a/pages/doc/integrations_aws_metrics.md b/pages/doc/integrations_aws_metrics.md
index 25e721a3c..a437e5bdf 100644
--- a/pages/doc/integrations_aws_metrics.md
+++ b/pages/doc/integrations_aws_metrics.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations, dashboards]
sidebar: doc_sidebar
permalink: integrations_aws_metrics.html
-summary: Monitor CloudWatch, CloudTrail, and Metrics+ with Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Monitor CloudWatch, CloudTrail, and Metrics+ with VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
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.
diff --git a/pages/doc/integrations_aws_overview-API.md b/pages/doc/integrations_aws_overview-API.md
index 44363be00..782e8c330 100644
--- a/pages/doc/integrations_aws_overview-API.md
+++ b/pages/doc/integrations_aws_overview-API.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_aws_overview_API.html
summary: Understand how to set up and manage the AWS integration by using our REST API.
---
-The Amazon Web Services integration allows you to ingest metrics directly from AWS to Tanzu Observability (formerly known as VMware Aria Operations for Applications). In addition to setting up and managing the AWS integration through the UI, you can also use the REST API for setting up and managing the AWS integration. This doc page provides some basic steps and examples on how to do this.
+The Amazon Web Services integration allows you to ingest metrics directly from AWS to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications). In addition to setting up and managing the AWS integration through the UI, you can also use the REST API for setting up and managing the AWS integration. This doc page provides some basic steps and examples on how to do this.
{% include note.html content="You must have the [**Proxy Management** permission](permissions_overview.html) to set up an AWS integration." %}
diff --git a/pages/doc/integrations_aws_overview.md b/pages/doc/integrations_aws_overview.md
index fbdf4ca08..96a0a0dfe 100644
--- a/pages/doc/integrations_aws_overview.md
+++ b/pages/doc/integrations_aws_overview.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_aws_overview.html
summary: Understand setup and services in the AWS integration.
---
-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 to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+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 to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
You can use the Amazon Web Services integration for initial setup, but additional steps might be needed for some of the services. This page gives an overview.
diff --git a/pages/doc/integrations_bigpanda_troubleshoot.md b/pages/doc/integrations_bigpanda_troubleshoot.md
index ed5d3af24..21ac96a4e 100644
--- a/pages/doc/integrations_bigpanda_troubleshoot.md
+++ b/pages/doc/integrations_bigpanda_troubleshoot.md
@@ -7,7 +7,7 @@ permalink: integrations_bigpanda_troubleshooting.html
summary: Investigate, troubleshoot, and remediate issues with BigPanda Webhook targets.
---
-BigPanda is an algorithmic event and alert management platform. This integration allows you to create BigPanda tickets from triggered alerts in Tanzu Observability (formerly known as VMware Aria Operations for Applications). Tanzu Observability and BigPanda both support webhooks, so you can configure an incoming webhook in BigPanda and an outgoing webhook in Tanzu Observability to pass notifications from Tanzu Observability alerts into BigPanda.
+BigPanda is an algorithmic event and alert management platform. This integration allows you to create BigPanda tickets from triggered alerts in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications). Tanzu Observability and BigPanda both support webhooks, so you can configure an incoming webhook in BigPanda and an outgoing webhook in Tanzu Observability to pass notifications from Tanzu Observability alerts into BigPanda.
## BigPanda Integration Configuration
diff --git a/pages/doc/integrations_cloudhealth.md b/pages/doc/integrations_cloudhealth.md
index 8ce0a696a..ec25823d0 100644
--- a/pages/doc/integrations_cloudhealth.md
+++ b/pages/doc/integrations_cloudhealth.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_cloudhealth.html
-summary: Learn how to send Tanzu Observability (formerly known as VMware Aria Operations for Applications) data to CloudHealth.
+summary: Learn how to send VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) data to CloudHealth.
---
The CloudHealth platform helps your team manage resource utilization and costs across multiple cloud environments. CloudHealth provides spending summary reports for each cost center, which helps you drive financial accountability and find ways to lower your cloud spend. You can create custom policies that automate daily cloud operations, support faster decision making, and reduce risk. CloudHealth also, reports on vulnerabilities so you can proactively monitor, detect, and remediate risks in real-time.
diff --git a/pages/doc/integrations_collectd.md b/pages/doc/integrations_collectd.md
index 64f1b6176..25c11d4b8 100644
--- a/pages/doc/integrations_collectd.md
+++ b/pages/doc/integrations_collectd.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd.html
-summary: Learn how to send data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn how to send data collected by collectd to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
To set up collectd to collect metrics, follow the in-product instructions on the Setup tab of the **collectd (Archived)** integration.
diff --git a/pages/doc/integrations_collectd_apache.md b/pages/doc/integrations_collectd_apache.md
index 558799f9a..3e19cd5eb 100644
--- a/pages/doc/integrations_collectd_apache.md
+++ b/pages/doc/integrations_collectd_apache.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_apache.html
-summary: Learn how to send Apache data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn how to send Apache data collected by collectd to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[Apache](https://httpd.apache.org/) is a popular open-source web server. To collect Apache data with collectd, use the collectd Apache plugin documentation found at [Plugin:Apache - collectd Wiki](https://collectd.org/wiki/index.php/Plugin:Apache).
diff --git a/pages/doc/integrations_collectd_cassandra.md b/pages/doc/integrations_collectd_cassandra.md
index 5b465facd..54addbd0f 100644
--- a/pages/doc/integrations_collectd_cassandra.md
+++ b/pages/doc/integrations_collectd_cassandra.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_cassandra.html
-summary: Learn how to send Cassandra data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn how to send Cassandra data collected by collectd to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[Apache Cassandra](http://cassandra.apache.org/) is a popular, distributed, NoSQL database system.
diff --git a/pages/doc/integrations_collectd_memcached.md b/pages/doc/integrations_collectd_memcached.md
index cc2db10da..12b52a804 100644
--- a/pages/doc/integrations_collectd_memcached.md
+++ b/pages/doc/integrations_collectd_memcached.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_memcached.html
-summary: Learn how to send memcached data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn how to send memcached data collected by collectd to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[memcached](https://memcached.org/) is a popular memory object cache system. See [collectd memcached plugin documentation](https://collectd.org/wiki/index.php/Plugin:memcached).
diff --git a/pages/doc/integrations_collectd_mysql.md b/pages/doc/integrations_collectd_mysql.md
index 4231e23b8..a64539b12 100644
--- a/pages/doc/integrations_collectd_mysql.md
+++ b/pages/doc/integrations_collectd_mysql.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_mysql.html
-summary: Learn how to send MySQL data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn how to send MySQL data collected by collectd to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[MySQL](https://www.mysql.com/) is a popular open-source relational database. See [collectd MySQL plugin documentation](https://collectd.org/wiki/index.php/Plugin:MySQL).
diff --git a/pages/doc/integrations_collectd_ngnix.md b/pages/doc/integrations_collectd_ngnix.md
index ada29bf8a..96e0cdc94 100644
--- a/pages/doc/integrations_collectd_ngnix.md
+++ b/pages/doc/integrations_collectd_ngnix.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_nginx.html
-summary: Learn how to send NGiNX data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn how to send NGiNX data collected by collectd to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[NGiNX](https://www.nginx.com/) is a popular web and proxy server. To collect NGiNX data with collectd, use the collectd NGiNX plugin documentation found at [Plugin:NGiNX - collectd Wiki](https://collectd.org/wiki/index.php/Plugin:nginx).
diff --git a/pages/doc/integrations_collectd_redis.md b/pages/doc/integrations_collectd_redis.md
index 19c83646c..183d71a5f 100644
--- a/pages/doc/integrations_collectd_redis.md
+++ b/pages/doc/integrations_collectd_redis.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_redis.html
-summary: Learn how to send Redis data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn how to send Redis data collected by collectd to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[Redis](https://redis.io/) is an in-memory data structure store, often used as a database, cache and message broker. Tanzu Observability supports a built-in integration that gets data from Redis using Telegraf. If you want to use collectd instead, follow the instructions on this page.
diff --git a/pages/doc/integrations_collectd_zookeeper.md b/pages/doc/integrations_collectd_zookeeper.md
index 91f97b5e5..66af3cd63 100644
--- a/pages/doc/integrations_collectd_zookeeper.md
+++ b/pages/doc/integrations_collectd_zookeeper.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_collectd_zookeeper.html
-summary: Learn how to send ZooKeeper data collected by collectd to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn how to send ZooKeeper data collected by collectd to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
[Apache ZooKeeper](https://zookeeper.apache.org/) is a popular service for maintaining configuration and coordinating distributed systems. ZooKeeper is used by technologies like Hadoop and Apache Solr to coordinate clusters and help them run reliably. Tanzu Observability supports a built-in integration that gets data from ZooKeeper using Telegraf. If you want to use collectd instead, follow the instructions on this page.
diff --git a/pages/doc/integrations_gcp_API.md b/pages/doc/integrations_gcp_API.md
index cad9cd88e..46b3dadbf 100644
--- a/pages/doc/integrations_gcp_API.md
+++ b/pages/doc/integrations_gcp_API.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_gcp_api.html
summary: Understand how to set up and manage the GCP integration by using our REST API.
---
-The Google Cloud Platform integration allows you to ingest metrics directly from GCP to Tanzu Observability (formerly known as VMware Aria Operations for Applications). In addition to setting up and managing the GCP integration through the UI, you can also use the REST API for setting up and managing the GCP integration. This doc page provides some basic steps and examples on how to do this.
+The Google Cloud Platform integration allows you to ingest metrics directly from GCP to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications). In addition to setting up and managing the GCP integration through the UI, you can also use the REST API for setting up and managing the GCP integration. This doc page provides some basic steps and examples on how to do this.
{% include note.html content="You must have the [**Proxy Management** permission](permissions_overview.html) to set up an GCP integration." %}
diff --git a/pages/doc/integrations_gcp_overview.md b/pages/doc/integrations_gcp_overview.md
index d7f459cab..6815997c5 100644
--- a/pages/doc/integrations_gcp_overview.md
+++ b/pages/doc/integrations_gcp_overview.md
@@ -7,7 +7,7 @@ permalink: integrations_gcp_overview.html
summary: Minimum permissions for Google Cloud Platform.
---
-When you set up a Google Cloud Platform integration, you have to give the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service permissions to access the data you want to visualize and analyze.
+When you set up a Google Cloud Platform integration, you have to give the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service permissions to access the data you want to visualize and analyze.
## Access Options
diff --git a/pages/doc/integrations_grafana.md b/pages/doc/integrations_grafana.md
index ff3d26605..311fe44c5 100644
--- a/pages/doc/integrations_grafana.md
+++ b/pages/doc/integrations_grafana.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations, grafana]
sidebar: doc_sidebar
permalink: integrations_grafana.html
-summary: Learn how you can set up Tanzu Observability (formerly known as VMware Aria Operations for Applications) as a Prometheus data source in Grafana.
+summary: Learn how you can set up VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) as a Prometheus data source in Grafana.
---
In addition to [setting up and using Tanzu Observability as a Wavefront Query Language data source in Grafana](grafana.html), you can also use Tanzu Observability as a Prometheus data source in Grafana.
diff --git a/pages/doc/integrations_log_data.md b/pages/doc/integrations_log_data.md
index 0847c74af..42762e27f 100644
--- a/pages/doc/integrations_log_data.md
+++ b/pages/doc/integrations_log_data.md
@@ -4,7 +4,7 @@ keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_log_data.html
-summary: Learn how to send log data to Tanzu Observability (formerly known as VMware Aria Operations for Applications) by setting up a proxy and configuring Filebeat or TCP.
+summary: Learn how to send log data to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) by setting up a proxy and configuring Filebeat or TCP.
---
Tanzu Observability supports two methods for sending log data metrics to a Wavefront proxy: Filebeat and TCP. Wavefront proxy 4.4 and later supports these methods.
diff --git a/pages/doc/integrations_new_changed.md b/pages/doc/integrations_new_changed.md
index 704d73ad2..3ea7d19d1 100644
--- a/pages/doc/integrations_new_changed.md
+++ b/pages/doc/integrations_new_changed.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_new_changed.html
summary: New and changed integrations.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations. We update our [**complete list of all integrations**](https://docs.wavefront.com/label_integrations%20list.html) each time we add new integrations.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations. We update our [**complete list of all integrations**](https://docs.wavefront.com/label_integrations%20list.html) each time we add new integrations.
## Announcement
diff --git a/pages/doc/integrations_new_changed_2020.md b/pages/doc/integrations_new_changed_2020.md
index 3f580644e..0c893a29a 100644
--- a/pages/doc/integrations_new_changed_2020.md
+++ b/pages/doc/integrations_new_changed_2020.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_new_changed_2020.html
summary: New and changed integrations released in 2019-2020
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations.
This document lists new and changed integrations for 2019 and 2020.
* We have a separate document for [Integrations Release Notes](integrations_new_changed.html).
diff --git a/pages/doc/integrations_new_changed_2021.md b/pages/doc/integrations_new_changed_2021.md
index 8ac8d05fc..5e0cd7c0c 100644
--- a/pages/doc/integrations_new_changed_2021.md
+++ b/pages/doc/integrations_new_changed_2021.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_new_changed_2021.html
summary: New and changed integrations released in 2021
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations.
This document lists new and changed integrations for 2021. For earlier releases, see [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).
diff --git a/pages/doc/integrations_new_changed_2022.md b/pages/doc/integrations_new_changed_2022.md
index 90b694bce..98f02d239 100644
--- a/pages/doc/integrations_new_changed_2022.md
+++ b/pages/doc/integrations_new_changed_2022.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_new_changed_2022.html
summary: New and changed integrations released in 2022.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) 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) 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).
diff --git a/pages/doc/integrations_new_changed_2023.md b/pages/doc/integrations_new_changed_2023.md
index e415081b9..0923f8b69 100644
--- a/pages/doc/integrations_new_changed_2023.md
+++ b/pages/doc/integrations_new_changed_2023.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: integrations_new_changed_2023.html
summary: New and changed integrations released in 2023.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) continuously adds new integrations to the existing set, and improves available integrations.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) 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).
diff --git a/pages/doc/integrations_pks.md b/pages/doc/integrations_pks.md
index d3158d615..9ae561e46 100644
--- a/pages/doc/integrations_pks.md
+++ b/pages/doc/integrations_pks.md
@@ -12,7 +12,7 @@ On this page, we list predefined alerts and give other details about the integra
## Predefined Alerts for the Integration
-The Tanzu Kubernetes Grid integration provides the following monitoring alerts for PKS. These alerts are predefined, no additional setup is required. You can [create additional alerts](alerts_manage.html) from the **Alerts** browser or from charts in the Tanzu Observability (formerly known as VMware Aria Operations for Applications) GUI.
+The Tanzu Kubernetes Grid integration provides the following monitoring alerts for PKS. These alerts are predefined, no additional setup is required. You can [create additional alerts](alerts_manage.html) from the **Alerts** browser or from charts in the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) GUI.
diff --git a/pages/doc/integrations_vrops.md b/pages/doc/integrations_vrops.md
index 980383498..eedc023a6 100644
--- a/pages/doc/integrations_vrops.md
+++ b/pages/doc/integrations_vrops.md
@@ -8,7 +8,7 @@ summary: Understand the setup and the VMware Aria Operations (SaaS) integration
---
[VMware Aria Operations (SaaS)](https://www.vmware.com/products/aria-operations.html) (formerly vRealize Operations Cloud) delivers intelligent operations management with application-to-storage visibility across physical, virtual, and cloud infrastructures. Using policy-based automation, operations teams automate key processes and improve the IT efficiency.
-The VMware Aria Operations (SaaS) integration is a full-featured native integration that offers agentless data ingestion of VMware Aria Operations (SaaS) metric data into Tanzu Observability (formerly known as VMware Aria Operations for Applications), as well as a predefined dashboard.
+The VMware Aria Operations (SaaS) integration is a full-featured native integration that offers agentless data ingestion of VMware Aria Operations (SaaS) metric data into VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications), as well as a predefined dashboard.
{% include important.html content="The VMware Aria Operations (SaaS) integration v1 is the first version of this integration and currently fetches only vCenter Server adapter resources, such as Cluster Compute Resource and Datastore. We will add more features to this integration in future releases." %}
diff --git a/pages/doc/logging_log_alerts.md b/pages/doc/logging_log_alerts.md
index 98e5a0259..1912a2bf4 100644
--- a/pages/doc/logging_log_alerts.md
+++ b/pages/doc/logging_log_alerts.md
@@ -6,7 +6,7 @@ permalink: logging_log_alerts.html
summary: Learn how you can create, snooze and delete a logs alert.
---
-{% include important.html content="Tanzu Observability (formerly known as VMware Aria Operations for Applications) retains logs for 30 days during the Logs free trial or retains logs for 7 days when on the freemium subscription! To retain logs for a longer period, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
+{% include important.html content="VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) retains logs for 30 days during the Logs free trial or retains logs for 7 days when on the freemium subscription! To retain logs for a longer period, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
You can create alerts for your logs data and see the firing events of an alert.
diff --git a/pages/doc/logging_logs_settings.md b/pages/doc/logging_logs_settings.md
index 3f98d9e96..814a5ff0e 100644
--- a/pages/doc/logging_logs_settings.md
+++ b/pages/doc/logging_logs_settings.md
@@ -3,7 +3,7 @@ title: Customize Logs Settings
tags: [logs]
sidebar: doc_sidebar
permalink: logging_logs_settings.html
-summary: Learn how you can customize logs settings in Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn how you can customize logs settings in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
Users with access to the logs settings can map metrics tags to logs tags, traces tags to logs tags, and customize the time window you see on a chart or Traces Browser when you drill into logs from a chart and trace.
diff --git a/pages/doc/logging_overview.md b/pages/doc/logging_overview.md
index b7493c1e0..8bbab66fa 100644
--- a/pages/doc/logging_overview.md
+++ b/pages/doc/logging_overview.md
@@ -3,7 +3,7 @@ title: Get Started with Logs
tags: [getting started, logs]
sidebar: doc_sidebar
permalink: logging_overview.html
-summary: Learn about Tanzu Observability (formerly known as VMware Aria Operations for Applications) metrics, logs, and traces.
+summary: Learn about VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) metrics, logs, and traces.
---
{% include important.html content="The Logs feature is enabled only for selected customers. To participate, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
diff --git a/pages/doc/logging_proxy_configurations.md b/pages/doc/logging_proxy_configurations.md
index 5c55b6269..3514b9130 100644
--- a/pages/doc/logging_proxy_configurations.md
+++ b/pages/doc/logging_proxy_configurations.md
@@ -3,7 +3,7 @@ title: Logs Proxy Configurations and Preprocessor Rules
tags: [getting started, logs]
sidebar: doc_sidebar
permalink: logging_proxy_configurations.html
-summary: Proxy configuration properties and preprocessor rules for ingesting logs into Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Proxy configuration properties and preprocessor rules for ingesting logs into VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
{% include important.html content="The Logs feature is enabled only for selected customers. To participate, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
diff --git a/pages/doc/logging_send_logs.md b/pages/doc/logging_send_logs.md
index 407d5234b..5e813a047 100644
--- a/pages/doc/logging_send_logs.md
+++ b/pages/doc/logging_send_logs.md
@@ -4,7 +4,7 @@ keywords: data, logs
tags: [getting started, logs]
sidebar: doc_sidebar
permalink: logging_send_logs.html
-summary: Learn about sending logs to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Learn about sending logs to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
{% include important.html content="The Logs feature is enabled only for selected customers. To participate, contact your account representative or [technical support](wavefront_support_feedback.html#support)."%}
diff --git a/pages/doc/metric_types.md b/pages/doc/metric_types.md
index 966fc836c..ed1b44cb7 100644
--- a/pages/doc/metric_types.md
+++ b/pages/doc/metric_types.md
@@ -7,7 +7,7 @@ permalink: metric_types.html
summary: Learn about gauges, counters, delta counters, histograms, and spans.
---
- Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports monitoring time series, histograms, and traces.
+ VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports monitoring time series, histograms, and traces.
* Each **time series** consists of numeric data points for a metric, for example, CPU load or failed network connections. Time series can use one of the [supported data formats](wavefront_data_format.html#supported-data-formats-for-metrics).
The type of data that you’re collecting determines the type of metric. Tanzu Observability supports gauges, counters, delta counters, and more.
diff --git a/pages/doc/metrics_managing.md b/pages/doc/metrics_managing.md
index f5031b6be..343e336d0 100644
--- a/pages/doc/metrics_managing.md
+++ b/pages/doc/metrics_managing.md
@@ -7,7 +7,7 @@ permalink: metrics_managing.html
summary: Understand metrics structure and how to explore metrics in the Metrics Browser
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) provides observability for several different [metric types](metric_types.html) including time series metrics, delta counters, histograms, and traces/spans. This page looks at the anatomy of a time series metric and shows you how to explore it in the Metrics Browser.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) provides observability for several different [metric types](metric_types.html) including time series metrics, delta counters, histograms, and traces/spans. This page looks at the anatomy of a time series metric and shows you how to explore it in the Metrics Browser.
## Videos
diff --git a/pages/doc/missing_data_troubleshooting.md b/pages/doc/missing_data_troubleshooting.md
index bb5ffa8d3..528d78293 100644
--- a/pages/doc/missing_data_troubleshooting.md
+++ b/pages/doc/missing_data_troubleshooting.md
@@ -7,7 +7,7 @@ permalink: missing_data_troubleshooting.html
summary: Learn how to troubleshoot when you expect to see data but it doesn't appear in charts.
---
-Sometimes you expect to see certain data in Tanzu Observability (formerly known as VMware Aria Operations for Applications) but, for some reason, it doesn't show up! This can be a frustrating and confusing experience, especially when you urgently need the data. Tanzu Observability does not delete data, and retains [metric data for 18 months](terms_of_service.html#data-retention). What could be the problem?
+Sometimes you expect to see certain data in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) but, for some reason, it doesn't show up! This can be a frustrating and confusing experience, especially when you urgently need the data. Tanzu Observability does not delete data, and retains [metric data for 18 months](terms_of_service.html#data-retention). What could be the problem?
This doc page, based on the extensive experience of our customer success team, helps you investigate, understand, and remedy possible causes. In addition to manually investigating and troubleshooting your issues, you can use the [Query Analyzer](query_language_performance.html#use-the-query-analyzer) which helps you identify where exactly the problem is.
diff --git a/pages/doc/optimize_data_shape.md b/pages/doc/optimize_data_shape.md
index 2bae3153e..a0cf0777f 100644
--- a/pages/doc/optimize_data_shape.md
+++ b/pages/doc/optimize_data_shape.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: optimize_data_shape.html
summary: Learn how to optimize your data in high-cardinality environments.
---
-Data shape refers to how each component of a time series is designed and formatted. Your data shapes in Tanzu Observability (formerly known as VMware Aria Operations for Applications) are important regardless of how you use the service and where you are in your work with the platform.
+Data shape refers to how each component of a time series is designed and formatted. Your data shapes in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) are important regardless of how you use the service and where you are in your work with the platform.
* **New users** who plan on sending data into Tanzu Observability need to understand the most efficient ways of sending data in.
* **Existing users** who explore data in dashboards and chart can investigate data shape and use that information to optimize data exploration. If they see that the data shape is not optimal, they might even request changes to how data are ingested.
diff --git a/pages/doc/proxies.md b/pages/doc/proxies.md
index 25cbdb2ac..b53ab201b 100644
--- a/pages/doc/proxies.md
+++ b/pages/doc/proxies.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: proxies.html
summary: Learn about Wavefront proxies.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) enables you to:
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) enables you to:
* Send data through Wavefront proxies. Most customers and our DevOps team use proxies.
* Send data directly using [direct ingestions](direct_ingestion.html).
diff --git a/pages/doc/proxies_configuring.md b/pages/doc/proxies_configuring.md
index eac808dbc..cd21e43f5 100644
--- a/pages/doc/proxies_configuring.md
+++ b/pages/doc/proxies_configuring.md
@@ -8,7 +8,7 @@ summary: Proxy files, logs, and configuration properties
---
-Even without additional customization, the Wavefront proxy ingests metrics and forwards them to Tanzu Observability (formerly known as VMware Aria Operations for Applications) in a secure, fast, and reliable manner. If needed, you can customize your proxy.
+Even without additional customization, the Wavefront proxy ingests metrics and forwards them to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) in a secure, fast, and reliable manner. If needed, you can customize your proxy.
* **[Proxy configuration properties](#configuration-properties)** allow you to change how the proxy processes your data. For example, you can change ports or perform other advanced installation management.
diff --git a/pages/doc/proxies_container.md b/pages/doc/proxies_container.md
index 15e2ad026..3d47d0196 100644
--- a/pages/doc/proxies_container.md
+++ b/pages/doc/proxies_container.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: proxies_container.html
summary: Configure Wavefront proxy and Telegraf in a Docker container
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports container proxy setup. This page discusses running a proxy and Telegraf agent as Docker containers, but the guidance (though not some specifics) applies to other container solutions as well.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports container proxy setup. This page discusses running a proxy and Telegraf agent as Docker containers, but the guidance (though not some specifics) applies to other container solutions as well.
## Run a Proxy in a Docker Container
diff --git a/pages/doc/proxies_histograms.md b/pages/doc/proxies_histograms.md
index c8242b65c..fae312707 100644
--- a/pages/doc/proxies_histograms.md
+++ b/pages/doc/proxies_histograms.md
@@ -7,7 +7,7 @@ published: true
permalink: proxies_histograms.html
summary: Learn how to use histograms.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports histograms for computing, storing, and using **distributions of metrics** rather than single metrics. Histograms are useful for high-velocity metrics about your applications and infrastructure – particularly those gathered across many distributed sources. You can send histograms to a Wavefront proxy or use direct ingestion.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports histograms for computing, storing, and using **distributions of metrics** rather than single metrics. Histograms are useful for high-velocity metrics about your applications and infrastructure – particularly those gathered across many distributed sources. You can send histograms to a Wavefront proxy or use direct ingestion.
This page explain how to send histogram distributions. After the data is available, you can [visualize histogram distributions](visualize_histograms.html) using Histogram charts or Heatmap charts.
diff --git a/pages/doc/proxies_installing.md b/pages/doc/proxies_installing.md
index d42a215eb..6f6281304 100644
--- a/pages/doc/proxies_installing.md
+++ b/pages/doc/proxies_installing.md
@@ -5,7 +5,7 @@ sidebar: doc_sidebar
permalink: proxies_installing.html
summary: Learn how to install and manage Wavefront proxies.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) offers several [deployment options](proxies.html#proxy-deployment-options). During development, a single proxy is often sufficient for all data sources. In production, place a team of proxies behind a load balancer.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) offers several [deployment options](proxies.html#proxy-deployment-options). During development, a single proxy is often sufficient for all data sources. In production, place a team of proxies behind a load balancer.
In most cases, a Wavefront proxy must be running in your environment before metrics begin streaming to your Tanzu Observability service from a host or application.
diff --git a/pages/doc/proxies_kube_container.md b/pages/doc/proxies_kube_container.md
index aaa906750..305f2d34f 100644
--- a/pages/doc/proxies_kube_container.md
+++ b/pages/doc/proxies_kube_container.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: proxies_kube_container.html
summary: Run a Wavefront proxy in a Kubernetes container and customize it.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports setting up the Wavefront proxy to run [in a Kubernetes container](kubernetes.html#kubernetes-manual-install). However, you cannot rely on a single `wavefront.conf` file. Instead, a ConfigMap file governs deployment.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports setting up the Wavefront proxy to run [in a Kubernetes container](kubernetes.html#kubernetes-manual-install). However, you cannot rely on a single `wavefront.conf` file. Instead, a ConfigMap file governs deployment.
1. Create a custom ConfigMap file that contains the custom setup, for example preprocessing rules, for your proxy configuration. This doc page creates a `00_proxy-preprocessor-config.yaml` file.
2. Edit `wavefront.yaml` so it points to the ConfigMap file.
diff --git a/pages/doc/proxies_manual_install.md b/pages/doc/proxies_manual_install.md
index fe5e1b46d..2e63a094a 100644
--- a/pages/doc/proxies_manual_install.md
+++ b/pages/doc/proxies_manual_install.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: proxies_manual_install.html
summary: Learn how to manually install a Wavefront proxy and Telegraf agent.
---
-Most Tanzu Observability (formerly known as VMware Aria Operations for Applications) customers use an automated proxy install:
+Most VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) customers use an automated proxy install:
* Option 1: Install the Wavefront proxy and the Telegraf agent when the set up an integration.
* Option 2: Perform a [scripted installation](proxies_installing.html#scripted-proxy-installation) of the Wavefront proxy and Telegraf agent.
diff --git a/pages/doc/proxies_preprocessor_rules.md b/pages/doc/proxies_preprocessor_rules.md
index 494ab38b9..a73d77f44 100644
--- a/pages/doc/proxies_preprocessor_rules.md
+++ b/pages/doc/proxies_preprocessor_rules.md
@@ -7,7 +7,7 @@ permalink: proxies_preprocessor_rules.html
summary: Learn how to write proxy preprocessor rules.
---
-For fine-grained control before data are sent to Tanzu Observability (formerly known as VMware Aria Operations for Applications), the Wavefront proxy supports:
+For fine-grained control before data are sent to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications), the Wavefront proxy supports:
* Point filtering and point altering rules
* Span filtering and span altering rules
diff --git a/pages/doc/proxies_troubleshooting.md b/pages/doc/proxies_troubleshooting.md
index e23e7126d..2eeda6fa8 100644
--- a/pages/doc/proxies_troubleshooting.md
+++ b/pages/doc/proxies_troubleshooting.md
@@ -7,7 +7,7 @@ permalink: proxies_troubleshooting.html
summary: Troubleshoot proxy problems.
---
-Wavefront proxies give you a lot of flexibility and control in your Tanzu Observability (formerly known as VMware Aria Operations for Applications) environment. But with flexibility comes the potential for problems, so it's a best practice to [monitor you proxies](monitoring_proxies.html). For example, on the Proxies Browser page, you can see the account used to set up a specific proxy.
+Wavefront proxies give you a lot of flexibility and control in your VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) environment. But with flexibility comes the potential for problems, so it's a best practice to [monitor you proxies](monitoring_proxies.html). For example, on the Proxies Browser page, you can see the account used to set up a specific proxy.
In addition, our SaaS Value Engineering team has put together the following troubleshooting advice.
diff --git a/pages/doc/purchase-additional-capacity.md b/pages/doc/purchase-additional-capacity.md
index c8b1fae8a..36c126af5 100644
--- a/pages/doc/purchase-additional-capacity.md
+++ b/pages/doc/purchase-additional-capacity.md
@@ -7,7 +7,7 @@ permalink: purchase_additional_capacity.html
summary: Learn how to add capacity to your current Tanzu Observability (formerly known as VMware Aria Operations for Applications) subscription.
---
-{% include note.html content="Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
- For VMware Cloud services subscriptions, to purchase additional capacity, you must hold the [**Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) in the VMware Cloud organization running the service as well as at least one [Tanzu Observability service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance. If your enterprise domain is federated, to access the organization billing account, you must have a VMware account linked to your corporate account.
- For original Tanzu Observability subscriptions, to purchase additional capacity, you must be a **Super Admin** user."%}
diff --git a/pages/doc/query_editor.md b/pages/doc/query_editor.md
index 245d39ef1..f361831e4 100644
--- a/pages/doc/query_editor.md
+++ b/pages/doc/query_editor.md
@@ -7,7 +7,7 @@ permalink: query_editor.html
summary: Query your metrics with query language functions and variables.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports two tools for working with queries:
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports two tools for working with queries:
* [Chart Builder](chart_builder.html) is the fasted way to customize which metrics you see and to display them in charts.
* Query Editor, discussed on this page, allows advanced users to extract exactly the metrics they need from ingested data. If a chart uses functions that are not supported in Chart Builder, or if the chart has been opened in Query Editor before, we show Query editor when you open the chart for edit.
diff --git a/pages/doc/query_language_aggregate_functions.md b/pages/doc/query_language_aggregate_functions.md
index ae90c2d08..15658e2d6 100644
--- a/pages/doc/query_language_aggregate_functions.md
+++ b/pages/doc/query_language_aggregate_functions.md
@@ -7,7 +7,7 @@ permalink: query_language_aggregate_functions.html
summary: How to aggregate points from multiple time series with or without interpolation.
---
-You can combine points from multiple time series using an [**aggregation function**](query_language_reference.html#aggregation-functions) such as `sum()`, `avg()`, `min()`, `count()`, `percentile()` etc. An aggregation function returns a series of points whose values are calculated from corresponding points in two or more input time series. Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports aggregation with interpolation or without interpolation:
+You can combine points from multiple time series using an [**aggregation function**](query_language_reference.html#aggregation-functions) such as `sum()`, `avg()`, `min()`, `count()`, `percentile()` etc. An aggregation function returns a series of points whose values are calculated from corresponding points in two or more input time series. VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports aggregation with interpolation or without interpolation:
* Standard aggregation functions (e.g. `sum()`, `avg()`, or `max()`) first interpolate the points of the underlying set of series, and then apply the aggregation function to the interpolated series. These functions aggregate multiple series down, usually to a single series.
* Raw aggregation functions (e.g. `rawsum()`, `rawavg()`) do **not** interpolate the underlying series before aggregation.
diff --git a/pages/doc/query_language_align_function.md b/pages/doc/query_language_align_function.md
index 1de069a31..bf590f5ee 100644
--- a/pages/doc/query_language_align_function.md
+++ b/pages/doc/query_language_align_function.md
@@ -7,7 +7,7 @@ permalink: query_language_align_function.html
summary: Learn where to use the align() function and why the query engine does pre-alignment.
---
-In Tanzu Observability (formerly known as VMware Aria Operations for Applications) charts, point buckets represent data that has been summarized over a certain length of time.
+In VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) charts, point buckets represent data that has been summarized over a certain length of time.
Both the **Summarize By** chart option and the [`align()` function](ts_align.html) group points into buckets and allow you to specify how those points are aggregated (e.g., averaged, counted, summed, etc.). The `align()` function allows you to specify the desired bucket size. By default, the summarization method that aggregation functions use is based on the bucket size of the [chart resolution](ui_charts.html#chart-resolution).
diff --git a/pages/doc/query_language_discrete_continuous.md b/pages/doc/query_language_discrete_continuous.md
index 7712f78fc..068a1ba2f 100644
--- a/pages/doc/query_language_discrete_continuous.md
+++ b/pages/doc/query_language_discrete_continuous.md
@@ -7,7 +7,7 @@ permalink: query_language_discrete_continuous.html
summary: Understand discrete and continuous time series and when the query engine performs interpolation.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports both discrete and continuous time series. Understanding how to work with them is important for best performance.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports both discrete and continuous time series. Understanding how to work with them is important for best performance.
## Basics
diff --git a/pages/doc/query_language_getting_started.md b/pages/doc/query_language_getting_started.md
index 2ce7fd12c..5f2ca108d 100644
--- a/pages/doc/query_language_getting_started.md
+++ b/pages/doc/query_language_getting_started.md
@@ -7,7 +7,7 @@ permalink: query_language_getting_started.html
summary: Watch some videos, run a query, apply filters and functions, and more.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Wavefront Query Language (WQL), which lets you retrieve and display data that has been ingested.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Wavefront Query Language (WQL), which lets you retrieve and display data that has been ingested.
* **Time series data** The query language is particularly well suited to time series data because it accommodates the periodicity, potential irregularity, and streaming nature of that data type.
* **Histograms** The query language includes functions for [manipulating histograms](query_language_reference.html#histogram-functions).
* **Traces and spans** Use the [tracing UI](tracing_traces_browser.html) to query traces and spans.
diff --git a/pages/doc/query_language_metadata_functions.md b/pages/doc/query_language_metadata_functions.md
index 70d24ea64..589773bc4 100644
--- a/pages/doc/query_language_metadata_functions.md
+++ b/pages/doc/query_language_metadata_functions.md
@@ -7,7 +7,7 @@ permalink: query_language_metadata_functions.html
summary: Learn how to rename metrics and sources and create point tags with aliasSource, aliasMetric, and taggify.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes metadata (label manipulation) functions that enable users to temporarily rename a source, rename a metric or create a synthetic point tag. Dashboards and charts display the changed name or aggregated point tag. We support:
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes metadata (label manipulation) functions that enable users to temporarily rename a source, rename a metric or create a synthetic point tag. Dashboards and charts display the changed name or aggregated point tag. We support:
* [`aliasSource`](ts_aliasSource.html) - Manipulate a source name
* [`aliasMetric`](ts_aliasMetric.html) - Manipulate a metric name
* [`taggify`](ts_taggify.html) - Manipulate a point tag name
diff --git a/pages/doc/query_language_performance.md b/pages/doc/query_language_performance.md
index ec7686483..ffd83fa63 100644
--- a/pages/doc/query_language_performance.md
+++ b/pages/doc/query_language_performance.md
@@ -7,7 +7,7 @@ permalink: query_language_performance.html
summary: Tricks for improving the query language performance.
---
-The Wavefront Query Language (WQL) lets you retrieve and display the data that has been ingested into Tanzu Observability (formerly known as VMware Aria Operations for Applications) and create alerts that use this data.
+The Wavefront Query Language (WQL) lets you retrieve and display the data that has been ingested into VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) and create alerts that use this data.
diff --git a/pages/doc/query_language_point_tags.md b/pages/doc/query_language_point_tags.md
index 82ce9a167..2cc9f0ddd 100644
--- a/pages/doc/query_language_point_tags.md
+++ b/pages/doc/query_language_point_tags.md
@@ -20,7 +20,7 @@ Many of our cloud integrations generate point tags automatically to help you fil
### Point Tag Maximum
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports up 20 point tags per time series. A larger number of point tags does not improve the user experience and can lead to performance problems.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports up 20 point tags per time series. A larger number of point tags does not improve the user experience and can lead to performance problems.
{% include note.html content="If the number of point tags exceeds 20, then we drop the metrics that have those point tags." %}
diff --git a/pages/doc/query_language_recipes.md b/pages/doc/query_language_recipes.md
index 25bbd58b4..d788552f4 100644
--- a/pages/doc/query_language_recipes.md
+++ b/pages/doc/query_language_recipes.md
@@ -115,7 +115,7 @@ For more details, see [Display Daily Average](query_language_windows_trends.html
## Data Pipeline Queries
-Data pipeline queries allow you to determine whether data is flowing to the proxies or to the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service. You can also examine the point rate and potentially set an alert if data is larger than a threshold.
+Data pipeline queries allow you to determine whether data is flowing to the proxies or to the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service. You can also examine the point rate and potentially set an alert if data is larger than a threshold.
### Point Rate for All Proxies
diff --git a/pages/doc/query_language_reference.md b/pages/doc/query_language_reference.md
index a2f48b8fd..fde4506d4 100644
--- a/pages/doc/query_language_reference.md
+++ b/pages/doc/query_language_reference.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: query_language_reference.html
summary: Learn about the query syntax, operators, and functions supported by Wavefront Query Language (WQL).
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Wavefront Query Language, which allows you to extract the information you need from your data. You use the query language for queries that display in charts and for alerts. This page is a complete reference to all query language elements and functions. You can click most functions for a page with details and examples.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Wavefront Query Language, which allows you to extract the information you need from your data. You use the query language for queries that display in charts and for alerts. This page is a complete reference to all query language elements and functions. You can click most functions for a page with details and examples.
## Query Expressions
diff --git a/pages/doc/query_language_series_joining.md b/pages/doc/query_language_series_joining.md
index d035ee777..ed08e8ebc 100644
--- a/pages/doc/query_language_series_joining.md
+++ b/pages/doc/query_language_series_joining.md
@@ -7,7 +7,7 @@ permalink: query_language_series_joining.html
summary: Use relationships among your time series to build full stack correlations.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports a `join()` function that lets you:
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports a `join()` function that lets you:
* Compare two or more time series and find matches, or, conversely, find the time series that do not match.
* Combine the data points from any matching time series to form a new synthetic time series with point tags from one or both of the input series.
diff --git a/pages/doc/query_language_series_matching.md b/pages/doc/query_language_series_matching.md
index 0a64bae7f..04edb4d3e 100644
--- a/pages/doc/query_language_series_matching.md
+++ b/pages/doc/query_language_series_matching.md
@@ -7,7 +7,7 @@ permalink: query_language_series_matching.html
summary: Learn how implicit series matching operates on pairs of time series that have corresponding sources and point tags.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) performs **series matching** to identify meaningful pairs of individual time series to operate on. For example, because of implicit series matching in the following operation, the query engine compares metrics for disk reads and disk writes only when they come from the same source and have common point tag values:
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) performs **series matching** to identify meaningful pairs of individual time series to operate on. For example, because of implicit series matching in the following operation, the query engine compares metrics for disk reads and disk writes only when they come from the same source and have common point tag values:
```
ts(~sample.disk.bytes.read) > ts(~sample.disk.bytes.written)
diff --git a/pages/doc/query_language_windows_trends.md b/pages/doc/query_language_windows_trends.md
index 258c480c6..23a4a4e79 100644
--- a/pages/doc/query_language_windows_trends.md
+++ b/pages/doc/query_language_windows_trends.md
@@ -7,7 +7,7 @@ permalink: query_language_windows_trends.html
summary: Highlight trends with moving and tumbling windows.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports moving time window functions for calculating continuous aggregation over a sliding time window. [Moving time window functions](query_language_reference.html#moving-window-time-functions) are useful if, for example, you want to calculate the moving average over the past 24 hours.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports moving time window functions for calculating continuous aggregation over a sliding time window. [Moving time window functions](query_language_reference.html#moving-window-time-functions) are useful if, for example, you want to calculate the moving average over the past 24 hours.
But if you want to look at the daily average for each day, you have to create fixed-size time window. This page explains how use moving and fixed-sized time windows.
diff --git a/pages/doc/sources_managing.md b/pages/doc/sources_managing.md
index a8d0af3e4..6ed467b87 100644
--- a/pages/doc/sources_managing.md
+++ b/pages/doc/sources_managing.md
@@ -7,7 +7,7 @@ permalink: sources_managing.html
summary: Learn about sources and how to manage them.
---
-In Tanzu Observability (formerly known as VMware Aria Operations for Applications), a **source** is a unique application, host, container, or instance that emits metrics. The source is explicitly set in the `source` field of an [Tanzu Observability data format](wavefront_data_format.html) metric. For AWS integrations, the source is extracted from the [AWS CloudWatch service properties or dimensions](integrations_aws_metrics.html#aws_sources).
+In VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications), a **source** is a unique application, host, container, or instance that emits metrics. The source is explicitly set in the `source` field of an [Tanzu Observability data format](wavefront_data_format.html) metric. For AWS integrations, the source is extracted from the [AWS CloudWatch service properties or dimensions](integrations_aws_metrics.html#aws_sources).
* To view and manage sources, click **Browse > Sources** on the toolbar.
* To filter and group in charts, use the Wavefront Query Language. You can filter by source and [filter and group by source tags](tags_overview.html#source-tags).
diff --git a/pages/doc/start_trial.md b/pages/doc/start_trial.md
index d60ad5684..ab2e179b3 100644
--- a/pages/doc/start_trial.md
+++ b/pages/doc/start_trial.md
@@ -1,15 +1,15 @@
----Console
+---
title: Start a Tanzu Observability Free Trial
keywords: administration
tags: [administration]
sidebar: doc_sidebar
permalink: start_trial.html
-summary: VMware offers a free trial of the Tanzu Observability service where you can explore all of the service capabilities.
+summary: We offer a free trial of the VMware Tanzu Observability service where you can explore all of the service capabilities.
---
-You can start a 30-day free trial of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service from the VMware Cloud Services Console.
+You can start a 30-day free trial of the VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service from the VMware Cloud Services Console.
## Tanzu Observability and VMware Cloud Services
diff --git a/pages/doc/tags_overview.md b/pages/doc/tags_overview.md
index df61ed5b3..ef166aa87 100644
--- a/pages/doc/tags_overview.md
+++ b/pages/doc/tags_overview.md
@@ -5,7 +5,7 @@ sidebar: doc_sidebar
permalink: tags_overview.html
summary: Learn how to use tags to focus and speed up queries display and to unclutter the UI.
---
-In Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports tags for adding application-specific metadata to objects such alerts, dashboards, events, sources, and metrics.
+In VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports tags for adding application-specific metadata to objects such alerts, dashboards, events, sources, and metrics.
## Videos
diff --git a/pages/doc/upgrade-and-purchase.md b/pages/doc/upgrade-and-purchase.md
index 33b16d6d7..bd82cb11b 100644
--- a/pages/doc/upgrade-and-purchase.md
+++ b/pages/doc/upgrade-and-purchase.md
@@ -7,7 +7,7 @@ permalink: upgrade_and_purchase.html
summary: Learn how to upgrade from a trial version and purchase the service.
---
-When you register for the trial version of Tanzu Observability (formerly known as VMware Aria Operations for Applications), your trial expires after 30 days. One of the options that we offer is to purchase the service by using our self-service workflow. Another option is to contact the Tanzu Observability sales team, so that they guide you through the purchase process. For large commitments and more PPS, we strongly recommend the latter option.
+When you register for the trial version of VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications), your trial expires after 30 days. One of the options that we offer is to purchase the service by using our self-service workflow. Another option is to contact the Tanzu Observability sales team, so that they guide you through the purchase process. For large commitments and more PPS, we strongly recommend the latter option.
{% include note.html content="Starting September 20, 2023, all [**new trial**](start_trial.html) instances of Tanzu Observability are **onboarded** to VMware Cloud services. Trial service instances before this date are considered **original**. The upgrade procedure is slightly different for a [trial service instance on VMware Cloud services](upgrade_and_purchase.html#upgrade-a-trial-service-instance-on-vmware-cloud-services) and for an [original trial service instance](upgrade_and_purchase.html#upgrade-an-original-trial-service-instance)." %}
diff --git a/pages/doc/visualize_histograms.md b/pages/doc/visualize_histograms.md
index 27f526028..4774727f2 100644
--- a/pages/doc/visualize_histograms.md
+++ b/pages/doc/visualize_histograms.md
@@ -7,7 +7,7 @@ published: true
permalink: visualize_histograms.html
summary: Learn how to visualize histograms.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports histograms for computing, storing, and using distributions of metrics rather than single metrics. You can [send histograms](proxies_histograms.html#sending-histogram-distributions) to a Wavefront proxy or use direct ingestion.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports histograms for computing, storing, and using distributions of metrics rather than single metrics. You can [send histograms](proxies_histograms.html#sending-histogram-distributions) to a Wavefront proxy or use direct ingestion.
You can find histogram metrics in the histogram browser and query for them using an `hs()` query. You can also visualize histograms different chart types.
diff --git a/pages/doc/wavefront_data_format.md b/pages/doc/wavefront_data_format.md
index 4e693a37a..c150315d5 100644
--- a/pages/doc/wavefront_data_format.md
+++ b/pages/doc/wavefront_data_format.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: wavefront_data_format.html
summary: Learn about the data format syntax and parameters.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports the same native data format with Wavefront proxies and with direct ingestion. This page is a reference to the data format and includes best practices.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports the same native data format with Wavefront proxies and with direct ingestion. This page is a reference to the data format and includes best practices.
## Metrics
diff --git a/pages/doc/wavefront_data_ingestion.md b/pages/doc/wavefront_data_ingestion.md
index 64a6c9c62..6155880f6 100644
--- a/pages/doc/wavefront_data_ingestion.md
+++ b/pages/doc/wavefront_data_ingestion.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: wavefront_data_ingestion.html
summary: Learn how to set up the data ingestion pipeline.
---
-How you get your data into Tanzu Observability (formerly known as VMware Aria Operations for Applications) depends on your use case, but you have many options. You can use one of the supported integrations, or you can instrument your application and send data directly.
+How you get your data into VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) depends on your use case, but you have many options. You can use one of the supported integrations, or you can instrument your application and send data directly.
Watch this video to listen to the Wavefront co-founder Clement Pang's talk about data ingestion. Note that this video was created in 2018 and some of the information in it might have changed.
diff --git a/pages/doc/wavefront_prometheus.md b/pages/doc/wavefront_prometheus.md
index c79408743..63cd854c6 100644
--- a/pages/doc/wavefront_prometheus.md
+++ b/pages/doc/wavefront_prometheus.md
@@ -6,7 +6,7 @@ permalink: wavefront_prometheus.html
summary: Run PromQL queries in the Query Editor
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports both PromQL and Wavefront Query Language (WQL) queries. The Query Editor includes admin-level organization settings for enabling PromQL and a query line GUI that includes a translation option.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports both PromQL and Wavefront Query Language (WQL) queries. The Query Editor includes admin-level organization settings for enabling PromQL and a query line GUI that includes a translation option.
{% include note.html content="Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
- For VMware Cloud services subscriptions, users with the **Super Admin** service role (in Super Admin mode) and users with the **Admin** service role can enable the PromQL support.
diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md
index 372e91ac5..91700fb5e 100644
--- a/pages/doc/wavefront_release_notes.md
+++ b/pages/doc/wavefront_release_notes.md
@@ -4,7 +4,7 @@ keywords:
tags:
sidebar: doc_sidebar
permalink: wavefront_release_notes.html
-summary: Announcements and new and updated features in Tanzu Observability (formerly known as VMware Aria Operations for Applications).
+summary: Announcements and new and updated features in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
This page lists new and updated features for the Tanzu Observability service.
diff --git a/pages/labels/label_integrations%20list.md b/pages/labels/label_integrations%20list.md
index aee969632..6fd5cde55 100644
--- a/pages/labels/label_integrations%20list.md
+++ b/pages/labels/label_integrations%20list.md
@@ -7,7 +7,7 @@ sidebar: doc_sidebar
folder: labels
---
-
If your Tanzu Observability (formerly known as VMware Aria Operations for Applications) service is onboarded to VMware Cloud services, you still can see, but cannot configure some of our integrations. For the list of integrations that we support when your Tanzu Observability service is onboarded to VMware Cloud services, see Integrations Supported for Onboarded Subscriptions.
+
If your VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) service is onboarded to VMware Cloud services, you still can see, but cannot configure some of our integrations. For the list of integrations that we support when your Tanzu Observability service is onboarded to VMware Cloud services, see Integrations Supported for Onboarded Subscriptions.
The documentation pages only for a limited number of integrations contain the setup steps and instructions. If you do not see the setup steps on a certain integration doc page:
Navigate to the Tanzu Observability GUI and click Integrations on the toolbar.
From bcf1eac3e0dd8e5514df5734e14964b4aed8b111 Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Thu, 14 Mar 2024 10:46:26 +0200
Subject: [PATCH 05/26] Rebarnding Administering sections
---
_data/sidebars/doc_sidebar.yml | 2 +-
pages/doc/access.md | 6 ++--
pages/doc/accounts-service.md | 8 +++---
pages/doc/accounts.md | 4 +--
pages/doc/api_tokens.md | 6 ++--
pages/doc/auth_ss_sso.md | 4 +--
pages/doc/authentication-model.md | 10 +++----
pages/doc/authentication.md | 6 ++--
pages/doc/authorization.md | 4 +--
pages/doc/authorization_faq.md | 12 ++++----
pages/doc/csp_access.md | 14 ++++-----
pages/doc/csp_accounts-service.md | 22 +++++++-------
pages/doc/csp_api_tokens.md | 24 ++++++++--------
pages/doc/csp_authentication.md | 8 +++---
pages/doc/csp_authorization.md | 10 +++----
pages/doc/csp_getting_started.md | 26 ++++++++---------
pages/doc/csp_permissions_overview.md | 20 ++++++-------
pages/doc/csp_security_policy.md | 8 +++---
pages/doc/csp_server_to_server_apps.md | 24 ++++++++--------
pages/doc/csp_sign_up_or_log_in.md | 30 +++++++++----------
pages/doc/csp_user_management.md | 26 ++++++++---------
pages/doc/csp_users_account_managing.md | 14 ++++-----
pages/doc/csp_users_roles.md | 38 ++++++++++++-------------
pages/doc/permissions_overview.md | 12 ++++----
pages/doc/security_policy.md | 6 ++--
pages/doc/users_account_managing.md | 6 ++--
pages/doc/users_roles.md | 8 +++---
pages/doc/wavefront_administer.md | 14 ++++-----
28 files changed, 186 insertions(+), 186 deletions(-)
diff --git a/_data/sidebars/doc_sidebar.yml b/_data/sidebars/doc_sidebar.yml
index a7b1be773..f531c43bc 100755
--- a/_data/sidebars/doc_sidebar.yml
+++ b/_data/sidebars/doc_sidebar.yml
@@ -970,7 +970,7 @@ entries:
output: web
- title: Security Policy Rules
- url: /csp_metrics_security.html
+ url: /csp_security_policy.html
output: web
- title: Authentication Model
diff --git a/pages/doc/access.md b/pages/doc/access.md
index 22e8ee607..6a3db443c 100644
--- a/pages/doc/access.md
+++ b/pages/doc/access.md
@@ -7,9 +7,9 @@ permalink: access.html
summary: Control access to individual dashboards and alerts.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Managing Access to Dashboards and Alerts in Operations for Applications on VMware Cloud Services](csp_access.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Managing Access to Dashboards and Alerts in Tanzu Observability on VMware Cloud Services](csp_access.html)."%}
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports the roles, permissions, and groups authorization paradigm for managing global permissions. For example, a user with **Dashboards** permission can manage *all* dashboards. This paradigm is sufficient for many of our customers.
+Tanzu Observability supports the roles, permissions, and groups authorization paradigm for managing global permissions. For example, a user with **Dashboards** permission can manage *all* dashboards. This paradigm is sufficient for many of our customers.
Super Admins or users with the **Accounts** permission who need finer-grained control can manage access on a per-object basis. We currently support access control for dashboards and alerts.
@@ -26,7 +26,7 @@ This video shows how to limit access for a dashboard, how to give access (share)
## How Access Control Works
-Operations for Applications supports granting and revoking access to dashboards and alerts.
+Tanzu Observability supports granting and revoking access to dashboards and alerts.
* By default, all users can view all dashboards and alerts.
* Users with **Dashboards** permission can:
- Restrict or grant access to individual dashboards from the Dashboard browser.
diff --git a/pages/doc/accounts-service.md b/pages/doc/accounts-service.md
index 47980ac0f..7464564a4 100644
--- a/pages/doc/accounts-service.md
+++ b/pages/doc/accounts-service.md
@@ -7,9 +7,9 @@ permalink: service-accounts.html
summary: Create and manage service accounts.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Manage Server to Server Apps](csp_server_to_server_apps.html) and [Manage Service Accounts](csp_service_accounts.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Manage Server to Server Apps](csp_server_to_server_apps.html) and [Manage Service Accounts](csp_service_accounts.html)."%}
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports service accounts that can be used to automate management of objects such as dashboards, alerts, etc. A service account can't perform the **UI operations** that all user accounts can [perform by default](user-accounts.html#what-can-a-new-user-do). There's no limit on the number of service accounts that you can create in your organization.
+Tanzu Observability supports service accounts that can be used to automate management of objects such as dashboards, alerts, etc. A service account can't perform the **UI operations** that all user accounts can [perform by default](user-accounts.html#what-can-a-new-user-do). There's no limit on the number of service accounts that you can create in your organization.
{% include note.html content="Service accounts have no permissions by default. As a user with the **Accounts** permission, you must explicitly grant each service account only the permission required for the task that’s being automated (least required privilege). Doing so, you ensure that permissions for service accounts are always very limited. Service accounts do not have the view permissions that user accounts have by default. A service account must have **permissions** to perform tasks. To run queries, a service account must have **Metrics** permission. To manage dashboards and alerts, the service account might need both permissions and [access](access.html)." %}
@@ -27,7 +27,7 @@ As a user with the **Accounts** permission, you [generate (and revoke, if needed
## How Service Accounts Work
-If you build a service or tool that manages proxies or ingests data, then that tool must authenticate to the Operations for Applications REST API.
+If you build a service or tool that manages proxies or ingests data, then that tool must authenticate to the Tanzu Observability REST API.
1. Create a service account from the UI. The service account name must be unique.
2. Assign a role to the account to give the account the permissions it needs. Service accounts can perform get, modify, and delete tasks **only if** they have the necessary permissions.
@@ -54,7 +54,7 @@ Creating a service account is different from creating a user account.
Account ID
-
ID of the account. We prefix this ID with sa::.
A service account name must be unique. Operations for Applications converts service account ID to lower case to avoid confusion that can result from almost identical account names (e.g. Service-1 and service-1). Users can type upper case or lower case.
+
ID of the account. We prefix this ID with sa::.
A service account name must be unique. Tanzu Observability converts service account ID to lower case to avoid confusion that can result from almost identical account names (e.g. Service-1 and service-1). Users can type upper case or lower case.
diff --git a/pages/doc/accounts.md b/pages/doc/accounts.md
index f9e3a48c5..bedb77288 100644
--- a/pages/doc/accounts.md
+++ b/pages/doc/accounts.md
@@ -7,9 +7,9 @@ permalink: user-accounts.html
summary: Create and manage user accounts.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Manage Users of Operations for Applications on VMware Cloud Services](csp_user_management.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Manage Users of Tanzu Observability on VMware Cloud Services](csp_user_management.html)."%}
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports:
+Tanzu Observability supports:
* User accounts, discussed here, which authenticate with a username and password.
* [Service accounts](service-accounts.html), which authenticate with a token.
diff --git a/pages/doc/api_tokens.md b/pages/doc/api_tokens.md
index 09fb63429..0176e7f06 100644
--- a/pages/doc/api_tokens.md
+++ b/pages/doc/api_tokens.md
@@ -4,17 +4,17 @@ keywords: getting started
tags: [getting started]
sidebar: doc_sidebar
permalink: api_tokens.html
-summary: Learn how you can generate and manage API tokens in VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront).
+summary: Learn how you can generate and manage Tanzu Observability API tokens.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Manage Tokens](csp_api_tokens.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Manage Tokens](csp_api_tokens.html)."%}
Before you can invoke the [REST API](wavefront_api.html) using `curl` or from an API client, you must have an API token. An API token is a string of hexadecimal characters and dashes. For example:
```
a411c16b-3cf7-4f03-bf11-8ca05aab898d
```
-Operations for Applications allows [user accounts](user-accounts.html) and [service accounts](service-accounts.html) to use the [REST API](wavefront_api.html).
+Tanzu Observability allows [user accounts](user-accounts.html) and [service accounts](service-accounts.html) to use the [REST API](wavefront_api.html).
{% include tip.html content="You generate API tokens for your user account explicitly. For service accounts, a user with the **Accounts** permission can generate tokens from the **Service Accounts** page." %}
diff --git a/pages/doc/auth_ss_sso.md b/pages/doc/auth_ss_sso.md
index 87ecc8f2f..05a69ddeb 100644
--- a/pages/doc/auth_ss_sso.md
+++ b/pages/doc/auth_ss_sso.md
@@ -7,9 +7,9 @@ permalink: auth_self_service_sso.html
summary: Learn how to enable single-tenant authentication and set up self-service SSO.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Authentication Model in Operations for Applications on VMware Cloud Services](csp_authentication.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Authentication Model in Tanzu Observability on VMware Cloud Services](csp_authentication.html)."%}
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports a number of third-party authentication solutions that use SAML. The SAML (Security Assertion Markup Language) standard enables an identity provider (IdP) to pass authorization credentials to service providers (SP). In environments that use SAML, users log in once and authenticate to many different services.
+Tanzu Observability supports a number of third-party authentication solutions that use SAML. The SAML (Security Assertion Markup Language) standard enables an identity provider (IdP) to pass authorization credentials to service providers (SP). In environments that use SAML, users log in once and authenticate to many different services.
* Self-Service SAML SSO is not available for customers who have set up [multi-tenant authentication](authentication.html#multi-tenant-authentication).
* Self-Service SAML SSO is not available for trial customers.
diff --git a/pages/doc/authentication-model.md b/pages/doc/authentication-model.md
index 3ccb2610f..64cedea18 100644
--- a/pages/doc/authentication-model.md
+++ b/pages/doc/authentication-model.md
@@ -7,15 +7,15 @@ permalink: wavefront-authentication.html
summary: Learn about the authentication for user and service accounts.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Authentication Model in Operations for Applications on VMware Cloud Services](csp_authentication.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Authentication Model in Tanzu Observability on VMware Cloud Services](csp_authentication.html)."%}
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports these authentication options:
+Tanzu Observability supports these authentication options:
* **Direct authentication**: With direct authentication, users authentication with user name and password and service accounts authenticate with a token.
* **Authentication through an SSO identity provider**: You can choose from supported self-service SAML SSO provider or request and multi-tenant SSO support.
## Direct Authentication
-Operations for Applications supports direct authentication for user accounts and service accounts.
+Tanzu Observability supports direct authentication for user accounts and service accounts.
* [User accounts](user-accounts.html) must authenticate with a user name and password.
@@ -27,7 +27,7 @@ Operations for Applications supports direct authentication for user accounts and
## Self-Service SAML SSO
-You can use the authentication provided by Operations for Applications or use one of the supported authentication integrations. Operations for Applications supports several authentication solutions including:
+You can use the authentication provided by Tanzu Observability or use one of the supported authentication integrations. Tanzu Observability supports several authentication solutions including:
* [Google](google.html)
* [OneLogin](onelogin.html)
@@ -39,7 +39,7 @@ We also support [self-service SAML SSO](auth_self_service_sso.html) setup. After
{% include important.html content="If your environment requires Self-Service SAML SSO setup with an IdP that is not available in the list for self-service SAML SSO (for example, Azure AD or ADFS), create a [support ticket](wavefront_support_feedback.html#support)."%}
-If a customer's chosen authentication solution supports two-factor authentication, Operations for Applications requires two-factor authentication for login.
+If a customer's chosen authentication solution supports two-factor authentication, Tanzu Observability requires two-factor authentication for login.
## Multi-Tenant SSO
diff --git a/pages/doc/authentication.md b/pages/doc/authentication.md
index d381475e1..ad3a372fe 100644
--- a/pages/doc/authentication.md
+++ b/pages/doc/authentication.md
@@ -7,16 +7,16 @@ permalink: authentication.html
summary: Learn how to enable multi-tenant authentication.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Authentication Model in Operations for Applications on VMware Cloud Services](csp_authentication.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Authentication Model in Tanzu Observability on VMware Cloud Services](csp_authentication.html)."%}
-Most of our customers use [single-tenant authentication](auth_self_service_sso.html). If your company wants to set up different tenants for different teams, VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports multi-tenancy.
+Most of our customers use [single-tenant authentication](auth_self_service_sso.html). If your company wants to set up different tenants for different teams, Tanzu Observability supports multi-tenancy.
{% include note.html content="Switching tenants in multi-tenant environments require [the extra steps listed below](#point-a-proxy-to-a-different-tenant-in-a-multi-tenant-environment)." %}
## Multi-Tenant Authentication
-Several of our customers have asked for an environment that supports separate tenants for different teams. For example, here at VMware it made sense to keep the VMware vSphere team separate from the VMware NSX team -- both teams use Operations for Applications. This separation of teams, called multi-tenancy, works like this:
+Several of our customers have asked for an environment that supports separate tenants for different teams. For example, here at VMware it made sense to keep the VMware vSphere team separate from the VMware NSX team -- both teams use Tanzu Observability. This separation of teams, called multi-tenancy, works like this:
* The administrator at the customer site requests tenants from our Technical Support team and provides the tenant administrator emails and other information such as the IdP.
* After our Technical Support team has set up the tenants, each tenant administrator (a Super Admin or a user with the **Accounts** permission) invites users to that tenant.
diff --git a/pages/doc/authorization.md b/pages/doc/authorization.md
index 25de828b0..8a80e36be 100644
--- a/pages/doc/authorization.md
+++ b/pages/doc/authorization.md
@@ -7,9 +7,9 @@ permalink: authorization.html
summary: Learn about authorization of groups and users.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Authorization Model in Operations for Applications on VMware Cloud Services](csp_authorization.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Authorization Model in Tanzu Observability on VMware Cloud Services](csp_authorization.html)."%}
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports both role-based control that use global permissions and object-based access control for individual dashboards and alerts.
+Tanzu Observability supports both role-based control that use global permissions and object-based access control for individual dashboards and alerts.
Users with the **Accounts** permission can:
diff --git a/pages/doc/authorization_faq.md b/pages/doc/authorization_faq.md
index b891fc4c3..35e039354 100644
--- a/pages/doc/authorization_faq.md
+++ b/pages/doc/authorization_faq.md
@@ -7,13 +7,13 @@ permalink: authorization-faq.html
summary: Before you start managing users, groups, roles, and access, here are some FAQs.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Authorization Model in Operations for Applications on VMware Cloud Services](csp_authorization.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Authorization Model in Tanzu Observability on VMware Cloud Services](csp_authorization.html)."%}
### What Are User & Service Accounts?
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports two account types:
-* [**User accounts**](user-accounts.html) are for human users who work with Operations for Applications. A user account authenticates with a user name and password.
-* [**Service accounts**](service-accounts.html) are for services that interact with Operations for Applications through an API and use a **token** to authenticate. Service accounts are used to automate management tasks. As a user with the **Accounts** permission, you generate (and revoke, if needed) authentication tokens for the service account. It’s also possible to deactivate a service account completely.
+Tanzu Observability supports two account types:
+* [**User accounts**](user-accounts.html) are for human users who work with Tanzu Observability. A user account authenticates with a user name and password.
+* [**Service accounts**](service-accounts.html) are for services that interact with Tanzu Observability through an API and use a **token** to authenticate. Service accounts are used to automate management tasks. As a user with the **Accounts** permission, you generate (and revoke, if needed) authentication tokens for the service account. It’s also possible to deactivate a service account completely.
Service accounts:
- Don't have **default permissions** (unless one or more roles with permissions are assigned to the **Service Accounts** group.).
- Can't perform the **UI operations** that user accounts can perform by default.
@@ -21,7 +21,7 @@ VMware Aria Operations for Applications (formerly known as Tanzu Observability b
### Who Is the Super Admin User?
-When your company signs up with Operations for Applications, we ask you which users you want as Super Admin users for your service instance.
+When your company signs up with Tanzu Observability, we ask you which users you want as Super Admin users for your service instance.
When a Super Admin user [enables Super Admin mode](users_account_managing.html#enable-or-disable-super-admin-mode), that user:
@@ -50,7 +50,7 @@ Groups allow you to combine a set of users. You can then:
* Assign a role to the group.
* Give [view or modify access](access.html) for individual dashboards and alerts to the group.
-The groups in your Operations for Applications environment do *not* currently synchronize with the groups in your identity provider (IdP) such as Active Directory or LDAP.
+The groups in your Tanzu Observability environment do *not* currently synchronize with the groups in your identity provider (IdP) such as Active Directory or LDAP.
### What's the Everyone Group?
diff --git a/pages/doc/csp_access.md b/pages/doc/csp_access.md
index 0964f9629..26755879b 100644
--- a/pages/doc/csp_access.md
+++ b/pages/doc/csp_access.md
@@ -1,5 +1,5 @@
---
-title: Managing Access to Dashboards and Alerts in Operations for Applications on VMware Cloud Services
+title: Managing Access to Dashboards and Alerts in Tanzu Observability on VMware Cloud Services
keywords: administration
tags: [administration]
sidebar: doc_sidebar
@@ -7,15 +7,15 @@ permalink: csp_access.html
summary: Control access to individual dashboards and alerts.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Managing Access to Dashboards and Alerts](access.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Managing Access to Dashboards and Alerts](access.html)."%}
-VMware Cloud services supports the roles and groups authorization paradigm for managing global permissions in VMware Aria Operations for Applications. For example, a user with the **Dashboards** service role can manage *all* dashboards in Operations for Applications. This paradigm is sufficient for many of our customers.
+VMware Cloud services supports the roles and groups authorization paradigm for managing global permissions in Tanzu Observability. For example, a user with the **Dashboards** service role can manage *all* dashboards in Tanzu Observability. This paradigm is sufficient for many of our customers.
Users with the **Admin** and **Super Admin** service roles who need finer-grained control can manage access on a per-object basis. We currently support access control for dashboards and alerts.
{% include note.html content="Permission and access control are additive. To make changes to a dashboard, you must have a role with the **Dashboards** permission and **View and Modify** access for that dashboard." %}
-{% include tip.html content="In addition to access control, Operations for Applications also supports [metrics security policy rules](csp_metrics_security.html) which allow fine-grained control over which users can see which metrics." %}
+{% include tip.html content="In addition to access control, Tanzu Observability also supports [metrics security policy rules](csp_metrics_security.html) which allow fine-grained control over which users can see which metrics." %}
{% include note.html content="After the access setting is set to **Object Creator** in an environment, only the creator of a new object and users the **Super Admin** service role can view and modify new objects initially. Those users can give access to the object with other groups or users." %}
@@ -23,7 +23,7 @@ Users with the **Admin** and **Super Admin** service roles who need finer-graine
## How Access Control Works
-Operations for Applications supports granting and revoking access to dashboards and alerts.
+Tanzu Observability supports granting and revoking access to dashboards and alerts.
* By default, all users can view all dashboards and alerts.
* Users with the **Dashboards** permission can:
- Restrict or grant access to individual dashboards from the Dashboard browser.
@@ -85,7 +85,7 @@ After the change, access to new dashboards and new alerts is initially limited t
{% include note.html content="A change to the security setting applies only to dashboards and alerts created **after** the change. If you change the setting to **Object Creator**, only new dashboards and alerts have restricted access. If you later change the setting to **Everyone**, all dashboards and alerts that were created while the setting was **Object Creator** keep the restricted access." %}
-By default, service accounts (which includes the [server to server apps](csp_server_to_server_apps.html) in VMware Cloud services as well as the [service accounts](csp_service_accounts.html) in Operations for Applications) don't have browse permissions. However, you can also grant access for new dashboards and alerts to service accounts:
+By default, service accounts (which includes the [server to server apps](csp_server_to_server_apps.html) in VMware Cloud services as well as the [service accounts](csp_service_accounts.html) in Tanzu Observability) don't have browse permissions. However, you can also grant access for new dashboards and alerts to service accounts:
1. From the gear icon on the toolbar, select **Organization Settings**.
2. Click the **Security** tab, select **Grant Modify Access To: Everyone** and **Service Accounts**.
@@ -166,4 +166,4 @@ A permanently deleted dashboard does not show in the trash and becomes inaccessi
10. Validate that the dashboard is now live again.
- For example, navigate to `https://.wavefront.com/dashboards/MY-DASHBOARD/history` and you should now be able to review the dashboard history by using the Operations for Applications UI.
+ For example, navigate to `https://.wavefront.com/dashboards/MY-DASHBOARD/history` and you should now be able to review the dashboard history by using the Tanzu Observability UI.
diff --git a/pages/doc/csp_accounts-service.md b/pages/doc/csp_accounts-service.md
index 8b4b6ea80..d07e1602f 100644
--- a/pages/doc/csp_accounts-service.md
+++ b/pages/doc/csp_accounts-service.md
@@ -1,5 +1,5 @@
---
-title: Manage Service Accounts in Operations for Applications on VMware Cloud Services
+title: Manage Service Accounts in Tanzu Observability on VMware Cloud Services
keywords: administration
tags: [administration]
sidebar: doc_sidebar
@@ -7,24 +7,24 @@ permalink: csp_service_accounts.html
summary: Learn how you can create and manage service accounts.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage Service Accounts](service-accounts.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage Service Accounts](service-accounts.html)."%}
-{% include warning.html content="The usage of service accounts in Operations for Applications on VMware Cloud services is **restricted** to support only a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Operations for Applications API tokens. We are in the process of updating all of our integrations to authenticate with VMware Cloud services access tokens. Service accounts and Operations for Applications API tokens will be deprecated in the future."%}
+{% include warning.html content="The usage of service accounts in Tanzu Observability on VMware Cloud services is **restricted** to support only a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens) that still authenticate with Tanzu Observability API tokens. We are in the process of updating all of our integrations to authenticate with VMware Cloud services access tokens. Service accounts and Tanzu Observability API tokens will be deprecated in the future."%}
If your service was recently onboarded to VMware Cloud services, you might have some legacy service accounts for backward compatibility. It's strongly recommended that you incrementally switch to using [server to server OAuth apps](csp_server_to_server_apps.html) which authenticate with more secure VMware Cloud services access tokens. See [How to Replace a Service Account with a Server to Server App?](csp_migration.html#how-to-replace-a-service-account-with-a-server-to-server-app).
## What Are Service Accounts?
-* A service account uses an **Operations for Applications API token** to authenticate.
+* A service account uses an **Tanzu Observability API token** to authenticate.
* By default, service accounts don't have any permissions, even view permissions. Users with the **Admin** service role must explicitly grant each service account only the permission required for the task that’s being automated (least required privilege). There's no limit on the number of service accounts that you can create in your service instance.
-As a user with the **Admin** service role, you [generate (and revoke, if needed)](csp_api_tokens.html#manage-the-operations-for-applications-api-tokens-for-a-service-account) the API tokens for the service account. It’s also possible to [deactivate](csp_service_accounts.html#deactivate-or-activate-a-service-account) a service account completely.
+As a user with the **Admin** service role, you [generate (and revoke, if needed)](csp_api_tokens.html#manage-the-tanzu-observability-api-tokens-for-a-service-account) the API tokens for the service account. It’s also possible to [deactivate](csp_service_accounts.html#deactivate-or-activate-a-service-account) a service account completely.
-{% include note.html content="Operations for Applications includes the **Service Accounts** internal system group, where all service accounts together with the [server to server apps](csp_server_to_server_apps.html) that have access to the service are added automatically. This group doesn't have any roles and permissions. This group can be used when managing [access to dashboards and alerts](csp_access.html), [metrics security policy rules](csp_metrics_security.html), and [ingestion policies](ingestion_policies.html)."%}
+{% include note.html content="Tanzu Observability includes the **Service Accounts** internal system group, where all service accounts together with the [server to server apps](csp_server_to_server_apps.html) that have access to the service are added automatically. This group doesn't have any roles and permissions. This group can be used when managing [access to dashboards and alerts](csp_access.html), [metrics security policy rules](csp_metrics_security.html), and [ingestion policies](ingestion_policies.html)."%}
## How Service Accounts Work
-If you plan to set up an integration that uses a proxy authentication with an Operations for Applications API token, you must create a service account with the **Proxies** permission and generate an API token for it.
+If you plan to set up an integration that uses a proxy authentication with a Tanzu Observability API token, you must create a service account with the **Proxies** permission and generate an API token for it.
1. Create a service account from the UI. The service account name must be unique.
2. Assign the service account with the **Proxies** permission.
@@ -37,7 +37,7 @@ You can disable a service account if you temporarily don't need it, or you can d
## Create a Service Account
-Service accounts are created in Operations for Applications.
+Service accounts are created in Tanzu Observability.
1. Log in to your service instance as a user with the **Admin** service role.
1. From the gear icon on the toolbar, select **Accounts**.
@@ -52,12 +52,12 @@ Service accounts are created in Operations for Applications.
Account ID
-
ID of the account. We prefix this ID with sa::.
A service account name must be unique. Operations for Applications converts a service account ID to lower case to avoid confusion that can result from almost identical account names (e.g. Service-1 and service-1). Users can type upper case or lower case.
+
ID of the account. We prefix this ID with sa::.
A service account name must be unique. Tanzu Observability converts a service account ID to lower case to avoid confusion that can result from almost identical account names (e.g. Service-1 and service-1). Users can type upper case or lower case.
Tokens
-
List of API tokens that the service account can use to authenticate to the Operations for Applications service instance.
+
List of API tokens that the service account can use to authenticate to the Tanzu Observability service instance.
Click the Edit icon to change the token name.
Click Revoke to revoke a token. Any service account that uses the token can no longer authenticate to the service instance.
Click Generate to generate additional tokens. Having multiple active tokens makes it possible to revoke some tokens. For example, if the service connects to several proxies, you can generate a token to connect to each proxy. You can revoke the token for one proxy but leave the others. You can have up to 20 API tokens per service account at any given time.
@@ -66,7 +66,7 @@ Tokens
Permissions
-
Individual permissions assigned to this service account. Assign the service account with the Proxies permission, so that you can use it for the proxy setup of an integration that authenticates with an Operations for Applications API token.
+
Individual permissions assigned to this service account. Assign the service account with the Proxies permission, so that you can use it for the proxy setup of an integration that authenticates with a Tanzu Observability API token.
diff --git a/pages/doc/csp_api_tokens.md b/pages/doc/csp_api_tokens.md
index 51c48b476..d5d181f41 100644
--- a/pages/doc/csp_api_tokens.md
+++ b/pages/doc/csp_api_tokens.md
@@ -1,5 +1,5 @@
---
-title: Manage Tokens for Operations for Applications on VMware Cloud Services
+title: Manage Tokens for Tanzu Observability on VMware Cloud Services
keywords: getting started
tags: [getting started]
sidebar: doc_sidebar
@@ -7,17 +7,17 @@ permalink: csp_api_tokens.html
summary: Learn how you can generate and manage API tokens and access tokens.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage API Tokens](api_tokens.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage API Tokens](api_tokens.html)."%}
-Invoking the [Operations for Applications REST API](wavefront_api.html), using `curl` or an API client, requires a **VMware Cloud services access token**. In a few cases, when setting up a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens), authentication with an **Operations for Applications API token** is also supported.
+Invoking the [Tanzu Observability REST API](wavefront_api.html), using `curl` or an API client, requires a **VMware Cloud services access token**. In a few cases, when setting up a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens), authentication with an **Tanzu Observability API token** is also supported.
To obtain a VMware Cloud services access token, you must make an API call to the VMware Cloud services REST API and exchange it from:
* A VMware Cloud services API token associated with your user account.
* The credentials of a server to server OAuth app associated with the VMware Cloud organization running the service.
-To obtain an Operations for Applications API token, you can also create a service account and generate an API token associated with it.
+To obtain a Tanzu Observability API token, you can also create a service account and generate an API token associated with it.
-{% include note.html content="If your original Operations for Applications subscription was recently [onboarded to VMware Cloud services](csp_migration.html), for backward compatibility, you might have some legacy Operations for Applications API tokens that are associated with user accounts and service accounts. It’s recommended that you incrementally replace them with VMware Cloud services API tokens and sever to server OAuth apps."%}
+{% include note.html content="If your original Tanzu Observability subscription was recently [onboarded to VMware Cloud services](csp_migration.html), for backward compatibility, you might have some legacy Tanzu Observability API tokens that are associated with user accounts and service accounts. It’s recommended that you incrementally replace them with VMware Cloud services API tokens and sever to server OAuth apps."%}
## Manage the VMware Cloud Services API Tokens for Your User Account
@@ -25,7 +25,7 @@ If you want to make REST API calls on your own behalf, you must generate a VMwar
You can generate VMware Cloud services API tokens only for your user account. You must assign each API token with the minimum required subset of the roles that you own. The access tokens associated with an API token inherit its roles. These roles include:
* At least one organization role.
-* At least one Operations for Applications service role.
+* At least one Tanzu Observability service role.
* Optionally, one or more custom roles.
You must also set each API token with a time to live (TTL), which is the time that the API token will be valid unless revoked earlier. Before an API token expires, you must generate a new API token and update your scripts and API calls.
@@ -55,18 +55,18 @@ To create and manage server to server OAuth apps in your VMware Cloud organizati
You must assign each server to server app only with the minimum required roles for its tasks and add it to your VMware Cloud organization. The access tokens associated with a server to server app inherit its roles within the organizations it belongs. These roles include:
* At least one organization role.
-* At least one Operations for Applications service role.
+* At least one Tanzu Observability service role.
* Optionally, one or more custom roles.
You must also set each server to server app with a time to live (TTL), which is the time that the access tokens associated with the app will be valid. The credentials of a sever to server app never expire, so that your script can periodically exchange them for new access tokens. Only if you regenerate the app secret, you must update your scripts and API calls.
For details on how to create, view, and modify the details of the OAuth 2.0 apps in your organization, see [How to manage OAuth 2.0 apps](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-229F9BCE-0C1F-4948-8792-23F51B5482BE.html) in the VMware Cloud services documentation.
-## Manage the Operations for Applications API Tokens for a Service Account
+## Manage the Tanzu Observability API Tokens for a Service Account
-If you want to set up one of the [integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with an **Operations for Applications API token**, you must create a [service account](csp_service_accounts.html) and generate an API token associated with it.
+If you want to set up one of the [integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens) that still authenticate with an **Tanzu Observability API token**, you must create a [service account](csp_service_accounts.html) and generate an API token associated with it.
-{% include warning.html content="The usage of service accounts in Operations for Applications on VMware Cloud services is **restricted** to support only a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Operations for Applications API tokens. We are in the process of updating all of our integrations to authenticate with VMware Cloud services access tokens. It is strongly recommended that you gradually [switch to using server to server OAuth apps](csp_migration.html#how-to-replace-a-service-account-with-a-server-to-server-app) which authenticate with more secure VMware Cloud services access tokens. Service accounts and Operations for Applications API tokens will be deprecated in the future. "%}
+{% include warning.html content="The usage of service accounts in Tanzu Observability on VMware Cloud services is **restricted** to support only a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens) that still authenticate with Tanzu Observability API tokens. We are in the process of updating all of our integrations to authenticate with VMware Cloud services access tokens. It is strongly recommended that you gradually [switch to using server to server OAuth apps](csp_migration.html#how-to-replace-a-service-account-with-a-server-to-server-app) which authenticate with more secure VMware Cloud services access tokens. Service accounts and Tanzu Observability API tokens will be deprecated in the future. "%}
@@ -88,11 +88,11 @@ To generate and manage the API tokens for an existing **service account**:
-## Manage the Operations for Applications API Tokens in Your Service Instance
+## Manage the Tanzu Observability API Tokens in Your Service Instance
As a user with the **Admin** service role, you can view and revoke the API tokens of any service account in your service instance.
-{% include warning.html content="If your original Operations for Applications subscription was onboarded to VMware Cloud services, for backward compatibility, you might have some legacy Operations for Applications API tokens that are associated with user accounts. It’s recommended that you incrementally [replace them with VMware Cloud services API tokens](csp_migration.html#how-to-replace-an-operations-for-applications-api-token-with-a-vmware-cloud-services-access-token)."%}
+{% include warning.html content="If your original Tanzu Observability subscription was onboarded to VMware Cloud services, for backward compatibility, you might have some legacy Tanzu Observability API tokens that are associated with user accounts. It’s recommended that you incrementally [replace them with VMware Cloud services API tokens](csp_migration.html#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token)."%}
1. Log in to your service instance as an **Admin** user.
2. Click the gear icon on the toolbar and select **Accounts**.
diff --git a/pages/doc/csp_authentication.md b/pages/doc/csp_authentication.md
index 891bd2acd..f06838f9c 100644
--- a/pages/doc/csp_authentication.md
+++ b/pages/doc/csp_authentication.md
@@ -1,5 +1,5 @@
---
-title: Authentication Model in Operations for Applications on VMware Cloud Services
+title: Authentication Model in Tanzu Observability on VMware Cloud Services
keywords:
tags: [integrations, administration]
sidebar: doc_sidebar
@@ -7,15 +7,15 @@ permalink: csp_authentication.html
summary: Learn how to enable multi-tenant authentication.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Authentication Model](wavefront-authentication.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Authentication Model](wavefront-authentication.html)."%}
-VMware Cloud services provides a central single sign-on (SSO) to all of your services running on the platform, including VMware Aria Operations for Applications. Users authenticate with VMware Cloud services accounts. Server-to-server apps, which correspond to service accounts in Operations for Applications, authenticate with OAuth 2.0 client credentials and VMware Cloud services API tokens are issued directly to them.
+VMware Cloud services provides a central single sign-on (SSO) to all of your services running on the platform, including Tanzu Observability. Users authenticate with VMware Cloud services accounts. Server-to-server apps, which correspond to service accounts in Tanzu Observability, authenticate with OAuth 2.0 client credentials and VMware Cloud services API tokens are issued directly to them.
VMware Cloud services supports these user authentication options:
* **Authentication through a VMware ID**: The VMware Cloud services account is based on the VMware ID (VMware account) credentials that the user creates in the VMware Cloud Services Console.
* **Authentication through a federated domain**: The VMware Cloud services account is based on the corporate account credentials.
-VMware Cloud services also supports **multi-tenant SSO**, where each Operations for Applications tenant is onboarded as a separate Operations for Applications service instance in the same VMware Cloud organization.
+VMware Cloud services also supports **multi-tenant SSO**, where each Tanzu Observability tenant is onboarded as a separate Tanzu Observability service instance in the same VMware Cloud organization.
## VMware ID Authentication
diff --git a/pages/doc/csp_authorization.md b/pages/doc/csp_authorization.md
index 14455dcf8..071dc44bb 100644
--- a/pages/doc/csp_authorization.md
+++ b/pages/doc/csp_authorization.md
@@ -1,19 +1,19 @@
---
-title: Authorization Model in Operations for Applications on VMware Cloud Services
+title: Authorization Model in Tanzu Observability on VMware Cloud Services
keywords: administration
tags: [administration]
sidebar: doc_sidebar
permalink: csp_authorization.html
-summary: Learn about authorization of groups, users, and server to server apps to access VMware Aria Operations for Applications on VMware Cloud services.
+summary: Learn about authorization of groups, users, and server to server apps to access VMware Tanzu Observability on VMware Cloud services.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Authorization Model](authorization.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Authorization Model](authorization.html)."%}
-VMware Cloud services supports role-based access control for the services on its platform, including Operations for Applications. Operations for Applications supports object-based access control for individual dashboards and alerts as well as metrics security policy.
+VMware Cloud services supports role-based access control for the services on its platform, including Tanzu Observability. Tanzu Observability supports object-based access control for individual dashboards and alerts as well as metrics security policy.
## Role-Based Access Control with Global Permissions
-[Operations for Applications permissions](csp_permissions_overview.html) always apply to all objects of a certain type. For example, a user with the **Dashboards** permission can view and modify all dashboards.
+[Tanzu Observability permissions](csp_permissions_overview.html) always apply to all objects of a certain type. For example, a user with the **Dashboards** permission can view and modify all dashboards.
Users with the VMware Cloud **Organization Owner** or **Organization Administrator** role manage authorization with [roles and groups](csp_users_roles.html). They can:
* Create **groups** and add users to each group.
diff --git a/pages/doc/csp_getting_started.md b/pages/doc/csp_getting_started.md
index 6cd06515b..bf3923cec 100644
--- a/pages/doc/csp_getting_started.md
+++ b/pages/doc/csp_getting_started.md
@@ -1,17 +1,17 @@
---
-title: Getting Started with Operations for Applications on VMware Cloud Services
+title: Getting Started with Tanzu Observability on VMware Cloud Services
tags: [administration]
sidebar: doc_sidebar
permalink: csp_getting_started.html
summary: Learn the basics for administering your service on the VMware Cloud services platform.
---
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. From this date, we support two types of subscriptions: Operations for Applications subscriptions **onboarded** to VMware Cloud services and **original** subscriptions.
+Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. From this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to VMware Cloud services and **original** subscriptions.
Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services. We are in the process of incrementally [onboarding](csp_migration.html) all original subscriptions to VMware Cloud services. For information about original and VMware Cloud services subscriptions and the differences between them, see [Differences Between Original and VMware Cloud Services Subscriptions](csp-differences-by-area.html).
-{% include note.html content="Starting September 20, 2023, all [**new trial**](start_trial.html) instances of Operations for Applications are **onboarded** to VMware Cloud services."%}
+{% include note.html content="Starting September 20, 2023, all [**new trial**](start_trial.html) instances of Tanzu Observability are **onboarded** to VMware Cloud services."%}
-VMware Cloud services provides features to your Operations for Applications environment, such as:
+VMware Cloud services provides features to your Tanzu Observability environment, such as:
- Single sign-on (SSO) with VMware Cloud services accounts.
- SAML 2.0 SSO identity federation with your enterprise identity provider.
- Identity access management (IAM) with built-in and custom service roles.
@@ -22,18 +22,18 @@ See the [Advantages of VMware Cloud Services Subscriptions Over Original Subscri
## What's VMware Cloud Services Console?
-The VMware Cloud Services Console lets you manage your entire VMware Cloud services portfolio across hybrid and native public clouds. Operations for Applications is one of the many services that you can access, configure, and consume through this console.
+The VMware Cloud Services Console lets you manage your entire VMware Cloud services portfolio across hybrid and native public clouds. Tanzu Observability is one of the many services that you can access, configure, and consume through this console.
To open the VMware Cloud Services Console:
- In a Web browser, go to `https://console.cloud.vmware.com`.
-- From the Operations for Applications UI, click the **VMware Cloud Services Applications Menu** icon () in the top-right corner and select **Cloud Services Console**.
+- From the Tanzu Observability UI, click the **VMware Cloud Services Applications Menu** icon () in the top-right corner and select **Cloud Services Console**.
See [Using VMware Cloud Services Console](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-20D62AFF-024B-4901-976D-69BFD71BECC8.html) in the VMware Cloud services documentation.
## What's a VMware Cloud Services Account?
-A VMware Cloud services account is a user (human) account in VMware Cloud services with which you can access all of your service instances, including Operations for Applications. A VMware Cloud services account logs in to VMware Cloud services with an email address and a password. A VMware Cloud services account can be one of the following:
+A VMware Cloud services account is a user (human) account in VMware Cloud services with which you can access all of your service instances, including Tanzu Observability. A VMware Cloud services account logs in to VMware Cloud services with an email address and a password. A VMware Cloud services account can be one of the following:
- A VMware account (VMware ID) that you create in the VMware Cloud Services Console.
You can create a VMware account independently, while [onboarding](start_trial.html) a service, or while [signing up](csp_sign_up_or_log_in.html) to a service with an invitation link.
@@ -46,9 +46,9 @@ VMware Cloud services uses organizations to provide controlled access to one or
* Users can belong to multiple organizations.
* Multiple service instances can run in the same or in different organizations.
-For example, you can have a multi-tenant Operations for Applications environment with multiple service instances (tenants) in the same organization.
+For example, you can have a multi-tenant Tanzu Observability environment with multiple service instances (tenants) in the same organization.
-{% include note.html content="You can create a VMware Cloud organization only when you are onboarding a new service instance, for example, when you are [starting an Operations for Applications free trial](start_trial.html)."%}
+{% include note.html content="You can create a VMware Cloud organization only when you are onboarding a new service instance, for example, when you are [starting an Tanzu Observability free trial](start_trial.html)."%}
See [How do I manage my Cloud Services organizations](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-CF9E9318-B811-48CF-8499-9419997DC1F8.html) in the VMware Cloud services documentation.
@@ -81,16 +81,16 @@ See [What organization roles are available in VMware Cloud Services](https://doc
## What Are Service Roles and Custom Roles?
-VMware Cloud services includes service-specific built-in roles, including [Operations for Applications service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in). A service role is required to grant certain access to the corresponding service instance in the organization.
+VMware Cloud services includes service-specific built-in roles, including [Tanzu Observability service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in). A service role is required to grant certain access to the corresponding service instance in the organization.
While the service roles are built-in and not editable, as a VMware Cloud **Organization Administrator** or **Organization Owner**, you can create [custom roles](csp_users_roles.html#create-edit-or-delete-a-custom-role) with service permissions of your choice, including [Operations for Application permissions](csp_permissions_overview.html#operations-for-applications-permissions). Custom roles are optional and apply to all service instances for which the target user or server to server app has at least one service role.
## What's a Server to Server App?
-If you want to use an application for automating management tasks in your service, for example, in Operations for Applications, your application requires direct access to your service, without user authorization.
+If you want to use an application for automating management tasks in your service, for example, in Tanzu Observability, your application requires direct access to your service, without user authorization.
-For that purpose, VMware Cloud services supports server to server apps, which are based on OAuth 2.0 client credentials grant type. You can configure your application to pass the OAuth 2.0 client credentials (id and secret) to the VMware Cloud services REST API and exchange the credentials for a VMware Cloud services access token. Your application can use the VMware Cloud services access token to interact with the Operations for Applications REST API.
+For that purpose, VMware Cloud services supports server to server apps, which are based on OAuth 2.0 client credentials grant type. You can configure your application to pass the OAuth 2.0 client credentials (id and secret) to the VMware Cloud services REST API and exchange the credentials for a VMware Cloud services access token. Your application can use the VMware Cloud services access token to interact with the Tanzu Observability REST API.
See [How to use OAuth 2.0 for server to server apps](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-327AE12A-85DB-474B-89B2-86651DF91C77.html) in the VMware Cloud services documentation.
-{% include important.html content="For each server to server app with access to an Operations for Applications service instance, we create a corresponding **internal service account** in that service instance and add it the **Service Accounts** internal system group. So that, when you configure [the access control security settings](csp_access.html#change-the-access-control-security-setting), [ingestion polices](ingestion_policies.html#step-1-specify-the-scope-and-pps-limit), or [metrics security rules](csp_metrics_security.html), the server to server apps that are assigned with Operations for Applications service roles are represented as service accounts together with the [service accounts](csp_service_accounts.html) created in Operations for Applications."%}
+{% include important.html content="For each server to server app with access to a Tanzu Observability service instance, we create a corresponding **internal service account** in that service instance and add it the **Service Accounts** internal system group. So that, when you configure [the access control security settings](csp_access.html#change-the-access-control-security-setting), [ingestion polices](ingestion_policies.html#step-1-specify-the-scope-and-pps-limit), or [metrics security rules](csp_metrics_security.html), the server to server apps that are assigned with Tanzu Observability service roles are represented as service accounts together with the [service accounts](csp_service_accounts.html) created in Tanzu Observability."%}
diff --git a/pages/doc/csp_permissions_overview.md b/pages/doc/csp_permissions_overview.md
index 0669aec3f..814f5ff07 100644
--- a/pages/doc/csp_permissions_overview.md
+++ b/pages/doc/csp_permissions_overview.md
@@ -1,15 +1,15 @@
---
-title: Operations for Applications Permissions in VMware Cloud Services
+title: Tanzu Observability Permissions in VMware Cloud Services
keywords: administration
tags: [administration]
sidebar: doc_sidebar
permalink: csp_permissions_overview.html
-summary: Learn about the permissions in VMware Aria Operations for Applications on VMware Cloud services.
+summary: Learn about the permissions in VMware Tanzu Observability on VMware Cloud services.
---
All users can perform certain default tasks. However, you must have the appropriate permissions to manage objects. If you do not have permission, UI menu selections and buttons required to perform management tasks are not visible.
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Permissions Reference](permissions_overview.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Permissions Reference](permissions_overview.html)."%}
## Default Tasks
@@ -26,11 +26,11 @@ All users can:
Users with the [**Super Admin** service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) have full administrative access to the service.
-## Operations for Applications Permissions
+## Tanzu Observability Permissions
-VMware Cloud services allows users with the VMware Cloud **Organization Owner** and **Organization Administrator** roles to perform access control for object management based on Operations for Applications permissions.
+VMware Cloud services allows users with the VMware Cloud **Organization Owner** and **Organization Administrator** roles to perform access control for object management based on Tanzu Observability permissions.
- Permissions can be assigned to roles only, and roles can be assigned to users, user groups, and server to server apps.
-- For each permission, there is a corresponding built-in [Operations for Applications service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) with only that permission assigned.
+- For each permission, there is a corresponding built-in [Tanzu Observability service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) with only that permission assigned.
- Permissions can be assigned to [custom roles](csp_users_roles.html#create-edit-or-delete-a-custom-role).
@@ -40,7 +40,7 @@ VMware Cloud services allows users with the VMware Cloud **Organization Owner**
Admin
-
Manage the Operations for Applications organization settings: set the default display options, PromQL support, and the default way of building queries for all users of the service instance. Can define logs settings, if the logs feature is enabled. Can restrict access to new dashboards and alerts. Can manage service accounts, if enabled for the service instance.
+
Manage the Tanzu Observability organization settings: set the default display options, PromQL support, and the default way of building queries for all users of the service instance. Can define logs settings, if the logs feature is enabled. Can restrict access to new dashboards and alerts. Can manage service accounts, if enabled for the service instance.
Alerts
@@ -56,7 +56,7 @@ VMware Cloud services allows users with the VMware Cloud **Organization Owner**
Charts Embedding
-
Generate HTML snippets of charts in Operations for Applications and embed a corresponding interactive chart outside of Operations for Applications. Embedded chart URLs are associated with a specific user account. If a user embeds a chart and later that user’s account is removed, the embedded chart no longer works.
+
Generate HTML snippets of charts in Tanzu Observability and embed a corresponding interactive chart outside of Tanzu Observability. Embedded chart URLs are associated with a specific user account. If a user embeds a chart and later that user’s account is removed, the embedded chart no longer works.
Dashboards
@@ -68,7 +68,7 @@ VMware Cloud services allows users with the VMware Cloud **Organization Owner**
Direct Data Ingestion
-
Directly ingest metrics using the REST API or one of the SDKs, bypassing the proxy. Grant this permission only to users who have a deep understanding of APIs and the Operations for Applications ingestion path.
+
Directly ingest metrics using the REST API or one of the SDKs, bypassing the proxy. Grant this permission only to users who have a deep understanding of APIs and the Tanzu Observability ingestion path.
Events
@@ -89,7 +89,7 @@ VMware Cloud services allows users with the VMware Cloud **Organization Owner**
Logs
View logs and drill into logs from charts, alerts, and traces. In combination with the Dashboards permission, you can create logs charts.
-
Note: Logs (Beta) is enabled only for selected customers. To participate, contact your Operations for Applications account representative.
+
Note: Logs (Beta) is enabled only for selected customers. To participate, contact your Tanzu Observability account representative.
Metrics
diff --git a/pages/doc/csp_security_policy.md b/pages/doc/csp_security_policy.md
index 8ebae8a72..7f04ebef0 100644
--- a/pages/doc/csp_security_policy.md
+++ b/pages/doc/csp_security_policy.md
@@ -1,5 +1,5 @@
---
-title: Security Policy Rules in Operations for Applications on VMware Cloud Services
+title: Security Policy Rules in Tanzu Observability on VMware Cloud Services
keywords: administration
tags: [administration]
sidebar: doc_sidebar
@@ -7,9 +7,9 @@ permalink: csp_security_policy.html
summary: Use security policies to control access to metrics, such as time series, histograms, RED metrics, and delta counters, as well as traces.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Metrics Security Policy Rules in Operations for Applications on VMware Cloud Services](csp_metrics_security.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Security Policy Rules](security_policy.html)."%}
-You can create security policies on VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) to protect your metrics and traces security data.
+You can create security policies in Tanzu Observability to protect your metrics and traces security data.
@@ -153,7 +153,7 @@ Data protected by a metrics security policy rule can become invisible to users.
### Alert Notifications
-To protect metrics or RED metrics from inclusion in alert notifications, use the **Secure Metrics Details** check box. Operations for Applications looks at all metrics when determining when an alert status should change and shows them in alert notifications. When the check box is selected, [details are not shown](alerts_notifications.html#alert-notification-with-secured-metrics-details) in the notification.
+To protect metrics or RED metrics from inclusion in alert notifications, use the **Secure Metrics Details** check box. Tanzu Observability looks at all metrics when determining when an alert status should change and shows them in alert notifications. When the check box is selected, [details are not shown](alerts_notifications.html#alert-notification-with-secured-metrics-details) in the notification.
### Derived Metrics and Events
diff --git a/pages/doc/csp_server_to_server_apps.md b/pages/doc/csp_server_to_server_apps.md
index 906f658c0..4c82912bf 100644
--- a/pages/doc/csp_server_to_server_apps.md
+++ b/pages/doc/csp_server_to_server_apps.md
@@ -4,16 +4,16 @@ keywords: administration
tags: [administration]
sidebar: doc_sidebar
permalink: csp_server_to_server_apps.html
-summary: Create server to server apps and grant them access to VMware Aria Operations for Applications on VMware Cloud services.
+summary: Create server to server apps and grant them access to VMware Tanzu Observability on VMware Cloud services.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage Service Accounts](service-accounts.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage Service Accounts](service-accounts.html)."%}
-VMware Cloud services supports server to server apps that you can use to automate management of Operations for Applications objects, such as dashboards, alerts, etc. A server to server app can't perform the **UI operations** that all user accounts can [perform by default](csp_permissions_overview.html#default-tasks).
+VMware Cloud services supports server to server apps that you can use to automate management of Tanzu Observability objects, such as dashboards, alerts, etc. A server to server app can't perform the **UI operations** that all user accounts can [perform by default](csp_permissions_overview.html#default-tasks).
You can also use a server to server app for a [Wavefront proxy authentication](proxies_installing.html#proxy-authentication-types). For example, see our [Windows Host Integration Tutorial](windows_host_tutorial.html), which includes installing a Wavefront proxy with server to server OAuth app credentials.
-{% include note.html content="A server to server app must hold roles with certain [permissions](csp_permissions_overview.html#operations-for-applications-permissions) to perform tasks. For example, to run queries, a server to server app must hold the [**Metrics** service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) or a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with the **Metrics** permission. To manage dashboards and alerts, the server to server app might need both roles with permissions and [access](csp_access.html)." %}
+{% include note.html content="A server to server app must hold roles with certain [permissions](csp_permissions_overview.html#tanzu-observability-permissions) to perform tasks. For example, to run queries, a server to server app must hold the [**Metrics** service role](csp_users_roles.html#tanzu-observability-service-roles-built-in) or a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with the **Metrics** permission. To manage dashboards and alerts, the server to server app might need both roles with permissions and [access](csp_access.html)." %}
## What Are Server to Server Apps?
@@ -25,29 +25,29 @@ Server to server apps are used for automating management tasks.
{% include note.html content="You must explicitly grant each server to server app only the role with the permission required for the task that’s being automated (least required privilege). Doing so, you ensure that permissions for server to server app are always very limited." %}
* A server to server app can be used in multiple organizations. The owner of a server to server app is the organization in which it was created.
-{% include important.html content="For each server to server app with access to an Operations for Applications service instance, we create a corresponding **internal service account** in that service instance and add it the **Service Accounts** internal system group. So that, when you configure [the access control security settings](csp_access.html#change-the-access-control-security-setting), [ingestion polices](ingestion_policies.html#step-1-specify-the-scope-and-pps-limit), or [metrics security rules](csp_metrics_security.html), the server to server apps that are assigned with Operations for Applications service roles are represented as service accounts together with the [service accounts](csp_service_accounts.html) created in Operations for Applications."%}
+{% include important.html content="For each server to server app with access to a Tanzu Observability service instance, we create a corresponding **internal service account** in that service instance and add it the **Service Accounts** internal system group. So that, when you configure [the access control security settings](csp_access.html#change-the-access-control-security-setting), [ingestion polices](ingestion_policies.html#step-1-specify-the-scope-and-pps-limit), or [metrics security rules](csp_metrics_security.html), the server to server apps that are assigned with Tanzu Observability service roles are represented as service accounts together with the [service accounts](csp_service_accounts.html) created in Tanzu Observability."%}
## How Server to Server Apps Work
{% include note.html content="To manage server to server apps, you must hold either the VMware Cloud **Organization Owner** role or any other organization role paired with the **Developer** additional role. See [What organization roles are available in VMware Cloud Services](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-C11D3AAC-267C-4F16-A0E3-3EDF286EBE53.html) in the VMware Cloud services documentation." %}
-If you build an application or tool that manages proxies or ingests data, then that tool must authenticate to the Operations for Applications REST API with a VMware Cloud services access token. Here's how it works:
+If you build an application or tool that manages proxies or ingests data, then that tool must authenticate to the Tanzu Observability REST API with a VMware Cloud services access token. Here's how it works:
1. Create a server to server app in VMware Cloud services. See [How to use OAuth 2.0 for server to server apps](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-327AE12A-85DB-474B-89B2-86651DF91C77.html) in the VMware Cloud services documentation.
-1. Assign the server to server app with one or more [Operations for Applications service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance.
+1. Assign the server to server app with one or more [Tanzu Observability service roles](csp_users_roles.html#tanzu-observability-service-roles-built-in) for the service instance.
{% include important.html content="Ensure that you assign the server to server app **only** with the roles and permissions that are needed. Do not assign all roles listed in the VMware Cloud Services Console." %}
- For example, to use a server to server app only for setting up the Operations for Applications integrations, assign only the **Proxies** service role to the app.
+ For example, to use a server to server app only for setting up the Tanzu Observability integrations, assign only the **Proxies** service role to the app.
- If you plan to assign the server to server app a custom role, you must assign that server to server app at least one Operations for Applications service role, for example **Viewer**.
+ If you plan to assign the server to server app a custom role, you must assign that server to server app at least one Tanzu Observability service role, for example **Viewer**.
-1. Optionally, assign the server to server app a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with an [Operations for Applications permission](csp_permissions_overview.html#operations-for-applications-permissions).
+1. Optionally, assign the server to server app a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with an [Tanzu Observability permission](csp_permissions_overview.html#tanzu-observability-permissions).
- {% include important.html content="In a multi-tenant Operations for Applications environment, custom roles apply to **all** service instances (tenants) to which the server to server app has access, that is, for which the server to server app has at least one service role."%}
+ {% include important.html content="In a multi-tenant Tanzu Observability environment, custom roles apply to **all** service instances (tenants) to which the server to server app has access, that is, for which the server to server app has at least one service role."%}
1. Obtain the OAuth 2.0 client credentials of the server to server app and save them to a secure place.
-1. Add the app to your VMware Cloud organization running the Operations for Applications service.
+1. Add the app to your VMware Cloud organization running the Tanzu Observability service.
1. Configure your tool to pass the OAuth 2.0 client credentials to the REST API and exchange them to an access token. See [Make API Calls by Using a Server to Server App](using_wavefront_api.html#make-api-calls-by-using-a-server-to-server-app).
The access token is directly issued to your tool and it authenticates seamlessly to the API.
diff --git a/pages/doc/csp_sign_up_or_log_in.md b/pages/doc/csp_sign_up_or_log_in.md
index e2e24af67..5d9b56e4f 100644
--- a/pages/doc/csp_sign_up_or_log_in.md
+++ b/pages/doc/csp_sign_up_or_log_in.md
@@ -5,20 +5,20 @@ sidebar: doc_sidebar
permalink: csp_sign_up_or_log_in.html
summary: Learn how you can sign up and log in to your service instance if it's onboarded to VMware Cloud services.
---
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform.
+Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform.
-{% include note.html content="After July 3, 2023, we support two types of subscriptions: Operations for Applications subscriptions **onboarded** to VMware Cloud services and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services. We are in the process of incrementally [onboarding](csp_migration.html) original subscriptions to VMware Cloud services. For information about original and VMware Cloud services subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html). "%}
+{% include note.html content="After July 3, 2023, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to VMware Cloud services and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services. We are in the process of incrementally [onboarding](csp_migration.html) original subscriptions to VMware Cloud services. For information about original and VMware Cloud services subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html). "%}
-When your Operations for Applications instance is onboarded to VMware Cloud services, you use a single [VMware Cloud services account](csp_getting_started.html#whats-a-vmware-cloud-services-account) to access your entire VMware Cloud services portfolio across hybrid and native public clouds, including Operations for Applications.
+When your Tanzu Observability instance is onboarded to VMware Cloud services, you use a single [VMware Cloud services account](csp_getting_started.html#whats-a-vmware-cloud-services-account) to access your entire VMware Cloud services portfolio across hybrid and native public clouds, including Tanzu Observability.
Here’s how the signup works:
-1. If you don't belong to the VMware Cloud organization in which the Operations for Applications service instance is running, you can be added to that organization in one the following ways:
+1. If you don't belong to the VMware Cloud organization in which the Tanzu Observability service instance is running, you can be added to that organization in one the following ways:
- A VMware Cloud **Organization Owner** or **Organization Administrator** adds you individually. See [How do I add users to my organization](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-47AA313E-9DAC-447C-B6C8-DF71ED45B0D5.html) in the VMware Cloud services documentation.
- A VMware Cloud **Organization Owner** and **Enterprise Administrator** federate your corporate domain with VMware Cloud services. See [What is enterprise federation and how does it work](https://docs.vmware.com/en/VMware-Cloud-services/services/setting-up-enterprise-federation-cloud-services/GUID-76FAECB3-CFAA-461E-B9C9-2A49C39CD17F.html) in the VMware Cloud services documentation.
2. A VMware Cloud **Organization Owner** or **Organization Administrator** grants you access to the organization's resources with an [organization role](csp_getting_started.html#whats-a-vmware-cloud-organization-role).
-3. A VMware Cloud **Organization Owner** or **Organization Administrator** grants you access to the Operations for Applications service instance with an [Operations for Applications service role](csp_users_roles.html). In addition, they can grant you a custom role with Operations for Application permissions.
+3. A VMware Cloud **Organization Owner** or **Organization Administrator** grants you access to the Tanzu Observability service instance with an [Tanzu Observability service role](csp_users_roles.html). In addition, they can grant you a custom role with Operations for Application permissions.
- In a multi-tenancy environment, you can have different service and custom roles for the different Operations for Applications service instances (tenants).
+ In a multi-tenancy environment, you can have different service and custom roles for the different Tanzu Observability service instances (tenants).
4. After you’ve been added to an organization, you receive an email notification with information about the VMware Cloud organization to which you were added, your organization role, and any other roles. You can now [sign up](#sign-up-with-an-email-invitation) in the VMware Cloud Services Console.
{% include note.html content="The invitation link is valid for seven days."%}
@@ -26,9 +26,9 @@ Here’s how the signup works:
## Sign Up with an Email Invitation
-If you received an email notification with information that you are added to a VMware Cloud organization with Operations for Applications access, follow these steps:
+If you received an email notification with information that you are added to a VMware Cloud organization with Tanzu Observability access, follow these steps:
-1. Click the **VMware Aria Operations for Applications** link in your email notification.
+1. Click the **VMware Tanzu Observability** link in your email notification.
2. Authenticate yourself to VMware Cloud services.
- If your account is not federated, sign in with your VMware account credentials.
@@ -36,8 +36,8 @@ If you received an email notification with information that you are added to a V
- If your account is federated, sign in with your corporate credentials.
{% include note.html content="As a user of a federated account, you must create a VMware account only if you want to file a support ticket or perform billing and subscription-related operations."%}
-3. On the **Organization** tab of the **Services** page, locate the **VMware Aria Operations for Applications** tile from the list of the services available to the organization.
-4. In the **VMware Aria Operations for Applications** tile, click **Launch Service**.
+3. On the **Organization** tab of the **Services** page, locate the **VMware Tanzu Observability** tile from the list of the services available to the organization.
+4. In the **VMware Tanzu Observability** tile, click **Launch Service**.
@@ -52,15 +52,15 @@ From now on, you can log in to your service instance from the [VMware Cloud Serv
## Log In from the VMware Cloud Services Console
-You can log in to the VMware Cloud Services Console and launch your service instance. If you have access to multiple Operations for Applications service instances, you can select the tenant to which you want to log in, because VMware Cloud Services also supports a multi-tenancy login.
+You can log in to the VMware Cloud Services Console and launch your service instance. If you have access to multiple Tanzu Observability service instances, you can select the tenant to which you want to log in, because VMware Cloud Services also supports a multi-tenancy login.
1. In a Web browser, go to [https://console.cloud.vmware.com/](https://console.cloud.vmware.com/).
2. Authenticate yourself.
- If your account is not federated, sign in with your VMware account credentials.
- If your account is federated, sign in with your corporate credentials.
-3. If you belong to multiple organizations, switch to the organization in which the Operations for Applications service instance runs. See [How do I access another one of my organizations](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-432417CF-CE0C-48EB-BEBB-8C27751577D1.html) in the VMware Cloud services documentation.
-4. On the **Organization** tab of the **Services** page, locate the **VMware Aria Operations for Applications** tile from the list of the services available to the organization.
-5. In the **VMware Aria Operations for Applications** tile, click **Launch service**.
+3. If you belong to multiple organizations, switch to the organization in which the Tanzu Observability service instance runs. See [How do I access another one of my organizations](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-432417CF-CE0C-48EB-BEBB-8C27751577D1.html) in the VMware Cloud services documentation.
+4. On the **Organization** tab of the **Services** page, locate the **VMware Tanzu Observability** tile from the list of the services available to the organization.
+5. In the **VMware Tanzu Observability** tile, click **Launch service**.
@@ -69,7 +69,7 @@ You can log in to the VMware Cloud Services Console and launch your service inst
-You are redirected to your Operations for Applications service instance and you're logged in with your VMware Cloud services account.
+You are redirected to your Tanzu Observability service instance and you're logged in with your VMware Cloud services account.
diff --git a/pages/doc/csp_user_management.md b/pages/doc/csp_user_management.md
index efc03d555..4bef0ff07 100644
--- a/pages/doc/csp_user_management.md
+++ b/pages/doc/csp_user_management.md
@@ -1,36 +1,36 @@
---
-title: Manage Users of Operations for Applications on VMware Cloud Services
+title: Manage Users of Tanzu Observability on VMware Cloud Services
keywords: administration
sidebar: doc_sidebar
permalink: csp_user_management.html
-summary: Add and manage users of VMware Aria Operations for Applications on VMware Cloud services.
+summary: Add and manage users of VMware Tanzu Observability on VMware Cloud services.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage User Accounts](user-accounts.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage User Accounts](user-accounts.html)."%}
-VMware Cloud services provides identity access management for the users of your services, including Operations for Applications. For example, see our tutorial [Invite New Users from the VMware Cloud Services Console](csp_new_users_tutorial.html).
+VMware Cloud services provides identity access management for the users of your services, including Tanzu Observability. For example, see our tutorial [Invite New Users from the VMware Cloud Services Console](csp_new_users_tutorial.html).
{% include note.html content="To manage user access to the services in your VMware Cloud organization, you must hold the VMware Cloud **Organization Owner** or **Organization Administrator** role. See [What organization roles are available in VMware Cloud Services](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-C11D3AAC-267C-4F16-A0E3-3EDF286EBE53.html) in the VMware Cloud services documentation."%}
## Adding Users to Your Service Instance
-To add a user to your Operations for Applications service instance, you must assign that user:
+To add a user to your Tanzu Observability service instance, you must assign that user:
1. An [organization role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) for the VMware Cloud organization running the service instance.
{% include note.html content="I you are a VMware Cloud **Organization Administrator**, you can assign only the VMware Cloud **Organization Member** role. Only a VMware Cloud **Organization Owner** can add VMware Cloud **Organization Owners** and VMware Cloud **Organization Administrators**."%}
-1. An [Operations for Applications service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance.
+1. An [Tanzu Observability service role](csp_users_roles.html#tanzu-observability-service-roles-built-in) for the service instance.
You can assign a combination of service roles. For example, if the user that you want to invite will set up integrations, make sure that you assign that user both the **Integrations** and the **Proxies** service roles.
- If you plan to assign that user a custom role, you must assign that user at least the **Viewer** Operations for Applications service role, so that the user can access the service instance.
+ If you plan to assign that user a custom role, you must assign that user at least the **Viewer** Tanzu Observability service role, so that the user can access the service instance.
- {% include important.html content="Make sure that you assign the [**Super Admin** service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) to at least one user of your Operations for Applications service instance. There are some Super Admin tasks that no one else can perform. "%}
+ {% include important.html content="Make sure that you assign the [**Super Admin** service role](csp_users_roles.html#tanzu-observability-service-roles-built-in) to at least one user of your Tanzu Observability service instance. There are some Super Admin tasks that no one else can perform. "%}
-1. Optionally, a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with an [Operations for Applications permission](csp_permissions_overview.html#operations-for-applications-permissions).
+1. Optionally, a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with an [Tanzu Observability permission](csp_permissions_overview.html#tanzu-observability-permissions).
- {% include important.html content="In a multi-tenant Operations for Applications environment, custom roles apply to **all** service instances (tenants) to which the user has access, that is, for which the user has at least one Operations for Applications service role."%}
+ {% include important.html content="In a multi-tenant Tanzu Observability environment, custom roles apply to **all** service instances (tenants) to which the user has access, that is, for which the user has at least one Tanzu Observability service role."%}
You can assign users with these roles in the following ways:
@@ -54,13 +54,13 @@ The newly added users receive an invitation email with an account activation lin
### Editing a User's Roles
-If a user already belongs to the VMware Cloud organization running the service instance, you can edit the user's roles to assign that user with Operations for Applications service or custom roles.
+If a user already belongs to the VMware Cloud organization running the service instance, you can edit the user's roles to assign that user with Tanzu Observability service or custom roles.
For details, see [How do I change user roles](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-A70DBFDC-86FD-4C84-8753-0E55C8C98F8E.html) in the VMware Cloud services documentation.
## Remove a User
-- To remove a user from your service instance, you must remove their [Operations for Applications service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in).
+- To remove a user from your service instance, you must remove their [Tanzu Observability service roles](csp_users_roles.html#tanzu-observability-service-roles-built-in).
- If the roles are individually assigned to the user, edit the user's roles. See [How do I change user roles](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-A70DBFDC-86FD-4C84-8753-0E55C8C98F8E.html) in the VMware Cloud services documentation.
- If the roles are inherited from a group, edit the group and remove that user from the list of members. See [How do I work with groups](hhttps://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-0BD8A07B-C3C0-4220-8CD0-18FA070D3DAD.html) in the VMware Cloud services documentation.
@@ -68,7 +68,7 @@ For details, see [How do I change user roles](https://docs.vmware.com/en/VMware-
## Sign Out a User
-As a user with the [**Super Admin** service role](csp_users_roles.html#operations-for-applications-service-roles-built-in), you can sign out other users by using the [REST API](wavefront_api.html). To sign out a user while you [enabled Super Admin mode](csp_users_account_managing.html#enable-or-disable-super-admin-mode), simply run a POST request with the `logout` API call. For example:
+As a user with the [**Super Admin** service role](csp_users_roles.html#tanzu-observability-service-roles-built-in), you can sign out other users by using the [REST API](wavefront_api.html). To sign out a user while you [enabled Super Admin mode](csp_users_account_managing.html#enable-or-disable-super-admin-mode), simply run a POST request with the `logout` API call. For example:
```
POST https://.wavefront.com/api/logout/{identifier}
diff --git a/pages/doc/csp_users_account_managing.md b/pages/doc/csp_users_account_managing.md
index 5de89a129..60cce83c6 100644
--- a/pages/doc/csp_users_account_managing.md
+++ b/pages/doc/csp_users_account_managing.md
@@ -6,9 +6,9 @@ permalink: csp_users_account_managing.html
summary: Learn how to manage your password and preferences.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Customize Your Account](users_account_managing.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Customize Your Account](users_account_managing.html)."%}
-When your Operations for Applications instance is onboarded to VMware Cloud services, you use a single [VMware Cloud services account](csp_getting_started.html#whats-a-vmware-cloud-services-account) to access your entire VMware Cloud services portfolio across hybrid and native public clouds, including Operations for Applications.
+When your Tanzu Observability instance is onboarded to VMware Cloud services, you use a single [VMware Cloud services account](csp_getting_started.html#whats-a-vmware-cloud-services-account) to access your entire VMware Cloud services portfolio across hybrid and native public clouds, including Tanzu Observability.
## Manage Your Password
@@ -18,7 +18,7 @@ It's a best practice to change your password every few months. See [How do I res
## Configure Your Preferences
-In your user profile page in Operations for Applications, you can configure several preferences, for example, select our light theme or chart title size.
+In your user profile page in Tanzu Observability, you can configure several preferences, for example, select our light theme or chart title size.
1. Log in to your service instance.
1. From the gear icon on the toolbar, select your user name.
1. On the **User Information** page, make the necessary changes.
@@ -26,7 +26,7 @@ In your user profile page in Operations for Applications, you can configure seve
{% include note.html content="Some preferences, managed by the users with the **Super Admin** service role, are preset for all users of the service instance." %}
In your user profile page in the VMware Cloud Services Console, you can configure several preferences, such as language and regional format, dark or light theme, motion reduction, and What's New banner appearance.
-1. In the Operations for Applications UI or in the VMware Cloud Services Console, click your user name on the menu bar and select **My Account**.
+1. In the Tanzu Observability UI or in the VMware Cloud Services Console, click your user name on the menu bar and select **My Account**.
1. On the **Preferences** tab, in the corresponding panel for language, appearance, accessibility, etc., click **Edit**.
1. Make the necessary changes and click **Save**.
@@ -69,7 +69,7 @@ If you hold the [**Super Admin** service role](csp_users_roles.html#operations-f
As a result:
-
When the Super Admin mode is enabled, you have full administrative privileges for the Operations for Applications service. See the Super Admin service role for details.
+
When the Super Admin mode is enabled, you have full administrative privileges for the Tanzu Observability service. See the Super Admin service role for details.
When the Super Admin mode is disabled, you have only the permissions from your other roles if any.
@@ -80,9 +80,9 @@ If you hold the [**Super Admin** service role](csp_users_roles.html#operations-f
## Generate an API Token
-Operations for Applications allows users to interact with the service instance using the [REST API](wavefront_api.html).
+Tanzu Observability allows users to interact with the service instance using the [REST API](wavefront_api.html).
-Before you can invoke the Operations for Applications API using `curl` or from an API client, you must have a VMware Cloud services access token with the relevant organization and service access. To obtain an access token, you must first generate a VMware Cloud services API token with relevant roles, and then exchange that API token for an access token.
+Before you can invoke the Tanzu Observability API using `curl` or from an API client, you must have a VMware Cloud services access token with the relevant organization and service access. To obtain an access token, you must first generate a VMware Cloud services API token with relevant roles, and then exchange that API token for an access token.
You [manage your VMware Cloud services API tokens](csp_api_tokens.html#manage-the-vmware-cloud-services-api-tokens-for-your-user-account) in the VMware Cloud Services Console.
diff --git a/pages/doc/csp_users_roles.md b/pages/doc/csp_users_roles.md
index 2e70d3304..5fba4575d 100644
--- a/pages/doc/csp_users_roles.md
+++ b/pages/doc/csp_users_roles.md
@@ -4,19 +4,19 @@ keywords: administration
tags: [administration]
sidebar: doc_sidebar
permalink: csp_users_roles.html
-summary: Manage Operations for Applications permissions with roles.
+summary: Manage Tanzu Observability permissions with roles.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage Roles, Groups, and Permissions](users_roles.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage Roles, Groups, and Permissions](users_roles.html)."%}
-VMware Cloud services supports roles to manage authorization in your services on the platform, including VMware Aria Operations for Applications.
+VMware Cloud services supports roles to manage authorization in your services on the platform, including Tanzu Observability.
From the VMware Cloud Services Console, users with the VMware Cloud **Organization Owner** or **Organization Administrator** role can:
* Create **groups** and add new and existing users to each group.
-* Create **custom roles** and assign Operations for Applications permissions to each role.
+* Create **custom roles** and assign Tanzu Observability permissions to each role.
* Assign one or more **service roles** and **custom roles** to each group. It's also possible to assign roles to individual users and server to server apps.
-In addition to the roles model, Operations for Applications also supports [access control for individual objects](csp_access.html), for example, users with the **Super Admin** service role can limit access to a sensitive dashboard.
+In addition to the roles model, Tanzu Observability also supports [access control for individual objects](csp_access.html), for example, users with the **Super Admin** service role can limit access to a sensitive dashboard.
## Manage Roles
@@ -24,13 +24,13 @@ The roles model allows you to make sure nobody can perform tasks without the cor
Assigning roles to groups of users is most efficient and least error prone. It's possible to assign a role to an individual account -- that might make sense during a POC.
-VMware Cloud services includes built-in **service roles** for each service on the platform, including Operations for Applications service roles. Additionally, VMware Cloud services supports **custom roles**.
+VMware Cloud services includes built-in **service roles** for each service on the platform, including Tanzu Observability service roles. Additionally, VMware Cloud services supports **custom roles**.
- A role can be assigned for a certain time period or without an expiration date.
-- At least one Operations for Applications service role is required for a user to have access to the Operations for Applications service instance. Custom roles are optional.
-- In a multi-tenant environment, a user can have different service roles for the different Operations for Applications service instances (tenants). Custom roles apply to **all** tenants for which the user has a service role.
+- At least one Tanzu Observability service role is required for a user to have access to the Tanzu Observability service instance. Custom roles are optional.
+- In a multi-tenant environment, a user can have different service roles for the different Tanzu Observability service instances (tenants). Custom roles apply to **all** tenants for which the user has a service role.
- {% include note.html content="When you invite new users in a multi-tenant environment, make sure that you assign them the roles they need for each Operations for Applications service instance (tenant). For information on how to do this, see [Invite New Users from the VMware Cloud Services Console](csp_new_users_tutorial.html)."%}
+ {% include note.html content="When you invite new users in a multi-tenant environment, make sure that you assign them the roles they need for each Tanzu Observability service instance (tenant). For information on how to do this, see [Invite New Users from the VMware Cloud Services Console](csp_new_users_tutorial.html)."%}
The VMware Cloud Services Console **Roles** page lists all service roles and custom roles in your VMware Cloud organization. To navigate to this page:
@@ -38,10 +38,10 @@ The VMware Cloud Services Console **Roles** page lists all service roles and cus
1. If necessary, switch to the target organization. See [How do I access another one of my Organizations](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-432417CF-CE0C-48EB-BEBB-8C27751577D1.html).
1. In the left navigation pane, select **Identity & Access Management** > **Roles**.
-### Operations for Applications Service Roles (Built-in)
+### Tanzu Observability Service Roles (Built-in)
-The VMware Cloud Services Console **Roles** page includes the following built-in Operations for Applications service roles:
-- A corresponding Operations for Applications service role for each [Operations for Applications permission](csp_permissions_overview.html#operations-for-applications-permissions), that is, each of the following service roles has only one permission assigned:
+The VMware Cloud Services Console **Roles** page includes the following built-in Tanzu Observability service roles:
+- A corresponding Tanzu Observability service role for each [Tanzu Observability permission](csp_permissions_overview.html#operations-for-applications-permissions), that is, each of the following service roles has only one permission assigned:
* **Admin**
* **Alerts**
@@ -59,7 +59,7 @@ The VMware Cloud Services Console **Roles** page includes the following built-in
* **Metrics**
* **Proxies**
* **Sources**
-- Two special Operations for Applications service roles - one that grants full administrative access to the service, and another one that grants read-only access to the service:
+- Two special Tanzu Observability service roles - one that grants full administrative access to the service, and another one that grants read-only access to the service:
@@ -69,7 +69,7 @@ The VMware Cloud Services Console **Roles** page includes the following built-in
Tip: Assign the Viewer service role individually or in combination with custom roles.
@@ -87,14 +87,14 @@ The VMware Cloud Services Console **Roles** page includes the following built-in
### Create, Edit, or Delete a Custom Role
-Custom roles let you combine service permissions of your choice, for example, [Operations for Applications permissions](csp_permissions_overview.html#operations-for-applications-permissions). A custom role can have permissions for one or multiple services in your organization. For example, you can have a custom role that grants administrative permissions for one service and read-only permissions for another service.
+Custom roles let you combine service permissions of your choice, for example, [Tanzu Observability permissions](csp_permissions_overview.html#operations-for-applications-permissions). A custom role can have permissions for one or multiple services in your organization. For example, you can have a custom role that grants administrative permissions for one service and read-only permissions for another service.
-{% include important.html content="The Operations for Applications permissions in a custom role apply to **all** Operations for Applications service instances to which the target user account or server to server app has access. Therefore, to obtain the Operations for Applications permissions from a custom role for a given Operations for Applications service instance, the user account or server to server app assigned with that custom role must have at least one Operations to Applications service role for that service instance, for example, the **Viewer** service role."%}
+{% include important.html content="The Tanzu Observability permissions in a custom role apply to **all** Tanzu Observability service instances to which the target user account or server to server app has access. Therefore, to obtain the Tanzu Observability permissions from a custom role for a given Tanzu Observability service instance, the user account or server to server app assigned with that custom role must have at least one Operations to Applications service role for that service instance, for example, the **Viewer** service role."%}
To create a custom role:
1. On the VMware Cloud Services Console **Roles** page, click **Add Role**.
-1. On the **Add permissions** tab, in the left panel, expand **VMware Aria Operations for Applications**.
+1. On the **Add permissions** tab, in the left panel, expand **VMware Tanzu Observability**.
1. In the panel on the right, select the permissions that you want to assign to the role, and click **Continue**.
1. On the **Role information** tab, enter a meaningful role name and description, and click **Continue**.
1. On the **Review added permission** tab, verify your selections and click **Save**.
@@ -119,7 +119,7 @@ For efficient user management, you can create groups of users and assign roles t
See [How do I work with groups](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-0BD8A07B-C3C0-4220-8CD0-18FA070D3DAD.html) in the VMware Cloud services documentation.
-{% include note.html content="Operations for Applications includes an internal **Everyone** system group, where any new user account is added automatically. This group doesn't have any roles and permissions. This group can be used when managing [access to dashboards and alerts](csp_access.html), [metrics security policy rules](csp_metrics_security.html), and [ingestion policies](ingestion_policies.html)."%}
+{% include note.html content="Tanzu Observability includes an internal **Everyone** system group, where any new user account is added automatically. This group doesn't have any roles and permissions. This group can be used when managing [access to dashboards and alerts](csp_access.html), [metrics security policy rules](csp_metrics_security.html), and [ingestion policies](ingestion_policies.html)."%}
## Grant or Revoke a User's Role Explicitly
diff --git a/pages/doc/permissions_overview.md b/pages/doc/permissions_overview.md
index 1cf6937d2..782af4aae 100644
--- a/pages/doc/permissions_overview.md
+++ b/pages/doc/permissions_overview.md
@@ -7,9 +7,9 @@ permalink: permissions_overview.html
summary: Learn about the permissions in the service.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Operations for Applications permissions in VMware Cloud services](csp_permissions_overview.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Tanzu Observability permissions in VMware Cloud services](csp_permissions_overview.html)."%}
-Permissions allow access control for the feature sets in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront). [Super Admin users](authorization-faq.html#who-is-the-super-admin-user) and users with the **Accounts** permission can manage permissions for groups and accounts.
+Permissions allow access control for the feature sets in Tanzu Observability. [Super Admin users](authorization-faq.html#who-is-the-super-admin-user) and users with the **Accounts** permission can manage permissions for groups and accounts.
{% include note.html content="Every user can [perform certain tasks](user-accounts.html#what-can-a-new-user-do). However, you must have the appropriate permission to manage objects. If you do not have permission, UI menu selections and buttons required to perform management tasks are not visible." %}
@@ -36,11 +36,11 @@ The following list gives an overview of permissions. To learn more, click the li
- **Batch Query Priority**
- When an account with the **Batch Query Priority** permission runs queries, Operations for Applications treats every query executed by that account as if it was wrapped in the [`bestEffort()` function](ts_bestEffort.html).
+ When an account with the **Batch Query Priority** permission runs queries, Tanzu Observability treats every query executed by that account as if it was wrapped in the [`bestEffort()` function](ts_bestEffort.html).
- **[Chart Embedding](ui_sharing.html#embed-a-chart-in-other-uis)**
- Users with the **Chart Embedding** permission can generate HTML snippets of charts in Operations for Applications and embed a corresponding interactive chart outside of Operations for Applications. Embedded chart URLs are associated with a specific user account. If a user embeds a chart and later that user's account is removed, the embedded chart no longer works.
+ Users with the **Chart Embedding** permission can generate HTML snippets of charts in Tanzu Observability and embed a corresponding interactive chart outside of Tanzu Observability. Embedded chart URLs are associated with a specific user account. If a user embeds a chart and later that user's account is removed, the embedded chart no longer works.
- **[Dashboards](ui_dashboards.html)**
@@ -54,7 +54,7 @@ The following list gives an overview of permissions. To learn more, click the li
- **[Direct Data Ingestion](direct_ingestion.html)**
- An account with the **Direct Data Ingestion** permission can directly ingest metrics using the REST API or one of the SDKs, bypassing the proxy. Grant this permission only to users who have a deep understanding of APIs and the Operations for Applications ingestion path.
+ An account with the **Direct Data Ingestion** permission can directly ingest metrics using the REST API or one of the SDKs, bypassing the proxy. Grant this permission only to users who have a deep understanding of APIs and the Tanzu Observability ingestion path.
- **[Events](events.html)**
@@ -74,7 +74,7 @@ The following list gives an overview of permissions. To learn more, click the li
- **[Logs](logging_overview.html)**
- {% include important.html content="Logs is enabled only for selected customers. To participate, contact your Operations for Applications account representative."%}
+ {% include important.html content="Logs is enabled only for selected customers. To participate, contact your Tanzu Observability account representative."%}
Users with the **Logs** permission can view the Logs Browser and drill into logs from charts, alerts, and traces.
diff --git a/pages/doc/security_policy.md b/pages/doc/security_policy.md
index 3ce6d3cf8..68f679a03 100644
--- a/pages/doc/security_policy.md
+++ b/pages/doc/security_policy.md
@@ -7,9 +7,9 @@ permalink: security_policy.html
summary: Use security policies to control access to metrics, such as time series, histograms, RED metrics, and delta counters, as well as traces.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Metrics Security Policy Rules in Operations for Applications on VMware Cloud Services](csp_metrics_security.html)."%}
+{% include note.html content="Starting July 3, 2023, VVMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Metrics Security Policy Rules in Tanzu Observability on VMware Cloud Services](csp_metrics_security.html)."%}
-You can create security policies on VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) to protect your metrics and traces security data.
+You can create security policies in Tanzu Observability to protect your metrics and traces security data.
@@ -197,7 +197,7 @@ Data protected by a metrics security policy rule can become invisible to users.
### Alert Notifications
-To protect metrics or RED metrics from inclusion in alert notifications, use the **Secure Metrics Details** check box. Operations for Applications looks at all metrics when determining when an alert status should change and shows them in alert notifications. When the check box is selected, [details are not shown](alerts_notifications.html#alert-notification-with-secured-metrics-details) in the notification.
+To protect metrics or RED metrics from inclusion in alert notifications, use the **Secure Metrics Details** check box. Tanzu Observability looks at all metrics when determining when an alert status should change and shows them in alert notifications. When the check box is selected, [details are not shown](alerts_notifications.html#alert-notification-with-secured-metrics-details) in the notification.
### Derived Metrics and Events
diff --git a/pages/doc/users_account_managing.md b/pages/doc/users_account_managing.md
index 15b227736..a819aa7ab 100644
--- a/pages/doc/users_account_managing.md
+++ b/pages/doc/users_account_managing.md
@@ -5,9 +5,9 @@ sidebar: doc_sidebar
permalink: users_account_managing.html
summary: Learn how to manage your passwords and preferences.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Manage Your VMware Cloud Services Account](csp_users_account_managing.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For VMware Cloud services subscriptions, see [Manage Your VMware Cloud Services Account](csp_users_account_managing.html)."%}
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports administrator-level customization for all users of an instance, and user-level customization, discussed on this page.
+Tanzu Observability supports administrator-level customization for all users of an instance, and user-level customization, discussed on this page.
You manage your account from the gear icon in the top right corner. From there, all users can manage passwords and configure preferences. Users in a [multi-tenant environment](authentication.html#multi-tenant-authentication) who have been invited to more than one tenant can also switch tenants from the gear icon.
@@ -115,7 +115,7 @@ If you are a Super Admin user for the Wavefront service, you can temporarily ena
## Generate an API Token
-VMware Aria Operations for Applications allows [user accounts](user-accounts.html) and [service accounts](service-accounts.html) to interact with the product instance using the [REST API](wavefront_api.html).
+Tanzu Observability allows [user accounts](user-accounts.html) and [service accounts](service-accounts.html) to interact with the product instance using the [REST API](wavefront_api.html).
{% include tip.html content="You generate API tokens for your user account explicitly. For service accounts, a user with the **Accounts** permission can generate tokens from the **Service Accounts** page." %}
diff --git a/pages/doc/users_roles.md b/pages/doc/users_roles.md
index a8d06420a..16410af39 100644
--- a/pages/doc/users_roles.md
+++ b/pages/doc/users_roles.md
@@ -7,18 +7,18 @@ permalink: users_roles.html
summary: Manage global permissions with roles.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Manage Roles and Groups in VMware Cloud Services](csp_users_roles.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscriptions. For VMware Cloud services subscriptions, see [Manage Roles and Groups in VMware Cloud Services](csp_users_roles.html)."%}
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports roles to fine-tune authorization in the Wavefront environment.
+Tanzu Observability supports roles to fine-tune authorization in the Wavefront environment.
Users with the **Accounts** permission can:
1. Create one or more **roles** and assign one or more [permissions](permissions_overview.html) to each role.
2. Create one or more **groups** and add one or more accounts to each group. Accounts can be user accounts or service accounts.
3. Assign one or more roles to each group. It's also possible to assign a role to individual users.
-In addition to the global roles and permissions model, Operations for Applications also supports [access control for individual objects](access.html), for example, users with the **Accounts** permission can limit access to a sensitive dashboard.
+In addition to the global roles and permissions model, Tanzu Observability also supports [access control for individual objects](access.html), for example, users with the **Accounts** permission can limit access to a sensitive dashboard.
-{% include note.html content="You must have the **Accounts** permission to view and manage authorization in your Operations for Applications environment. If you don't have the permission, the corresponding UI menu selections, buttons, and links are not visible." %}
+{% include note.html content="You must have the **Accounts** permission to view and manage authorization in your Tanzu Observability environment. If you don't have the permission, the corresponding UI menu selections, buttons, and links are not visible." %}
## Manage Roles and Permissions
diff --git a/pages/doc/wavefront_administer.md b/pages/doc/wavefront_administer.md
index 5063b7c6d..f33d4688a 100644
--- a/pages/doc/wavefront_administer.md
+++ b/pages/doc/wavefront_administer.md
@@ -7,14 +7,14 @@ permalink: wavefront_administer.html
summary: Understand what you can do if you have administrative privileges.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For information about VMware Cloud services subscriptions and original subscriptions and how they differ, see [Subscription Types](subscriptions-differences.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for **original** subscribers. For information about VMware Cloud services subscriptions and original subscriptions and how they differ, see [Subscription Types](subscriptions-differences.html)."%}
-In VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront), Super Admin users and users with the **Accounts** permission can perform a variety of tasks, such as:
+In Tanzu Observability, Super Admin users and users with the **Accounts** permission can perform a variety of tasks, such as:
-* Manage the authorization and access to the Operations for Applications environment.
-* Select the authentication model in the Operations for Applications environment, for example, by setting up SSO using an identity provider (IdP).
-* Monitor and troubleshoot the Operations for Applications environment and usage.
-* Purchase initial and additional Operations for Applications capacity by using the self-service workflows in the UI.
+* Manage the authorization and access to the Tanzu Observability environment.
+* Select the authentication model in the Tanzu Observability environment, for example, by setting up SSO using an identity provider (IdP).
+* Monitor and troubleshoot the Tanzu Observability environment and usage.
+* Purchase initial and additional Tanzu Observability capacity by using the self-service workflows in the UI.
## Authorization
@@ -34,7 +34,7 @@ You can select your preferred authentication method for your environment by sett
## Monitor and Troubleshoot
-You can use the Operations for Applications Usage integration dashboards to monitor and troubleshoot your environment. By using the dashboards in this integration, you can:
+You can use the Tanzu Observability Usage integration dashboards to monitor and troubleshoot your environment. By using the dashboards in this integration, you can:
* Get usage information for your service instance and Wavefront proxy.
* Drill down into the metrics namespaces to discover trends.
From 09da6adba11402819a18141f5dea929321d7de41 Mon Sep 17 00:00:00 2001
From: shavidissa
Date: Fri, 15 Mar 2024 13:03:13 -0700
Subject: [PATCH 06/26] rename the about section
---
pages/doc/tobs_faq.md | 16 ++++++++--------
pages/doc/wavefront_introduction.md | 10 +++++-----
2 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/pages/doc/tobs_faq.md b/pages/doc/tobs_faq.md
index a34a87e1c..95b25ce2e 100644
--- a/pages/doc/tobs_faq.md
+++ b/pages/doc/tobs_faq.md
@@ -4,7 +4,7 @@ keywords: alerts
tags: [getting started]
sidebar: doc_sidebar
permalink: tobs_faq.html
-summary: Get answers to the top frequently asked questions for VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Get answers to the top frequently asked questions for Tanzu Observability (formerly known as VMware Aria Operations for Applications) .
---
## Do You Have Tutorials?
@@ -14,8 +14,8 @@ Yes!
- Detailed step-by-step instructions for ingesting data from AWS
- Links to next steps
* The [Windows Host Integration Tutorial](windows_host_tutorial.html) has:
- - Detailed step-by-step instructions for ingesting data from a Windows host machine, when your Operations for Applications service **is onboarded** to VMware Cloud services.
- - A video about ingesting data from a Windows machine when your Operations for Applications service is **not onboarded** to VMware Cloud services.
+ - Detailed step-by-step instructions for ingesting data from a Windows host machine, when your Tanzu Observability service **is onboarded** to VMware Cloud services.
+ - A video about ingesting data from a Windows machine when your Tanzu Observability service is **not onboarded** to VMware Cloud services.
* The [Explore Data Tutorial](tutorial_dashboards.html) gives step-by-step instructions for exploring a sample dashboard. You don't need special permissions follow these steps.
* The [Query Language Tutorial](query_language_getting_started.html) explores the anatomy of a query, includes a few videos, and includes hands-on practice.
* The [Alerts Browser Tutorial](alerts.html#alerts-browser-tutorial) and the [Create Alerts Tutorial](alerts_manage.html#create-alert-tutorial) get you started with alerts.
@@ -40,7 +40,7 @@ See [REST API](wavefront_api.html) for details on finding the API token and more
-
VMware Aria Operations for Applications has more than 250 integrations. Click [here](label_integrations%20list.html) for the full list of integrations.
+
Tanzu Observability has more than 250 integrations. Click [here](label_integrations%20list.html) for the full list of integrations.
Most of the documentation of the integrations comes from the code and is generated by a script. For best practices and details about some of our integrations, expand Integrations in the TOC on the left and click Integration Details.
@@ -53,7 +53,7 @@ By default, all users can view dashboards and alerts. They can also edit dashboa
Action
1. Check your permissions. See:
- * [Examine Groups, Roles, and Permissions in Operations for Applications](users_account_managing.html#examine-groups-roles-and-permissions) -- Applicable for original subscribers.
+ * [Examine Groups, Roles, and Permissions in Tanzu Observability](users_account_managing.html#examine-groups-roles-and-permissions) -- Applicable for original subscribers.
* [Examine Your Groups, Roles, and Permissions in VMware Cloud services](csp_users_account_managing.html#examine-your-groups-roles-and-permissions) -- Applicable for new subscribers.
2. If you don't have the permissions you need, ask a user with the proper administration permissions or to grant you the permissions.
3. If that doesn't solve the problem, the individual dashboard or alert you're trying to edit might be protected by access control. The creator of the alert or dashboard or a Super Admin user can grant access.
@@ -64,16 +64,16 @@ PPS and Overage determine what a customer is billed:
* **PPS** -- Or Points per Second, means data points ingested per second to the service. All customers are billed based on their PPS.
* **Overage** -- Many of our customers have a contract that specifies a certain PPS for a certain amount of time. If the customer exceeds that PPS, the customer is billed for overage.
-Because the service runs on AWS, we have to bill based on how much data is ingested. However, we're interested in helping you lower your bill and get more out of VMware Aria Operations for Applications. We encourage you to find out:
+Because the service runs on AWS, we have to bill based on how much data is ingested. However, we're interested in helping you lower your bill and get more out of Tanzu Observability. We encourage you to find out:
* Are there dashboards or alerts that ingest data but that are never used?
* Are your queries looking at too much data, that is, could you filter as part of the query?
Start with [Improve PPS Usage and Prevent Overage](wavefront_usage_info.html) and learn how to examine your data and how to improve PPS.
-## Why Is VMware Aria Operations for Applications So Slow?
+## Why Is Tanzu Observability So Slow?
-VMware Aria Operations for Applications can handle a lot of data, but sometimes you need it faster!
+Tanzu Observability can handle a lot of data, but sometimes you need it faster!
Action
diff --git a/pages/doc/wavefront_introduction.md b/pages/doc/wavefront_introduction.md
index 31ceb3f1c..96632d849 100644
--- a/pages/doc/wavefront_introduction.md
+++ b/pages/doc/wavefront_introduction.md
@@ -5,13 +5,13 @@ sidebar: doc_sidebar
permalink: wavefront_introduction.html
summary: Learn about the architecture, interfaces, and how to get started.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) is a high-performance streaming analytics platform that supports observability for metrics, counters, histograms, and traces/spans. The product is unique because it scales to very high data ingestion rates and query loads. You can collect data from many services and sources across your entire application stack, and can look at details for earlier data that were ingested earlier.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a high-performance streaming analytics platform that supports observability for metrics, counters, histograms, and traces/spans. The product is unique because it scales to very high data ingestion rates and query loads. You can collect data from many services and sources across your entire application stack, and can look at details for earlier data that were ingested earlier.
## Where Do I Start?
You can [sign up for a free trial](start_trial.html) and try out our service.
-Starting July 3, 2023, Operations for Applications is a service on the [VMware Cloud services platform](https://console.cloud.vmware.com/). After this date, we support two types of subscriptions: Operations for Applications subscriptions **onboarded** to the VMware Cloud services platform and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until [onboarded](csp_migration.html) to VMware Cloud services. For information about the subscription types and how they differ, see [Subscription Types](subscriptions-differences.html).
+Starting July 3, 2023, Tanzu Observability is a service on the [VMware Cloud services platform](https://console.cloud.vmware.com/). After this date, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to the VMware Cloud services platform and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until [onboarded](csp_migration.html) to VMware Cloud services. For information about the subscription types and how they differ, see [Subscription Types](subscriptions-differences.html).
After your free trial expires, you can [upgrade and purchase our service](upgrade_and_purchase.html).
@@ -94,7 +94,7 @@ After you've set up an alert with that information, we'll send alert notificatio
We support [over 200 integrations](label_integrations%20list.html) including cloud providers, DevOps tools, big data, and more.
-To interact with our service, you can use our rich Graphical User Interface, which includes many pre-built system dashboards, charts, and alerts. You can also use SDKs available on our [GitHub page](https://github.com/wavefrontHQ), the Operations for Applications REST API, and CLIs.
+To interact with our service, you can use our rich Graphical User Interface, which includes many pre-built system dashboards, charts, and alerts. You can also use SDKs available on our [GitHub page](https://github.com/wavefrontHQ), the Tanzu Observability REST API, and CLIs.
In addition, tight integrations with Spring Boot, Kubernetes, and Tanzu Mission Control are available.
@@ -135,7 +135,7 @@ It's easy to monitor any of the clusters:
## How Do I Set Up a Data Ingestion Pipeline?
-You can use VMware Aria Operations for Applications with time-series (metric) data, and also with traces and spans, and with histograms from diverse sources.
+You can use Tanzu Observability with time-series (metric) data, and also with traces and spans, and with histograms from diverse sources.
* **Cloud:** Perform minimal setup to let the service access the data in your cloud environment. The result is direct ingestion of cloud services data such as Amazon Web Services or Google Cloud Platform.
* **Integrations:** For other data sources, we support [over 200 integrations](label_integrations%20list.html). You modify a simple configuration file and you’re good to go.
* **Start Where You Are:** If your environment already has a metrics infrastructure, you can do some pre-processing on the data so that it corresponds to our data format, and send them directly to the Wavefront proxy.
@@ -173,4 +173,4 @@ Our service runs the metrics collection engine. The service runs in the cloud an
* The proxy can also ingest metrics from your log files. See [Log Data Metrics Integration](integrations_log_data.html)
-
+
From 97f3af4ebde4eb6616d7d36d1aabc0f05fd0f73b Mon Sep 17 00:00:00 2001
From: shavidissa
Date: Mon, 18 Mar 2024 12:05:52 -0700
Subject: [PATCH 07/26] updatet the Quickstart and Tutorials
---
pages/doc/csp_invite-AoA-users_tutorial.md | 54 ++++++++++-----------
pages/doc/documentation_getting_started.md | 20 ++++----
pages/doc/hello_wavefront_aws_tutorial.md | 10 ++--
pages/doc/query_language_getting_started.md | 2 +-
pages/doc/query_language_reference.md | 2 +-
pages/doc/tutorial_dashboards.md | 2 +-
pages/doc/ui_chart_reference.md | 2 +-
pages/doc/videos.md | 8 ++-
pages/doc/windows_host_tutorial.md | 22 ++++-----
9 files changed, 60 insertions(+), 62 deletions(-)
diff --git a/pages/doc/csp_invite-AoA-users_tutorial.md b/pages/doc/csp_invite-AoA-users_tutorial.md
index 95a80c7b5..24f03138f 100644
--- a/pages/doc/csp_invite-AoA-users_tutorial.md
+++ b/pages/doc/csp_invite-AoA-users_tutorial.md
@@ -4,20 +4,20 @@ keywords:
tags: [tutorials]
sidebar: doc_sidebar
permalink: csp_new_users_tutorial.html
-summary: Learn how to invite new users to VMware Aria Operations for Applications through the VMware Cloud Services Console.
+summary: Learn how to invite new users to Tanzu Observability (formerly known as VMware Aria Operations for Applications) through the VMware Cloud Services Console.
---
-Starting July 3, 2023, Operations for Applications is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions:
-* Operations for Applications subscriptions **onboarded** to the VMware Cloud services platform.
+Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions:
+* Tanzu Observability subscriptions **onboarded** to the VMware Cloud services platform.
* **Original** subscriptions -- the existing ones which remain as is until they migrate to VMware Cloud services.
-In this tutorial, you’ll learn how to invite new users to Operations for Applications through the VMware Cloud Services Console.
+In this tutorial, you’ll learn how to invite new users to Tanzu Observability through the VMware Cloud Services Console.
## Requirements
When your service **is onboarded** to VMware Cloud services, all new users are invited through the VMware Cloud Services Console.
-To invite users, you must have the VMware Cloud **Organization Owner** or **Organization Administrator** role. You can invite users to your organization and grant them access to the services associated with it - in this case, this is Operations for Applications. You can also track the invitations you send. Invitations are valid for up to seven days. If you have sent an invitation in error, you can revoke it.
+To invite users, you must have the VMware Cloud **Organization Owner** or **Organization Administrator** role. You can invite users to your organization and grant them access to the services associated with it - in this case, this is Tanzu Observability. You can also track the invitations you send. Invitations are valid for up to seven days. If you have sent an invitation in error, you can revoke it.
## Roles to Assign
@@ -28,7 +28,7 @@ When you invite new users, you must assign them:
Note that you can assign the **Organization Owner** role to another user only if you have the **Organization Owner** role.
-* A role within the Operations for Applications service instance.
+* A role within the Tanzu Observability service instance.
Optionally, you can also assign a custom role created in the VMware Cloud organization. Custom roles are composed of different service permissions.
@@ -42,10 +42,10 @@ Optionally, you can also assign a custom role created in the VMware Cloud organi
### Step 2: Navigate to Your Organization
-VMware Cloud uses organizations to provide controlled access to one or more services. As an enterprise using multiple cloud services, Organizations provide an easy way to map your business groups and processes to different organizations. If you belong to more organizations, you must navigate to the organization to which Operations for Applications is onboarded.
+VMware Cloud uses organizations to provide controlled access to one or more services. As an enterprise using multiple cloud services, Organizations provide an easy way to map your business groups and processes to different organizations. If you belong to more organizations, you must navigate to the organization to which Tanzu Observability is onboarded.
1. Click your username and click **Change Organization**.
-2. Select the name of the organization to which Operations for Applications is **onboarded**.
+2. Select the name of the organization to which Tanzu Observability is **onboarded**.
### Step 3: Find Your Roles Within the Organization
@@ -56,12 +56,12 @@ If do not have the VMware Cloud **Organization Owner** or **Organization Adminis
## Invite a New User and Assign Service Roles Only
-We provide a number of built-in Operations for Applications service roles.
+We provide a number of built-in Tanzu Observability service roles.
- A corresponding service role for each [permission](csp_permissions_overview.html#operations-for-applications-permissions).
- Two special service roles - one that grants full administrative access to the service, and another one that grants read-only access to the service.
-For more information, see [Operations for Applications Service Roles (Built-in)](csp_users_roles.html#operations-for-applications-service-roles-built-in).
+For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#operations-for-applications-service-roles-built-in).
### Step 1: Enter the New User Details
@@ -73,7 +73,7 @@ For more information, see [Operations for Applications Service Roles (Built-in)]
### Step 2: Assign Roles and Invite the User
-In a multi-tenant environment, you can assign different service roles for each Operations for Applications instance. Let's first assign the mandatory organization role and then we will assign different service roles for two Operations for Applications instances.
+In a multi-tenant environment, you can assign different service roles for each Tanzu Observability instance. Let's first assign the mandatory organization role and then we will assign different service roles for two Tanzu Observability instances.
1. Select a mandatory organization role to assign.
@@ -83,12 +83,12 @@ In a multi-tenant environment, you can assign different service roles for each O
-2. Assign Operations for Applications service roles for the first Operations for Applications instance.
+2. Assign Tanzu Observability service roles for the first Tanzu Observability instance.
1. Click **Add a Service**.
- 1. From the drop-down menu, select **VMware Aria Operations for Applications**.
- 
+ 1. From the drop-down menu, select **Tanzu Observability**.
+ 
1. From the **in** drop-down menu, select the service instance to which you want to invite the new user.
- 
+ 
1. Assign the service roles to the user.
Let's say that the user you're inviting will:
@@ -100,17 +100,17 @@ In a multi-tenant environment, you can assign different service roles for each O
For this purpose, select the following service roles: **Proxies**, **Integrations**, **Dashboards**, and **Alerts**.
- 
+ 
1. Leave the never expires access field as is.
-3. Assign the **Super Admin** service role for another Operations for Applications instance.
+3. Assign the **Super Admin** service role for another Tanzu Observability instance.
1. Click **+ Add an Instance**.
1. From the **in** drop-down menu, select the other service instance to which you want to invite the new user.
- 
+ 
1. Assign the **Super Admin** service role to the user.
- 
+ 
1. Leave the never expires access field as is.
4. Leave the **Send emails to all invited users notifying them of this role assignment** selected and click **Add**.
@@ -124,7 +124,7 @@ If you have created custom roles and want to assign custom roles to a user, you
* At least one service role, for example **Viewer**
* The custom roles of interest
-Custom roles work only in combination with service roles. The Operations for Applications permissions in a custom role apply to all service instances (tenants) for which the user has at least one Operations for Applications service role.
+Custom roles work only in combination with service roles. The Tanzu Observability permissions in a custom role apply to all service instances (tenants) for which the user has at least one Tanzu Observability service role.
### Step 1: Enter the New User Details
@@ -142,23 +142,23 @@ Let's assign **Organization Administrator** as a mandatory organization role, th
-2. Assign the **Viewer** service role for a specific Operations for Applications service instance.
+2. Assign the **Viewer** service role for a specific Tanzu Observability service instance.
1. Click **Add a Service**.
- 1. From the drop-down menu, select **VMware Aria Operations for Applications**.
- 
+ 1. From the drop-down menu, select **Tanzu Observability**.
+ 
1. From the **in** drop-down menu, select the service instance to which you want to invite the new user and leave the **Viewer** service role selected so that you assign it to the user.
- 
+ 
1. Leave the never expires access field as is.
-3. Assign the **Ingestion Policies** service role for another Operations for Applications service instance.
+3. Assign the **Ingestion Policies** service role for another Tanzu Observability service instance.
1. Click **+Add an Instance**.
1. From the **in** drop-down menu, select the other service instance to which you want to invite the new user.
1. Select the **Ingestion Policies** service role to assign it to the user.
- 
+ 
1. Leave the never expires access field as is.
3. Assign the custom role to the user.
- The custom role is assigned for the already selected Operations for Applications service instances.
+ The custom role is assigned for the already selected Tanzu Observability service instances.
1. Click **+ Add Custom Roles Access**.
1. In the **Add custom role access** popup window, search for, select the custom role that you want to assign, and click **Add**.
diff --git a/pages/doc/documentation_getting_started.md b/pages/doc/documentation_getting_started.md
index a7f6d9d46..43962f0e2 100644
--- a/pages/doc/documentation_getting_started.md
+++ b/pages/doc/documentation_getting_started.md
@@ -7,19 +7,19 @@ permalink: tutorial_overview.html
summary: Come up to speed with tutorials in product, GitHub, and docs.
---
-Learn VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) with in-product or external resources:
+Learn about Tanzu Observability (formerly known as VMware Aria Operations for Applications) with in-product or external resources:
* **Learn from the Product**: Getting Started workflow, tutorial and tour integrations, help panel, integration setup examples.
* **Tutorials, Videos, and More**: Tutorials, Reference documentation, FAQs and Recipes, videos, and more.
- Start with the [Integrations](hello_wavefront_aws_tutorial.html) tutorial.
- - Watch the videos in the [Get Started with VMware Aria Operations for Applications](https://vmwaretv.vmware.com/embedplaylist/secure/embed/v2/1/playlistId/1_zcafsh0j/uiConfId/47611883) playlist on VMware TV.
+ - Watch the videos in the [Get Started with Tanzu Observability](https://vmwaretv.vmware.com/embedplaylist/secure/embed/v2/1/playlistId/1_zcafsh0j/uiConfId/47611883) playlist on VMware TV.
## Learn from the Product
-
The Getting Started onboarding flow helps you get data in, build a dashboard, and create an alert.
+
The Getting Started onboarding flow helps you get data in, build a dashboard, and create an alert.
All trial users go through a Getting Started flow.
All other users can click Getting Started on the toolbar to start.
You can use the customer-wide or user-level preferences to control whether Getting Started is visible on the toolbar.
@@ -28,19 +28,19 @@ You can use the customer-wide or user-level preferences to control whether
-The Operations for Applications Tutorial allows you to experiment with charts and alerts to learn (clone the integration to save your results).
+The Tanzu Observability Tutorial allows you to experiment with charts and alerts to learn (clone the integration to save your results).
Click Integrations on the toolbar.
-
Click the Operations for Applications Tutorial tile and click the Dashboards tab.
+
Click the Tanzu Observability Tutorial tile and click the Dashboards tab.
Click a dashboard and follow the instructions on the left to explore the charts (with sample data) on the right.
-
+
-The Operations for Applications Tour integration is a deep dive into the product functionality.
+The Tanzu Observability Tour integration is a deep dive into the product functionality.
You can explore dashboards and charts, which use sample data to highlight functionalities such as Anomaly Detection or fine-tuning alerts. The tour also includes single-host and cluster metrics exploration dashboards.
Click Integrations on the toolbar.
-
Search for and click the Operations for Applications Tour tile and click the Dashboards tab.
+
Search for and click the Tanzu Observability Tour tile and click the Dashboards tab.
Click any of the dashboards to explore data.
@@ -87,7 +87,7 @@ Our documentation includes reference documentation for API, query language, and
Our FAQ info helps both new and advanced users. We're updating this list as we hear from you in conversations or on Slack.
-
Charts FAQ explains how to set color mapping, how to define drilldown links, and more.
+
Charts FAQ explains how to set color mapping, how to define drill down links, and more.
Kubernetes FAQ addresses common questions, such as integrating with third-party applications.
Tracing FAQ helps with common tasks like filtering RED metrics with custom span tags.
Wavefront and Spring Boot FAQ explains differences between Freemium and trial clusters, how to visualize metrics and traces, and more.
@@ -101,7 +101,7 @@ Our documentation includes reference documentation for API, query language, and
This doc set includes a set of tutorials for common use cases and links to short videos that help you get up to speed quickly.
-The [VMware Aria Operations for Applications channel on VMware TV](https://vmwaretv.vmware.com/channel/Tanzu%2BObservability/252649793) offers 50+ videos including conceptual lightboard videos and many short how-to videos.
+The [Tanzu Observability channel on VMware TV](https://vmwaretv.vmware.com/channel/Tanzu%2BObservability/252649793) offers 50+ videos including conceptual lightboard videos and many short how-to videos.
You can watch the Getting Started playlist videos on VMware TV or click below to start.
diff --git a/pages/doc/hello_wavefront_aws_tutorial.md b/pages/doc/hello_wavefront_aws_tutorial.md
index bb2f123fe..73160e61e 100644
--- a/pages/doc/hello_wavefront_aws_tutorial.md
+++ b/pages/doc/hello_wavefront_aws_tutorial.md
@@ -60,11 +60,11 @@ Follow these steps:
1. Click the **AWS Account** tile and select the **Another AWS account** radio button.
1. Copy the **Account ID** value shown in the AWS integration setup instructions.
1. Paste it in the **Account ID** text box in the AWS UI.
- 
+ 
1. Select the **Require external ID** check box.
1. Enter the **External ID**. Copy the **External ID** value shown in the AWS integration setup instructions and paste it here.
- 
+ 
1. Click **Next**.
1. Set Permissions:
1. Search for the **ReadOnlyAccess** permission and select it.
@@ -76,7 +76,7 @@ Follow these steps:
1. Click **Create role**.
1. Once the list of roles appears, click `example-role` (the role you just created), and copy the **ARN** value.
-{% include note.html content="See [Giving Limited Access](integrations_aws_overview.html#giving-limited-access) if you want to specify a more restrictive IAM policy for VMware Aria Operations for Applications." %}
+{% include note.html content="See [Giving Limited Access](integrations_aws_overview.html#giving-limited-access) if you want to specify a more restrictive IAM policy for Tanzu Observability." %}
### Step 3: Configure the AWS Integration
@@ -94,7 +94,7 @@ Go back to the product instance where you opened the AWS integration tile, and f
-VMware Aria Operations for Applications can now connect to your AWS account and get data. Once the data starts flowing, you can visualize it. It will take a few minutes for the data to show.
+Tanzu Observability can now connect to your AWS account and get data. Once the data starts flowing, you can visualize it. It will take a few minutes for the data to show.
### Step 4: (Optional) Launch an EC2 Instance
@@ -218,7 +218,7 @@ Our Success Value Engineering team shared some frequently asked questions -- and
* How do I manage my account (permissions, preferences, etc.)? See [Customize Your Account](users_account_managing.html).
* How can admins add other users? See [Manage User Accounts](user-accounts.html).
* How do admins set up SSO? See [Single-Tenant Authentication and Self-Service SAML SSO](auth_self_service_sso.html)
-* How do I track usage? See [Monitor Your Service with the Operations for Applications Usage Integration](wavefront_monitoring.html).
+* How do I track usage? See [Monitor Your Service with the Tanzu Observability Usage Integration](wavefront_monitoring.html).
* Why did my alert (not) fire? See [Why Did My Alert Not Fire?](alerts_faq.html#why-did-my-alert-not-fire) and [Why Did My Alert Misfire](alerts_faq.html#why-did-my-alert-misfire).
* How do I contact support? See [Support and Feedback](wavefront_support_feedback.html).
* Do you have videos? Yes! We have a [video channel on VMware TV](https://vmwaretv.vmware.com/channel/Tanzu%2BObservability/252649793)!
diff --git a/pages/doc/query_language_getting_started.md b/pages/doc/query_language_getting_started.md
index 3547f7ddb..2ce7fd12c 100644
--- a/pages/doc/query_language_getting_started.md
+++ b/pages/doc/query_language_getting_started.md
@@ -7,7 +7,7 @@ permalink: query_language_getting_started.html
summary: Watch some videos, run a query, apply filters and functions, and more.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes the Wavefront Query Language (WQL), which lets you retrieve and display data that has been ingested.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Wavefront Query Language (WQL), which lets you retrieve and display data that has been ingested.
* **Time series data** The query language is particularly well suited to time series data because it accommodates the periodicity, potential irregularity, and streaming nature of that data type.
* **Histograms** The query language includes functions for [manipulating histograms](query_language_reference.html#histogram-functions).
* **Traces and spans** Use the [tracing UI](tracing_traces_browser.html) to query traces and spans.
diff --git a/pages/doc/query_language_reference.md b/pages/doc/query_language_reference.md
index bb72b7c74..a2f48b8fd 100644
--- a/pages/doc/query_language_reference.md
+++ b/pages/doc/query_language_reference.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: query_language_reference.html
summary: Learn about the query syntax, operators, and functions supported by Wavefront Query Language (WQL).
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes the Wavefront Query Language, which allows you to extract the information you need from your data. You use the query language for queries that display in charts and for alerts. This page is a complete reference to all query language elements and functions. You can click most functions for a page with details and examples.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Wavefront Query Language, which allows you to extract the information you need from your data. You use the query language for queries that display in charts and for alerts. This page is a complete reference to all query language elements and functions. You can click most functions for a page with details and examples.
## Query Expressions
diff --git a/pages/doc/tutorial_dashboards.md b/pages/doc/tutorial_dashboards.md
index a2210b3d8..55d729625 100644
--- a/pages/doc/tutorial_dashboards.md
+++ b/pages/doc/tutorial_dashboards.md
@@ -17,7 +17,7 @@ The focus in tutorial is on exploration, so you don't need any permissions to go
## Task 1: Find a Sample Dashboard in the Dashboards Browser
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes pre-built tutorial and tour integrations with dashboards that show how to use the product with sample metrics. Let's explore a tour dashboard, which contains sample data.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes pre-built tutorial and tour integrations with dashboards that show how to use the product with sample metrics. Let's explore a tour dashboard, which contains sample data.
diff --git a/pages/doc/ui_chart_reference.md b/pages/doc/ui_chart_reference.md
index ea8cc7244..bec029eb2 100644
--- a/pages/doc/ui_chart_reference.md
+++ b/pages/doc/ui_chart_reference.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: ui_chart_reference.html
summary: Chart types and configuration options for each chart type.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) provides charts viewing and examining your data. You can interact directly with charts in real time -- zoom in, zoom out, change the time window, and so on.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) provides charts viewing and examining your data. You can interact directly with charts in real time -- zoom in, zoom out, change the time window, and so on.
Users with dashboard permission can customize many aspects of the chart and save their changes. This page is a detailed reference to the tabs in the different chart types. We repeat tab reference for each chart type.
diff --git a/pages/doc/videos.md b/pages/doc/videos.md
index daf659858..b35ec8e0d 100644
--- a/pages/doc/videos.md
+++ b/pages/doc/videos.md
@@ -4,13 +4,11 @@ keywords: videos
tags: [getting started]
sidebar: doc_sidebar
permalink: videos.html
-summary: Learn about VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) with videos.
+summary: Learn about Tanzu Observability (formerly known as VMware Aria Operations for Applications) with videos.
---
-This page contains the playlists with our videos. You can instead watch them from the [VMware Aria Operations for Applications channel on VMware TV here](https://vmwaretv.vmware.com/channel/Tanzu%2BObservability/252649793).
+This page contains the playlists with our videos. You can instead watch them from the [Tanzu Observability channel on VMware TV here](https://vmwaretv.vmware.com/channel/Tanzu%2BObservability/252649793).
-Note that in most of our videos we still refer to VMware Aria Operations for Applications as Tanzu Observability or Wavefront.
-
-{% include note.html content="In most of our videos we still refer to VMware Aria Operations for Applications as Tanzu Observability or Wavefront. These videos were created between 2017 and 2022 and some of the information in them might have changed." %}
+{% include note.html content="In most of our videos we still refer to Tanzu Observability as Wavefront. These videos were created between 2017 and 2022 and some of the information in them might have changed." %}
## Getting Started
diff --git a/pages/doc/windows_host_tutorial.md b/pages/doc/windows_host_tutorial.md
index e296e3976..f398c4c97 100644
--- a/pages/doc/windows_host_tutorial.md
+++ b/pages/doc/windows_host_tutorial.md
@@ -4,14 +4,14 @@ keywords:
tags: [tutorials]
sidebar: doc_sidebar
permalink: windows_host_tutorial.html
-summary: Get data from a Windows host and monitor in VMware Aria Operations for Applications.
+summary: Get data from a Windows host and monitor in Tanzu Observability.
---
-Starting July 3, 2023, Operations for Applications is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions:
-* Operations for Applications subscriptions **onboarded** to the VMware Cloud services platform.
+Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions:
+* Tanzu Observability subscriptions **onboarded** to the VMware Cloud services platform.
* **Original** subscriptions -- the existing ones which remain as is until they migrate to VMware Cloud services.
-In this tutorial, you’ll learn how to ingest data from a Windows host machine to Operations for Applications by using a Wavefront proxy. Although Operations for Applications supports direct ingestion in non-production environments, such as POC or development and test environments, in production environments using a Wavefront proxy is the recommended and supported way for ingesting data.
+In this tutorial, you’ll learn how to ingest data from a Windows host machine to Tanzu Observability by using a Wavefront proxy. Although Tanzu Observability supports direct ingestion in non-production environments, such as POC or development and test environments, in production environments using a Wavefront proxy is the recommended and supported way for ingesting data.
## Onboarded Subscriptions
@@ -47,7 +47,7 @@ Let's create a server to server OAuth app and retrieve the app ID and app secret
6. Define the scopes by assigning roles to the server to server app.
For example:
1. Assign the **Organization Member** organization role.
- 1. Search for `Operations for Applications` in the list of scopes, expand the **VMware Aria Operations for Applications** service roles, and select **Proxies**.
+ 1. Search for `Tanzu Observability` in the list of scopes, expand the **Tanzu Observability** service roles, and select **Proxies**.
{% include note.html content="Note that these are the minimum required roles for the server to server app that you'll use to install the Wavefront proxy." %}
@@ -72,21 +72,21 @@ You will need the organization ID when you install the Wavefront proxy.
{% include note.html content="To install the Wavefront proxy, you need the long organization ID." %}
-### Step 3: Navigate to Operations for Applications
+### Step 3: Navigate to Tanzu Observability
-To install the Wavefront proxy, set up an integration, and install integration dashboards, you must have the **Proxies** and **Integrations** permissions. For more information see [Operations for Applications Permissions in VMware Cloud Services](csp_permissions_overview.html).
+To install the Wavefront proxy, set up an integration, and install integration dashboards, you must have the **Proxies** and **Integrations** permissions. For more information see [Tanzu Observability Permissions in VMware Cloud Services](csp_permissions_overview.html).
1. In the VMware Cloud Services Console, click VMware Cloud Services.
-2. Search for Operations for Applications and click the **VMware Aria Operations for Applications** tile.
+2. Search for Tanzu Observability and click the **Tanzu Observability** tile.
3. Click **Launch Service**.
In a multi-tenant environment, you should also select a tenant.
- 
+ 
### Step 4: Start the Setup Process
-1. In your Operations for Applications service instance, click **Integrations** on the toolbar.
+1. In your Tanzu Observability service instance, click **Integrations** on the toolbar.
2. Click the **Windows Host** integration tile.
3. Click the **Setup** tab.
@@ -115,7 +115,7 @@ Once installed, the proxy automatically starts. Check `Program Files (x86)\Wavef
### Step 7: Verify That Metrics Are Flowing
-When the Wavefront proxy and the Telegraf agent are installed and the proxy starts ingesting data to Operations for Applications, on the **Metrics** tab, you'll see the metrics that are flowing along with charts for each metric.
+When the Wavefront proxy and the Telegraf agent are installed and the proxy starts ingesting data to Tanzu Observability, on the **Metrics** tab, you'll see the metrics that are flowing along with charts for each metric.
From 165780382fbc6eb5359fc369c02f673803eef823 Mon Sep 17 00:00:00 2001
From: shavidissa
Date: Mon, 18 Mar 2024 12:20:29 -0700
Subject: [PATCH 08/26] Updated the rest of the pages: Quickstart and Tutorials
---
pages/doc/glossary.md | 6 ++--
pages/doc/privacy.md | 2 +-
pages/doc/terms_of_service.md | 2 +-
pages/doc/wavefront_acessibility.md | 2 +-
pages/doc/wavefront_api.md | 36 +++++++++++-----------
pages/doc/wavefront_obsolescence_policy.md | 14 ++++-----
pages/doc/wavefront_searching.md | 2 +-
pages/doc/wavefront_support_feedback.md | 5 ++-
8 files changed, 34 insertions(+), 35 deletions(-)
diff --git a/pages/doc/glossary.md b/pages/doc/glossary.md
index bb96f9721..6e3109dbe 100644
--- a/pages/doc/glossary.md
+++ b/pages/doc/glossary.md
@@ -7,7 +7,7 @@ permalink: glossary.html
summary: Learn how we use technical terms.
---
-This VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) glossary defines technical terms that are commonly used in the documentation or in the product. Click the links or search this documentation for details.
+This Tanzu Observability (formerly known as VMware Aria Operations for Applications) glossary defines technical terms that are commonly used in the documentation or in the product. Click the links or search this documentation for details.
@@ -200,7 +200,7 @@ This VMware Aria Operations for Applications (formerly known as Tanzu Observabil
Object tags help you filter your display. You apply an object tag to Operations for Applications UI objects such as dashboards. You can later find and display groups of objects based on their object tag.
+
Object tags help you filter your display. You apply an object tag to Tanzu Observability UI objects such as dashboards. You can later find and display groups of objects based on their object tag.
@@ -334,7 +334,7 @@ You can manage authorization with user-level permissions or user and group-level
-
VMware Aria Operations for Applications service
+
Tanzu Observability service
The service runs the metrics collection engine. It can receive telemetry data from a Wavefront proxy or through direct ingestion.
diff --git a/pages/doc/privacy.md b/pages/doc/privacy.md
index 9c22fef8d..7b593bcb6 100644
--- a/pages/doc/privacy.md
+++ b/pages/doc/privacy.md
@@ -6,7 +6,7 @@ toc: false
permalink: privacy.html
summary: Privacy policy for pre-acquisition customers.
---
-{% include important.html content="In 2023, the product name for Tanzu Observability by Wavefront has been changed to VMware Aria Operations for Applications."%}
+{% include important.html content="In 2023, the product name for VMware Aria Operations for Applications is changed to Tanzu Observability."%}
Last modified: March 7, 2023
This privacy policy applies to you **ONLY** if you became a customer before August 17, 2017. See the Terms of Service for details.
diff --git a/pages/doc/terms_of_service.md b/pages/doc/terms_of_service.md
index 766ee0437..66a82d3ff 100644
--- a/pages/doc/terms_of_service.md
+++ b/pages/doc/terms_of_service.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: terms_of_service.html
summary: Data Retention and Terms of Service
---
-The terms of service and data retention for VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) differ depending on the contract your company has with VMware. This page gives a summary and links to some relevant information.
+The terms of service and data retention for Tanzu Observability (formerly known as VMware Aria Operations for Applications) differ depending on the contract your company has with VMware. This page gives a summary and links to some relevant information.
{% include tip.html content="Details vary depending on when you became a customer and on your Service Agreement with VMware." %}
diff --git a/pages/doc/wavefront_acessibility.md b/pages/doc/wavefront_acessibility.md
index 0ebf38c2f..ca7b42891 100644
--- a/pages/doc/wavefront_acessibility.md
+++ b/pages/doc/wavefront_acessibility.md
@@ -6,7 +6,7 @@ permalink: wavefront_keyboard_shortcuts.html
summary: Use the keyboard shortcuts to navigate through pages and menus.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) is committed to continuous improvement of product accessibility. We recently addressed accessibility issues and included level-A accessibility fixes for keyboard navigation and colorblind support. We also addressed several level-AA accessibility issues. Here are some highlights:
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) is committed to continuous improvement of product accessibility. We recently addressed accessibility issues and included level-A accessibility fixes for keyboard navigation and colorblind support. We also addressed several level-AA accessibility issues. Here are some highlights:
* Keyboard shortcuts allow you to navigate through pages and menus without using a mouse.
* Color contrast supports colorblind accessibility. We continuously check our UI elements and change color as needed.
diff --git a/pages/doc/wavefront_api.md b/pages/doc/wavefront_api.md
index d584c7317..03b897e3f 100644
--- a/pages/doc/wavefront_api.md
+++ b/pages/doc/wavefront_api.md
@@ -4,10 +4,10 @@ keywords: getting started
tags: [getting started]
sidebar: doc_sidebar
permalink: wavefront_api.html
-summary: Learn about the REST API for managing VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront).
+summary: Learn about the REST API for managing Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-The REST API enables you to write scripts to perform management tasks, such as defining alerts and creating events. You can use the REST API to perform any task that is supported by the Operations for Applications GUI. The REST API is based on Swagger, so you can generate the API client of your choice (including a CLI client).
+The REST API enables you to write scripts to perform management tasks, such as defining alerts and creating events. You can use the REST API to perform any task that is supported by the Tanzu Observability GUI. The REST API is based on Swagger, so you can generate the API client of your choice (including a CLI client).
@@ -19,13 +19,13 @@ The current version of the REST API is v2. You can access the API at `
-## Invoking the Operations for Applications REST API
+## Invoking the Tanzu Observability REST API
You can invoke the API using `curl` or from an API client. In either case, you must use a token.
The token that you need depends on your [subscription type](subscriptions-differences.html).
-* For VMware Cloud services subscriptions, invoking the Operations for Application REST API requires a VMware Cloud services access token.
-* For original subscriptions, invoking the Operations for Application REST API requires an Operations for Application API token.
+* For VMware Cloud services subscriptions, invoking the Tanzu Observability REST API requires a VMware Cloud services access token.
+* For original subscriptions, invoking the Tanzu Observability REST API requires a Tanzu Observability API token.
-See [Use the Operations for Applications REST API](using_wavefront_api.html) for details and examples.
+See [Use the Tanzu Observability REST API](using_wavefront_api.html) for details and examples.
## Generate an API Client Using Swagger
@@ -87,7 +87,7 @@ Here's an example for generating a Java client:
`swagger-codegen generate -i https://mydomain.wavefront.com/api/v2/swagger.json -c swagger-config.json -l java`
-## Operations for Applications REST API Categories
+## Tanzu Observability REST API Categories
The REST API supports the following objects corresponding to different categories of management tasks:
@@ -95,11 +95,11 @@ The REST API supports the following objects corresponding to different categorie
- **Access** - Provides information on the access level of an entity. See [Notes on the Access Category](#access) below.
- **Account (User and Service Account)** - Allows users with [**Accounts** permission](permissions_overview.html) to retrieve a list of all [accounts](users_roles.html), create, update, and delete accounts and manage permissions and groups associated with accounts.
- {% include note.html content="Applies only to original subscriptions. See the [Operations for Applications subscription types](subscriptions-differences.html)."%}
+ {% include note.html content="Applies only to original subscriptions. See the [Tanzu Observability subscription types](subscriptions-differences.html)."%}
- **Alert** - Retrieve active, snoozed, in-maintenance, and invalid alerts. Users with [**Alerts** permission](permissions_overview.html) can create and update alerts.
- **ApiToken** - Allows users with [**Accounts** permission](permissions_overview.html) to retrieve, create, and manage API tokens. Used primarily in conjunction with service accounts.
- {% include note.html content="Applies only to original subscriptions. See the [Operations for Applications subscription types](subscriptions-differences.html)."%}
+ {% include note.html content="Applies only to original subscriptions. See the [Tanzu Observability subscription types](subscriptions-differences.html)."%}
- **Cloud Integration** - Retrieve cloud integration data types such as those available with the [AWS integration](integrations_aws_metrics.html), [Google Cloud Platform Integration](gcp.html), [Google Cloud Billing Integration](gcp_billing.html), [New Relic Integration](newrelic.html), [AppDynamics Integration](appdynamics.html), [Dynatrace Integration](dynatrace.html), [Microsoft Azure Integration](azure.html), [VMware Aria Operations (SaaS) Integration](vrops.html), and the [Snowflake Integration](snowflake.html). Users with [**Proxies** permission](permissions_overview.html) can add and remove cloud integration data types.
- **Dashboard** - Retrieve data about dashboards, list dashboards, and return version history. Users with [**Dashboards** permission](permissions_overview.html) can save, create, delete, clone, undelete dashboards.
- **Derived Metric** - Manage derived metrics.
@@ -115,7 +115,7 @@ The REST API supports the following objects corresponding to different categorie
- **Query** - Perform queries.
- **Role** - Retrieve information about a role and manage roles and role assignees.
- {% include note.html content="Applies only to original subscriptions. See the [Operations for Applications subscription types](subscriptions-differences.html)."%}
+ {% include note.html content="Applies only to original subscriptions. See the [Tanzu Observability subscription types](subscriptions-differences.html)."%}
- **Saved Search** - Retrieve, add, and remove saved searches.
- **Search** - Search agents, alerts, integrations, dashboards, external links, maintenance windows, sources, and webhook alert targets.
- **Source** - Retrieve sources and tags associated with a source. Users with [**Source Tags** permission](permissions_overview.html) can add and remove source tags and set descriptions.
@@ -123,7 +123,7 @@ The REST API supports the following objects corresponding to different categorie
- **User** - Deprecated API. Use **Account (User and Service Account)** instead.
- **UserGroup** - Allows users with [**Accounts** permission](permissions_overview.html) to retrieve a list of all groups, create, update, and delete groups, and manage the users and roles associated with a group.
- {% include note.html content="Applies only to original subscriptions. See the [Operations for Applications subscription types](subscriptions-differences.html)."%}
+ {% include note.html content="Applies only to original subscriptions. See the [Tanzu Observability subscription types](subscriptions-differences.html)."%}
- **Webhook** - Retrieve webhooks. Users with [**Alerts** permission](permissions_overview.html) can create, update, and delete webhooks.
@@ -133,7 +133,7 @@ The `/api/access/{entity}` endpoint provides information on how often an entity
{% include important.html content="In order to use this API, users must have both the Direct Data Ingestion and Metrics [permissions](permissions_overview.html)."%}
-{% include note.html content="VMware Aria Operations for Applications uses a bloom filter to determine the access pattern. As a result, even if data access returns true, there’s a very low probability that data actually hasn't been accessed. If data access returns false, it is guaranteed that the data has not been accessed.
+{% include note.html content="Tanzu Observability uses a bloom filter to determine the access pattern. As a result, even if data access returns true, there’s a very low probability that data actually hasn't been accessed. If data access returns false, it is guaranteed that the data has not been accessed.
"%}
This GET endpoint has the following parameters:
@@ -149,7 +149,7 @@ This GET endpoint has the following parameters:
hostPrefix
Prefix of the host name, e.g. you can use test-2a-app67 if the whole host name is test-2a-app67-id-12345
-Warning:hostPrefix must be somewhat specific. There's a limit on how many hosts VMware Aria Operations for Applications scans.
+Warning:hostPrefix must be somewhat specific. There's a limit on how many hosts Tanzu Observability scans.
usageThresholdDays
How many days to look back. 7 days by default.
diff --git a/pages/doc/wavefront_obsolescence_policy.md b/pages/doc/wavefront_obsolescence_policy.md
index 75310e045..dc8927ad0 100644
--- a/pages/doc/wavefront_obsolescence_policy.md
+++ b/pages/doc/wavefront_obsolescence_policy.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: wavefront_obsolescence_policy.html
summary: Learn about deprecated and EOL features and how to prevent potential problems.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) product features and APIs move to end-of-life as part of the normal software development lifecycle, security improvements, and other factors. To support planning for upgrades, this document provides information on upcoming lifecycle changes. While every effort is made to provide sufficient notice of changes, security issues or other factors may occasionally lead to accelerated end-of-life dates.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) product features and APIs move to end-of-life as part of the normal software development lifecycle, security improvements, and other factors. To support planning for upgrades, this document provides information on upcoming lifecycle changes. While every effort is made to provide sufficient notice of changes, security issues or other factors may occasionally lead to accelerated end-of-life dates.
## Lifecycle Stages
@@ -78,7 +78,7 @@ The following proxy versions are deprecated or moved to end-of-life.
## Delta Counters
-Delta counter behavior changed with [Release 2020.26](2020.26.x_release_notes.html). The original delta counter implementation was Deprecated with [Release 2020.26](2020.26.x_release_notes.html). We changed delta counter queries to use `cs()` in the Operations for Applications Usage integration and tracing RED metrics. The original delta counter implementation is End of Life March 31, 2021.
+Delta counter behavior changed with [Release 2020.26](2020.26.x_release_notes.html). The original delta counter implementation was Deprecated with [Release 2020.26](2020.26.x_release_notes.html). We changed delta counter queries to use `cs()` in the Tanzu Observability Usage integration and tracing RED metrics. The original delta counter implementation is End of Life March 31, 2021.
### Automatic Updates and Required Changes
@@ -167,13 +167,13 @@ For the above example if the data measured across 3 minutes had been a total of:
Starting with release 2020.26, a new data type for storing delta counters is part of the product. Data ingestion of delta counters remains unchanged, and a delta (∆) is still required to indicate a delta counter, but the data is now queried via `cs()` instead of `ts()`. The original delta counters still report minutely, but instead of maintaining a monotonically increasing count they report the total number of increments that occurred within each minute. In our example, `cs(errors.count)` displays values of 10, 15, and 5. See [Counters and Delta Counters](delta_counters.html#counters-and-delta-counters-basics) for details and examples.
-## Operations for Applications Authentication and Authorization
+## Tanzu Observability Authentication and Authorization
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. VMware Cloud services provides centralized authentication and authorization to your entire VMware Cloud services portfolio across hybrid and native public clouds, including Operations for Applications. See [Advantages of VMware Cloud Services Subscriptions Over Original Subscriptions](subscriptions-differences.html#advantages-of-vmware-cloud-services-subscriptions-over-original-subscriptions).
+Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. VMware Cloud services provides centralized authentication and authorization to your entire VMware Cloud services portfolio across hybrid and native public clouds, including Tanzu Observability. See [Advantages of VMware Cloud Services Subscriptions Over Original Subscriptions](subscriptions-differences.html#advantages-of-vmware-cloud-services-subscriptions-over-original-subscriptions).
-Starting September 20, 2023, all **new trial** instances of Operations for Applications are **onboarded** to VMware Cloud services.
+Starting September 20, 2023, all **new trial** instances of Tanzu Observability are **onboarded** to VMware Cloud services.
-In October, 2023, we start to incrementally [onboard](csp_migration.html) all **original** subscriptions, which use Operations for Applications authentication and authorization, to VMware Cloud services.
+In October, 2023, we start to incrementally [onboard](csp_migration.html) all **original** subscriptions, which use Tanzu Observability authentication and authorization, to VMware Cloud services.
-{% 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)." %}
+{% include warning.html content="The Tanzu Observability 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 Tanzu Observability 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 Tanzu Observability API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy)." %}
diff --git a/pages/doc/wavefront_searching.md b/pages/doc/wavefront_searching.md
index 83ada4d4c..906c4102f 100644
--- a/pages/doc/wavefront_searching.md
+++ b/pages/doc/wavefront_searching.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: wavefront_searching.html
summary: Learn how to search for objects using tags and other search features.
---
-To help you find exactly what you need, VMware Aria Operations for Applications (formerly known s Tanzu Observability by Wavefront) supports tags and other search features.
+To help you find exactly what you need, Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports tags and other search features.
Here's a video to get you started. Note that this video was created in 2021 and some of the information in it might have changed. It also uses the 2021 version of the UI.
diff --git a/pages/doc/wavefront_support_feedback.md b/pages/doc/wavefront_support_feedback.md
index a84449582..983aefc53 100644
--- a/pages/doc/wavefront_support_feedback.md
+++ b/pages/doc/wavefront_support_feedback.md
@@ -6,17 +6,16 @@ permalink: wavefront_support_feedback.html
summary: Get help with and give feedback.
---
-
## Support
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) support is available as follows:
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) support is available as follows:
* Get in touch with Technical Support and create a support ticket.
1. Navigate to the [Support Portal](https://cloudhealth.zendesk.com/).
2. Sign up and create an account.
3. [Submit a ticket](https://vmwaoa.zendesk.com/hc/en-us/requests/new).
-* Get support from within Operations for Applications:
+* Get support from within Tanzu Observability:
1. Log in to your service instance.
1. From the gear icon on the toolbar, select Support.
From b01302d37f827bbbe6e449bbc9f85b4e9812304c Mon Sep 17 00:00:00 2001
From: shavidissa
Date: Tue, 19 Mar 2024 10:26:54 -0700
Subject: [PATCH 09/26] rename the charts and dashboards section
---
pages/doc/dashboards_variables.md | 2 +-
pages/doc/external_links_managing.md | 2 +-
pages/doc/log_integration.md | 2 +-
pages/doc/ui_charts.md | 2 +-
pages/doc/ui_charts_faq.md | 4 ++--
pages/doc/ui_dashboards.md | 4 ++--
pages/doc/ui_examine_data.md | 2 +-
pages/doc/ui_sharing.md | 4 ++--
8 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/pages/doc/dashboards_variables.md b/pages/doc/dashboards_variables.md
index cc5e42fc7..38f641e1d 100644
--- a/pages/doc/dashboards_variables.md
+++ b/pages/doc/dashboards_variables.md
@@ -7,7 +7,7 @@ permalink: dashboards_variables.html
summary: Use dashboard variables and global filters switch between different data sources.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes dashboard variables and global filters. Both are excellent ways of focusing the metrics that a dashboard displays.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes dashboard variables and global filters. Both are excellent ways of focusing the metrics that a dashboard displays.
All users can set predefined variables for a dashboard. The change applies to all charts in that dashboard.
diff --git a/pages/doc/external_links_managing.md b/pages/doc/external_links_managing.md
index 9494b6c92..d699b86e2 100644
--- a/pages/doc/external_links_managing.md
+++ b/pages/doc/external_links_managing.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: external_links_managing.html
summary: Learn how to manage external links.
---
-External links provide integration between VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) and external systems.
+External links provide integration between Tanzu Observability (formerly known as VMware Aria Operations for Applications) and external systems.
* **External links** are general purpose: you can link through to any type of system accessible from a URL.
* The **Log integration** lets you drill down from a time series to a log entry in a logging system such as Scalyr, ELK, or Splunk. See [Access and Examine External Logs](log_integration.html) for details.
diff --git a/pages/doc/log_integration.md b/pages/doc/log_integration.md
index 8dccb215b..3e323a75a 100644
--- a/pages/doc/log_integration.md
+++ b/pages/doc/log_integration.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: log_integration.html
summary: Learn how to manage and view external logs.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) log integration lets you drill down from time series that is displayed in a chart to a log entry in a logging system such as Scalyr, ELK, or Splunk.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) log integration lets you drill down from time series that is displayed in a chart to a log entry in a logging system such as Scalyr, ELK, or Splunk.
Suppose while analyzing metrics data you find an anomaly such as an unexpected drop in transaction rate. You want to look at corresponding log entries. Set up the Log Integration and you
* Look at the problem in a chart
diff --git a/pages/doc/ui_charts.md b/pages/doc/ui_charts.md
index f39d41271..c6d9dc4d0 100644
--- a/pages/doc/ui_charts.md
+++ b/pages/doc/ui_charts.md
@@ -6,7 +6,7 @@ permalink: ui_charts.html
summary: Create charts, add and manage queries, and customize the chart.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) provides many different types of charts for examining data, creating alerts, and more! For example:
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) provides many different types of charts for examining data, creating alerts, and more! For example:
Create a chart and fine-tune the data it displays using filters and functions.
Customize your charts.
diff --git a/pages/doc/ui_charts_faq.md b/pages/doc/ui_charts_faq.md
index ff88ac5eb..1a14dbfad 100644
--- a/pages/doc/ui_charts_faq.md
+++ b/pages/doc/ui_charts_faq.md
@@ -5,7 +5,7 @@ sidebar: doc_sidebar
permalink: ui_charts_faq.html
summary: Learn chart customization from the experts.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes a variety of charts, with many customization options. [Create and Customize Charts](ui_charts.html) describes most of the things you need to know to get started. This page has some special tips and tricks to help you create the user experience you're after.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes a variety of charts, with many customization options. [Create and Customize Charts](ui_charts.html) describes most of the things you need to know to get started. This page has some special tips and tricks to help you create the user experience you're after.
{% include note.html content="You must have [Dashboard permission](permissions_overview.html) to save a chart to a dashboard. If you do not have permission, the UI menu selections and buttons required to perform the task are not visible." %}
@@ -40,7 +40,7 @@ The following example shows how to use color mapping with a single stat chart.
## Why the Color Can Be Different from What I Expect?
-In some cases, the color on a chart, for which you have set color mapping, can be different from what you expect to see. This can be caused by the decimal precision value that is set on the chart. When you use color mapping, Operations for Applications considers the real values in the system and changes the colors accordingly, while the values displayed on the chart can be rounded because of the decimal precision that is set on the chart.
+In some cases, the color on a chart, for which you have set color mapping, can be different from what you expect to see. This can be caused by the decimal precision value that is set on the chart. When you use color mapping, Tanzu Observability considers the real values in the system and changes the colors accordingly, while the values displayed on the chart can be rounded because of the decimal precision that is set on the chart.
Consider the following scenario:
diff --git a/pages/doc/ui_dashboards.md b/pages/doc/ui_dashboards.md
index 2ab24ba3d..7fcdca68d 100644
--- a/pages/doc/ui_dashboards.md
+++ b/pages/doc/ui_dashboards.md
@@ -6,7 +6,7 @@ permalink: ui_dashboards.html
summary: Create dashboards, add charts, customize dashboard layout, and troubleshoot dashboards.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes many out-of-the box dashboards, and supports creation and fine-grained customization of dashboards. You organize the information about your environment and fine-tune what users see. For example:
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes many out-of-the box dashboards, and supports creation and fine-grained customization of dashboards. You organize the information about your environment and fine-tune what users see. For example:
Organize charts into sections.
Perform global operations such as setting the dashboard time window.
@@ -629,7 +629,7 @@ Each time you save a dashboard, you create a dashboard version. Up to 100 versio
Select a version and revert or clone that version.
diff --git a/pages/doc/ui_examine_data.md b/pages/doc/ui_examine_data.md
index 87598a8cb..0de80fa62 100644
--- a/pages/doc/ui_examine_data.md
+++ b/pages/doc/ui_examine_data.md
@@ -6,7 +6,7 @@ permalink: ui_examine_data.html
summary: Examine data with dashboards and charts
---
-With dashboards and charts, all VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) users can examine data. By default, everyone can explore: set dashboard time window, zoom in and out, and perform other customizations.
+With dashboards and charts, all Tanzu Observability (formerly known as VMware Aria Operations for Applications) users can examine data. By default, everyone can explore: set dashboard time window, zoom in and out, and perform other customizations.
{% include note.html content="All users can view and explore charts. You must have the [**Dashboards** permission](permissions_overview.html) to make permanent changes, such as saving a chart to a dashboard." %}
diff --git a/pages/doc/ui_sharing.md b/pages/doc/ui_sharing.md
index f46f83c08..bd5b81bd3 100644
--- a/pages/doc/ui_sharing.md
+++ b/pages/doc/ui_sharing.md
@@ -5,7 +5,7 @@ sidebar: doc_sidebar
permalink: ui_sharing.html
summary: Share links to dashboards and charts, give dashboard access, and create embedded charts.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports sharing links, sharing access, and embedding charts.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports sharing links, sharing access, and embedding charts.
You can
* Share a link to a dashboard or chart so someone else can see what's going on.
@@ -102,7 +102,7 @@ You can embed an interactive chart in another product or on a Website. You must
### Allow or Deny Access to Embedded Charts
-You can apply access policies and deny or allow access to the embedded charts by using our REST API. The `Access Policy` controls which IP addresses can access the embedded charts and doesn't affect any other URLs or other functionality. Learn more about the [categories in the REST API](wavefront_api.html#operations-for-applications-rest-api-categories).
+You can apply access policies and deny or allow access to the embedded charts by using our REST API. The `Access Policy` controls which IP addresses can access the embedded charts and doesn't affect any other URLs or other functionality. Learn more about the [categories in the REST API](wavefront_api.html#tanzu-observability-rest-api-categories).
When you apply an access policy rule, take in mind the following:
From c8e6615f6ddc6fd5659250a0e6c8a1535f7ff9e4 Mon Sep 17 00:00:00 2001
From: shavidissa
Date: Tue, 19 Mar 2024 10:56:53 -0700
Subject: [PATCH 10/26] rename the Kubernetes section
---
pages/doc/integrations_tas_howto.md | 22 +++++++++---------
pages/doc/integrations_tmc.md | 10 ++++-----
pages/doc/integrations_tmc_howto.md | 30 ++++++++++++-------------
pages/doc/kubernetes_troubleshooting.md | 12 +++++-----
pages/doc/tas_to_troubleshoot.md | 2 +-
pages/doc/videos_kubernetes.md | 6 ++---
pages/doc/wavefront_kubernetes.md | 20 ++++++++---------
pages/doc/wavefront_kubernetes_faq.md | 4 ++--
8 files changed, 53 insertions(+), 53 deletions(-)
diff --git a/pages/doc/integrations_tas_howto.md b/pages/doc/integrations_tas_howto.md
index 003398e18..7edcc34a2 100644
--- a/pages/doc/integrations_tas_howto.md
+++ b/pages/doc/integrations_tas_howto.md
@@ -9,7 +9,7 @@ summary: Set up the Tanzu Observability tile and monitor your environment.
[VMware Tanzu Application Service](https://docs.pivotal.io/application-service/2-12/concepts/overview.html), previously known as Pivotal Cloud Foundry, is a popular platform for building cloud-native applications.
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) is a cloud-hosted service for full-featured observability. When you Tanzu Application Service to send data to the Wavefront proxy, you can take advantage of preconfigured dashboards, clone and customize dashboards, and more.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a cloud-hosted service for full-featured observability. When you Tanzu Application Service to send data to the Wavefront proxy, you can take advantage of preconfigured dashboards, clone and customize dashboards, and more.
{% include important.html content="This document is for the Tanzu Application Service nozzle version 4.0 and later. Earlier versions are [documented here](https://docs.pivotal.io/wavefront-nozzle/3-x/). " %}
@@ -73,7 +73,7 @@ We've streamlined the getting started process so it involves a few simple steps
1. Download the Tanzu Observability by Wavefront nozzle file from the [Tanzu Network](https://network.pivotal.io/)
2. In Tanzu Ops Manager, install, configure, and deploy the nozzle. At a minimum:
- 1. In the **Wavefront Proxy Config** section, specify the Operations for Applications instance, authentication credentials, and a user-friendly host name.
+ 1. In the **Wavefront Proxy Config** section, specify the Tanzu Observability instance, authentication credentials, and a user-friendly host name.
2. In the **Telegraf Agent Config** section, specify the Foundation name.
@@ -168,12 +168,12 @@ Ensure that your environment meet requirements on the Ops Manager side and on th
* **Ops Manager Requirements**
VMware Tanzu Observability by Wavefront nozzle has the following requirements:
* Read-only access to the Doppler Firehose and Cloud Controller.
- * Access to an Operations for Applications instance.
- * Authentication credentials. The authentication credentials depend on whether your Operations for Applications service is onboarded to VMware Cloud services.
+ * Access to an Tanzu Observability instance.
+ * Authentication credentials. The authentication credentials depend on whether your Tanzu Observability service is onboarded to VMware Cloud services.
* **Tanzu Observability by Wavefront Requirements**
- To set up the Tanzu Application Service integration on your Operations for Applications instance, you must have:
- * Access to an Operations for Applications instance.
- * At a minimum, **Integrations** permission on that Operations for Applications instance.
+ To set up the Tanzu Application Service integration on your OTanzu Observability instance, you must have:
+ * Access to an Tanzu Observability instance.
+ * At a minimum, **Integrations** permission on that Tanzu Observability instance.
* This version of the Tanzu Observability by Wavefront nozzle is compatible with Wavefront proxy version 10.14 and later.
See [Tanzu Observability and TAS Troubleshooting](tas_to_troubleshooting.html) for more.
@@ -185,7 +185,7 @@ This section explains each step in the flow in detail.
### Prerequisites
* You must have a Tanzu Network account to configure the Tanzu Observability Nozzle in Ops Manager.
-* You must have login credentials for an Operations for Applications instance to configure the integration.
+* You must have login credentials for an Tanzu Observability instance to configure the integration.
* Ensure that the root certificate for Ops Manager is included in data coming from Tanzu Application Service. See the [No Data Flowing and Certificate Error](tas_to_troubleshooting.html#symptom-no-data-flowing-in-and-certificate-error) troubleshooting section.
@@ -227,12 +227,12 @@ In Ops Manager, click the Tanzu Observability by Wavefront tile. With **Settings
Step 2. Click Wavefront Proxy Config and specify:
-
The URL of your Operations for Applications instance, for example, https://example.wavefront.com.
+
The URL of your Tanzu Observability instance, for example, https://example.wavefront.com.
The authentication credentials for your Wavefront proxy.
-
If your Operations for Applications service is onboarded to VMware Cloud services, use server to server OAuth app credentials, such as app ID and app secret. The server to server app must have the Proxies service role and must belong to the VMware Cloud organization running the Operations for Applications service instance.
-
If your Operations for Applications service is not onboarded to VMware Cloud services, you can still use a valid Operations for Applications API token.
+
If your Tanzu Observability service is onboarded to VMware Cloud services, use server to server OAuth app credentials, such as app ID and app secret. The server to server app must have the Proxies service role and must belong to the VMware Cloud organization running the Tanzu Observability instance.
+
If your Tanzu Observability service is not onboarded to VMware Cloud services, you can still use a valid Tanzu Observability API token.
For information about the original and onboarded subscriptions and how they differ, see Subscription Types.
diff --git a/pages/doc/integrations_tmc.md b/pages/doc/integrations_tmc.md
index 7e04ad2a5..51248cdab 100644
--- a/pages/doc/integrations_tmc.md
+++ b/pages/doc/integrations_tmc.md
@@ -9,8 +9,8 @@ summary: Learn about Tanzu Mission Control and how to generate a token.
[VMware Tanzu Mission Control](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-concepts/GUID-E2B5BE05-596E-4999-9B21-1CDB875A1BBF.html) provides a centralized management platform for consistently operating and securing your Kubernetes infrastructure and modern applications across multiple teams and clouds.
-You can set up seamless authentication from Tanzu Mission Control to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) from the Tanzu Mission Control console. Follow these high-level steps:
-1. In the VMware Aria Operations for Applications GUI, generate an API token (discussed below).
+You can set up seamless authentication from Tanzu Mission Control to Tanzu Observability (formerly known as VMware Aria Operations for Applications) from the Tanzu Mission Control console. Follow these high-level steps:
+1. In our service's GUI, generate an API token (discussed below).
2. From the Tanzu Mission Control console, create a [credential](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-A70E57A8-2C45-46D4-8E1F-6D5E7026473F.html) and paste the token into the credential.
{% include tip.html content="The account associated with the generated API token must have **Proxies** and **Integrations** permission. To avoid problems, for example when a (human) user leaves or is not available, use a service account." %}
@@ -18,15 +18,15 @@ You can set up seamless authentication from Tanzu Mission Control to VMware Aria
## Generate an API Token for Tanzu Mission Control
-
diff --git a/pages/doc/integrations_tmc_howto.md b/pages/doc/integrations_tmc_howto.md
index 242311b61..fedbc7d97 100644
--- a/pages/doc/integrations_tmc_howto.md
+++ b/pages/doc/integrations_tmc_howto.md
@@ -10,7 +10,7 @@ summary: Monitor clusters in Tanzu Mission Control.
[VMware Tanzu Mission Control](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-concepts/GUID-E2B5BE05-596E-4999-9B21-1CDB875A1BBF.html) provides a centralized management platform for consistently operating and securing your Kubernetes infrastructure and modern applications across multiple teams and clouds.
This document explains:
-* How to set up and enable the integration from Tanzu Mission Control to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+* How to set up and enable the integration from Tanzu Mission Control to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
* How to monitor your Kubernetes environment with our pre-defined dashboards, and how to clone and customize those dashboards.
* How to troubleshoot common problems.
@@ -21,12 +21,12 @@ If you want to monitor Tanzu Mission Control with Wavefront, you have two option
## Create the Credential
-To get started, you set up the integration from Tanzu Mission Control to VMware Aria Operations for Applications:
+To get started, you set up the integration from Tanzu Mission Control to Tanzu Observability:
### Step 1: Generate an API Token
-
In your product cluster, [Generate a Service Account API Token for Tanzu Mission Control](integrations_tmc.html#generate-an-api-token-for-tanzu-mission-control).
@@ -63,9 +63,9 @@ In your product cluster, [Generate a Service Account API Token for Tanzu Mission
{% include tip.html content="For details, see the [Tanzu Mission Control documentation](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-A70E57A8-2C45-46D4-8E1F-6D5E7026473F.html)" %}
-## Enable Operations for Applications for a Cluster in Tanzu Mission Control
+## Enable Tanzu Observability for a Cluster in Tanzu Mission Control
-After you have set up the credential from Tanzu Mission Control, you can start enabling VMware Aria Operations for Applications for individual clusters that are managed by Tanzu Mission Control.
+After you have set up the credential from Tanzu Mission Control, you can start enabling Tanzu Observability for individual clusters that are managed by Tanzu Mission Control.
@@ -85,15 +85,15 @@ After you have set up the credential from Tanzu Mission Control, you can start e
-You can now click the link to VMware Aria Operations for Applications. You are redirected to a dashboard in the VMware Aria Operations for Applications instance that shows the metrics for the cluster.
+You can now click the link to Tanzu Observability. You are redirected to a dashboard in the Tanzu Observability instance that shows the metrics for the cluster.
## Modify the Collector Configuration for a Cluster
-You can use Tanzu Mission Control to modify the collector configuration that controls how data is sent to Operations for Applications.
+You can use Tanzu Mission Control to modify the collector configuration that controls how data is sent to Tanzu Observability.
-The collector configuration for Operations for Applications specifies the details about the data that is sent to your Operations for Applications account, such as what data is collected and how often it is sent. Using Tanzu Mission Control, you can change the configuration to fine-tune the data collection for each of your clusters.
+The collector configuration for OTanzu Observability specifies the details about the data that is sent to your Tanzu Observability account, such as what data is collected and how often it is sent. Using Tanzu Mission Control, you can change the configuration to fine-tune the data collection for each of your clusters.
-For more information about collector configuration for Operations for Applications, see the Wavefront Collector for Kubernetes [configuration file in GitHub](https://github.com/wavefrontHQ/wavefront-collector-for-kubernetes/blob/main/docs/configuration.md#configuration-file).
+For more information about collector configuration for Tanzu Observability, see the Wavefront Collector for Kubernetes [configuration file in GitHub](https://github.com/wavefrontHQ/wavefront-collector-for-kubernetes/blob/main/docs/configuration.md#configuration-file).
1. Log in to the Tanzu Mission Control console as a user who has the **cluster.admin** role on the cluster.
2. Navigate to the cluster that you want to configure.
@@ -103,7 +103,7 @@ For more information about collector configuration for Operations for Applicatio
4. Edit the YAML code to modify the Collector configuration.
* You can edit the code directly in the provided code text box.
- * If you have already edited the Collector, you can click **Reset to Default Configuration** to pull the default configuration from your Operations for Applications account.
+ * If you have already edited the Collector, you can click **Reset to Default Configuration** to pull the default configuration from your Tanzu Observability account.
* To load a new configuration from a file, click **Import** and select the file to import.
5. To apply the changes to the YAML code, click **Save**.
@@ -134,7 +134,7 @@ If you want to customize the charts in the dashboards or add more charts, you ca
Select Clone from the ellipsis menu in the top right.
Give the cloned dashboard a new name and click OK.
-You must have the Dashboards permission inside VMware Aria Operations for Applications to clone or edit a dashboard.
+You must have the Dashboards permission inside Tanzu Observability to clone or edit a dashboard.
@@ -184,15 +184,15 @@ Follow these steps to remediate problems:
**Symptom**
-You're monitoring your Kubernetes cluster with VMware Aria Operations for Applications. You installed VMware Aria Operations for Applications from Tanzu Mission Control. Now you're having problems making a change to the Wavefront proxy.
+You're monitoring your Kubernetes cluster with Tanzu Observability. You installed Tanzu Observability from Tanzu Mission Control. Now you're having problems making a change to the Wavefront proxy.
**Cause**
-If you installed VMware Aria Operations for Applications from Tanzu Mission Control, you cannot make changes to the Wavefront proxy.
+If you installed Tanzu Observability from Tanzu Mission Control, you cannot make changes to the Wavefront proxy.
**Remediation**
-If your environment has a standalone VMware Aria Operations for Applications instance, use that instance. We are working on resolving the issue.
+If your environment has a standalone Tanzu Observability instance, use that instance. We are working on resolving the issue.
## Learn More
diff --git a/pages/doc/kubernetes_troubleshooting.md b/pages/doc/kubernetes_troubleshooting.md
index 953e5623b..72d7d3504 100644
--- a/pages/doc/kubernetes_troubleshooting.md
+++ b/pages/doc/kubernetes_troubleshooting.md
@@ -14,9 +14,9 @@ For an in depth overview of the Kubernetes integration and how it is deployed, n
{% include note.html content="If you currently use the Helm-managed and installed version of the Wavefront proxy and Kubernetes Metrics Collector, see our [legacy troubleshooting page](wf_kubernetes_troubleshooting.html) for instructions on how to troubleshoot your integration." %}
-## Not Enough Instances of VMware Aria Operations for Applications Components
+## Not Enough Instances of Tanzu Observability Components
-You might see a message containing information that there are not enough instances of the VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) components, such as:
+You might see a message containing information that there are not enough instances of the Tanzu Observability (formerly known as VMware Aria Operations for Applications) components, such as:
* Wavefront proxy
* Wavefront cluster collector
@@ -46,9 +46,9 @@ If the issue persists, check the logs for more details:
kubectl logs daemonset/wavefront-logging -n observability-system
```
-## No Data Flowing into VMware Aria Operations for Applications
+## No Data Flowing into Tanzu Observability
-If you identify that there is a problem with data flowing into VMware Aria Operations for Applications, follow the steps below.
+If you identify that there is a problem with data flowing into Tanzu Observability, follow the steps below.
### Step 1: Check the Status of the Integration Locally
@@ -85,7 +85,7 @@ To verify that the system is healthy, run:
### Step 2: Verify That the Wavefront Proxy Is Running
-The Wavefront proxy forwards logs, metrics, traces, and spans from all components to VMware Aria Operations for Applications. If no data is flowing, this means that the proxy might be not running.
+The Wavefront proxy forwards logs, metrics, traces, and spans from all components to Tanzu Observability. If no data is flowing, this means that the proxy might be not running.
To check the Wavefront proxy logs for errors, run:
@@ -233,7 +233,7 @@ If you want to change the metrics being filtered, follow the steps in our [examp
### Check Whether the Custom Resource Config File Is Configured Correctly
-Check the status of VMware Aria Operations for Applications components.
+Check the status of Tanzu Observability components.
```
kubectl get wavefront -n observability-system
diff --git a/pages/doc/tas_to_troubleshoot.md b/pages/doc/tas_to_troubleshoot.md
index d198e172a..f6bd1eb08 100644
--- a/pages/doc/tas_to_troubleshoot.md
+++ b/pages/doc/tas_to_troubleshoot.md
@@ -127,7 +127,7 @@ You have successfully set up the nozzle and the integration. However, you don't
* Ensure that the installation of the Wavefront Nozzle in has completed.
-* Verify that the proxy uses the correct authentication credentials and Operations for Applications instance URL. You specify that information in Ops Manager in the **Proxy Config** page.
+* Verify that the proxy uses the correct authentication credentials and Tanzu Observability instance URL. You specify that information in Ops Manager in the **Proxy Config** page.
* In your Tanzu Application Service environment, verify that the BOSH jobs for Wavefront proxy and for the Telegraf agent are running.
* In the BOSH CLI, use the `bosh deps` command to identify your wavefront-nozzle deployment, then tail the logs using `bosh ssh`.
diff --git a/pages/doc/videos_kubernetes.md b/pages/doc/videos_kubernetes.md
index 08ca42bcb..35b7f18c0 100644
--- a/pages/doc/videos_kubernetes.md
+++ b/pages/doc/videos_kubernetes.md
@@ -4,11 +4,11 @@ keywords: videos
tags: [kubernetes]
sidebar: doc_sidebar
permalink: videos_kubernetes.html
-summary: Watch our first videos on VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) and Kubernetes.
+summary: Watch our first videos on Tanzu Observability (formerly known as VMware Aria Operations for Applications) and Kubernetes.
---
-The following videos get you started. Note that in most of the videos we still refer to VMware Aria Operations for Applications as Tanzu Observability or Wavefront. Note that these videos were created between 2019 and 2022 and some of the information in them might have changed.
+The following videos get you started. Note that in most of the videos we still refer to Tanzu Observability as Wavefront. Note that these videos were created between 2019 and 2022 and some of the information in them might have changed.
@@ -42,7 +42,7 @@ The following videos get you started. Note that in most of the videos we still r
-This video gives you the big picture. It explains the different ways of monitoring Kubernetes with VMware Aria Operations for Applications (Tanzu Observability).
+This video gives you the big picture. It explains the different ways of monitoring Kubernetes with Tanzu Observability.
diff --git a/pages/doc/wavefront_kubernetes.md b/pages/doc/wavefront_kubernetes.md
index 272ea590a..c0821594e 100644
--- a/pages/doc/wavefront_kubernetes.md
+++ b/pages/doc/wavefront_kubernetes.md
@@ -4,14 +4,14 @@ keywords: containers, kubernetes
tags: [containers, kubernetes]
sidebar: doc_sidebar
permalink: wavefront_kubernetes.html
-summary: Monitor Kubernetes infrastructure and applications. Scale Kubernetes workloads based on metrics in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Monitor Kubernetes infrastructure and applications. Scale Kubernetes workloads based on metrics in Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
**Monitor your Kubernetes environment** at the infrastructure level and at the applications level with our Kubernetes Metrics Collector.
* Monitor Kubernetes infrastructure metrics (containers, pods, etc.) from our dashboards -- and create alerts from those dashboards.
* Automatically collect metrics from applications and workloads using built-in plug-ins such as Prometheus, Telegraf, etc.
-**Scale your Kubernetes environment** based on the metrics sent to VMware Aria Operations for Applications with our Horizontal Pod Autoscaler Adapter.
+**Scale your Kubernetes environment** based on the metrics sent to Tanzu Observability with our Horizontal Pod Autoscaler Adapter.
## Videos
@@ -50,7 +50,7 @@ The following videos get you started.
-This video gives you the big picture. It explains the different ways of monitoring Kubernetes with Operations for Applications.
+This video gives you the big picture. It explains the different ways of monitoring Kubernetes with Tanzu Observability.
@@ -61,16 +61,16 @@ This video gives you the big picture. It explains the different ways of monitori
## Send Data from Your Kubernetes Environment
-You can send data to VMware Aria Operations for Applications in several ways:
+You can send data to our service in several ways:
* **Direct**: Use our Kubernetes Metrics Collector to send data directly from your Kubernetes cluster to the Wavefront proxy. The Collector can collect metrics from Prometheus compatible applications and support a number of Telegraf plugins.
-* **Prometheus**: If you are already using Prometheus to view your data and want to monitor your Kubernetes data with VMware Aria Operations for Applications, send data to the Kubernetes Metrics Collector.
+* **Prometheus**: If you are already using Prometheus to view your data and want to monitor your Kubernetes data using our service, send data to the Kubernetes Metrics Collector.
To use our Kubernetes Metrics Collector, you must set up our Kubernetes integration. Use one of the following options:
-* [**Recommended**] Directly by using the VMware Aria Operations for Applications user interface.
+* [**Recommended**] Directly using the user interface.
The new [Observability for Kubernetes Operator](https://github.com/wavefrontHQ/observability-for-kubernetes) supports deploying the Collector and the Wavefront proxy in Kubernetes with a few clicks.
@@ -91,7 +91,7 @@ To use our Kubernetes Metrics Collector, you must set up our Kubernetes integrat
Our Kubernetes Metrics Collector supports monitoring for your Kubernetes infrastructure at all levels of the stack. See the [list of metrics collected by the Kubernetes Metrics Collector](kubernetes.html#metrics).
* Set up the Kubernetes Collector to have much of the monitoring happen automatically.
-* Fine-tune and customize the solution with configuration options available in the Operations for Applications Kubernetes Metrics Collector.
+* Fine-tune and customize the solution with configuration options available in the Tanzu Observability Kubernetes Metrics Collector.
{% include tip.html content="To avoid [high-cardinality](cardinality.html) and ensure optimal [query performance](query_language_performance.html), consider reducing the retention period of the Kubernetes metrics from 18 months (default) to 28 days. For that purpose, convert the `kubernetes.` metrics namespace from persistent to ephemeral. For details, see [Change the Retention Period of Metrics](metrics_managing.html#change-the-retention-period-of-metrics)." %}
@@ -99,7 +99,7 @@ Our Kubernetes Metrics Collector supports monitoring for your Kubernetes infrast
Our Kubernetes Metrics Collector collects metrics to give comprehensive insight into all layers of your Kubernetes environment, such as nodes, pods, services, and config maps.
-Depending on the selected setup, metrics are sent to the Wavefront proxy and from there to the VMware Aria Operations for Applications service. It's possible to send metrics using direct ingestion, but the Wavefront proxy is preferred for most cases.
+Depending on the selected setup, metrics are sent to the Wavefront proxy and from there to our service. It's possible to send metrics using direct ingestion, but the Wavefront proxy is preferred for most cases.
@@ -109,7 +109,7 @@ The collector runs as a DaemonSet for high scalability and supports leader elect
The Kubernetes Metrics Collector supports automatic monitoring of host-level metrics and host-level `systemd` metrics. When you set up the collector, it auto-discovers pods and services in your environment and starts collecting host-level metrics.
-You can [filter the metrics](https://github.com/wavefrontHQ/wavefront-kubernetes-collector/blob/main/docs/filtering.md) before they are reported to the VMware Aria Operations for Applications service.
+You can [filter the metrics](https://github.com/wavefrontHQ/wavefront-kubernetes-collector/blob/main/docs/filtering.md) before they are reported to our service.
### Application Monitoring
@@ -260,7 +260,7 @@ The default Kubernetes infrastructure can include a [Horizontal Pod Autoscaler](
Our [Horizontal Pod Autoscaler Adapter](https://www.github.com/wavefrontHQ/wavefront-kubernetes-adapter) allows you to scale based on *any* metric that it knows about.
-For example, you can scale based on networking or disk metrics, or any application metrics that are available to VMware Aria Operations for Applications. The Autoscaler Adapter sends the recommendation to the Horizontal Pod Autoscaler, and the Kubernetes environment is kept healthy as a result.
+For example, you can scale based on networking or disk metrics, or any application metrics that are available to Tanzu Observability. The Autoscaler Adapter sends the recommendation to the Horizontal Pod Autoscaler, and the Kubernetes environment is kept healthy as a result.
diff --git a/pages/doc/wavefront_kubernetes_faq.md b/pages/doc/wavefront_kubernetes_faq.md
index 8f9500f46..acb8fc388 100644
--- a/pages/doc/wavefront_kubernetes_faq.md
+++ b/pages/doc/wavefront_kubernetes_faq.md
@@ -4,10 +4,10 @@ keywords: containers, kubernetes
tags: [containers, kubernetes]
sidebar: doc_sidebar
permalink: wavefront_kubernetes_faq.html
-summary: Answers about viewing Kubernetes metrics in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Answers about viewing Kubernetes metrics in Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-The [Kubernetes Metrics Collector on GitHub](https://github.com/wavefrontHQ/observability-for-kubernetes) enables monitoring Kubernetes clusters and sending metrics to VMware Aria Operations for Applications. Much of the doc for the project is in the [docs folder on GitHub](https://github.com/wavefrontHQ/observability-for-kubernetes/tree/main/docs/collector). This page has some special tips and tricks to help you create the user experience you're after.
+The [Kubernetes Metrics Collector on GitHub](https://github.com/wavefrontHQ/observability-for-kubernetes) enables monitoring Kubernetes clusters and sending metrics to Tanzu Observability. Much of the doc for the project is in the [docs folder on GitHub](https://github.com/wavefrontHQ/observability-for-kubernetes/tree/main/docs/collector). This page has some special tips and tricks to help you create the user experience you're after.
From eeb1e68b249f283ac3cd8f247c93d6342c60d736 Mon Sep 17 00:00:00 2001
From: shavidissa
Date: Thu, 21 Mar 2024 08:48:31 -0700
Subject: [PATCH 11/26] rename Springboot and some tracing pages
---
pages/doc/opentelemetry_overview.md | 2 +-
.../opentracing_to_opentelemetry_migration.md | 8 +-
pages/doc/trace_data_details.md | 96 +++++++++----------
pages/doc/tracing_basics.md | 12 +--
pages/doc/tracing_service_dashboard.md | 4 +-
pages/doc/tracing_ui_overview.md | 6 +-
pages/doc/wavefront_spring_boot.md | 20 ++--
pages/doc/wavefront_spring_boot3.md | 38 ++++----
pages/doc/wavefront_spring_boot_faq.md | 2 +-
9 files changed, 94 insertions(+), 94 deletions(-)
diff --git a/pages/doc/opentelemetry_overview.md b/pages/doc/opentelemetry_overview.md
index 80dadfb3d..4a9efc85d 100644
--- a/pages/doc/opentelemetry_overview.md
+++ b/pages/doc/opentelemetry_overview.md
@@ -6,5 +6,5 @@ source: opentelemetry-examples
tags: [tracing]
sidebar: doc_sidebar
permalink: opentelemetry_overview.html
-summary: Send OpenTelemetry traces and metrics data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Send OpenTelemetry traces and metrics data to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
\ No newline at end of file
diff --git a/pages/doc/opentracing_to_opentelemetry_migration.md b/pages/doc/opentracing_to_opentelemetry_migration.md
index 96e488c61..ea0ad5c87 100644
--- a/pages/doc/opentracing_to_opentelemetry_migration.md
+++ b/pages/doc/opentracing_to_opentelemetry_migration.md
@@ -7,7 +7,7 @@ permalink: opentracing_to_opentelemetry_migration.html
summary: Migrate your Java application from OpenTracing to use OpenTelemetry.
---
-OpenTracing is deprecated. ([OpenTracing](https://opentracing.io/) and [OpenCensus](https://opencensus.io/) have merged to form [OpenTelemetry](https://opentelemetry.io/).) To send trace data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront), use OpenTelemetry.
+OpenTracing is deprecated. ([OpenTracing](https://opentracing.io/) and [OpenCensus](https://opencensus.io/) have merged to form [OpenTelemetry](https://opentelemetry.io/).) To send trace data to Tanzu Observability (formerly known as VMware Aria Operations for Applications)), use OpenTelemetry.
{% include note.html content="Read the [OpenTelemetry documentation](https://opentelemetry.io/docs/migration/opentracing/) for migration options and strategies." %}
@@ -153,7 +153,7 @@ public class OTelConfig {
## Create Your Tracer
-For OpenTracing, you created the tracer using the Operations for Applications SDKs. To create the Tracer for OpenTelemetry, use the OpenTracing Shim.
+For OpenTracing, you created the tracer using the Tanzu Observability SDKs. To create the Tracer for OpenTelemetry, use the OpenTracing Shim.
1. Create the tracer using the OpenTelemetry to OpenTracing Shim.
Example:
@@ -168,8 +168,8 @@ For OpenTracing, you created the tracer using the Operations for Applications SD
Resource resource = OTelConfig.resource(appName, serviceName);
```
-Save the changes and run the application to send the trace data to Operations for Applications.
+Save the changes and run the application to send the trace data to Tanzu Observability.
## Next Steps
-For details on configuring your application to send traces or metrics to Operations for Applications using the Wavefront proxy or the OpenTelemetry Collector, see [Send OpenTelemetry Data](opentelemetry_tracing.html).
+For details on configuring your application to send traces or metrics to Tanzu Observability using the Wavefront proxy or the OpenTelemetry Collector, see [Send OpenTelemetry Data](opentelemetry_tracing.html).
diff --git a/pages/doc/trace_data_details.md b/pages/doc/trace_data_details.md
index e8f961441..f05c8c9ae 100644
--- a/pages/doc/trace_data_details.md
+++ b/pages/doc/trace_data_details.md
@@ -7,7 +7,7 @@ permalink: trace_data_details.html
summary: Get to know the concepts around distributed tracing.
---
-{% include important.html content="OpenTracing is deprecated. ([OpenTracing](https://opentracing.io/) and [OpenCensus](https://opencensus.io/) have merged to form [OpenTelemetry](https://opentelemetry.io/).) To send trace data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront), use OpenTelemetry."%}
+{% include important.html content="OpenTracing is deprecated. ([OpenTracing](https://opentracing.io/) and [OpenCensus](https://opencensus.io/) have merged to form [OpenTelemetry](https://opentelemetry.io/).) To send trace data to Tanzu Observability (formerly known as VMware Aria Operations for Applications), use OpenTelemetry."%}
## Traces
@@ -38,24 +38,24 @@ You can think of the trace as a tree of related spans. The trace has a unique tr
## Spans
-A trace consists of one or more spans, which are the individual segments of work in the trace. Each Operations for Applications span represents time spent by an operation in a service (often a microservice).
+A trace consists of one or more spans, which are the individual segments of work in the trace. Each Tanzu Observability span represents time spent by an operation in a service (often a microservice).
Spans are the fundamental units of trace data. This page provides details about the format we use for a span, and the RED metrics that we automatically derive from each span. These details are useful for advanced customization.
-### Operations for Applications Span Format
+### Tanzu Observability Span Format
-A well-formed Operations for Applications span consists of fields and span tags that capture span attributes. We use these to identify and describe a span, organize it into a trace, and display the trace according to the service and application that emitted it. Some attributes are required by the OpenTelemetry specification and others are required by the Operations for Applications service.
+A well-formed Tanzu Observability span consists of fields and span tags that capture span attributes. We use these to identify and describe a span, organize it into a trace, and display the trace according to the service and application that emitted it. Some attributes are required by the OpenTelemetry specification and others are required by the Tanzu Observability service.
-Most use cases do not require you to know exactly how the Operations for Applications service expects a span to be formatted:
+Most use cases do not require you to know exactly how the Tanzu Observability service expects a span to be formatted:
* When you instrument your application with OpenTelemetry your application emits spans with the required tags.
* When you instrument your application with a [sender SDK](wavefront_sdks.html#sdks-for-sending-raw-data), your application emits spans that are automatically constructed from raw data you pass as parameters.
* When you instrument your application with a 3rd party distributed tracing system (Jaeger or Zipkin), your application emits spans that are automatically transformed by the [integration](tracing_integrations.html#tracing-system-integrations-and-exporters) you set up.
-It is possible to manually construct a well-formed span and send it either [directly to the Operations for Applications service](direct_ingestion.html#trace-data-spans) or to a TCP port that the Wavefront proxy is listening on for trace data. You might want to do this if you instrumented your application with a proprietary distributed tracing system.
+It is possible to manually construct a well-formed span and send it either [directly to the Tanzu Observability service](direct_ingestion.html#trace-data-spans) or to a TCP port that the Wavefront proxy is listening on for trace data. You might want to do this if you instrumented your application with a proprietary distributed tracing system.
{{site.data.alerts.important}}
The valid characters in an application and service name are: a-z, A-Z, 0-9, hyphen ("-"), underscore ("_"), dot ("."), forward slash ("/") and comma (",").
-
If your application or service names have any other characters other than the valid characters, the Operations for Applications service replaces each of those characters with a hyphen ("-").
+
If your application or service names have any other characters other than the valid characters, the Tanzu Observability service replaces each of those characters with a hyphen ("-").
{{site.data.alerts.end}}
@@ -166,7 +166,7 @@ Here’s the maximum number of characters for span tags:
Span tag key
128
-
If the span tag key exceeds the maximum length, the span associated with it is blocked by the Operations for Applications service.
+
If the span tag key exceeds the maximum length, the span associated with it is blocked by the Tanzu Observability service.
Span tag value
@@ -210,7 +210,7 @@ The following table lists span tags that contain information about the span's id
-The following table lists span tags that describe the architecture of the instrumented application that emitted the span. We use these tags to aggregate and filter trace data at different levels of granularity. These tags correspond to the [application tags](#how-the-operations-for-applications-uses-application-tags) you set through an Operations for Applications SDK.
+The following table lists span tags that describe the architecture of the instrumented application that emitted the span. We use these tags to aggregate and filter trace data at different levels of granularity. These tags correspond to the [application tags](#how-the-tanzu-observability-uses-application-tags) you set through an Tanzu Observability SDK.
@@ -228,7 +228,7 @@ The following table lists span tags that describe the architecture of the instru
Yes
Name of the instrumented application that emitted the span.
The valid characters are: a-z, A-Z, 0-9, hyphen ("-"), underscore ("_"), dot ("."), forward slash ("/") and comma (",").
-
If your application or service names have special characters, Operations for Applications replaces each special character with a hyphen ("-").
+
If your application or service names have special characters, Tanzu Observability replaces each special character with a hyphen ("-").
String
@@ -238,7 +238,7 @@ The following table lists span tags that describe the architecture of the instru
Name of the instrumented microservice that emitted the span.
The valid characters are: a-z, A-Z, 0-9, hyphen ("-"), underscore ("_"), dot ("."), forward slash ("/") and comma (",").
-
If your application or service names have special characters, Operations for Applications replaces each special character with a hyphen ("-").
+
If your application or service names have special characters, Tanzu Observability replaces each special character with a hyphen ("-").
String
@@ -274,9 +274,9 @@ Because operations are normally composed of other operations, each span is norma
### Time-Value Precision in Spans
-A span has two time-value fields for specifying the start time (`start_milliseconds`) and duration (`duration_milliseconds`). Express these values in milliseconds, because Operations for Applications uses milliseconds for span storage and visualization. For convenience, you can specify time values in other units, and we convert them to milliseconds.
+A span has two time-value fields for specifying the start time (`start_milliseconds`) and duration (`duration_milliseconds`). Express these values in milliseconds, because Tanzu Observability uses milliseconds for span storage and visualization. For convenience, you can specify time values in other units, and we convert them to milliseconds.
-You must use the same precision for _both_ time values. Operations for Applications identifies the precision of the `start_milliseconds` value, and interprets the `duration_milliseconds` value using the same unit. The following table shows how to indicate the start-time precision:
+You must use the same precision for _both_ time values. Tanzu Observability identifies the precision of the `start_milliseconds` value, and interprets the `duration_milliseconds` value using the same unit. The following table shows how to indicate the start-time precision:
@@ -322,9 +322,9 @@ You must use the same precision for _both_ time values. Operations for Applicati
-{% include note.html content="When specifying a span in Operations for Applications span format, adjust values as necessary so that the units match." %}
+{% include note.html content="When specifying a span in Tanzu Observability span format, adjust values as necessary so that the units match." %}
-For example, suppose you know a span started at `1533529977627` epoch milliseconds, and lasted for `3` seconds. In Operations for Applications span format, you could specify either of the following pairs of time values:
+For example, suppose you know a span started at `1533529977627` epoch milliseconds, and lasted for `3` seconds. In Tanzu Observability span format, you could specify either of the following pairs of time values:
| `1533529977` | `3` | (both values in seconds) |
| `1533529977627` | `3000` | (both values in milliseconds) |
@@ -337,7 +337,7 @@ For example, suppose you know a span started at `1533529977627` epoch millisecon
### Indexed and Unindexed Span Tags
-Operations for Applications uses indexes to optimize the performance of queries that filter on certain span tags. For example, we index the application tags (`application`, `service`, `cluster`, `shard`) so you can quickly query for spans that represent operations from a particular application, service, cluster, or shard. We also index certain built-in span tags, such as `span.kind`, `component`, `http.method`, and `error`.
+Tanzu Observability uses indexes to optimize the performance of queries that filter on certain span tags. For example, we index the application tags (`application`, `service`, `cluster`, `shard`) so you can quickly query for spans that represent operations from a particular application, service, cluster, or shard. We also index certain built-in span tags, such as `span.kind`, `component`, `http.method`, and `error`.
For performance reasons, we automatically index built-in span tags with low cardinality. (A tag with low cardinality has comparatively few unique values that can be assigned to it.) So, for example, a tag like `spanId` is not indexed.
@@ -356,7 +356,7 @@ In the [Application Map](tracing_ui_overview.html#application-map-features), tra
In the image shown below each arrow shows tracing traffic between application components. The arrows show direction of traffic.
-
+
To understand how to query for tracing traffic in the tracing browser, see [Use Spans to Examine Applications and Services](spans_function.html#spans-operators).
@@ -368,7 +368,7 @@ To understand how to query for tracing traffic in the tracing browser, see [Use
## RED Metrics
-Operations for Applications derives RED metrics from the spans that are sent from the instrumented application. We automatically aggregate and display RED metrics for different levels of detail with no additional configuration or instrumentation on your part.
+Tanzu Observability derives RED metrics from the spans that are sent from the instrumented application. We automatically aggregate and display RED metrics for different levels of detail with no additional configuration or instrumentation on your part.
RED metrics are key indicators of the health of your services, and you can use them to help you discover problem traces. RED metrics are measures of:
@@ -378,7 +378,7 @@ RED metrics are key indicators of the health of your services, and you can use t
### Span RED Metrics and Trace RED Metrics
-Operations for Applications uses ingested spans to derive RED metrics for two kinds of request:
+Tanzu Observability uses ingested spans to derive RED metrics for two kinds of request:
* Span RED metrics measure individual operations, typically within a single service. For example, a span RED metric might measure the number of calls per minute to the `dispatch` operation in the `delivery` service.
We use span RED metrics as the basis for certain predefined charts, such as the [Service Dashboard](/tracing_service_dashboard.html).
@@ -397,11 +397,11 @@ Operations for Applications uses ingested spans to derive RED metrics for two ki
### RED Metric Counters and Histograms
-In the predefined charts, such as the Service Dashboard, are rates and 95th percentile distributions. These metrics are themselves based on underlying delta counters and histograms that Operations for Applications automatically derives from spans. You can use these underlying delta counters and histograms in [RED metrics queries](#red-metrics-queries), for example, to create alerts on trace data.
+In the predefined charts, such as the Service Dashboard, are rates and 95th percentile distributions. These metrics are themselves based on underlying delta counters and histograms that Tanzu Observability automatically derives from spans. You can use these underlying delta counters and histograms in [RED metrics queries](#red-metrics-queries), for example, to create alerts on trace data.
-Operations for Applications constructs the names of the underlying delta counters and histograms as shown in the table below. The name components ``, ``, and `` are string values that are obtained from the spans on which the metrics are derived. If necessary, Operations for Applications modifies these strings to comply with the [Operations for Applications data format](wavefront_data_format.html#operations-for-applications-data-format-fields) for metrics. Each metric is associated with point tags `application`, `service`, and `operationName`, and the corresponding span tag values are assigned to these point tags. The span tag values are used without modification.
+Tanzu Observability constructs the names of the underlying delta counters and histograms as shown in the table below. The name components ``, ``, and `` are string values that are obtained from the spans on which the metrics are derived. If necessary, Tanzu Observability modifies these strings to comply with the [Tanzu Observability data format](wavefront_data_format.html#tanzu-observability-data-format-fields) for metrics. Each metric is associated with point tags `application`, `service`, and `operationName`, and the corresponding span tag values are assigned to these point tags. The span tag values are used without modification.
-{% include warning.html content="Do not configure the Wavefront proxy to add prefixes to metric names. Doing so will change the names of the RED metric counters and histograms, and prevent these metrics from appearing in the Operations for Applications UI, e.g., in the Service Dashboard." %}
+{% include warning.html content="Do not configure the Wavefront proxy to add prefixes to metric names. Doing so will change the names of the RED metric counters and histograms, and prevent these metrics from appearing in the Tanzu Observability UI, e.g., in the Service Dashboard." %}
@@ -425,7 +425,7 @@ Operations for Applications constructs the names of the underlying delta counter
`tracing.derived....duration.micros.m`
-
Operations for Applications histogram
+
Tanzu Observability histogram
The duration of each invoked operation, in microseconds, aggregated in one-minute intervals. Used in the Duration chart that is generated for a service.
@@ -455,7 +455,7 @@ Operations for Applications constructs the names of the underlying delta counter
`tracing.root.derived....duration.millis.m`
-
Operations for Applications histogram
+
Tanzu Observability histogram
The duration of each trace, in milliseconds, aggregated in one-minute intervals. Duration is measured from the start of the earliest root span to the end of the last span in a trace.
@@ -498,12 +498,12 @@ You can specify the RED metric counters and histograms in a query with the metri
```
cs(tracing.derived.beachshirts.delivery.dispatch.error.count)
```
-* Use the point tags `application`, `service`, and `operationName` that Operations for Applications automatically associates with the metric, for example:
+* Use the point tags `application`, `service`, and `operationName` that Tanzu Observability automatically associates with the metric, for example:
```
cs(tracing.derived.*.invocation.count, application="beachshirts" and service="delivery" and operationName="dispatch")
```
-The point tag technique is useful when the metric name contains string values for ``, ``, and `` that have been modified to comply with the [Operations for Applications data format](wavefront_data_format.html#operations-for-applications-data-format-fields). The point tag value always corresponds exactly to the span tag values.
+The point tag technique is useful when the metric name contains string values for ``, ``, and `` that have been modified to comply with the [Tanzu Observability data format](wavefront_data_format.html#tanzu-observability-data-format-fields). The point tag value always corresponds exactly to the span tag values.
@@ -515,7 +515,7 @@ The point tag technique is useful when the metric name contains string values fo
Pre-aggregated RED metrics speed up RED metric queries. service level RED metrics by aggregating the [RED metrics derived from spans](#span-red-metrics-and-trace-red-metrics). Querying and aggregating these metrics can be slow due to high cardinality from operation tags, source tags, and custom tags.
-Operations for Applications constructs the names of the underlying aggregated delta counters, and histograms as shown in the table below. The `` and `` in the name are string values that are obtained from the spans from which the metrics are derived. You can filter the aggregated RED metrics using the `application`, `service`, `cluster`, `shard`, `source`, and `span.kind` point tags. The screenshot below filters by application. Operations for Applications assigns the corresponding span tag values to these point tags.
+Tanzu Observability constructs the names of the underlying aggregated delta counters, and histograms as shown in the table below. The `` and `` in the name are string values that are obtained from the spans from which the metrics are derived. You can filter the aggregated RED metrics using the `application`, `service`, `cluster`, `shard`, `source`, and `span.kind` point tags. The screenshot below filters by application. Tanzu Observability assigns the corresponding span tag values to these point tags.
{% include note.html content="To filter RED metrics using operation names, sources, or [custom span tags](tracing_customize_spans_and_alerts.html), use [RED metrics derived from spans](#span-red-metrics-and-trace-red-metrics)." %}
@@ -544,7 +544,7 @@ Operations for Applications constructs the names of the underlying aggregated de
`tracing.aggregated.derived...duration.millis.m`
-
Operations for Applications histogram
+
Tanzu Observability histogram
Duration of each spans, in microseconds, aggregated in one-minute intervals. Duration is measured from the start of the earliest root span to the end of the last span in a trace.
@@ -696,7 +696,7 @@ You can visualize tracing traffic data in charts using tracing traffic derived m
`tracing.edge.derived...duration.millis.m`
-
Operations for Applications histogram
+
Tanzu Observability histogram
Duration of the request in milliseconds, aggregated in one-minute intervals.
@@ -712,7 +712,7 @@ You can visualize tracing traffic data in charts using tracing traffic derived m
```
cs(tracing.edge.derived.beachshirts.shopping.error.count, cluster=us-west)
```
-* Duration in the form of Operations for Applications histograms.
+* Duration in the form of Tanzu Observability histograms.
```
hs(tracing.edge.derived.beachshirts.shopping.duration.millis.m, to.service=delivery)
```
@@ -735,9 +735,9 @@ The Tracing Browser shows you all the spans that make up a trace and the critica
### Trace Sampling and Derived RED Metrics
-If you have instrumented your application with an Operations for Applications SDK, Operations for Applications derives the RED metrics from 100% of the generated spans, _before_ any sampling is performed. This is true when the sampling is performed by the SDK or when the sampling is performed by a Wavefront proxy. Consequently, the RED metrics provide a highly accurate picture of your application's behavior. However, if you click through a chart to inspect a particular trace, you might discover that the trace has not actually been ingested. You can consider configuring a less restrictive [sampling strategy](trace_data_sampling.html).
+If you have instrumented your application with an Tanzu Observability SDK, Tanzu Observability derives the RED metrics from 100% of the generated spans, _before_ any sampling is performed. This is true when the sampling is performed by the SDK or when the sampling is performed by a Wavefront proxy. Consequently, the RED metrics provide a highly accurate picture of your application's behavior. However, if you click through a chart to inspect a particular trace, you might discover that the trace has not actually been ingested. You can consider configuring a less restrictive [sampling strategy](trace_data_sampling.html).
-If you have instrumented your application using a 3rd party distributed tracing system, Operations for Applications derives the RED metrics _after_ sampling has occurred. The Wavefront proxy receives only a subset of the generated spans, and the derived RED metrics will reflect just that subset. See [Trace Sampling and RED Metrics from an Integration](tracing_integrations.html#trace-sampling-and-red-metrics-from-an-integration).
+If you have instrumented your application using a 3rd party distributed tracing system, Tanzu Observability derives the RED metrics _after_ sampling has occurred. The Wavefront proxy receives only a subset of the generated spans, and the derived RED metrics will reflect just that subset. See [Trace Sampling and RED Metrics from an Integration](tracing_integrations.html#trace-sampling-and-red-metrics-from-an-integration).
@@ -761,7 +761,7 @@ Amazon Simple Notification Service (SNS), and external databases. For details, s
## Apdex
The Application Performance Index ([Apdex](https://www.apdex.org)) helps you understand how the response time of a service compares to the predefined response time threshold.
-Operations for Applications detects ingested application trace data as first-class citizens and calculates the Apdex score using the threshold value (T) you define. The default threshold value (T) is set to 100ms, and only Super Admin users and users with the [**Applications** permission](permissions_overview.html) can configure the threshold value.
+Tanzu Observability detects ingested application trace data as first-class citizens and calculates the Apdex score using the threshold value (T) you define. The default threshold value (T) is set to 100ms, and only Super Admin users and users with the [**Applications** permission](permissions_overview.html) can configure the threshold value.
@@ -868,14 +868,14 @@ Trace data is reported automatically whenever spans are complete, so a `Wavefron
### Metrics Reporter Objects
-You can use one or more reporter objects to gather metrics and histograms and forward that data to the Wavefront sender. Different Operations for Applications reporter objects gather data from different components of your application. For example, a `WavefrontJvmReporter` reports runtime data from the JVM.
+You can use one or more reporter objects to gather metrics and histograms and forward that data to the Wavefront sender. Different Tanzu Observability reporter objects gather data from different components of your application. For example, a `WavefrontJvmReporter` reports runtime data from the JVM.
-An Operations for Applications reporter object specifies:
-* The reporting interval for metrics and histograms. The reporting interval controls how often data is reported to the Wavefront sender and therefore determines the timestamps of data points sent to Operations for Applications. The default reporting interval is once a minute.
+An Tanzu Observability reporter object specifies:
+* The reporting interval for metrics and histograms. The reporting interval controls how often data is reported to the Wavefront sender and therefore determines the timestamps of data points sent to Tanzu Observability. The default reporting interval is once a minute.
* The source of the reported metrics and histograms -- by default, the host that the code is running on. You can optionally specify a more useful source name explicitly during setup, for example, an IP address, a container or instance name, or some other unique data source. All reporter objects for a particular microservice must specify the same source.
-{% include note.html content="You can use an Operations for Applications reporter object to set a nondefault reporting interval." %}
+{% include note.html content="You can use an Tanzu Observability reporter object to set a nondefault reporting interval." %}
diff --git a/pages/doc/tracing_basics.md b/pages/doc/tracing_basics.md
index c574c6fe6..a802172c4 100644
--- a/pages/doc/tracing_basics.md
+++ b/pages/doc/tracing_basics.md
@@ -11,7 +11,7 @@ Distributed tracing enables you to track the flow of work that is performed by a
In an application that consists of multiple services, an incoming request typically starts a chain of requests that are propagated from one service to the next. Distributed tracing gives you end-to-end visibility into that chain across services, even when those services are running in different environments.
-In VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront), you can use the tracing dashboards and browsers to:
+In Tanzu Observability (formerly known as VMware Aria Operations for Applications), you can use the tracing dashboards and browsers to:
* Monitor your application to make sure its response times are as expected.
* Troubleshoot and analyze reported errors.
@@ -21,7 +21,7 @@ In VMware Aria Operations for Applications (formerly known as Tanzu Observabilit
Watch these videos to listen to our co-founder Clement Pang introduce distributed tracing, and give updates including improved ingestion options and intelligent sampling. Note that these videos were created in 2019 and 2020 and some of the information in them might have changed.
-{% include note.html content="You need either the [**Proxies** permission](permissions_overview.html) or [**Direct Data Ingestion** permission](permissions_overview.html) to send trace data from your application to the Wavefront proxy or the Operations for Applications service." %}
+{% include note.html content="You need either the [**Proxies** permission](permissions_overview.html) or [**Direct Data Ingestion** permission](permissions_overview.html) to send trace data from your application to the Wavefront proxy or the Tanzu Observability service." %}
@@ -33,10 +33,10 @@ Watch these videos to listen to our co-founder Clement Pang introduce distribute
## Instrument Your Application
-OpenTracing is deprecated. ([OpenTracing](https://opentracing.io/) and [OpenCensus](https://opencensus.io/) have merged to form [OpenTelemetry](https://opentelemetry.io/).) To send trace data to Operations for Applications, use OpenTelemetry.
+OpenTracing is deprecated. ([OpenTracing](https://opentracing.io/) and [OpenCensus](https://opencensus.io/) have merged to form [OpenTelemetry](https://opentelemetry.io/).) To send trace data to Tanzu Observability, use OpenTelemetry.
If your application uses an OpenTelemetry SDK, you can configure the application to send trace data [to the Wavefront proxy](opentelemetry_overview.html)
-
+
## Visualize Distributed Tracing Data
@@ -53,7 +53,7 @@ Get an overview of how the applications and services are linked, understand the
* [**Table view**](tracing_ui_overview.html#table-view-features) lists the applications and services in the form of a table. You can see the Request, Error, and Duration (RED) metrics at a glance and sort the data.
-
+
* [**Grid view**](tracing_ui_overview.html#grid-view-features) lists the application and services in a grid. You can see the RED metrics for each of the application’s services.
@@ -81,7 +81,7 @@ You can export traces you view in the Traces Browser, save them locally as JSON
### Create a Sampling Policy
-Our intelligent sampling algorithm reduces the volume of ingested traces. The goals of intelligent sampling are to retain traces that are likely to be informative. But sometimes intelligent sampling discards traces that you want to keep. You can [create a sampling policy](trace_sampling_policies.html) to fine-tune intelligent sampling and let the Operations for Applications service know that you want to keep certain spans.
+Our intelligent sampling algorithm reduces the volume of ingested traces. The goals of intelligent sampling are to retain traces that are likely to be informative. But sometimes intelligent sampling discards traces that you want to keep. You can [create a sampling policy](trace_sampling_policies.html) to fine-tune intelligent sampling and let the Tanzu Observability service know that you want to keep certain spans.
diff --git a/pages/doc/tracing_service_dashboard.md b/pages/doc/tracing_service_dashboard.md
index e1f37707c..348465205 100644
--- a/pages/doc/tracing_service_dashboard.md
+++ b/pages/doc/tracing_service_dashboard.md
@@ -7,7 +7,7 @@ permalink: tracing_service_dashboard.html
summary: Identify potential hot spots of a service.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes the Service Dashboard, which you can use to identify potential hot spots of a service, and then drill down to the Traces Browser.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Service Dashboard, which you can use to identify potential hot spots of a service, and then drill down to the Traces Browser.
## Explore the Default Service Dashboard
@@ -43,7 +43,7 @@ style="vertical-align:text-bottom;width:25px" alt="icon to click to get the link
* Select a region of the histogram chart and click **Search Traces** to view the traces for the selected duration.
* Click a bar on a TopK chart.
* Click the vertical ellipsis in the top right of any chart, click **Traces**, and click a service.
- {% include note.html content="If you don’t see **Traces**, check whether your metrics include `application` and `service point` tags.
These tags are defined when you instrument your application for tracing via [Application tags](trace_data_details.html#application-tags). If your application is already sending this data to the Operations for Applications service via the Wavefront proxy, you can add point tags using [Wavefront proxy preprocessor rules](proxies_preprocessor_rules.html#addtag-and-addtagifnotexists)." %}
+ {% include note.html content="If you don’t see **Traces**, check whether your metrics include `application` and `service point` tags.
These tags are defined when you instrument your application for tracing via [Application tags](trace_data_details.html#application-tags). If your application is already sending this data to the Tanzu Observability service via the Wavefront proxy, you can add point tags using [Wavefront proxy preprocessor rules](proxies_preprocessor_rules.html#addtag-and-addtagifnotexists)." %}
## Custom Service Dashboard
diff --git a/pages/doc/tracing_ui_overview.md b/pages/doc/tracing_ui_overview.md
index e42c945c9..25431cf48 100644
--- a/pages/doc/tracing_ui_overview.md
+++ b/pages/doc/tracing_ui_overview.md
@@ -4,10 +4,10 @@ keywords: data, distributed tracing
tags: [tracing]
sidebar: doc_sidebar
permalink: tracing_ui_overview.html
-summary: Overview of services and applications that send data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Overview of services and applications that send data to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-As part of troubleshooting an application, you need an overview of the services and applications that send data to Operations for Applications. Use our application map to understand the health of each service, and troubleshoot when your applications or services run into issues. You can see the overall health of each application using the application map, table view, and grid view.
+As part of troubleshooting an application, you need an overview of the services and applications that send data to Tanzu Observability. Use our application map to understand the health of each service, and troubleshoot when your applications or services run into issues. You can see the overall health of each application using the application map, table view, and grid view.
@@ -177,7 +177,7 @@ See the table view:
1. From the toolbar, select **Applications** > **Application Status** and click the Table View icon ( )
-
+
Using the table view, you can:
* Examine the applications and services, or search for a particular application or service by applying filters.
diff --git a/pages/doc/wavefront_spring_boot.md b/pages/doc/wavefront_spring_boot.md
index 7cdff848a..324df7e23 100644
--- a/pages/doc/wavefront_spring_boot.md
+++ b/pages/doc/wavefront_spring_boot.md
@@ -4,7 +4,7 @@ keywords:
tags:
sidebar: doc_sidebar
permalink: wavefront_springboot.html
-summary: Examine Spring Boot 2 data in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) dashboards and charts
+summary: Examine Spring Boot 2 data in Tanzu Observability (formerly known as VMware Aria Operations for Applications) dashboards and charts
---
Wavefront for Spring Boot allows you to quickly configure your environment, so Spring Boot 2 components send metrics, histograms, and traces/spans to our service.
@@ -57,8 +57,8 @@ This is the default dashboard you see when you run the Spring Boot initializer.
Getting started is easy. Here are some things to know before you start:
* **Ingestion Method**: Wavefront for Spring Boot sends data to our service via [direct ingestion](direct_ingestion.html) by default. You can [configure your application to send data via the Wavefront proxy](#proxy).
-* **Target**: Wavefront for Spring Boot sends data to the freemium instance by default. You can [configure your application to send data to your Operations for Applications instance](#step-2-optional-specify-your-operations-for-applications-instance).
-* **Account**: By default, the starter sends you to the Freemium instance, auto-negotiates an account, and saves the API token in the `~/.wavefront_freemium` file in your home directory. If you customize the starter to go to your Operations for Applications instance (see Step 2 below) you need to include an API token for that instance.
+* **Target**: Wavefront for Spring Boot sends data to the freemium instance by default. You can [configure your application to send data to your Tanzu Observability instance](#step-2-optional-specify-your-tanzu-observability-instance).
+* **Account**: By default, the starter sends you to the Freemium instance, auto-negotiates an account, and saves the API token in the `~/.wavefront_freemium` file in your home directory. If you customize the starter to go to your Tanzu Observability instance (see Step 2 below) you need to include an API token for that instance.
### Prerequisites for Wavefront Spring Boot Starter
@@ -307,17 +307,17 @@ dependencies {
-### Step 2 (Optional): Specify Your Operations for Applications Instance
+### Step 2 (Optional): Specify Your Tanzu Observability Instance
-By default, the Wavefront Spring Boot Starter creates an account for you and sends data to the Freemium instance. If you already have an Operations for Applications account, you can send data there instead by specifying the `uri` and `api-token` properties, as follows:
+By default, the Wavefront Spring Boot Starter creates an account for you and sends data to the Freemium instance. If you already have an Tanzu Observability account, you can send data there instead by specifying the `uri` and `api-token` properties, as follows:
```
management.metrics.export.wavefront.api-token=$API_Token
management.metrics.export.wavefront.uri=$wavefront_instance
```
-* `$API_Token` is a valid [API token for your Operations for Applications instance](users_account_managing.html#generate-an-api-token).
-* `$wavefront_instance` is the name of your Operations for Applications instance, for example, `https://example.wavefront.com`.
+* `$API_Token` is a valid [API token for your Tanzu Observability instance](users_account_managing.html#generate-an-api-token).
+* `$wavefront_instance` is the name of your Tanzu Observability instance, for example, `https://example.wavefront.com`.
### Step 3: View Your Data in Our Service
@@ -391,7 +391,7 @@ You can invite users and let them send data to the same cluster:
```
wavefront.freemium-account=true
```
- {% include tip.html content="If you don’t want Operations for Applications to auto-negotiate a freemium account for you, set the value to `false`."%}
+ {% include tip.html content="If you don’t want Tanzu Observability to auto-negotiate a freemium account for you, set the value to `false`."%}
1. Restart your application.
@@ -408,7 +408,7 @@ management.metrics.export.wavefront.uri=proxy://:2878
Access the Dashboard with the Actuator Endpoint
-If you have a web app, you can expose the Operations for Applications Actuator endpoint at `/actuator/wavefront` to access your Operations for Applications dashboard.
+If you have a web app, you can expose the Tanzu Observability Actuator endpoint at `/actuator/wavefront` to access your Tanzu Observability dashboard.
Example:
```
management.endpoints.web.exposure.include=health,info,...,wavefront
@@ -447,7 +447,7 @@ You can configure the cluster and shard the same way. This information is used t
## Wavefront Spring Boot Integration
-If you already have an Operations for Applications account, you can start the setup and examine the dashboards from the Wavefront Spring Boot integration. This is supported for [free trial accounts](https://tanzu.vmware.com/observability).
+If you already have an Tanzu Observability account, you can start the setup and examine the dashboards from the Wavefront Spring Boot integration. This is supported for [free trial accounts](https://tanzu.vmware.com/observability).
1. Select **Integrations**, search for Spring Boot, and click the Spring Boot integration.
1. Use the information displayed on the **Setup** tab to set up the integration.
diff --git a/pages/doc/wavefront_spring_boot3.md b/pages/doc/wavefront_spring_boot3.md
index 0a1b9bce5..e30d7bb88 100644
--- a/pages/doc/wavefront_spring_boot3.md
+++ b/pages/doc/wavefront_spring_boot3.md
@@ -4,7 +4,7 @@ keywords:
tags:
sidebar: doc_sidebar
permalink: wavefront_springboot3.html
-summary: Examine Spring Boot 3 data in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) dashboards and charts
+summary: Examine Spring Boot 3 data in Tanzu Observability (formerly known as VMware Aria Operations for Applications) dashboards and charts
---
Wavefront for Spring Boot allows you to quickly configure your environment, so Spring Boot 3 components send metrics, histograms, and traces or spans to our service.
@@ -56,8 +56,8 @@ This is the default dashboard you see when you run the Spring Boot initializer.
Getting started is easy. Here are some things to know before you start:
* **Ingestion Method**: Wavefront for Spring Boot sends data to our service via [direct ingestion](direct_ingestion.html) by default. You can [configure your application to send data via the Wavefront proxy](#proxy).
-* **Target**: Wavefront for Spring Boot sends data to our freemium instance. You can change the default behavior and [configure your application to send data to your Operations for Applications instance](#step-2-optional-specify-your-operations-for-applications-instance).
-* **Account**: By default, the starter sends you to the Freemium instance, auto-negotiates an account, and saves the API token in the `~/.wavefront_freemium` file in your home directory. If you customize the starter to go to your Operations for Applications instance (see Step 2 below), you must include an API token for that instance.
+* **Target**: Wavefront for Spring Boot sends data to our freemium instance. You can change the default behavior and [configure your application to send data to our service](#step-2-optional-specify-your-tanzu-observability-instance).
+* **Account**: By default, the starter sends you to the Freemium instance, auto-negotiates an account, and saves the API token in the `~/.wavefront_freemium` file in your home directory. If you customize the starter to go to and instance of our service (see Step 2 below), you must include an API token for that instance.
### Prerequisites for Wavefront Spring Boot Starter
@@ -136,7 +136,7 @@ Initialize a new project using the Spring Initializer or add the required depend
-
Follow these steps if you don't have an Operations for Applications account and need to use the freemium account.
+
Follow these steps if you don't have a Tanzu Observability account and need to use the freemium account.
Add the Wavefront dependency.
@@ -243,7 +243,7 @@ dependencies {
-
Follow these steps if you already have an Operations for Applications account.
+
Follow these steps if you already have a Tanzu Observability account.
Import the Wavefront for Spring Boot Bill of Materials (BOM) to your project.
@@ -318,15 +318,15 @@ dependencies {
- 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.
+ You need to Specify the VMware Cloud Services account instance or the Tanzu Observability 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.
-### Step 2 (Optional): Specify Your Operations for Applications Instance
+### Step 2 (Optional): Specify Your Tanzu Observability Instance
-By default, the Wavefront Spring Boot Starter creates an account for you and sends data to the Freemium instance. If you already have a VMware Cloud Services account or an Operations for Applications account, you can send data there instead by specifying the properties shown below:
+By default, the Wavefront Spring Boot Starter creates an account for you and sends data to the Freemium instance. If you already have a VMware Cloud Services account or an Tanzu Observability account, you can send data there instead by specifying the properties shown below:
- Replace {ENTER_WAVEFRONT_INSTANCE_URL} with the name of your Operations for Applications instance, for example, https://example.wavefront.com.
+ Replace {ENTER_WAVEFRONT_INSTANCE_URL} with the name of your Tanzu Observability instance, for example, https://example.wavefront.com.
- Replace {ENTER_CLIENT-ID} and {ENTER_SECRET} with the credentials (client ID and client secret) of an existing server-to-server OAuth app which has the Direct Data Ingestion service role assigned and is added to the VMware Cloud organization running the Operations for Applications service.
+ Replace {ENTER_CLIENT-ID} and {ENTER_SECRET} with the credentials (client ID and client secret) of an existing server-to-server OAuth app which has the Direct Data Ingestion service role assigned and is added to the VMware Cloud organization running the Tanzu Observability service.
The {OPTIONAL_ORG_ID} parameter is optional, and you can replace it with the long ID of the VMware Cloud organization running the service.
- Set wavefront.freemium-account as false. Because you have an Operations for Applications instance, you do not need a freemium account.
+ Set wavefront.freemium-account as false. Because you have an Tanzu Observability instance, you do not need a freemium account.
- Replace {ENTER_WAVEFRONT_INSTANCE_URL} with the name of your Operations for Applications instance, for example, https://example.wavefront.com.
+ Replace {ENTER_WAVEFRONT_INSTANCE_URL} with the name of your Tanzu Observability instance, for example, https://example.wavefront.com.
Replace {ENTER_CSP_API_TOKEN} with your VMware Cloud Services API token. The API token must be generated in the VMware Cloud Services Console by an active user account and must be assigned the Direct Data Ingestionservice role.
- Set wavefront.freemium-account as false. Because you have an Operations for Applications instance, you do not need a freemium account.
+ Set wavefront.freemium-account as false. Because you have an Tanzu Observability instance, you do not need a freemium account.
- Operations for Applications API Token: If you have an Operations for Applications account, add the following properties to authenticate with the API Token (legacy).
+ Tanzu Observability API Token: If you have an Tanzu Observability account, add the following properties to authenticate with the API Token (legacy).
- Replace {ENTER_WAVEFRONT_INSTANCE_URL} with the name of your Operations for Applications instance, for example, https://example.wavefront.com.
+ Replace {ENTER_WAVEFRONT_INSTANCE_URL} with the name of your Tanzu Observability instance, for example, https://example.wavefront.com.
- Replace {WAVEFRONT_INSTANCE_URL} with the name of your Operations for Applications instance, for example, https://example.wavefront.com.
+ Replace {WAVEFRONT_INSTANCE_URL} with the name of your Tanzu Observability instance, for example, https://example.wavefront.com.
- Set wavefront.freemium-account as false. Because you have an Operations for Applications instance, you do not need a freemium account.
+ Set wavefront.freemium-account as false. Because you have an Tanzu Observability instance, you do not need a freemium account.
@@ -474,7 +474,7 @@ You can invite users and let them send data to the same cluster:
```
wavefront.freemium-account=true
```
- {% include tip.html content="If you don’t want Operations for Applications to auto-negotiate a freemium account for you, set the value to `false`."%}
+ {% include tip.html content="If you don’t want Tanzu Observability to auto-negotiate a freemium account for you, set the value to `false`."%}
1. Restart your application.
@@ -522,7 +522,7 @@ You can configure the cluster and shard names under the `management.wavefront.ap
## Wavefront Spring Boot Integration
-If you already have an Operations for Applications account, you can start the setup and examine the dashboards from the Wavefront Spring Boot integration. This is supported for [free trial accounts](https://tanzu.vmware.com/observability).
+If you already have an Tanzu Observability account, you can start the setup and examine the dashboards from the Wavefront Spring Boot integration. This is supported for [free trial accounts](https://tanzu.vmware.com/observability).
1. Click **Integrations** on the toolbar, search for Spring Boot, and click the Spring Boot integration.
1. Use the information displayed on the **Setup** tab to set up the integration.
diff --git a/pages/doc/wavefront_spring_boot_faq.md b/pages/doc/wavefront_spring_boot_faq.md
index c3dbeb0a5..c569836c3 100644
--- a/pages/doc/wavefront_spring_boot_faq.md
+++ b/pages/doc/wavefront_spring_boot_faq.md
@@ -42,7 +42,7 @@ Production clusters currently offer 18 months of full-resolution (no downsamplin
* Currently, only our freemium cluster supports automatic account provisioning with Spring Boot. If you are using a different cluster, you won’t see a link.
* You have configured an API token in your application's `application.properties` file. If you want to see the link printed on the console, add `wavefront.freemium-account=true` to the `application.properties` file.
-* If you have a web application, expose the VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) actuator endpoint to easily access your dashboard.
+* If you have a web application, expose the Tanzu Observability (formerly known as VMware Aria Operations for Applications) actuator endpoint to easily access your dashboard.
## How Do I Ensure I Send Data to the Same Account All the Time (Across Multiple Machines and Deployments)?
* If you are just trying out our service, see [Manage Service Accounts](service-accounts.html) to create a service account that has a static token for reporting. Once you have the token, add it to the `application.properties` file.
From 55dec0f6340f6f9dacfc1ed3a51e04b1bc31d681 Mon Sep 17 00:00:00 2001
From: shavidissa
Date: Thu, 21 Mar 2024 11:33:21 -0700
Subject: [PATCH 12/26] rename the tracing pages
---
pages/doc/hs_adpex_function.md | 6 +--
pages/doc/trace_data_query.md | 4 +-
pages/doc/trace_data_sampling.md | 40 +++++++++----------
pages/doc/trace_sampling_policies.md | 4 +-
pages/doc/tracing_apdex.md | 6 +--
pages/doc/tracing_best_practices.md | 38 +++++++++---------
.../doc/tracing_customize_spans_and_alerts.md | 8 ++--
pages/doc/tracing_faq.md | 14 +++----
pages/doc/tracing_operation_dashboard.md | 2 +-
pages/doc/tracing_traces_browser.md | 6 +--
pages/doc/tracing_view_offline_traces.md | 4 +-
11 files changed, 66 insertions(+), 66 deletions(-)
diff --git a/pages/doc/hs_adpex_function.md b/pages/doc/hs_adpex_function.md
index 46b8f690c..5bde3eb52 100644
--- a/pages/doc/hs_adpex_function.md
+++ b/pages/doc/hs_adpex_function.md
@@ -97,7 +97,7 @@ Use the basic or advanced query format.
## Description
-You can use the basic or advanced `apdex()` function to query the Apdex score. VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) derives the Apdex score for each service. Therefore, you must specify the service you want to get the Apdex data.
+You can use the basic or advanced `apdex()` function to query the Apdex score. Our service derives the Apdex score for each service. Therefore, you must specify the service you want to get the Apdex data.
The **basic queries** use `hs(tracing.aggregated.derived.*.duration.micros.m)` as the underlying query to get the Apdex scores. See [Aggregated RED Metrics](trace_data_details.html#aggregated-red-metrics). Basic queries only give you the Apdex score for a given service. Therefore, you need to specify the application and service filters.
@@ -116,7 +116,7 @@ Here's how you can use these queries:
```
-* Use an advanced query to return the Apdex score of all the services that send data to Operations for Applications every 30 minutes.
+* Use an advanced query to return the Apdex score of all the services that send data to our service every 30 minutes.
@@ -129,7 +129,7 @@ apdex(align(1vw, merge(hs(tracing.aggregated.derived.*.m, application=beachshirt
- Operations for Applications rounds the Apdex score to 2 decimal points so that it is easy for you to [interpret the score](tracing_apdex.html#interpreting-the-apdex-score). You need to update the gauge chart settings to get the color to value mapping and round the value to 2 decimal points.
+ Our service rounds the Apdex score to 2 decimal points so that it is easy for you to [interpret the score](tracing_apdex.html#interpreting-the-apdex-score). You need to update the gauge chart settings to get the color to value mapping and round the value to 2 decimal points.
diff --git a/pages/doc/trace_data_query.md b/pages/doc/trace_data_query.md
index 941367896..637fb2a55 100644
--- a/pages/doc/trace_data_query.md
+++ b/pages/doc/trace_data_query.md
@@ -7,7 +7,7 @@ permalink: trace_data_query.html
summary: Learn how to query for trace data.
---
-After your application starts sending trace data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront), you can examine that data in the Traces Browser. By fine-tuning the trace query in the Traces Browser, you find the traces that you're interested in by describing the spans they must contain.
+After your application starts sending trace data to Tanzu Observability (formerly known as VMware Aria Operations for Applications), you can examine that data in the Traces Browser. By fine-tuning the trace query in the Traces Browser, you find the traces that you're interested in by describing the spans they must contain.
## View Tracing Critical Path Data in Charts
@@ -135,7 +135,7 @@ To query traces, select **Applications > Traces** and navigate to the Traces Bro
You might not see search results:
- If you search for a trace after 7 days because Operations for Applications retains trace data only for 7 days.
+ If you search for a trace after 7 days because our service retains trace data only for 7 days.
If you search for a trace after 1 hour because you have enabled intelligent sampling for traces.
diff --git a/pages/doc/trace_data_sampling.md b/pages/doc/trace_data_sampling.md
index e064089ca..e1bbdd87d 100644
--- a/pages/doc/trace_data_sampling.md
+++ b/pages/doc/trace_data_sampling.md
@@ -7,7 +7,7 @@ permalink: trace_data_sampling.html
summary: Learn how we sample trace data and how you can control sampling.
---
-A cloud-scale web application generates a very large number of traces. VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports sampling to reduce the volume of stored trace data.
+A cloud-scale web application generates a very large number of traces. Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports sampling to reduce the volume of stored trace data.
## How It Works
@@ -15,11 +15,11 @@ Let's look at the following scenarios to understand how sampling works:
-Not all the trace data that you send to Operations for Applications is useful. When traces arrive, Operations for Applications identifies the important traces and those that add value to you and retains them. This process is known as [Intelligent Sampling](#intelligent-sampling).
+Not all the trace data that you send to our service is useful. When traces arrive, our service identifies the important traces and those that add value to you and retains them. This process is known as [Intelligent Sampling](#intelligent-sampling).
-However, when intelligent sampling is on, you might not see some traces when you search for them on the traces browser. If you and don't want that certain traces are discarded, use [Sampling Policies](#sampling-policies). With a sampling policy in place, Operations for Applications does not perform intelligent sampling on the data sampled by the sampling policy
+However, when intelligent sampling is on, you might not see some traces when you search for them on the traces browser. If you and don't want that certain traces are discarded, use [Sampling Policies](#sampling-policies). With a sampling policy in place, our service does not perform intelligent sampling on the data sampled by the sampling policy
-Creating a sampling policy affects your cost because Operations for Applications services more data for you.
+Creating a sampling policy affects your cost because Tanzu Observability services more data for you.
{% include note.html content="Only Super Admin users and users with the [Applications permission](permissions_overview.html) can create sampling policies." %}
@@ -35,7 +35,7 @@ Sampling has the following advantages:
## Intelligent Sampling
-Operations for Applications automatically performs intelligent sampling to reduce the volume of ingested traces. The goals of intelligent sampling are to retain traces that are likely to be informative, and to discard traces that are redundant or otherwise not worth inspecting.
+Our service automatically performs intelligent sampling to reduce the volume of ingested traces. The goals of intelligent sampling are to retain traces that are likely to be informative, and to discard traces that are redundant or otherwise not worth inspecting.
Intelligent sampling gives preference to:
@@ -43,11 +43,11 @@ Intelligent sampling gives preference to:
* Traces that contain at least one individual span that is abnormally long, as compared to other spans for the same operation.
* Traces that contain at least one span in which an error occurred.
-We use proprietary algorithms to decide which traces to retain (sample) and which traces to discard (not sample). When analyzing whether a trace is worth retaining, Operations for Applications compares the trace's characteristics to a historical context that is composed of similar traces. The historical context is based on the [RED metrics](trace_data_details.html#trace-sampling-and-derived-red-metrics) that Operations for Applications derives from the entire set of trace data that your application has emitted before any sampling occurs. This allows us to determine whether an analyzed trace is a true outlier.
+We use proprietary algorithms to decide which traces to retain (sample) and which traces to discard (not sample). When analyzing whether a trace is worth retaining, our service compares the trace's characteristics to a historical context that is composed of similar traces. The historical context is based on the [RED metrics](trace_data_details.html#trace-sampling-and-derived-red-metrics) that our service derives from the entire set of trace data that your application has emitted before any sampling occurs. This allows us to determine whether an analyzed trace is a true outlier.
-Intelligent sampling applies to entire traces after Operations for Applications receives them. If you have set up an [explicit sampling strategy](#explicit-sampling-strategies), then the output of your explicit sampling strategy is the input to intelligent sampling.
+Intelligent sampling applies to entire traces after our service receives them. If you have set up an [explicit sampling strategy](#explicit-sampling-strategies), then the output of your explicit sampling strategy is the input to intelligent sampling.
-Intelligent sampling is performed by the Operations for Applications service itself, not by the proxy or by an instrumented application. Consequently, intelligent sampling does not place any additional processing burden on your proxies or applications. Intelligent sampling does not add to your total cost of operation (TCO). If you already use one or more proxies to ingest your time-series data, you can start ingesting and sampling trace data without adding more hardware to support more proxies.
+Intelligent sampling is performed by our service itself, not by the proxy or by an instrumented application. Consequently, intelligent sampling does not place any additional processing burden on your proxies or applications. Intelligent sampling does not add to your total cost of operation (TCO). If you already use one or more proxies to ingest your time-series data, you can start ingesting and sampling trace data without adding more hardware to support more proxies.
{% include note.html content="If you are troubleshooting and need specific spans, annotate those spans with `debug=true`. Make sure to remove the annotation once you are done troubleshooting and don't overuse the annotation. For details on adding span tags via the Wavefront proxy, see [Proxy Preprocessor Rules](proxies_preprocessor_rules.html#spanaddtag-and-spanaddtagifnotexists)." %}
@@ -67,14 +67,14 @@ You can [monitor](wavefront-internal-metrics.html) your span storage by checking
Number of spans per second being sent directly to Operations for Applications (direct ingestion).
+
Number of spans per second being sent directly to our service (direct ingestion).
## Sampling Policies
-If you can’t find traces because Intelligent Sampling discarded them, create a sampling policy to let the Operations for Applications service know that you want to keep specific spans. Sampling policies impact the volume of spans that are ingested and can affect your [costs](wavefront_pricing.html#pricing-structure). See your Service Agreement for cost details.
+If you can’t find traces because Intelligent Sampling discarded them, create a sampling policy to let our service know that you want to keep specific spans. Sampling policies impact the volume of spans that are ingested and can affect your [costs](wavefront_pricing.html#pricing-structure). See your Service Agreement for cost details.
See [Managing Sampling Policies](trace_sampling_policies.html) for details.
@@ -84,10 +84,10 @@ See [Managing Sampling Policies](trace_sampling_policies.html) for details.
### Track the Volume of Stored Trace Data
-A sampling policy affects your costs because more data might be sent to Operations for Applications. To see the number of spans you store after the sampling policies are in effect:
+A sampling policy affects your costs because more data might be sent to our service. To see the number of spans you store after the sampling policies are in effect:
1. Click **Dashboards** > **All Dashboards**.
-1. Search for the **Operations for Applications Service and Proxy Data** dashboard and click it to navigate to the dashboard.
+1. Search for the **Tanzu Observability and Proxy Data** dashboard and click it to navigate to the dashboard.
1. On the dashboard, search for the **Spans Sampled by Policies Per Second** chart under **Proxies overview**.
You see the number of spans stored per second.
@@ -96,7 +96,7 @@ You see the number of spans stored per second.
## Explicit Sampling Strategies
-An explicit sampling strategy is a mechanism for selecting which traces to forward to Operations for Applications. You can set up an explicit sampling strategy by [configuring the Wavefront proxy](#setting-up-explicit-sampling-through-the-proxy). We support the following explicit sampling strategies:
+An explicit sampling strategy is a mechanism for selecting which traces to forward to our service. You can set up an explicit sampling strategy by [configuring the Wavefront proxy](#setting-up-explicit-sampling-through-the-proxy). We support the following explicit sampling strategies:
### Explicit Sampling Strategy Overview
@@ -111,16 +111,16 @@ An explicit sampling strategy is a mechanism for selecting which traces to forwa
Rate-based sampling
-
Sends N percent of the generated traces to Operations for Applications. Sometimes called probabilistic sampling. For example, a sampling rate of 10% causes 1 out of 10 traces to be sent and ingested.
+
Sends N percent of the generated traces to our service. Sometimes called probabilistic sampling. For example, a sampling rate of 10% causes 1 out of 10 traces to be sent and ingested.
Duration-based sampling
-
Sends spans only if they are longer than N milliseconds. For example, a sampling duration of 45 sends spans to Operations for Applications only if they are longer than 45 milliseconds.
+
Sends spans only if they are longer than N milliseconds. For example, a sampling duration of 45 sends spans to our service only if they are longer than 45 milliseconds.
-{% include note.html content="You can query and visualize only the traces and spans that Operations for Applications has ingested. If you set up an explicit sampling strategy that severely reduces the volume of ingested trace data, you might end up with queries that produce no results." %}
+{% include note.html content="You can query and visualize only the traces and spans that our service has ingested. If you set up an explicit sampling strategy that severely reduces the volume of ingested trace data, you might end up with queries that produce no results." %}
### Complete vs. Partial Traces
@@ -133,9 +133,9 @@ An ingested trace can be complete (a trace ingested with all of its member spans
### Result of Combining Explicit Sampling Strategies
-You can combine rate-based sampling and duration-based sampling in the same service. Doing so causes Operations for Applications to ingest the union of the spans that are selected by each sampler.
+You can combine rate-based sampling and duration-based sampling in the same service. Doing so causes our service to ingest the union of the spans that are selected by each sampler.
-For example, suppose you set the sampling rate to 20% and the sampling duration to 45ms for the same service. This causes Operations for Applications to receive:
+For example, suppose you set the sampling rate to 20% and the sampling duration to 45ms for the same service. This causes our service to receive:
* 20% of the traces generated by that service, regardless of the length of their spans.
* Any additional spans outside of that 20% that are longer than 45ms.
@@ -149,14 +149,14 @@ You can set up explicit sampling strategies through a [Wavefront proxy](proxies.
1. On the proxy host, open the proxy configuration file `wavefront.conf` for editing. The [path to the file](proxies_configuring.html#paths) depends on the host.
2. Add the `traceSamplingRate` property, the `traceSamplingDuration` property, or both to the `wavefront.conf` file. See [Tracing Proxy Properties](proxies_configuring.html#tracing-proxy-properties).
- In the following example, the `traceSamplingRate` property sends 10% of the trace to Operations for Applications and the `traceSamplingDuration` property sets the minimum sampling duration to 45 milliseconds:
+ In the following example, the `traceSamplingRate` property sends 10% of the trace to our service and the `traceSamplingDuration` property sets the minimum sampling duration to 45 milliseconds:
```
# Number from 0.0 to 1.0
traceSamplingRate=.1
...
traceSamplingDuration=45
```
- {% include important.html content="If you have more than one proxy, each proxy must have the same value for the `traceSamplingRate` property. If different proxies send different percentages of spans to your Operations for Applications service, you get incomplete traces."%}
+ {% include important.html content="If you have more than one proxy, each proxy must have the same value for the `traceSamplingRate` property. If different proxies send different percentages of spans to your Tanzu Observability service, you get incomplete traces."%}
3. Save the `wavefront.conf` file.
4. [Start the proxy](proxies_installing.html#start-and-stop-a-proxy).
diff --git a/pages/doc/trace_sampling_policies.md b/pages/doc/trace_sampling_policies.md
index 92a47fbcb..5942ea263 100644
--- a/pages/doc/trace_sampling_policies.md
+++ b/pages/doc/trace_sampling_policies.md
@@ -7,7 +7,7 @@ permalink: trace_sampling_policies.html
summary: Learn control trace data sampling with sampling policies.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) uses [intelligent sampling](trace_data_sampling.html) to reduce the volume of ingested traces. The goal of intelligent sampling is to retain traces that are likely to be informative. But sometimes intelligent sampling discards traces that you want to keep. You can create a sampling policy to fine-tune intelligent sampling and indicate that you want to keep certain spans.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) uses [intelligent sampling](trace_data_sampling.html) to reduce the volume of ingested traces. The goal of intelligent sampling is to retain traces that are likely to be informative. But sometimes intelligent sampling discards traces that you want to keep. You can create a sampling policy to fine-tune intelligent sampling and indicate that you want to keep certain spans.
Creating a sampling policy affects your costs as you store more data.
You can create a sampling policy, edit, delete, restore, deactivate, and see the version history of the policy you created:
@@ -91,7 +91,7 @@ Now, you see the policy you created listed under sampling policies.
When you [create a sampling policy](trace_sampling_policies.html), you need to define a policy expression that specifies the spans you want to keep. This expression needs to be in the YAML format.
-Let's look at a policy expression that asks the Operations for Applications service to store traces if the application name is beachshirts.
+Let's look at a policy expression that asks the Tanzu Observability service to store traces if the application name is beachshirts.
diff --git a/pages/doc/tracing_apdex.md b/pages/doc/tracing_apdex.md
index 5b7ddc6e0..eaf4e42aa 100644
--- a/pages/doc/tracing_apdex.md
+++ b/pages/doc/tracing_apdex.md
@@ -13,7 +13,7 @@ The Application Performance Index ([Apdex](https://www.apdex.org)) is an industr
You can measure the performance of a service using Request, Error, and Duration (RED) metrics for a given time frame. But it is hard to compare these values and understand how each service performs. Apdex helps you compare the response time of a service based on the response time threshold that you define.
-When you send your applications trace data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront), the application data is detected as first-class citizens using the traces, and the Apdex score is calculated using the threshold value (T) you define. Use [`apdex()`](hs_apdex_function.html) to query the Apdex score of a service, view the results in charts, and create alerts.
+When you send your applications trace data to Tanzu Observability (formerly known as VMware Aria Operations for Applications), the application data is detected as first-class citizens using the traces, and the Apdex score is calculated using the threshold value (T) you define. Use [`apdex()`](hs_apdex_function.html) to query the Apdex score of a service, view the results in charts, and create alerts.
The default threshold value (T) is set to 100ms, and only Super Admin users and users with the [**Applications** permission](permissions_overview.html) can configure the threshold (T).
@@ -183,7 +183,7 @@ A Super Admin user or users with the **Applications** permission can change the
From the Application Configuration page, you can update the threshold value of multiple services at once. Follow these steps:
-1. Click **Applications** > **Application Configuration**. You see a list of the applications that send trace data to the Operations for Applications service.
+1. Click **Applications** > **Application Configuration**. You see a list of the applications that send trace data to the Tanzu Observability service.
1. Click the application that has the services you want to configure. Now, you see a list of all the services in the application.
1. Select the check boxes next to the services that you want to edit and click the **Edit Settings** button on the top of the list.
{% include note.html content="Only a Super Admin user or users with the **Applications** permission can configure the Apdex threshold. If you are not a Super Admin user, you see the following message: **You don't have permission to update this page**."%}
@@ -200,7 +200,7 @@ You can update the response time threshold (T) using the Settings icon on the ap
1. Click **Configure Apdex**.
{% include note.html content="Only a Super Admin user or users with the **Applications** permission can configure the threshold (T). If you are not a Super Admin user, you don't see **Configure Apdex**."%}
- Now, you see a list of all the services that send trace data to the Operations for Applications service. You can sort the table by the service name, application name, service status (active or inactive), and the threshold (T) value.
+ Now, you see a list of all the services that send trace data to the Tanzu Observability service. You can sort the table by the service name, application name, service status (active or inactive), and the threshold (T) value.
1. Select the check boxes next to the services that you want to edit and click the **Edit Settings** button on the top of the list.
1. Update the **Apdex Threshold** value and click **Save**.
diff --git a/pages/doc/tracing_best_practices.md b/pages/doc/tracing_best_practices.md
index b5761321a..601dbe2ae 100644
--- a/pages/doc/tracing_best_practices.md
+++ b/pages/doc/tracing_best_practices.md
@@ -4,10 +4,10 @@ keywords: data, distributed tracing
tags: [tracing, best practice]
sidebar: doc_sidebar
permalink: tracing_best_practices.html
-summary: Best practices for collecting and sending trace data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Best practices for collecting and sending trace data to Tanzu Observability (formerly known as VMware Aria Operations for Applications)).
---
-The best practices on this page help you get optimal results from instrumenting your application for tracing with Operations for Applications.
+The best practices on this page help you get optimal results from instrumenting your application for tracing with our service.
## Planning for Tracing
@@ -26,13 +26,13 @@ The best practices on this page help you get optimal results from instrumenting
* If you have already instrumented your application with a 3rd party distributed tracing system such as Jaeger or Zipkin, set up an [**integration**](tracing_integrations.html).
- * Use **consistent instrumentation**, either Operations for Applications SDKs or a 3rd party tracing system for all services that participate in the same trace. Otherwise, spans cannot link to each other across service boundaries. You can intermix different Operations for Applications SDKs in different programming languages.
+ * Use **consistent instrumentation**, either Tanzu Observability SDKs or a 3rd party tracing system for all services that participate in the same trace. Otherwise, spans cannot link to each other across service boundaries. You can intermix different Tanzu Observability SDKs in different programming languages.
## Best Practices for Sending Trace Data Through a Wavefront Proxy
-For reliable performance, use a Wavefront proxy to send trace data to your Operations for Applications service. A proxy is required with the Jaeger and Zipkin integrations. [Direct ingestion](direct_ingestion.html#proxy-or-direct-ingestion) might seem like an easy way to get results quickly, but the buffering and queuing that the proxy performs is especially useful with trace data.
+For reliable performance, use a Wavefront proxy to send trace data to your Tanzu Observability service. A proxy is required with the Jaeger and Zipkin integrations. [Direct ingestion](direct_ingestion.html#proxy-or-direct-ingestion) might seem like an easy way to get results quickly, but the buffering and queuing that the proxy performs is especially useful with trace data.
-### Best Practices for Operations for Applications SDKs
+### Best Practices for Tanzu Observability SDKs
1. [Install and configure the Wavefront proxy](tracing_instrumenting_frameworks.html#to-prepare-for-using-a-wavefront-proxy) with listener ports for metrics, histograms, and trace data. All three types of data are necessary for displaying RED metrics derived from spans.
@@ -53,7 +53,7 @@ For reliable performance, use a Wavefront proxy to send trace data to your Opera
WavefrontSender wavefrontSender = wavefrontClientFactory.getClient();
```
-{% include tip.html content="Complete setup steps are in the README file for your Operations for Applications SDK on GitHub." %}
+{% include tip.html content="Complete setup steps are in the README file for your Tanzu Observability SDK on GitHub." %}
### Best Practices for Jaeger and Zipkin
@@ -95,16 +95,16 @@ Think of your instrumented application as a hierarchic inventory of constructs.
-Operations for Applications uses these names as span tag values, as filters for traces, as components in RED metric names, and as qualifiers for operation names, for example, `beachshirts.delivery.dispatch`.
+Our service uses these names as span tag values, as filters for traces, as components in RED metric names, and as qualifiers for operation names, for example, `beachshirts.delivery.dispatch`.
### Guidelines for Choosing Application Construct Names
* Choose a string name for each construct. Names at the same level must be unique.
- - **Example:** Specify only one application named `beachshirts` in an Operations for Applications instance, and only one service named `delivery` in a given application.
+ - **Example:** Specify only one application named `beachshirts` in an Tanzu Observability instance, and only one service named `delivery` in a given application.
{% include important.html content="Duplicate application, service, or component names might result in incorrect RED metrics. " %}
* Choose logical names that clearly map to your applications and services. Logical names might be simpler, more readable versions of code identifiers.
-### Best Practices for Operations for Applications SDKs
+### Best Practices for Tanzu Observability SDKs
* Set up an [Application tags object](trace_data_details.html#application-tags) in each service to define logical names for the application constructs. Specify the logical application and service names that apply to the service. Optionally, if you want to use the physical topology to filter your data, include logical cluster and shard names.
@@ -129,23 +129,23 @@ Operations for Applications uses these names as span tag values, as filters for
build();
```
-{% include tip.html content="Complete setup steps are in the README file for your Operations for Applications SDK on GitHub. " %}
+{% include tip.html content="Complete setup steps are in the README file for your Tanzu Observability SDK on GitHub. " %}
### Best Practices for 3rd Party Tracing Systems
-Operations for Applications automatically assigns standard application names, service names, and component names, based on the tags that are set for your 3rd party distributed tracing system.
+Our service automatically assigns standard application names, service names, and component names, based on the tags that are set for your 3rd party distributed tracing system.
## Source Names Best Practices
-A source is a host, container, Kubernetes pod, instance, or any other unique origination point for application code that is sending a span to Operations for Applications.
+A source is a host, container, Kubernetes pod, instance, or any other unique origination point for application code that is sending a span to our service.
-You must choose unique names for the sources that send spans. Operations for Applications uses source names to filter traces and to define RED metrics.
+You must choose unique names for the sources that send spans. Tanzu Observability uses source names to filter traces and to define RED metrics.
### Guidelines for Choosing Source Names
-* Choose a unique string name for every source that will send spans to Operations for Applications.
+* Choose a unique string name for every source that will send spans to our service.
- For example, use a machine's IP address or a descriptive logical name.
- If you use a machine's host name (the default), make sure all machines have unique host names. Use logical names to distinguish machines with the same host names in different data centers.
@@ -154,11 +154,11 @@ You must choose unique names for the sources that send spans. Operations for App
* See also the guidelines for choosing [source names for metric data and histograms](wavefront_data_format.html#source-names-best-practices).
-### Best Practices for Operations for Applications SDKs
+### Best Practices for Tanzu Observability SDKs
* Set up a [WavefrontSpanReporter object](trace_data_details.html#wavefronttracer-and-wavefrontspanreporter) to define a source name:
- Specify the source name explicitly, or leave it unspecified to automatically use the host name. Make sure the host name is unique.
- - If your Operations for Applications SDK defines additional reporters, specify the same source name in each one. All reporter objects for a particular service must specify the same source.
+ - If your Tanzu Observability SDK defines additional reporters, specify the same source name in each one. All reporter objects for a particular service must specify the same source.
**Java example:** Build a `WavefrontSpanReporter` that reports from a source called `wavefront-tracing-example`.
@@ -171,7 +171,7 @@ You must choose unique names for the sources that send spans. Operations for App
build(wavefrontSender);
```
-{% include tip.html content="Complete setup steps are in the README file for your Operations for Applications SDK on GitHub." %}
+{% include tip.html content="Complete setup steps are in the README file for your Tanzu Observability SDK on GitHub." %}
## Span Names Best Practices
@@ -202,7 +202,7 @@ If you are using Jaeger, verify that the number of generated span names will res
You can define custom span tags to let you query and filter for particular subsets of trace data.
-[Indexing](trace_data_details.html#indexed-and-unindexed-span-tags) optimizes the speed of querying and filtering with tags. By default, Operations for Applications indexes all point tags and certain built-in span tags. Indexing for custom span tags is available on request.
+[Indexing](trace_data_details.html#indexed-and-unindexed-span-tags) optimizes the speed of querying and filtering with tags. By default, our service indexes all point tags and certain built-in span tags. Indexing for custom span tags is available on request.
### Guidelines for Defining Custom Span Tags
@@ -222,7 +222,7 @@ The goal of instrumentation is to instrument enough methods to produce traces th
2. **Go deep:** Produce traces that contain a deep, meaningful hierarchy of spans.
* Identify the classes and methods that implement significant operations within each service, and instrument those methods.
-### Best Practices for Operations for Applications SDKs
+### Best Practices for Tanzu Observability SDKs
* Limit the number of spans in a trace to < 1000.
diff --git a/pages/doc/tracing_customize_spans_and_alerts.md b/pages/doc/tracing_customize_spans_and_alerts.md
index 9c7184f82..385a8a2b3 100644
--- a/pages/doc/tracing_customize_spans_and_alerts.md
+++ b/pages/doc/tracing_customize_spans_and_alerts.md
@@ -7,7 +7,7 @@ permalink: tracing_customize_spans_and_alerts.html
summary: Customize span level tags for RED metrics
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) derives RED metrics for spans that have the `application`, `service`, `cluster`, `shard`, `component`, or `operationName` span tags by default. See [Indexed and Unindexed Span Tags](trace_data_details.html#indexed-and-unindexed-span-tags) for details. If you want to filter RED metrics data using a span tag that is not a default span tag, you need to propagate it as a custom span tag to the RED metrics.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) derives RED metrics for spans that have the `application`, `service`, `cluster`, `shard`, `component`, or `operationName` span tags by default. See [Indexed and Unindexed Span Tags](trace_data_details.html#indexed-and-unindexed-span-tags) for details. If you want to filter RED metrics data using a span tag that is not a default span tag, you need to propagate it as a custom span tag to the RED metrics.
The following custom span tags are supported by default.
@@ -60,19 +60,19 @@ Follow the steps given below to propagate custom span tags when sending data fro
-
If you are using OpenTelemetry, you send data to Operations for Applications using Wavefront proxy. Add the configuration shown below to the <wavefront_config_path>/wavefront.conf file. See Paths to find out where the file is saved.
+
If you are using OpenTelemetry, you send data to our service using Wavefront proxy. Add the configuration shown below to the <wavefront_config_path>/wavefront.conf file. See Paths to find out where the file is saved.
traceDerivedCustomTagKeys=env
-
If you are using Jaeger, you send data to Operations for Applications using Wavefront proxy. Add the configuration shown below to the <wavefront_config_path>/wavefront.conf file. See Paths to find out where the file is saved.
+
If you are using Jaeger, you send data to our service using Wavefront proxy. Add the configuration shown below to the <wavefront_config_path>/wavefront.conf file. See Paths to find out where the file is saved.
traceDerivedCustomTagKeys=env
-
If you are using Zipkin, you send data to Operations for Applications using Wavefront proxy. Add the configuration shown below to the <wavefront_config_path>/wavefront.conf file. See Paths to find out where the file is saved.
+
If you are using Zipkin, you send data to our service using Wavefront proxy. Add the configuration shown below to the <wavefront_config_path>/wavefront.conf file. See Paths to find out where the file is saved.
traceDerivedCustomTagKeys=env
diff --git a/pages/doc/tracing_faq.md b/pages/doc/tracing_faq.md
index 213afcec8..3f2761478 100644
--- a/pages/doc/tracing_faq.md
+++ b/pages/doc/tracing_faq.md
@@ -4,9 +4,9 @@ keywords: data, distributed tracing, jaeger, zipkin, spans
tags: [tracing]
sidebar: doc_sidebar
permalink: tracing_faq.html
-summary: FAQ for distributed tracing with VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront)
+summary: FAQ for distributed tracing with Tanzu Observability (formerly known as VMware Aria Operations for Applications)
---
-This page has some special tips to help you instrument your applications and send trace data to Operations for Applications.
+This page has some special tips to help you instrument your applications and send trace data to our service.
## How do I send custom span level RED metrics?
@@ -36,13 +36,13 @@ To override the default application name when using [zipkin-js](https://github.c
```
{% include note.html content="Only one application can send traces to a proxy because there’s only one application name per proxy. "%}
-## How do I emit spans in Operations for Applications format?
+## How do I emit spans in Tanzu Observability format?
-If you are not using an [Operations for Applications SDK](wavefront_sdks.html), OpenTracing library, or OpenTelemetry library, you can still send spans to Operations for Applications using the Wavefront proxy.
+If you are not using an [Tanzu Observability SDK](wavefront_sdks.html), OpenTracing library, or OpenTelemetry library, you can still send spans to our service using the Wavefront proxy.
-Send spans to the Wavefront proxy's `customTracingListenerPorts` port in the Operations for Applications spans format. Open the [``](proxies_configuring.html#paths)`/wavefront.conf` file, and update or add the `customTracingListenerPorts` property.
+Send spans to the Wavefront proxy's `customTracingListenerPorts` port in the Tanzu Observability spans format. Open the [``](proxies_configuring.html#paths)`/wavefront.conf` file, and update or add the `customTracingListenerPorts` property.
-Given below is an example of the Operations for Applications span format:
+Given below is an example of the Tanzu Observability span format:
```
wavefrontSender.sendSpan("getAllUsers", System.currentTimeMillis(), 343, "localhost",
UUID.fromString("7b3bf470-9456-11e8-9eb6-529269fb1459"),
@@ -60,7 +60,7 @@ wavefrontSender.sendSpan("getAllUsers", System.currentTimeMillis(), 343, "localh
You might not see search results:
- If you search for a trace after 7 days because Operations for Applications retains trace data only for 7 days.
+ If you search for a trace after 7 days because Tanzu Observability retains trace data only for 7 days.
If you search for a trace after 1 hour because you have enabled intelligent sampling for traces.
diff --git a/pages/doc/tracing_operation_dashboard.md b/pages/doc/tracing_operation_dashboard.md
index 9bf4380c3..86b7fadd3 100644
--- a/pages/doc/tracing_operation_dashboard.md
+++ b/pages/doc/tracing_operation_dashboard.md
@@ -7,7 +7,7 @@ permalink: tracing_operation_dashboard.html
summary: Identify potential hot spots of operations.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes the Operation Dashboard, which you can use to identify potential hot spots in each operation, such as the GET operation of the beachshirts application's shopping service. From the Operation Dashboard you can then drill down to the Traces Browser.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Operation Dashboard, which you can use to identify potential hot spots in each operation, such as the GET operation of the beachshirts application's shopping service. From the Operation Dashboard you can then drill down to the Traces Browser.
## Explore the Default Operation Dashboard
diff --git a/pages/doc/tracing_traces_browser.md b/pages/doc/tracing_traces_browser.md
index ce42e75e9..002ac94e5 100644
--- a/pages/doc/tracing_traces_browser.md
+++ b/pages/doc/tracing_traces_browser.md
@@ -7,14 +7,14 @@ permalink: tracing_traces_browser.html
summary: Explore traces and spans from the Traces Browser
---
-The Traces Browser in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) lets you explore the context and the details of your application's traces.
+The Traces Browser in Tanzu Observability (formerly known as VMware Aria Operations for Applications) lets you explore the context and the details of your application's traces.
## Video
This video highlights the Traces Browser features and settings. Note that this video was created in 2019 and some of the information in it might have changed. It also uses the 2019 version of the UI.
-
+
## Explore the Traces Browser
@@ -113,7 +113,7 @@ In the trace details panel, you can:
In the trace details panel, you can view details about a particular span in the trace. If that span came from another service, you can navigate to the dashboard for that service.
-{% include note.html content="The Operations for Applications service can only retrieve up to 1000 spans for a given trace, and you only see up to 1000 spans when you drill down into spans. Therefore, as a best practice and for optimal performance, configure your application to have less than 1000 spans in a trace."%}
+{% include note.html content="The Tanzu Observability service can only retrieve up to 1000 spans for a given trace, and you only see up to 1000 spans when you drill down into spans. Therefore, as a best practice and for optimal performance, configure your application to have less than 1000 spans in a trace."%}
diff --git a/pages/doc/tracing_view_offline_traces.md b/pages/doc/tracing_view_offline_traces.md
index a222b52fc..d2b6ad676 100644
--- a/pages/doc/tracing_view_offline_traces.md
+++ b/pages/doc/tracing_view_offline_traces.md
@@ -7,14 +7,14 @@ permalink: tracing_view_offline_traces.html
summary: Download traces and view them later using offline traces.
---
-You can export traces from VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront). You can save traces locally as JSON files and view them later using the **Offline Traces**.
+You can export traces from Tanzu Observability (formerly known as VMware Aria Operations for Applications). You can save traces locally as JSON files and view them later using the **Offline Traces**.
## Export Traces
Follow the steps to export traces via the traces browser or the Wavefront API:
* Export the traces via the [Traces Browser](tracing_traces_browser.html) and save the JSON file.
* Export traces via the API.
- * Use the Operations for Applications Swagger UI. See [API Documentation (Product Instance)](wavefront_api.html#api-documentation-service-instance) for details on navigating to the Swagger UI.
+ * Use the Tanzu Observability Swagger UI. See [API Documentation (Product Instance)](wavefront_api.html#api-documentation-service-instance) for details on navigating to the Swagger UI.
Example:
* Use a `curl` command that has the `/api/v2/chart/api` URL.
From 975a473aef2e22a57864dd1860b899841e804764 Mon Sep 17 00:00:00 2001
From: shavidissa
Date: Thu, 21 Mar 2024 11:45:16 -0700
Subject: [PATCH 13/26] Rename the API ,SDKs, and CLI section
---
.../doc/wavefront_command-line_interfaces.md | 12 +++++------
pages/doc/wavefront_interfaces.md | 20 +++++++++----------
pages/doc/wavefront_sdks.md | 20 +++++++++----------
3 files changed, 26 insertions(+), 26 deletions(-)
diff --git a/pages/doc/wavefront_command-line_interfaces.md b/pages/doc/wavefront_command-line_interfaces.md
index 146114ff3..c39706fd4 100644
--- a/pages/doc/wavefront_command-line_interfaces.md
+++ b/pages/doc/wavefront_command-line_interfaces.md
@@ -1,21 +1,21 @@
---
-title: Operations for Applications CLIs
+title: Tanzu Observability CLIs
keywords: getting started
tags: [getting started]
sidebar: doc_sidebar
permalink: wavefront_clis.html
-summary: You can use different CLIs with VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront).
+summary: You can use different CLIs with Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-The Operations for Applications REST API is publicly available via Swagger. You can use Swagger to generate an [API client](wavefront_api.html#generate-an-api-client-using-swagger) that includes CLI options. Several of our customers have generated CLIs already.
+The Tanzu Observability REST API is publicly available via Swagger. You can use Swagger to generate an [API client](wavefront_api.html#generate-an-api-client-using-swagger) that includes CLI options. Several of our customers have generated CLIs already.
## External CLIs for the REST API
-Several Operations for Applications customers have generated CLIs from our REST API and made them available on GitHub.
+Several Tanzu Observability customers have generated CLIs from our REST API and made them available on GitHub.
-{% include note.html content="These external CLIs are not supported or maintained by the Operations for Applications team." %}
+{% include note.html content="These external CLIs are not supported or maintained by the Tanzu Observability team." %}
* Robert Fisher of Sysdef Ltd. created a [Ruby CLI](https://github.com/snltd/wavefront-cli) and gives installation instructions, examples, and more in [this post](https://sysdef.xyz/post/2017-07-26-wavefront-cli).
This [blog post](https://tanzu.vmware.com/content/vmware-aria-operations-for-applications-blog/commanding-the-waves-using-the-wavefront-cli) has details.
-* Operations for Applications customer Box open-sourced `wavectl`, their [automation tooling for Operations for Applications](https://github.com/box/wavectl). This command-line client for Operations for Applications is inspired by kubectl and git command line tools. This [blog post](https://tanzu.vmware.com/content/vmware-aria-operations-for-applications-blog/new-automation-tooling-for-wavefront-gets-boxed-up-by-box) discusses that CLI and includes links to the extensive doc and examples.
+* Tanzu Observability customer Box open-sourced `wavectl`, their [automation tooling for Tanzu Observability](https://github.com/box/wavectl). This command-line client for Tanzu Observability is inspired by kubectl and git command line tools. This [blog post](https://tanzu.vmware.com/content/vmware-aria-operations-for-applications-blog/new-automation-tooling-for-wavefront-gets-boxed-up-by-box) discusses that CLI and includes links to the extensive doc and examples.
diff --git a/pages/doc/wavefront_interfaces.md b/pages/doc/wavefront_interfaces.md
index 6b6e3bbf9..fec387f2b 100644
--- a/pages/doc/wavefront_interfaces.md
+++ b/pages/doc/wavefront_interfaces.md
@@ -4,10 +4,10 @@ keywords: getting started
tags: [getting started]
sidebar: doc_sidebar
permalink: wavefront_interfaces.html
-summary: An overview of the various interfaces for interacting with VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: An overview of the various interfaces for interacting with Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-Operations for Applications provides different kinds of interfaces for performing different kinds of tasks. Click on the links for further information about each type of interface.
+Our service provides different kinds of interfaces for performing different kinds of tasks. Click on the links for further information about each type of interface.
@@ -19,24 +19,24 @@ Operations for Applications provides different kinds of interfaces for performin
-
Operations for Applications user interface (UI)
-
Interacting directly with Operations for Applications from your browser. Sample tasks include visualizing metrics, histograms, and trace data in charts and dashboards, running queries, setting up alerts and alert notifications, installing and managing integrations, creating events, and so on.
-
In the original Operations for Applications subscriptions, this interface also provides support for managing users, user groups, roles, permissions, and preferences. For information about original and onboarded subscriptions and the differences between them, see Subscription Types.
+
Tanzu Observability user interface (UI)
+
Interacting directly with our service from your browser. Sample tasks include visualizing metrics, histograms, and trace data in charts and dashboards, running queries, setting up alerts and alert notifications, installing and managing integrations, creating events, and so on.
+
In the original Tanzu Observability subscriptions, this interface also provides support for managing users, user groups, roles, permissions, and preferences. For information about original and onboarded subscriptions and the differences between them, see Subscription Types.
VMware Cloud Services Console
-
In the onboarded Operations for Applications subscriptions, VMware Cloud services provides support for managing users, user groups, roles, and preferences. For information about original and onboarded subscriptions and the differences between them, see Subscription Types.
+
In the onboarded Tanzu Observability subscriptions, VMware Cloud services provides support for managing users, user groups, roles, and preferences. For information about original and onboarded subscriptions and the differences between them, see Subscription Types.
-
[Operations for Applications REST API](wavefront_api.html)
Writing scripts to perform UI actions programmatically. The REST API is based on Swagger, so you can generate the API client of your choice (including a CLI client).
-
[Operations for Applications SDKs](wavefront_sdks.html)
-
Instrumenting your application code to send metrics, histograms, and trace data to Operations for Applications, either through the Wavefront proxy or directly to the Operations for Applications service. These SDKs are available for most popular programming languages, and are available in GitHub.
+
[Tanzu Observability SDKs](wavefront_sdks.html)
+
Instrumenting your application code to send metrics, histograms, and trace data to our service, either through the Wavefront proxy or directly to the Tanzu Observability service. These SDKs are available for most popular programming languages, and are available in GitHub.
-
[Operations for Applications CLIs](wavefront_clis.html)
+
[Tanzu Observability CLIs](wavefront_clis.html)
Running command-line utilities to install and configure the Wavefront proxy, the Telegraf collector agent, or integrations.
diff --git a/pages/doc/wavefront_sdks.md b/pages/doc/wavefront_sdks.md
index 45ee39034..62e5880fc 100644
--- a/pages/doc/wavefront_sdks.md
+++ b/pages/doc/wavefront_sdks.md
@@ -1,15 +1,15 @@
---
-title: Operations for Applications SDKs
+title: Tanzu Observability SDKs
keywords: getting started
tags: [getting started]
sidebar: doc_sidebar
permalink: wavefront_sdks.html
-summary: Learn about SDKs that enable applications to report metrics, histograms, and trace data to VMware Aria Operations for Applications (previously known as Tanzu Observability by Wavefront).
+summary: Learn about SDKs that enable applications to report metrics, histograms, and trace data to Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-Operations for Applications supports a suite of open source SDKs that developers can use to instrument applications for observability. The instrumented application collects and sends metrics, histograms, and/or trace data to Operations for Applications for storage and visualization. The SDKs are available for most popular programming languages, and are available in GitHub.
+Tanzu Observability supports a suite of open source SDKs that developers can use to instrument applications for observability. The instrumented application collects and sends metrics, histograms, and/or trace data to Tanzu Observability for storage and visualization. The SDKs are available for most popular programming languages, and are available in GitHub.
-Watch this video to listen to our co-founder Clement Pang talk about how Operations for Applications expands application monitoring with its observability SDKs. Note that this video was created in 2019 and some of the information in it might have changed.
+Watch this video to listen to our co-founder Clement Pang talk about how Tanzu Observability expands application monitoring with its observability SDKs. Note that this video was created in 2019 and some of the information in it might have changed.
@@ -17,7 +17,7 @@ Watch this video to listen to our co-founder Clement Pang talk about how Operati
## What Do You Want to Collect?
-Operations for Applications SDKs let you instrument your application to collect and send different kinds of observability data.
+Tanzu Observability SDKs let you instrument your application to collect and send different kinds of observability data.
@@ -55,7 +55,7 @@ Operations for Applications SDKs let you instrument your application to collect
[Sender SDK](#sdks-for-sending-raw-data)
-
Lets you send raw values to Operations for Applications for storage as metrics, histograms, or traces, e.g., to import CSV data.
+
Lets you send raw values to our service for storage as metrics, histograms, or traces, e.g., to import CSV data.
@@ -146,7 +146,7 @@ Sample use case:
## SDKs for Sending Raw Data
-Some SDKs enable you to send raw values to Operations for Applications for ingestion as metrics, histograms, or trace data. You normally use these "sender" SDKs indirectly when you use other SDKs that depend on them. However, you might use a sender SDK directly, for example, to create a utility that obtains existing values from a data store or CSV file, and sends those values to Operations for Applications.
+Some SDKs enable you to send raw values to our service for ingestion as metrics, histograms, or trace data. You normally use these "sender" SDKs indirectly when you use other SDKs that depend on them. However, you might use a sender SDK directly, for example, to create a utility that obtains existing values from a data store or CSV file, and sends those values to our service.
We provide sender SDKs for:
@@ -200,12 +200,12 @@ We provide sender SDKs for:
{% include note.html content="If you want to instrument your tracing application using a Sender SDK, you won’t see span-level RED metrics by default. See [Instrument Your Application with Sender SDKs](tracing_instrumenting_frameworks.html#instrument-your-application-with-sender-sdks) to configure your application to send span-level RED metrics using a custom tracing port." %}
-A sender SDK is built into each of the other observability SDKs to enable applications to communicate with Operations for Applications in one of two ways:
-* Send data directly to Operations for Applications ([direct ingestion](direct_ingestion.html)). This technique gets you up and running with minimal preparation, but is best suited for proof of concept and small-scale uses.
+A sender SDK is built into each of the other observability SDKs to enable applications to communicate with our service in one of two ways:
+* Send data directly to our service ([direct ingestion](direct_ingestion.html)). This technique gets you up and running with minimal preparation, but is best suited for proof of concept and small-scale uses.
{% include note.html content= "Currently, if your service is onboarded to VMware Cloud services, direct ingestion by using SDK is not supported. For best performance, use a Wavefront proxy. " %}
-* Send data to a [Wavefront proxy](proxies_installing.html), which then forwards the data to Operations for Applications. This technique is recommended for large-scale deployments, because the proxy provides resilience to internet outages, control over data queuing and filtering, and more.
+* Send data to a [Wavefront proxy](proxies_installing.html), which then forwards the data to our service. This technique is recommended for large-scale deployments, because the proxy provides resilience to internet outages, control over data queuing and filtering, and more.
What are current usage details?
-
Start with the dashboards in the Operations for Applications Usage integration and the Usage Summary dashboard. The dashboards allow you to look at both current usage and usage over time. If you need to drill down more, use the wftop GUI for a detailed view of current spikes.
+
Start with the dashboards in the Tanzu Observability Usage integration and the Usage Summary dashboard. The dashboards allow you to look at both current usage and usage over time. If you need to drill down more, use the wftop GUI for a detailed view of current spikes.
Why do I have cardinality problems?
-
If you know there's a spike in data (for example, an ID burst), you can use wftop or the Spy utility during the spike to drill down into individual data points and tag values. Those two tools aren't as useful after the spike - use the Operations for Applications Usage integration dashboards instead.
+
If you know there's a spike in data (for example, an ID burst), you can use wftop or the Spy utility during the spike to drill down into individual data points and tag values. Those two tools aren't as useful after the spike - use the Tanzu Observability Usage integration dashboards instead.
From e271d732dd850300fccf79656af696572b0e376f Mon Sep 17 00:00:00 2001
From: shavidissa
Date: Thu, 21 Mar 2024 13:05:37 -0700
Subject: [PATCH 15/26] rename best practices
---
pages/doc/cardinality.md | 2 +-
pages/doc/csp_migration.md | 2 +-
pages/doc/wavefront_obsolescence_policy.md | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/pages/doc/cardinality.md b/pages/doc/cardinality.md
index f6863bd7d..44856cc3f 100644
--- a/pages/doc/cardinality.md
+++ b/pages/doc/cardinality.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: cardinality.html
summary: Learn about how the service deals with cardinality.
---
-VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports high cardinality when dealing with timeseries data and infinite cardinality in its distributed tracing offering. Tanzu Observability can handle more than 200,000 concurrently running containers per Kubernetes cluster. In certain situations, however, high cardinality can cause system slowdown and metrics retrieval issues.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports high cardinality when dealing with timeseries data and infinite cardinality in its distributed tracing offering. Tanzu Observability can handle more than 200,000 concurrently running containers per Kubernetes cluster. In certain situations, however, high cardinality can cause system slowdown and metrics retrieval issues.
## Video
diff --git a/pages/doc/csp_migration.md b/pages/doc/csp_migration.md
index ae07fc5cc..f373269d0 100644
--- a/pages/doc/csp_migration.md
+++ b/pages/doc/csp_migration.md
@@ -87,7 +87,7 @@ During the process of onboarding your Tanzu Observability service to VMware Clou
## How Are the Groups Migrated to VMware Cloud Services?
-Originally, your Operation for Applications service includes the **Everyone** and **Service Accounts** system groups as well as any other custom groups that you have created.
+Originally, your Tanzu Observability service includes the **Everyone** and **Service Accounts** system groups as well as any other custom groups that you have created.
### How Are the Custom Groups Migrated?
diff --git a/pages/doc/wavefront_obsolescence_policy.md b/pages/doc/wavefront_obsolescence_policy.md
index ec93ea85d..8215604c6 100644
--- a/pages/doc/wavefront_obsolescence_policy.md
+++ b/pages/doc/wavefront_obsolescence_policy.md
@@ -181,7 +181,7 @@ rawsum(align(1m, mean, ts(\"~agent.buffer.task-count\")))
rawsum(align(1m, mean, ts(\"~proxy.buffer.task-count\")))
```
-## Operations for Applications Authentication and Authorization
+## Tanzu Observability Authentication and Authorization
Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. VMware Cloud services provides centralized authentication and authorization to your entire VMware Cloud services portfolio across hybrid and native public clouds, including Tanzu Observability. See [Advantages of VMware Cloud Services Subscriptions Over Original Subscriptions](subscriptions-differences.html#advantages-of-vmware-cloud-services-subscriptions-over-original-subscriptions).
@@ -189,5 +189,5 @@ Starting September 20, 2023, all **new trial** instances of Tanzu Observability
In October, 2023, we start to incrementally [onboard](csp_migration.html) all **original** subscriptions, which use Tanzu Observability authentication and authorization, to VMware Cloud services.
-{% include warning.html content="The Tanzu Observability 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 Tanzu Observability 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 Tanzu Observability API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy)." %}
+{% include warning.html content="The Tanzu Observability 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 Tanzu Observability API tokens with VMware Cloud Services access tokens](csp_migration.html#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token), including [the Tanzu Observability API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy)." %}
From 0ae43690204893c1c0fa21cec7a7995ea04ecc07 Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Fri, 22 Mar 2024 15:37:23 +0200
Subject: [PATCH 16/26] rebranding updated RNs
---
pages/doc/2023-13.x_release_notes.md | 4 ++--
pages/doc/2023-29.x_release_notes.md | 2 +-
pages/doc/2023-52.x_release_notes.md | 10 +++++-----
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/pages/doc/2023-13.x_release_notes.md b/pages/doc/2023-13.x_release_notes.md
index d4b676923..cb17d7cae 100644
--- a/pages/doc/2023-13.x_release_notes.md
+++ b/pages/doc/2023-13.x_release_notes.md
@@ -56,7 +56,7 @@ These release notes give an overview of the changes for the 2023-07.x to 2023-13
## 2023-09.x Release Notes
-**Analyze Your Queries**: With this release you can use the Query Analyzer and [analyze your queries and their subqueries](query_language_performance.html#use-the-query-analyzer). When you expect to see certain data in Operations for Applications, but it doesn’t show up for some reason, charts display a **No Data** message. When you see this message on a chart, use the Query Analyzer to analyze and troubleshoot your queries and subqueries.
+**Analyze Your Queries**: With this release you can use the Query Analyzer and [analyze your queries and their subqueries](query_language_performance.html#use-the-query-analyzer). When you expect to see certain data in Tanzu Observability, but it doesn’t show up for some reason, charts display a **No Data** message. When you see this message on a chart, use the Query Analyzer to analyze and troubleshoot your queries and subqueries.
## 2023-08.x Release Notes
@@ -97,7 +97,7 @@ These release notes give an overview of the changes for the 2023-07.x to 2023-13
You can subscribe to notifications for incidents and scheduled maintenance of your service. Subscribe for Status Updates.
-
+
diff --git a/pages/doc/2023-29.x_release_notes.md b/pages/doc/2023-29.x_release_notes.md
index b3ed5af48..6a1305068 100644
--- a/pages/doc/2023-29.x_release_notes.md
+++ b/pages/doc/2023-29.x_release_notes.md
@@ -29,7 +29,7 @@ These release notes give an overview of the changes for the 2023-18.x to 2023-29
## 2023-25.x Release Notes
-* **Wavefront Proxy Release**: We’ve just released [Wavefront proxy 13](https://github.com/wavefrontHQ/wavefront-proxy/releases), which supports sending data to Operations for Applications subscriptions **onboarded** to VMware Cloud Services by using a VMware Cloud services access token.
+* **Wavefront Proxy Release**: We’ve just released [Wavefront proxy 13](https://github.com/wavefrontHQ/wavefront-proxy/releases), which supports sending data to Tanzu Observability subscriptions **onboarded** to VMware Cloud Services by using a VMware Cloud services access token.
* **New Fields in the Generic Webhook Alert Template**: We added two new fields to the Generic Webhook notification template which allow you to extract information about the filter-by and group-by keys. For information and examples, see [Extract Information About the Filter-by and Group-by Keys](alert_target_customizing.html#extract-information-about-the-filter-by-and-group-by-keys).
## 2023-20.x Release Notes
diff --git a/pages/doc/2023-52.x_release_notes.md b/pages/doc/2023-52.x_release_notes.md
index ec2ca1047..f49eb707d 100644
--- a/pages/doc/2023-52.x_release_notes.md
+++ b/pages/doc/2023-52.x_release_notes.md
@@ -6,7 +6,7 @@ permalink: 2023-52.x_release_notes.html
summary: New and updated features.
---
-These release notes give an overview of the changes for the 2023-31.x to 2023-52.x releases of the Aria Operations for Applications (previously known as Tanzu Observability by Wavefront) service.
+These release notes give an overview of the changes for the 2023-31.x to 2023-52.x releases of the VMware Tanzu Observability (previously known as VMware Aria Operations for Applications) service.
## 2023-52.x Release Notes
@@ -40,7 +40,7 @@ Example: An annotated screenshot of the create traces security policy for origin
### Onboarded Subscriptions
-**New Admin Permission and Service Role**: With this release, we introduce the **Admin** [permission](csp_permissions_overview.html#operations-for-applications-permissions) and [service role](csp_users_roles.html#operations-for-applications-service-roles-built-in). **Admin** users can manage the Operations for Applications organization settings.
+**New Admin Permission and Service Role**: With this release, we introduce the **Admin** [permission](csp_permissions_overview.html#operations-for-applications-permissions) and [service role](csp_users_roles.html#operations-for-applications-service-roles-built-in). **Admin** users can manage the Tanzu Observability organization settings.
### Original and Onboarded Subscriptions
@@ -74,7 +74,7 @@ On the **Cloud Integrations** page, now you can:
### Original and Onboarded Subscriptions
-* **Alerts Improvements**: When the **Resolve Window** for an alert is deleted by using an external tool, in the Operations for Applications UI, the **Alert** will now properly display that the **Resolve Window** matches the **Trigger Window**.
+* **Alerts Improvements**: When the **Resolve Window** for an alert is deleted by using an external tool, in the Tanzu Observability UI, the **Alert** will now properly display that the **Resolve Window** matches the **Trigger Window**.
* **Sources Browser Page Improvements**: The [**Sources** browser page](sources_managing.html#examine-sources-in-the-source-browser) is now improved and allows you to:
@@ -133,6 +133,6 @@ On the **Cloud Integrations** page, now you can:
### Onboarded Subscriptions Only
-* **Support for Kubernetes Integration Setup**: We added support for setting up the Kubernetes integration when your Operations for Applications service is onboarded to VMware Cloud services. See the [Integrations Release Notes](integrations_new_changed.html#august-2023) for details.
+* **Support for Kubernetes Integration Setup**: We added support for setting up the Kubernetes integration when your Tanzu Observability service is onboarded to VMware Cloud services. See the [Integrations Release Notes](integrations_new_changed.html#august-2023) for details.
-* **Support for Tanzu Application Service Integration Setup**: We added support for setting up the Tanzu Application Service integration when your Operations for Applications service is onboarded to VMware Cloud services. See the [Integrations Release Notes](integrations_new_changed.html#august-2023) for details.
+* **Support for Tanzu Application Service Integration Setup**: We added support for setting up the Tanzu Application Service integration when your Tanzu Observability service is onboarded to VMware Cloud services. See the [Integrations Release Notes](integrations_new_changed.html#august-2023) for details.
From db7e8dad221c782c4a24d106102e829333307533 Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Mon, 25 Mar 2024 17:49:31 +0200
Subject: [PATCH 17/26] some more renaming
---
pages/doc/cardinality.md | 2 +-
pages/doc/missing_data_troubleshooting.md | 2 +-
pages/doc/monitoring_overview.md | 6 ++---
pages/doc/telegraf_details.md | 2 +-
pages/doc/ts_aliasMetric.md | 4 +--
pages/doc/ts_aliasSource.md | 6 ++---
pages/doc/ts_cumulativeHisto.md | 18 ++++++-------
pages/doc/ts_frequencyHisto.md | 14 +++++-----
pages/doc/wavefront_api_usage.md | 22 ++++++++--------
pages/doc/wavefront_limits.md | 6 ++---
pages/doc/wavefront_pricing.md | 6 ++---
pages/doc/wavefront_release_notes.md | 2 +-
pages/doc/wavefront_security.md | 32 +++++++++++------------
13 files changed, 61 insertions(+), 61 deletions(-)
diff --git a/pages/doc/cardinality.md b/pages/doc/cardinality.md
index 44856cc3f..f6863bd7d 100644
--- a/pages/doc/cardinality.md
+++ b/pages/doc/cardinality.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: cardinality.html
summary: Learn about how the service deals with cardinality.
---
-Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports high cardinality when dealing with timeseries data and infinite cardinality in its distributed tracing offering. Tanzu Observability can handle more than 200,000 concurrently running containers per Kubernetes cluster. In certain situations, however, high cardinality can cause system slowdown and metrics retrieval issues.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) supports high cardinality when dealing with timeseries data and infinite cardinality in its distributed tracing offering. Tanzu Observability can handle more than 200,000 concurrently running containers per Kubernetes cluster. In certain situations, however, high cardinality can cause system slowdown and metrics retrieval issues.
## Video
diff --git a/pages/doc/missing_data_troubleshooting.md b/pages/doc/missing_data_troubleshooting.md
index 54421dc13..c908f0f72 100644
--- a/pages/doc/missing_data_troubleshooting.md
+++ b/pages/doc/missing_data_troubleshooting.md
@@ -7,7 +7,7 @@ permalink: missing_data_troubleshooting.html
summary: Learn how to troubleshoot when you expect to see data but it doesn't appear in charts.
---
-Sometimes you expect to see certain data in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) but, for some reason, it doesn't show up! This can be a frustrating and confusing experience, especially when you urgently need the data. Operations for Applications does not delete data - the [retention period](terms_of_service.html#data-retention) is 18 months for persistent metrics and 28 days for ephemeral metrics. What could be the problem?
+Sometimes you expect to see certain data in VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) but, for some reason, it doesn't show up! This can be a frustrating and confusing experience, especially when you urgently need the data. Tanzu Observability does not delete data - the [retention period](terms_of_service.html#data-retention) is 18 months for persistent metrics and 28 days for ephemeral metrics. What could be the problem?
This doc page, based on the extensive experience of our customer success team, helps you investigate, understand, and remedy possible causes. In addition to manually investigating and troubleshooting your issues, you can use the [Query Analyzer](query_language_performance.html#use-the-query-analyzer) which helps you identify where exactly the problem is.
diff --git a/pages/doc/monitoring_overview.md b/pages/doc/monitoring_overview.md
index 7e3a861a7..ac22c1b71 100644
--- a/pages/doc/monitoring_overview.md
+++ b/pages/doc/monitoring_overview.md
@@ -6,10 +6,10 @@ permalink: monitoring_overview.html
summary: Understand how out-of-the-box dashboards and tools help you find problems
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) is perfect if you want to monitor lots of hosts or lots of metrics. For example, you can monitor hundreds of thousands of Kubernetes containers. But how well the system performs can still depend on the quality of the input:
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is perfect if you want to monitor lots of hosts or lots of metrics. For example, you can monitor hundreds of thousands of Kubernetes containers. But how well the system performs can still depend on the quality of the input:
* Are the data points you're sending easy to ingest? Too many unique combinations of metric, source, and tag slow down the environment and make it hard to understand what's going on when you look at charts.
-* Are you actually using all the data you send in? It's tempting to send all data to Operations for Applications, and then analyze what seems suitable. But if you examine which data your dashboards and queries actually use, you might be able to get faster query displays and more easily stay within your allocated PPS budget.
+* Are you actually using all the data you send in? It's tempting to send all data to Tanzu Observability, and then analyze what seems suitable. But if you examine which data your dashboards and queries actually use, you might be able to get faster query displays and more easily stay within your allocated PPS budget.
## Find Slow Queries and Improve Dashboard Response
@@ -35,7 +35,7 @@ You can find queries that are exceptionally slow by checking the **Slow Query**
And even if a query isn't listed there, there are some guidelines for queries:
-1. When sending data to Operations for Applications, consider the [Operations for Applications data format best practices](wavefront_data_format.html#operations-for-applications-data-format-best-practices), for example:
+1. When sending data to Tanzu Observability, consider the [Tanzu Observability data format best practices](wavefront_data_format.html#tanzu-observability-data-format-best-practices), for example:
* Make the metrics the most stable part of your data. For example, don't include a unique ID in each metric.
* Keep the number of distinct combinations of metric, source, and tags under 1000. For example, avoid including a timestamp in your metric. Instead, look at the metric over time in chart.
diff --git a/pages/doc/telegraf_details.md b/pages/doc/telegraf_details.md
index 0ccd019a6..fc33823c9 100644
--- a/pages/doc/telegraf_details.md
+++ b/pages/doc/telegraf_details.md
@@ -6,7 +6,7 @@ sidebar: doc_sidebar
permalink: telegraf_details.html
summary: Troubleshoot your Telegraf installation
---
-A common way to collect and send metric data to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) is through a Telegraf agent that is configured to relay the metrics to a Wavefront proxy. This doc page has some Telegraf troubleshooting and tuning information. See [Proxy Troubleshooting](proxies_troubleshooting.html) for details on resolving proxy problems.
+A common way to collect and send metric data to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is through a Telegraf agent that is configured to relay the metrics to a Wavefront proxy. This doc page has some Telegraf troubleshooting and tuning information. See [Proxy Troubleshooting](proxies_troubleshooting.html) for details on resolving proxy problems.
## Connection Troubleshooting
diff --git a/pages/doc/ts_aliasMetric.md b/pages/doc/ts_aliasMetric.md
index a87dc970b..706e869b6 100644
--- a/pages/doc/ts_aliasMetric.md
+++ b/pages/doc/ts_aliasMetric.md
@@ -115,12 +115,12 @@ aliasMetric(ts(aws.instance.price), "Price/{{region}}/{{source}}")
```
{% endraw %}
-The specified replacement string acts like a template, in which VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) replaces each variable with the requested string value. If `ts(aws.instance.price)` describes a time series that has a point tag `region=us-west-2`, that time series is displayed with a metric name like `Price/us-west-2/mycluster-2c-ha2-i-00e421d1bef7fb88e`.
+The specified replacement string acts like a template, in which VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) replaces each variable with the requested string value. If `ts(aws.instance.price)` describes a time series that has a point tag `region=us-west-2`, that time series is displayed with a metric name like `Price/us-west-2/mycluster-2c-ha2-i-00e421d1bef7fb88e`.
### Single Extracted Node
-A common practice is to use naming conventions that provide structure to metric names, source names, or point tag values. Naming conventions typically subdivide metadata values into nodes, which are substrings that are delimited by certain characters. By default, Operations for Applications uses periods (".") as node delimiters, but your naming conventions might use other characters.
+A common practice is to use naming conventions that provide structure to metric names, source names, or point tag values. Naming conventions typically subdivide metadata values into nodes, which are substrings that are delimited by certain characters. By default, Tanzu Observability uses periods (".") as node delimiters, but your naming conventions might use other characters.
You can use `aliasMetric()` with a `zeroBasedNodeIndex` to extract a single node from an existing metadata value and use just the extracted node as the metric name for your time series. For example, you might want to simplify a metric name like `pdx.customerA_latency.i49f21a72` by displaying it as `customerA_latency`.
diff --git a/pages/doc/ts_aliasSource.md b/pages/doc/ts_aliasSource.md
index 7f597c8e0..c3af8ef1a 100644
--- a/pages/doc/ts_aliasSource.md
+++ b/pages/doc/ts_aliasSource.md
@@ -117,11 +117,11 @@ aliasSource(ts(aws.instance.price), "Price/{{region}}/{{source}}")
```
{% endraw %}
-The specified replacement string acts like a template, in which VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) replaces each variable with the requested string value. If a time series has a point tag `region=us-west-2`, that time series is displayed with a source name like `Price/us-west-2/mycluster-2c-ha2-i-00e421d1bef7fb88e`.
+The specified replacement string acts like a template, in which VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) replaces each variable with the requested string value. If a time series has a point tag `region=us-west-2`, that time series is displayed with a source name like `Price/us-west-2/mycluster-2c-ha2-i-00e421d1bef7fb88e`.
### Single Extracted Node
-A common practice is to use naming conventions that provide structure to metric names, source names, or point tag values. Naming conventions typically subdivide metadata values into nodes, which are substrings that are delimited by certain characters. By default, Operations for Applications uses periods (".") as node delimiters, but your naming conventions might use other characters.
+A common practice is to use naming conventions that provide structure to metric names, source names, or point tag values. Naming conventions typically subdivide metadata values into nodes, which are substrings that are delimited by certain characters. By default, Tanzu Observability uses periods (".") as node delimiters, but your naming conventions might use other characters.
You can use `aliasSource()` with a `zeroBasedNodeIndex` to extract a single node from an existing metadata value and use just the extracted node as the metric name for your time series. For example, you might want to simplify a source name like `dev.host1_appA.0fd795b1700` by displaying it as `host1_appA`.
@@ -188,7 +188,7 @@ aliasSource(ts("requests.failures.num"),1,"-")
### Extracted Node Example 2 - Renaming Source(s) with a Metric Name
-This example assumes 1 physical server running 8 virtual machines. Each virtual machine is sending stats into Operations for Applications. The source name is the physical server. The unique virtual machine name is only in the metric name:
+This example assumes 1 physical server running 8 virtual machines. Each virtual machine is sending stats into Tanzu Observability. The source name is the physical server. The unique virtual machine name is only in the metric name:
```
ts(disk.space.total.vm1)
diff --git a/pages/doc/ts_cumulativeHisto.md b/pages/doc/ts_cumulativeHisto.md
index a0c4f29eb..d8d74ecac 100644
--- a/pages/doc/ts_cumulativeHisto.md
+++ b/pages/doc/ts_cumulativeHisto.md
@@ -4,7 +4,7 @@ keywords: query language reference
tags: [reference page]
sidebar: doc_sidebar
permalink: ts_cumulativeHisto.html
-summary: Reference to the cumulativeHisto() function. Convert Prometheus cumulative histograms to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) histograms.
+summary: Reference to the cumulativeHisto() function. Convert Prometheus cumulative histograms to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) histograms.
---
## Summary
```
@@ -12,7 +12,7 @@ cumulativeHisto([,] [,]
[,metrics|sources|sourceTags|pointTags|] )
```
-Converts a cumulative histogram coming from Prometheus, Telegraf, or other source to an ordinary histogram in Operations for Applications histogram format. Users can then manipulate the histogram with [Operations for Applications histogram query functions](query_language_reference.html#histogram-functions).
+Converts a cumulative histogram coming from Prometheus, Telegraf, or other source to an ordinary histogram in Tanzu Observability histogram format. Users can then manipulate the histogram with [Tanzu Observability histogram query functions](query_language_reference.html#histogram-functions).
{% include note.html content ="Always use the `_bucket` metric. The `_count` and `_sum` metrics won't return results. "%}
@@ -51,15 +51,15 @@ When a chart displays the result of this function, it shows the median by defaul
### Ordinary and Cumulative Histograms
-Operations for Applications histogram distributions are ordinary histograms. In contrast, some other tools, such as Prometheus and Telegraf, use cumulative histograms.
+Tanzu Observability histogram distributions are ordinary histograms. In contrast, some other tools, such as Prometheus and Telegraf, use cumulative histograms.
(image credit: Wikipedia)
-If your data source emits cumulative histograms, you can use this function to visualize your histogram data in Operations for Applications dashboards and charts.
+If your data source emits cumulative histograms, you can use this function to visualize your histogram data in Tanzu Observability dashboards and charts.
-### How to Map Prometheus Queries to Operations for Applications Queries
+### How to Map Prometheus Queries to Tanzu Observability Queries
When you use Prometheus, you run queries like this:
```
@@ -68,7 +68,7 @@ histogram_quantile(0.90, sum(rate(req_latency_bucket[5m])) by (le))
This query displays the 90th quantile of a cumulative histogram that corresponds to the `req_latency_bucket` metric. The `le` parameter means less than or equal.
-The corresponding Operations for Applications query looks like this:
+The corresponding Tanzu Observability query looks like this:
```
percentile(90, cumulativeHisto(sum(rate(ts(req_latency_bucket)), le)))
```
@@ -136,10 +136,10 @@ Then we use the `cumulativeHisto()` function to return the cumulative histogram
## See Also
-* The [cumulativePercentile function doc page](ts_cumulativePercentile.html) that explains how to calculate the cumulative percentile without the need to convert the cumulative Prometheus histogram to an Operations for Applications ordinary histogram.
+* The [cumulativePercentile function doc page](ts_cumulativePercentile.html) that explains how to calculate the cumulative percentile without the need to convert the cumulative Prometheus histogram to an Tanzu Observability ordinary histogram.
* [This blog post](https://tanzu.vmware.com/content/vmware-tanzu-observability-blog/integrating-prometheus-with-wavefront-for-easy-scaling-and-failover) discusses the [Prometheus integration](prometheus.html) in some detail.
-* The [How to Make Prometheus Monitoring Enterprise Ready](https://tanzu.vmware.com/content/vmware-tanzu-observability-blog/how-to-make-prometheus-monitoring-enterprise-ready) blog post explores how using Prometheus for metrics collection and Operations for Applications for data storage and visualization can give you the best of both worlds.
-* Our [histogram doc page](proxies_histograms.html) gives background information about Operations for Applications histograms.
+* The [How to Make Prometheus Monitoring Enterprise Ready](https://tanzu.vmware.com/content/vmware-tanzu-observability-blog/how-to-make-prometheus-monitoring-enterprise-ready) blog post explores how using Prometheus for metrics collection and Tanzu Observability for data storage and visualization can give you the best of both worlds.
+* Our [histogram doc page](proxies_histograms.html) gives background information about Tanzu Observability histograms.
## Caveats
diff --git a/pages/doc/ts_frequencyHisto.md b/pages/doc/ts_frequencyHisto.md
index f2b3e54a1..88326abca 100644
--- a/pages/doc/ts_frequencyHisto.md
+++ b/pages/doc/ts_frequencyHisto.md
@@ -12,7 +12,7 @@ frequencyHisto([,] [,]
[,metrics|sources|sourceTags|pointTags|] )
```
-Converts a histogram coming from Google Cloud Platform(GCP) to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) histogram format. When GCP Detailed Histogram Metrics is enabled, the query engine will additionally ingest bucket counts for GCP distributions, with metric namegcp..bucket.
+Converts a histogram coming from Google Cloud Platform(GCP) to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) histogram format. When GCP Detailed Histogram Metrics is enabled, the query engine will additionally ingest bucket counts for GCP distributions, with metric namegcp..bucket.
Enabling GCP Detailed Histogram Metrics will increase your ingestion rate and cost.
@@ -33,7 +33,7 @@ Users can manipulate the resulting histograms with our [histogram query function
Optional string that describes the bucket. Default is lt, that is, less than. If your source histogram uses a different tag key to specify the buckets, specify that tag key here.
Optional group by parameter for organizing the time series into subgroups and then returning each histogram subgroup.
@@ -45,9 +45,9 @@ Use one or more parameters to group by metric names, source names, source tag na
## Description
-This function converts ordinary histogram data to Operations for Applications histograms. Histogram data is defined as a set of time series where each series represents the frequency of outcomes in a particular bucket, bounded by a tag such as `lt`.
+This function converts ordinary histogram data to Tanzu Observability histograms. Histogram data is defined as a set of time series where each series represents the frequency of outcomes in a particular bucket, bounded by a tag such as `lt`.
-One use case is to visualize GCP distributions, which can be ingested by the Operations for Applications service using the [Google Cloud Platform Integration](gcp.html). Distribution bucket data is ingested as `gcp..bucket` with an `lt` tag defining the upper bound of each bucket. You can use `frequencyHisto(ts(gcp..bucket))` to convert the bucket data to an Operations for Applications histogram.
+One use case is to visualize GCP distributions, which can be ingested by the Tanzu Observability service using the [Google Cloud Platform Integration](gcp.html). Distribution bucket data is ingested as `gcp..bucket` with an `lt` tag defining the upper bound of each bucket. You can use `frequencyHisto(ts(gcp..bucket))` to convert the bucket data to a Tanzu Observability histogram.
When a chart displays the result of this function, it shows the median by default. You can use `percentile()` to change that and, for example, show the 90% percentile.
@@ -79,15 +79,15 @@ Now let's do the same with WQL. The GCP integration ingests the distribution's b
-Then we use `frequencyHisto()` to convert the data to an Operations for Applications histogram and group by `location`, and finally, we use `percentile()` to find the 95th percentile of the histogram.
+Then we use `frequencyHisto()` to convert the data to a Tanzu Observability histogram and group by `location`, and finally, we use `percentile()` to find the 95th percentile of the histogram.
## See Also
-* Our [histogram doc page](proxies_histograms.html) gives background information about Operations for Applications histograms.
-* The `cumulativeHisto()` function is similar but converts Prometheus cumulative histograms to Operations for Applications ordinary histograms.
+* Our [histogram doc page](proxies_histograms.html) gives background information about Tanzu Observability histograms.
+* The `cumulativeHisto()` function is similar but converts Prometheus cumulative histograms to Tanzu Observability ordinary histograms.
## Caveats
diff --git a/pages/doc/wavefront_api_usage.md b/pages/doc/wavefront_api_usage.md
index d464ace16..c06251cd6 100644
--- a/pages/doc/wavefront_api_usage.md
+++ b/pages/doc/wavefront_api_usage.md
@@ -1,5 +1,5 @@
---
-title: Use the Operations for Applications REST API
+title: Use the Tanzu Observability REST API
keywords: getting started
tags: [getting started]
sidebar: doc_sidebar
@@ -7,7 +7,7 @@ permalink: using_wavefront_api.html
summary: Learn how to use the REST API outside of the in-product API documentation UI.
---
-The [REST API](wavefront_api.html) enables you to interact with the VMware Aria Operations for Applications service (formerly known as Tanzu Observability by Wavefront) by using standard REST API tools. You can use the REST API to automate commonly executed operations, for example, to tag sources automatically.
+The [REST API](wavefront_api.html) enables you to interact with the VMware Tanzu Observability service (formerly known as VMware Aria Operations for Applications) by using standard REST API tools. You can use the REST API to automate commonly executed operations, for example, to tag sources automatically.
When you make REST API calls outside the REST API documentation UI, you must use a token to authenticate. The token that you need depends on your [subscription type](subscriptions-differences.html).
@@ -15,7 +15,7 @@ When you make REST API calls outside the REST API documentation UI, you must use
- User accounts use VMware Cloud services API tokens to retrieve access tokens. See [How do I generate API tokens](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-E2A3B1C1-E9AD-4B00-A6B6-88D31FCDDF7C.html) in the VMware Cloud services documentation.
- - Server to server apps, which correspond to service accounts in Operations for Applications, use OAuth 2.0 client credentials (ID and secret) to retrieve access tokens. See [How to use OAuth 2.0 for server to server apps](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-327AE12A-85DB-474B-89B2-86651DF91C77.html) in the VMware Cloud services documentation.
+ - Server to server apps, which correspond to service accounts in Tanzu Observability, use OAuth 2.0 client credentials (ID and secret) to retrieve access tokens. See [How to use OAuth 2.0 for server to server apps](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-327AE12A-85DB-474B-89B2-86651DF91C77.html) in the VMware Cloud services documentation.
* For original subscriptions, invoking the Operations for Application REST API requires an Operations for Application API token. An API token can be associated with a user account or service account See [Manage API Tokens](api_tokens.html).
@@ -24,7 +24,7 @@ When you make REST API calls outside the REST API documentation UI, you must use
## VMware Cloud Services Subscriptions
-Invoking the REST API of an Operations for Applications subscription on VMware Cloud services requires a VMware Cloud services access token.
+Invoking the REST API of a Tanzu Observability subscription on VMware Cloud services requires a VMware Cloud services access token.
### Make API Calls by Using a User Account
@@ -51,7 +51,7 @@ If you want to use [your own user account](csp_users_account_managing.html) to m
curl 'https:///api/v2/cloudintegration' -H 'Authorization: Bearer '
```
- Here, `` is the name of your Operations for Applications service instance, and `` is the access token for your user account.
+ Here, `` is the name of your Tanzu Observability service instance, and `` is the access token for your user account.
### Make API Calls by Using a Server to Server App
@@ -59,9 +59,9 @@ If you want to use [your own user account](csp_users_account_managing.html) to m
If you want to use a [**server to server app**](csp_server_to_server_apps.html) to make the REST API calls, obtain the OAuth credentials (ID and secret) associated with the server to server app and exchange them for an access token.
1. Create a server to server app in VMware Cloud services.
-1. Assign one or more roles to the server to server app to grant it the Operations for Applications access it needs.
+1. Assign one or more roles to the server to server app to grant it the Tanzu Observability access it needs.
1. Obtain the OAuth 2.0 client credentials of the server to server app and save them to a secure place.
-1. Add the app to your VMware Cloud organization running the Operations for Applications service.
+1. Add the app to your VMware Cloud organization running the Tanzu Observability service.
1. Encode the server to server OAuth 2.0 client credentials (ID and secret) to Base64 format.
1. Exchange the Base64 encoded OAuth 2.0 client credentials for an access token.
@@ -78,13 +78,13 @@ If you want to use a [**server to server app**](csp_server_to_server_apps.html)
```
curl 'https:///api/v2/cloudintegration' -H 'Authorization: Bearer '
```
- Here, `` is the name of your Operations for Applications service instance, and `` is the access token for the server to server app.
+ Here, `` is the name of your Tanzu Observability service instance, and `` is the access token for the server to server app.
For more information, see [How to use OAuth 2.0 for server to server apps](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-327AE12A-85DB-474B-89B2-86651DF91C77.html) in the VMware Cloud services documentation.
## Original Subscriptions
-Invoking the REST API of an original Operations for Applications subscription requires an Operations for Applications API token.
+Invoking the REST API of an original Tanzu Observability subscription requires a Tanzu Observability API token.
### Make API Calls by Using a User Account
@@ -99,7 +99,7 @@ If you want to use [your own user account](users_account_managing.html) to make
curl 'https:///api/v2/cloudintegration' -H 'Authorization: Bearer '
```
- Here, `` is the name of your Operations for Applications service instance, and `` is the API token for your user account.
+ Here, `` is the name of your Tanzu Observability service instance, and `` is the API token for your user account.
### Make API Calls by Using a Service Account
@@ -117,4 +117,4 @@ If you want to use a [service account](service-accounts.html) to make REST API c
curl 'https:///api/v2/cloudintegration' -H 'Authorization: Bearer '
```
- Here, `` is the name of your Operations for Applications service instance, and `` is the API token for the service account.
+ Here, `` is the name of your Tanzu Observability service instance, and `` is the API token for the service account.
diff --git a/pages/doc/wavefront_limits.md b/pages/doc/wavefront_limits.md
index 8bce759b9..8a9692f8d 100644
--- a/pages/doc/wavefront_limits.md
+++ b/pages/doc/wavefront_limits.md
@@ -5,7 +5,7 @@ sidebar: doc_sidebar
permalink: wavefront_limits.html
summary: Limits and recommendations to promote efficient resource use.
---
-For best performance and cost reduction, VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) supports limits. Some limits are recommendations--if your environment exceeds the limits, you'll see significant performance issues. Other limits result in an error if you exceed the limit.
+For best performance and cost reduction, VMware Tanzu Observability (formerly known as Mware Aria Operations for Applications) supports limits. Some limits are recommendations--if your environment exceeds the limits, you'll see significant performance issues. Other limits result in an error if you exceed the limit.
@@ -198,7 +198,7 @@ Follow best practices to avoid hitting query limits and for improved query execu
- Organize metric names in a meaningful hierarchy from most general to most specific (i.e. `system.cpu0.loadavg.1m` instead of `1m.loadavg.cpu0.system`)
* For best performance, keep the number of distinct time series per metric and host to under 1000.
-See [Operations for Applications Data Naming](wavefront_data_format.html#operations-for-applications-data-format-best-practices) for more best practices.
+See [Tanzu Observability Data Naming](wavefront_data_format.html#tanzu-observability-data-format-best-practices) for more best practices.
@@ -206,6 +206,6 @@ See [Operations for Applications Data Naming](wavefront_data_format.html#operati
You can examine what's going on with your cluster in several ways:
-* [Monitor and troubleshoot your VMware Aria Operations for Applications instance](wavefront_monitoring.html)
+* [Monitor and troubleshoot your Tanzu Observability instance](wavefront_monitoring.html)
* [Examine ingestion breakdown and export usage data](ingestion_policies.html)
* [Use Wavefront Top or Spy to Investigate Traffic](wavefront_monitoring_spy.html)
diff --git a/pages/doc/wavefront_pricing.md b/pages/doc/wavefront_pricing.md
index 4509b1b62..f243dd42b 100644
--- a/pages/doc/wavefront_pricing.md
+++ b/pages/doc/wavefront_pricing.md
@@ -1,18 +1,18 @@
---
-title: Operations for Applications Pricing
+title: Tanzu Observability Pricing
tags: [administration]
sidebar: doc_sidebar
permalink: wavefront_pricing.html
summary: Summary of pricing information.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) pricing depends on the contract that your company has with VMware, on the types on data you're ingesting, and on some other factors. This page gives an overview of pricing for the different types of data you can send to Operations for Applications.
+VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) pricing depends on the contract that your company has with VMware, on the types on data you're ingesting, and on some other factors. This page gives an overview of pricing for the different types of data you can send to Tanzu Observability.
{% include note.html content="Some customers have special rates, for example, because they're helping us to test a new feature. The information on this page covers the most common case. "%}
## Pricing Structure
At the core of the model is the idea of consumption-based pricing. What you pay is based on data throughput, primarily:
-* **Data ingestion**. When the Operations for Applications service ingests data, the data is consumed and count toward your allocation.
+* **Data ingestion**. When the Tanzu Observability service ingests data, the data is consumed and count toward your allocation.
* **Data scanning**. When you run a query, either as part of an alert or when you look at a dashboard, the backend has to scan the data. Scanning counts toward your allocation.
The model has this basic pricing structure:
diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md
index 3b3829b49..feaee1e14 100644
--- a/pages/doc/wavefront_release_notes.md
+++ b/pages/doc/wavefront_release_notes.md
@@ -65,7 +65,7 @@ In October, 2023, we start to incrementally [**onboard**](csp_migration.html) al
## 2024-03.x Release Notes
-* **Updated Support Link**: The link for contacting our Technical Support team from within the Operations for Applications user interface is now updated. To open a support ticket, click the gear icon on the toolbar and select **Support**.
+* **Updated Support Link**: The link for contacting our Technical Support team from within the Tanzu Observability user interface is now updated. To open a support ticket, click the gear icon on the toolbar and select **Support**.
* **Derived Metrics Browser Improvements**: We improved the user experience of the **Derived Metrics Browser**. To navigate to this page, select **Browse > Derived Metrics**.
diff --git a/pages/doc/wavefront_security.md b/pages/doc/wavefront_security.md
index 8620650f6..930dc24fd 100644
--- a/pages/doc/wavefront_security.md
+++ b/pages/doc/wavefront_security.md
@@ -3,18 +3,18 @@ title: Security
tags: [administration]
sidebar: doc_sidebar
permalink: wavefront_security.html
-summary: Understand how VMware Aria Operations for Applications secures your data and supports fine-tuning security for your cluster.
+summary: Understand how VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) secures your data and supports fine-tuning security for your cluster.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) protects your data and includes facilities for you to customize authentication and authorization.
+Tanzu Observability protects your data and includes facilities for you to customize authentication and authorization.
This page gives a summary.
* Download this [white paper](https://tanzu.vmware.com/content/white-papers/vmware-tanzu-observability-security-and-privacy) for a detailed discussion.
-* Download and review the [Cloud Security Alliance Consensus Assessments Initiative Questionnaire for VMware Aria Operations for Applications](https://cloudsecurityalliance.org/star/registry/vmware-inc/) for our consensus assessment questionnaire.
+* Download and review the [Cloud Security Alliance Consensus Assessments Initiative Questionnaire for VMware Tanzu Observability](https://cloudsecurityalliance.org/star/registry/vmware-inc/) for our consensus assessment questionnaire.
## Certifications
-Operations for Applications has successfully completed all requirements for the following certifications and reports:
+Tanzu Observability has successfully completed all requirements for the following certifications and reports:
* ISO 27001/27017/27018
* SOC 2 Type 1
@@ -22,13 +22,13 @@ Operations for Applications has successfully completed all requirements for the
## Privacy
-Operations for Applications is used for monitoring applications. Operations for Applications securely stores user name and password information, but does not collect information about individual users. We do not install agents that collect user information.
+Tanzu Observability is used for monitoring applications. Tanzu Observability securely stores user name and password information, but does not collect information about individual users. We do not install agents that collect user information.
None of the built-in integrations collect user information. However, our customers can set up their service instances to collect any type of information they want.
## Data Protection
-Currently, Operations for Applications uses AWS to run the service and to store customer application data.
+Currently, Tanzu Observability uses AWS to run the service and to store customer application data.
* The service is served from a single AWS region spread across multiple availability zones for failover.
* All incoming and outgoing traffic is encrypted.
@@ -46,15 +46,15 @@ Customers retain control and ownership of their content. We do not replicate cus
## High Availability
-Operations for Applications is architected to be highly available. In the event of a hardware failure, we automatically migrate to or restart workloads, on another host machine in the cluster and automatically restart the failed host. If the host machine fails to restart, or the performance of the restarted host is degraded, the service is capable of replacing the failed host in a cluster with an entirely new host within minutes.
+Tanzu Observability is architected to be highly available. In the event of a hardware failure, we automatically migrate to or restart workloads, on another host machine in the cluster and automatically restart the failed host. If the host machine fails to restart, or the performance of the restarted host is degraded, the service is capable of replacing the failed host in a cluster with an entirely new host within minutes.
## Disaster Recovery
-Operations for Applications supports the option of Disaster Recovery (DR) across regions for customers. Contact your Operations for Applications representative for details.
+Tanzu Observability supports the option of Disaster Recovery (DR) across regions for customers. Contact your Tanzu Observability representative for details.
## Networking
-Applications send data to Operations for Applications using either the [Wavefront proxy](proxies.html) or [direct ingestion](direct_ingestion.html). We protect all data traffic with TLS (Transport Layer Security) and HTTPS. If you send data directly to Operations for Applications, we require TLS 1.2 connections.
+Applications send data to Tanzu Observability using either the [Wavefront proxy](proxies.html) or [direct ingestion](direct_ingestion.html). We protect all data traffic with TLS (Transport Layer Security) and HTTPS. If you send data directly to Tanzu Observability, we require TLS 1.2 connections.
The Wavefront proxy uses HTTPS, and we offer options to secure it further:
* Perform a manual install and place the Wavefront proxy [behind an HTTP proxy](proxies_manual_install.html#configure-wavefront-proxy-with-an-httphttps-proxy).
@@ -66,19 +66,19 @@ The Wavefront proxy uses HTTPS, and we offer options to secure it further:
## Authentication
-Operations for Applications supports three methods of authentication.
+Tanzu Observability supports three methods of authentication.
* By using a user name and password.
- Operations for Applications supports user accounts and service accounts. User accounts [must authenticate](authentication.html) with a user name and password, service accounts authenticate with a token.
+ Tanzu Observability supports user accounts and service accounts. User accounts [must authenticate](authentication.html) with a user name and password, service accounts authenticate with a token.
* SAML SSO
- You can use the authentication provided by Operations for Applications or use one of the supported authentication integrations. We support several authentication solutions including Azure AD, Google ID, and Okta.
+ You can use the authentication provided by Tanzu Observability or use one of the supported authentication integrations. We support several authentication solutions including Azure AD, Google ID, and Okta.
We also support [self-service SAML SSO](auth_self_service_sso.html) setup.
- If your chosen authentication solution supports two-factor authentication, Operations for Applications requires two-factor authentication for login.
+ If your chosen authentication solution supports two-factor authentication, Tanzu Observability requires two-factor authentication for login.
* Multi-Tenant SSO
@@ -87,9 +87,9 @@ Operations for Applications supports three methods of authentication.
## Authorization
-Operations for Applications supports multi-level authorization:
+Tanzu Observability supports multi-level authorization:
* **Roles and permissions** determine which groups or users can manage which objects or perform certain tasks. For example, you could create a read-only role with no permissions and assign it to a Novice group, or create a Developers role, assign **Dashboards**, **Alerts**, **Proxy**, **Metrics**, and **Chart Embedding** permissions, and assign it to a developer group.
-* [**Access control**](access.html) applies to individual objects (dashboards or alerts). Privileged groups or users can revoke grant access to individual groups or users. Operations for Applications supports a [high security mode](access.html#change-the-access-control-security-organization-setting) where only the object creator and the [Super Admin](authorization-faq.html#who-is-the-super-admin-user) user can view and modify new dashboards.
+* [**Access control**](access.html) applies to individual objects (dashboards or alerts). Privileged groups or users can revoke grant access to individual groups or users. Tanzu Observability supports a [high security mode](access.html#change-the-access-control-security-organization-setting) where only the object creator and the [Super Admin](authorization-faq.html#who-is-the-super-admin-user) user can view and modify new dashboards.
* [**Metrics security policy rules**](metrics_security.html) allow fine-grained control over metrics visibility in dashboards, charts, alerts, etc.
@@ -106,7 +106,7 @@ You can view changes that were made to dashboards, alerts, etc., by using [versi
Our cloud integrations support monitoring data from different cloud providers. The process is like this:
1. You open the integration.
-2. You give Operations for Applications [global read-only access](integrations_aws_overview.html#give-read-only-access-to-your-amazon-account-and-get-the-role-arn) or [limited access](integrations_aws_overview.html#giving-limited-access).
+2. You give Tanzu Observability [global read-only access](integrations_aws_overview.html#give-read-only-access-to-your-amazon-account-and-get-the-role-arn) or [limited access](integrations_aws_overview.html#giving-limited-access).
For details, see the individual integration.
From fb199a44b3827ab81b02f009503cdce9318c5faf Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Fri, 12 Apr 2024 11:57:27 +0300
Subject: [PATCH 18/26] internal links and hidden pages
---
pages/doc/2023-52.x_release_notes.md | 2 +-
pages/doc/csp_area_differences.md | 8 +++---
pages/doc/csp_getting_started.md | 4 +--
pages/doc/csp_invite-AoA-users_tutorial.md | 4 +--
pages/doc/csp_migration.md | 30 +++++++++++-----------
pages/doc/csp_permissions_overview.md | 4 +--
pages/doc/csp_users_account_managing.md | 4 +--
pages/doc/csp_users_roles.md | 6 ++---
pages/doc/documentation_getting_started.md | 2 +-
pages/doc/logging_overview.md | 2 +-
pages/doc/purchase-additional-capacity.md | 2 +-
pages/doc/query_language_reference.md | 2 +-
pages/doc/start_trial.md | 2 +-
pages/doc/tracing_integrations.md | 30 +++++++++++-----------
pages/doc/upgrade-and-purchase.md | 2 +-
pages/doc/wavefront_data_format.md | 2 +-
pages/doc/wavefront_data_naming.md | 14 +++++-----
pages/doc/wavefront_obsolescence_policy.md | 2 +-
pages/doc/wavefront_release_notes.md | 2 +-
19 files changed, 62 insertions(+), 62 deletions(-)
diff --git a/pages/doc/2023-52.x_release_notes.md b/pages/doc/2023-52.x_release_notes.md
index f49eb707d..ed27730f4 100644
--- a/pages/doc/2023-52.x_release_notes.md
+++ b/pages/doc/2023-52.x_release_notes.md
@@ -40,7 +40,7 @@ Example: An annotated screenshot of the create traces security policy for origin
### Onboarded Subscriptions
-**New Admin Permission and Service Role**: With this release, we introduce the **Admin** [permission](csp_permissions_overview.html#operations-for-applications-permissions) and [service role](csp_users_roles.html#operations-for-applications-service-roles-built-in). **Admin** users can manage the Tanzu Observability organization settings.
+**New Admin Permission and Service Role**: With this release, we introduce the **Admin** [permission](csp_permissions_overview.html#tanzu-observability-permissions) and [service role](csp_users_roles.html#tanzu-observability-service-roles-built-in). **Admin** users can manage the Tanzu Observability organization settings.
### Original and Onboarded Subscriptions
diff --git a/pages/doc/csp_area_differences.md b/pages/doc/csp_area_differences.md
index 6b8ae6ccb..54ef04975 100644
--- a/pages/doc/csp_area_differences.md
+++ b/pages/doc/csp_area_differences.md
@@ -161,7 +161,7 @@ Last sentence: Тo temporarily enable service accounts for your service instance
For original subscriptions, using the Tanzu Observability REST API requires an API token associated with a user account or a service account. To generate API tokens for your user account you need the **API Tokens** permission. To generate API tokens for service accounts and to manage the API tokens in your Tanzu Observability organization, you need the **Accounts** permission.
-When your service is onboarded to VMware Cloud services and you want to access the Tanzu Observability REST API, you need a VMware Cloud services **access token**. In a few cases, when setting up a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens), authentication with a Tanzu Observability API token is also supported. However, using a VMware Cloud services **access token** is the recommended way as we will deprecate the service accounts in the future. To obtain an **access token**, you can:
+When your service is onboarded to VMware Cloud services and you want to access the Tanzu Observability REST API, you need a VMware Cloud services **access token**. In a few cases, when setting up a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens), authentication with a Tanzu Observability API token is also supported. However, using a VMware Cloud services **access token** is the recommended way as we will deprecate the service accounts in the future. To obtain an **access token**, you can:
* Generate a VMware Cloud services API token associated with your user account and exchange it for an access token.
@@ -366,7 +366,7 @@ For details, see Manage API Tokens.
All users can view and revoke their own VMware Cloud services API tokens. For details, see How do I manage my API tokens in the VMware Cloud services documentation.
Users with the VMware Cloud Organization Owner role can monitor the API tokens created in the organization and can set constraints for idle and maximum Time to live (TTL) for all newly created tokens. For details and instructions, see How do I manage API tokens in my Organization in the VMware Cloud services documentation.
How: As a user with the Proxies permission, you must configure the proxy to authenticate to Tanzu Observability with a Tanzu Observability API token that have the Proxies permission. For details, see Install a Proxy from the UI.
-
Note: The Wavefront proxy authenticates with a VMware Cloud services access token obtained from server to server OAuth app credentials or from a VMware Cloud services API token. Proxy authentication with a Tanzu Observability API token is still possible and supported only for a limited list of integrations.
+
Note: The Wavefront proxy authenticates with a VMware Cloud services access token obtained from server to server OAuth app credentials or from a VMware Cloud services API token. Proxy authentication with a Tanzu Observability API token is still possible and supported only for a limited list of integrations.
Who:
For proxy installation, users with the Proxies Tanzu Observability service role.
@@ -451,7 +451,7 @@ In both ways, the access token is directly issued to the proxy. For details, see
Where: In the Tanzu Observability user interface.
How: Follow the instructions on the Setup tab of the integration that you want to install.
-
Note: Most of the integrations that use a Wavefront proxy authenticate with a VMware Cloud services access token. A limited list of integrations still use proxy authentication with a Tanzu Observability API token.
+
Note: Most of the integrations that use a Wavefront proxy authenticate with a VMware Cloud services access token. A limited list of integrations still use proxy authentication with a Tanzu Observability API token.
Who: Users with the Proxies Tanzu Observability service role who must have one of the following:
A valid VMware Cloud services API token with the Proxies service role assigned.
diff --git a/pages/doc/csp_getting_started.md b/pages/doc/csp_getting_started.md
index fd146d3af..2369d9714 100644
--- a/pages/doc/csp_getting_started.md
+++ b/pages/doc/csp_getting_started.md
@@ -81,9 +81,9 @@ See [What organization roles are available in VMware Cloud Services](https://doc
## What Are Service Roles and Custom Roles?
-VMware Cloud services includes service-specific built-in roles, including [Tanzu Observability service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in). A service role is required to grant certain access to the corresponding service instance in the organization.
+VMware Cloud services includes service-specific built-in roles, including [Tanzu Observability service roles](csp_users_roles.html#tanzu-observability-service-roles-built-in). A service role is required to grant certain access to the corresponding service instance in the organization.
-While the service roles are built-in and not editable, as a VMware Cloud **Organization Administrator** or **Organization Owner**, you can create [custom roles](csp_users_roles.html#create-edit-or-delete-a-custom-role) with service permissions of your choice, including [Operations for Application permissions](csp_permissions_overview.html#operations-for-applications-permissions). Custom roles are optional and apply to all service instances for which the target user or server to server app has at least one service role.
+While the service roles are built-in and not editable, as a VMware Cloud **Organization Administrator** or **Organization Owner**, you can create [custom roles](csp_users_roles.html#create-edit-or-delete-a-custom-role) with service permissions of your choice, including [Operations for Application permissions](csp_permissions_overview.html#tanzu-observability-permissions). Custom roles are optional and apply to all service instances for which the target user or server to server app has at least one service role.
## What's a Server to Server App?
diff --git a/pages/doc/csp_invite-AoA-users_tutorial.md b/pages/doc/csp_invite-AoA-users_tutorial.md
index 24f03138f..712280771 100644
--- a/pages/doc/csp_invite-AoA-users_tutorial.md
+++ b/pages/doc/csp_invite-AoA-users_tutorial.md
@@ -58,10 +58,10 @@ If do not have the VMware Cloud **Organization Owner** or **Organization Adminis
We provide a number of built-in Tanzu Observability service roles.
-- A corresponding service role for each [permission](csp_permissions_overview.html#operations-for-applications-permissions).
+- A corresponding service role for each [permission](csp_permissions_overview.html#tanzu-observability-permissions).
- Two special service roles - one that grants full administrative access to the service, and another one that grants read-only access to the service.
-For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#operations-for-applications-service-roles-built-in).
+For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#otanzu-observability-service-roles-built-in).
### Step 1: Enter the New User Details
diff --git a/pages/doc/csp_migration.md b/pages/doc/csp_migration.md
index f373269d0..9c4da3aeb 100644
--- a/pages/doc/csp_migration.md
+++ b/pages/doc/csp_migration.md
@@ -66,7 +66,7 @@ During the process of onboarding your Tanzu Observability service to VMware Clou
* If a user is a **Super Admin** in Tanzu Observability, we assign that user with the **Super Admin** Tanzu Observability service role in VMware Cloud services.
-* If a user is assigned with individual permissions in Tanzu Observability, we assign that user with the corresponding [Tanzu Observability service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in) in VMware Cloud services. For example, if a user has the **Alerts** permission in Tanzu Observability, we assign that user with the **Alerts** Tanzu Observability service role in VMware Cloud services. There are the following exceptions:
+* If a user is assigned with individual permissions in Tanzu Observability, we assign that user with the corresponding [Tanzu Observability service roles](csp_users_roles.html#tanzu-observability-service-roles-built-in) in VMware Cloud services. For example, if a user has the **Alerts** permission in Tanzu Observability, we assign that user with the **Alerts** Tanzu Observability service role in VMware Cloud services. There are the following exceptions:
- The **Accounts** permission is replaced by the [VMware Cloud **Organization Administrator** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) plus the **Admin** Tanzu Observability service role.
- The **API Tokens** permission is not replaced by any role, because this privilege is not needed in VMware Cloud services. Each VMware Cloud services user can manage their own VMware Cloud services API tokens.
@@ -159,7 +159,7 @@ During the process of onboarding your Tanzu Observability service to VMware Clou
During the process of onboarding your Tanzu Observability service to VMware Cloud services, the service accounts **are not** migrated to VMware Cloud services, because VMware Cloud services supports [server to server OAuth apps](csp_server_to_server_apps.html), which are equivalent to the services accounts in Tanzu Observability.
-{% include warning.html content="The usage of service accounts in Tanzu Observability on VMware Cloud services is **restricted** to support only a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Tanzu Observability API tokens. We are in the process of updating all of our integrations to authenticate with VMware Cloud services access tokens. Service accounts and Tanzu Observability API tokens will be deprecated in the future."%}
+{% include warning.html content="The usage of service accounts in Tanzu Observability on VMware Cloud services is **restricted** to support only a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens) that still authenticate with Tanzu Observability API tokens. We are in the process of updating all of our integrations to authenticate with VMware Cloud services access tokens. Service accounts and Tanzu Observability API tokens will be deprecated in the future."%}
For backward compatibility, all of your service accounts are **preserved** in Tanzu Observability as follows:
@@ -176,7 +176,7 @@ You should incrementally [replace](#how-to-replace-a-service-account-with-a-serv
### How to Replace a Service Account with a Server to Server App?
-Service accounts authenticate with Tanzu Observability API tokens, while server to server OAuth apps authenticate with the more secure VMware Cloud services access tokens. Service accounts are supported for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) but will be deprecated in the future.
+Service accounts authenticate with Tanzu Observability API tokens, while server to server OAuth apps authenticate with the more secure VMware Cloud services access tokens. Service accounts are supported for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens) but will be deprecated in the future.
@@ -231,7 +231,7 @@ After onboarding to VMware Cloud services, you should incrementally replace your
Service Roles
-
Required for service access. Assign the Tanzu Observability service roles that correspond to the permissions of the service account that you want to replace.
+
Required for service access. Assign the Tanzu Observability service roles that correspond to the permissions of the service account that you want to replace.
If you already assigned a custom role, you must assign at least the Viewer Tanzu Observability service role.
@@ -264,15 +264,15 @@ You must exchange a VMware Cloud services API token or the credentials (ID and s
For backward compatibility, all of your API tokens are **preserved** in Tanzu Observability as follows:
* The Tanzu Observability API tokens associated with user accounts are **no longer** editable. The users can still use, view, and revoke their Tanzu Observability API tokens until they expire, but they **cannot** generate new ones.
-* The Tanzu Observability API tokens associated with service accounts are editable, because we still support them for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens).
+* The Tanzu Observability API tokens associated with service accounts are editable, because we still support them for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens).
-You should incrementally [replace](#how-to-replace-an-operations-for-applications-api-token-with-a-vmware-cloud-services-access-token) your Tanzu Observability API tokens with VMware Cloud services API tokens and server to server OAuth apps.
+You should incrementally [replace](#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token) your Tanzu Observability API tokens with VMware Cloud services API tokens and server to server OAuth apps.
{% include tip.html content="From now on, all users must generate VMware Cloud services API tokens for their accounts and exchange them for access tokens. Users with the VMware Cloud **Organization Owner**, **Organization Administrator**, or **Organization Member** with **Developer** roles can create server to server OAuth apps and exchange the app credentials for access tokens."%}
### How to View and Manage the Tanzu Observability API Tokens?
-Users with the **Admin** Tanzu Observability service role can [manage](csp_api_tokens.html#manage-the-operations-for-applications-api-tokens-in-your-service-instance) the Tanzu Observability API tokens in the service instance.
+Users with the **Admin** Tanzu Observability service role can [manage](csp_api_tokens.html#manage-the-tanzu-observability-api-tokens-in-your-service-instance) the Tanzu Observability API tokens in the service instance.
Each user can view and revoke their own Tanzu Observability API tokens:
@@ -285,7 +285,7 @@ Each user can view and revoke their own Tanzu Observability API tokens:
### How to Replace a Tanzu Observability API Token with a VMware Cloud Services Access Token?
-It's recommended to use Tanzu Observability API tokens only for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens). We will update these integrations to authenticate with VMware Cloud services access tokens in a future release.
+It's recommended to use Tanzu Observability API tokens only for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens). We will update these integrations to authenticate with VMware Cloud services access tokens in a future release.
@@ -354,7 +354,7 @@ To replace a Tanzu Observability API token associated with your user account:
1. Reconfigure your scripts, API calls, or proxies to exchange the newly generated VMware Cloud services API token for an access token, instead of using the Tanzu Observability API token.
{% include important.html content="The TTL of the access tokens associated with user accounts is 30 minutes. Make sure that your script renews the access token periodically before it expires. The Wavefront proxy does this automatically. "%}
-1. [Revoke](#how-to-view-and-manage-the-operations-for-applications-api-tokens) the Tanzu Observability API token that you replaced.
+1. [Revoke](#how-to-view-and-manage-the-tanzu-observability-api-tokens) the Tanzu Observability API token that you replaced.
@@ -366,11 +366,11 @@ To replace a Tanzu Observability API token associated with your user account:
During the process of onboarding your Tanzu Observability service to VMware Cloud services, all of the existing Wavefront proxies are **preserved** with their existing Tanzu Observability API tokens.
-You should incrementally [replace](#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy) the tokens of your proxies to authenticate with the more secure VMware Cloud services access tokens.
+You should incrementally [replace](#how-to-replace-the-tanzu-observability-api-token-of-a-wavefront-proxy) the tokens of your proxies to authenticate with the more secure VMware Cloud services access tokens.
-{% include tip.html content="From now on, the users with the **Proxies** service role can create and manage the proxies in your Tanzu Observability service. New proxies must authenticate with VMware Cloud services access tokens unless used for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Tanzu Observability API tokens."%}
+{% include tip.html content="From now on, the users with the **Proxies** service role can create and manage the proxies in your Tanzu Observability service. New proxies must authenticate with VMware Cloud services access tokens unless used for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens) that still authenticate with Tanzu Observability API tokens."%}
-### How to Replace the Operations for Application API Token of a Wavefront Proxy?
+### How to Replace the Tanzu Observability API Token of a Wavefront Proxy?
{% include important.html content="Make sure the version of your Wavefront proxy is 13.0 or later."%}
@@ -395,7 +395,7 @@ You should incrementally [replace](#how-to-replace-the-operations-for-applicatio
```
cspAPIToken=
```
-1. [Revoke](#how-to-view-and-manage-the-operations-for-applications-api-tokens) the Tanzu Observability API token that you replaced.
+1. [Revoke](#how-to-view-and-manage-the-tanzu-observability-api-tokens) the Tanzu Observability API token that you replaced.
@@ -407,9 +407,9 @@ You should incrementally [replace](#how-to-replace-the-operations-for-applicatio
During the process of onboarding your Tanzu Observability service to VMware Cloud services, all of the existing integrations are **preserved** and continue to operate using proxy authentication with Tanzu Observability API tokens.
-You should incrementally [replace](#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy) the proxy tokens of your [integrations](integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens) that are updated to use proxy authentication with the more secure VMware Cloud services access token.
+You should incrementally [replace](#how-to-replace-the-csp_migration.html-api-token-of-a-wavefront-proxy) the proxy tokens of your [integrations](integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens) that are updated to use proxy authentication with the more secure VMware Cloud services access token.
-{% include tip.html content="From now on, the users with the **Proxies** and **Integrations** service roles can set up integrations in your Tanzu Observability service. New integrations must use proxy authentication with VMware Cloud services access tokens except for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens) that still authenticate with Tanzu Observability API tokens."%}
+{% include tip.html content="From now on, the users with the **Proxies** and **Integrations** service roles can set up integrations in your Tanzu Observability service. New integrations must use proxy authentication with VMware Cloud services access tokens except for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-csp_migration.html-api-tokens) that still authenticate with Tanzu Observability API tokens."%}
diff --git a/pages/doc/csp_permissions_overview.md b/pages/doc/csp_permissions_overview.md
index 814f5ff07..94bd2f1e4 100644
--- a/pages/doc/csp_permissions_overview.md
+++ b/pages/doc/csp_permissions_overview.md
@@ -24,13 +24,13 @@ All users can:
* Share links to dashboards and charts with other users.
* Access the user profile from the gear icon on the toolbar.
-Users with the [**Super Admin** service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) have full administrative access to the service.
+Users with the [**Super Admin** service role](csp_users_roles.html#tanzu-observability-service-roles-built-in) have full administrative access to the service.
## Tanzu Observability Permissions
VMware Cloud services allows users with the VMware Cloud **Organization Owner** and **Organization Administrator** roles to perform access control for object management based on Tanzu Observability permissions.
- Permissions can be assigned to roles only, and roles can be assigned to users, user groups, and server to server apps.
-- For each permission, there is a corresponding built-in [Tanzu Observability service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) with only that permission assigned.
+- For each permission, there is a corresponding built-in [Tanzu Observability service role](csp_users_roles.html#tanzu-observability-service-roles-built-in) with only that permission assigned.
- Permissions can be assigned to [custom roles](csp_users_roles.html#create-edit-or-delete-a-custom-role).
diff --git a/pages/doc/csp_users_account_managing.md b/pages/doc/csp_users_account_managing.md
index 60cce83c6..284cd07b4 100644
--- a/pages/doc/csp_users_account_managing.md
+++ b/pages/doc/csp_users_account_managing.md
@@ -58,7 +58,7 @@ To view your roles, see what access you have to services, and request additional
## Enable or Disable Super Admin Mode
-If you hold the [**Super Admin** service role](csp_users_roles.html#operations-for-applications-service-roles-built-in), you can temporarily enable Super Admin mode and perform your Super Admin tasks.
+If you hold the [**Super Admin** service role](csp_users_roles.html#tanzu-observabilitys-service-roles-built-in), you can temporarily enable Super Admin mode and perform your Super Admin tasks.
{% include note.html content="To avoid making unintentional changes in the system, after performing your current Super Admin tasks, disable the Super Admin mode." %}
@@ -69,7 +69,7 @@ If you hold the [**Super Admin** service role](csp_users_roles.html#operations-f
As a result:
-
When the Super Admin mode is enabled, you have full administrative privileges for the Tanzu Observability service. See the Super Admin service role for details.
+
When the Super Admin mode is enabled, you have full administrative privileges for the Tanzu Observability service. See the Super Admin service role for details.
When the Super Admin mode is disabled, you have only the permissions from your other roles if any.
diff --git a/pages/doc/csp_users_roles.md b/pages/doc/csp_users_roles.md
index 5fba4575d..5478b18b3 100644
--- a/pages/doc/csp_users_roles.md
+++ b/pages/doc/csp_users_roles.md
@@ -41,7 +41,7 @@ The VMware Cloud Services Console **Roles** page lists all service roles and cus
### Tanzu Observability Service Roles (Built-in)
The VMware Cloud Services Console **Roles** page includes the following built-in Tanzu Observability service roles:
-- A corresponding Tanzu Observability service role for each [Tanzu Observability permission](csp_permissions_overview.html#operations-for-applications-permissions), that is, each of the following service roles has only one permission assigned:
+- A corresponding Tanzu Observability service role for each [Tanzu Observability permission](csp_permissions_overview.html#tanzu-observability-permissions), that is, each of the following service roles has only one permission assigned:
* **Admin**
* **Alerts**
@@ -87,7 +87,7 @@ The VMware Cloud Services Console **Roles** page includes the following built-in
### Create, Edit, or Delete a Custom Role
-Custom roles let you combine service permissions of your choice, for example, [Tanzu Observability permissions](csp_permissions_overview.html#operations-for-applications-permissions). A custom role can have permissions for one or multiple services in your organization. For example, you can have a custom role that grants administrative permissions for one service and read-only permissions for another service.
+Custom roles let you combine service permissions of your choice, for example, [Tanzu Observability permissions](csp_permissions_overview.html#tanzu-observability-permissions). A custom role can have permissions for one or multiple services in your organization. For example, you can have a custom role that grants administrative permissions for one service and read-only permissions for another service.
{% include important.html content="The Tanzu Observability permissions in a custom role apply to **all** Tanzu Observability service instances to which the target user account or server to server app has access. Therefore, to obtain the Tanzu Observability permissions from a custom role for a given Tanzu Observability service instance, the user account or server to server app assigned with that custom role must have at least one Operations to Applications service role for that service instance, for example, the **Viewer** service role."%}
@@ -115,7 +115,7 @@ For a [federated domain](csp_authentication.html#federated-domain-authentication
## Manage User Groups
-For efficient user management, you can create groups of users and assign roles to these groups. You can add new and existing users to a group. You can assign [service roles](#operations-for-applications-service-roles-built-in) and [custom roles](#create-edit-or-delete-a-custom-role) to a group.
+For efficient user management, you can create groups of users and assign roles to these groups. You can add new and existing users to a group. You can assign [service roles](#tanzu-observability-service-roles-built-in) and [custom roles](#create-edit-or-delete-a-custom-role) to a group.
See [How do I work with groups](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-0BD8A07B-C3C0-4220-8CD0-18FA070D3DAD.html) in the VMware Cloud services documentation.
diff --git a/pages/doc/documentation_getting_started.md b/pages/doc/documentation_getting_started.md
index 43962f0e2..c3ba2c7f0 100644
--- a/pages/doc/documentation_getting_started.md
+++ b/pages/doc/documentation_getting_started.md
@@ -81,7 +81,7 @@ Our documentation includes reference documentation for API, query language, and
{{site.data.alerts.end}}
diff --git a/pages/doc/purchase-additional-capacity.md b/pages/doc/purchase-additional-capacity.md
index 36c126af5..9c303167a 100644
--- a/pages/doc/purchase-additional-capacity.md
+++ b/pages/doc/purchase-additional-capacity.md
@@ -8,7 +8,7 @@ summary: Learn how to add capacity to your current Tanzu Observability (formerly
---
{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability is a service on the VMware Cloud services platform. For information about VMware Cloud services subscriptions and original subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html).
-- For VMware Cloud services subscriptions, to purchase additional capacity, you must hold the [**Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) in the VMware Cloud organization running the service as well as at least one [Tanzu Observability service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance. If your enterprise domain is federated, to access the organization billing account, you must have a VMware account linked to your corporate account.
+- For VMware Cloud services subscriptions, to purchase additional capacity, you must hold the [**Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) in the VMware Cloud organization running the service as well as at least one [Tanzu Observability service role](csp_users_roles.html#tanzu-observability-service-roles-built-in) for the service instance. If your enterprise domain is federated, to access the organization billing account, you must have a VMware account linked to your corporate account.
- For original Tanzu Observability subscriptions, to purchase additional capacity, you must be a **Super Admin** user."%}
## Supported Contracts
diff --git a/pages/doc/query_language_reference.md b/pages/doc/query_language_reference.md
index fde4506d4..ee5c0136e 100644
--- a/pages/doc/query_language_reference.md
+++ b/pages/doc/query_language_reference.md
@@ -191,7 +191,7 @@ lowpass(12ms, spans("beachshirts.styling.makeShirts"))
Query expressions use a number of common parameters to specify names and values that describe the data of interest. You can use [wildcards or partial regex](#partial-regex-wildcards-aliases-and-variables) to match multiple names or values.
-* Rules for valid names are here: [Data Format](wavefront_data_format.html#operations-for-applications-data-format-fields).
+* Rules for valid names are here: [Data Format](wavefront_data_format.html#tanzu-observability-data-format-fields).
* Enclose a metric, source, or tag name, or a tag value, in double quotes if it is also a reserved word in the product, such as a function name or keyword. For example, if you're using a point tag named `default`, use `"default"`.
diff --git a/pages/doc/start_trial.md b/pages/doc/start_trial.md
index ab2e179b3..a420b4ff4 100644
--- a/pages/doc/start_trial.md
+++ b/pages/doc/start_trial.md
@@ -55,7 +55,7 @@ VMware Cloud services provides provides single sign-on (SSO) and identity access
You are redirected to the Tanzu Observability GUI. You are logged with your VMware account.
- {% include note.html content="Initially, you have only the [**Viewer** Tanzu Observability service role](csp_users_roles.html#operations-for-applications-service-roles-built-in). As a VMware Cloud **Organization Owner**, you can [change your roles](csp_users_roles.html#manage-roles). It's recommended that when you start your free trial, you change your role to **Super Admin**. You can also add users to your service. See [Manage User Accounts](csp_user_management.html) for details." %}
+ {% include note.html content="Initially, you have only the [**Viewer** Tanzu Observability service role](csp_users_roles.html#tanzu-observability-service-roles-built-in). As a VMware Cloud **Organization Owner**, you can [change your roles](csp_users_roles.html#manage-roles). It's recommended that when you start your free trial, you change your role to **Super Admin**. You can also add users to your service. See [Manage User Accounts](csp_user_management.html) for details." %}
## Learn More!
* [Get Started with Tanzu Observability on VMware Cloud Services](csp_getting_started.html).
diff --git a/pages/doc/tracing_integrations.md b/pages/doc/tracing_integrations.md
index 0a7fa512d..2b45cfcac 100644
--- a/pages/doc/tracing_integrations.md
+++ b/pages/doc/tracing_integrations.md
@@ -4,22 +4,22 @@ keywords: data, distributed tracing, OpenTelemetry
tags: [tracing]
sidebar: doc_sidebar
permalink: tracing_integrations.html
-summary: Learn how to send trace data from Jaeger or Zipkin to VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront).
+summary: Learn how to send trace data from Jaeger or Zipkin to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
-{% include important.html content="OpenTracing is deprecated. ([OpenTracing](https://opentracing.io/) and [OpenCensus](https://opencensus.io/) have merged to form [OpenTelemetry](https://opentelemetry.io/).) To send trace data to Operations for Applications, use OpenTelemetry."%}
+{% include important.html content="OpenTracing is deprecated. ([OpenTracing](https://opentracing.io/) and [OpenCensus](https://opencensus.io/) have merged to form [OpenTelemetry](https://opentelemetry.io/).) To send trace data to Tanzu Observability, use OpenTelemetry."%}
-You can collect traces with Jaeger or Zipkin and send the trace data to Operations for Applications, which:
+You can collect traces with Jaeger or Zipkin and send the trace data to Tanzu Observability, which:
* Provides managed, highly scalable storage for your trace data.
* Allows you to examine and alert on RED metrics that are derived from the spans.
-Suppose you have already instrumented your application using Jaeger or Zipkin with OpenTracing or OpenTelemetry. You can continue using that system for application development, and then switch to using Operations for Applications by changing a few configuration settings.
+Suppose you have already instrumented your application using Jaeger or Zipkin with OpenTracing or OpenTelemetry. You can continue using that system for application development, and then switch to using Tanzu Observability by changing a few configuration settings.
{{site.data.alerts.note}}
-
You can use OpenTracing or OpenTelemetry to send traces to Operations for Applications using the Jaeger or Zipkin integration.
+
You can use OpenTracing or OpenTelemetry to send traces to Tanzu Observability using the Jaeger or Zipkin integration.
- The OpenTelemetry collector can identify data coming from applications instrumented with Jaeger or Zipkin and convert them to Open Telemetry format. Next, the Tanzu Observability (Wavefront) trace exporter converts the data to the Operations for Applications data format. See OpenTelemetry to configure your application.
+ The OpenTelemetry collector can identify data coming from applications instrumented with Jaeger or Zipkin and convert them to Open Telemetry format. Next, the Tanzu Observability (Wavefront) trace exporter converts the data to the Tanzu Observability data format. See OpenTelemetry to configure your application.
For OpenTracing, follow the steps given below.
@@ -39,11 +39,11 @@ To get data flowing:
Each integration
1. Configures your distributed tracing system to send trace data to a Wavefront proxy. During integration setup, follow the prompts to create a new integration or use an existing integration.
-2. The proxy processes the data and sends it to your Operations for Applications service.
+2. The proxy processes the data and sends it to your Tanzu Observabilityservice.
Part of setting up the integration is to configure the Wavefront proxy to listen for the trace data on an integration-specific port.
-Using an integration is the simplest way - [but not the only way](#alternatives-to-integrations) - to send trace data to Operations for Applications from a 3rd part tracing system.
+Using an integration is the simplest way - [but not the only way](#alternatives-to-integrations) - to send trace data to Tanzu Observabilityfrom a 3rd part tracing system.
## Trace Data from an Integration
@@ -55,7 +55,7 @@ The Wavefront proxy:
### Required Span Tags
-Operations for Applications requires certain [span tags](trace_data_details.html#span-tags) on well-formed spans. The following spans tags enable you to filter and visualize trace data from the different services in your instrumented application:
+Tanzu Observability requires certain [span tags](trace_data_details.html#span-tags) on well-formed spans. The following spans tags enable you to filter and visualize trace data from the different services in your instrumented application:
@@ -84,13 +84,13 @@ The proxy preserves any tags that you assigned through your distributed tracing
The mandatory span tags cannot have multiple values. Ensure that your application does not send spans with multiple application or service tags.
For example, a span with two span tags `service=notify` and `service=backend` is invalid.
-{% include note.html content="Operations for Applications ignores span tags with empty values." %}
+{% include note.html content="Tanzu Observability ignores span tags with empty values." %}
### Derived RED Metrics
-Operations for Applications automatically derives RED metrics from the spans that are sent from the instrumented application services. RED metrics are measures of the request Rate, Errors, and Duration that are obtained from the reported spans. These metrics are key indicators of the health of your services, and you can use them as context to help you discover problem traces.
+Tanzu Observability automatically derives RED metrics from the spans that are sent from the instrumented application services. RED metrics are measures of the request Rate, Errors, and Duration that are obtained from the reported spans. These metrics are key indicators of the health of your services, and you can use them as context to help you discover problem traces.
-Operations for Applications stores the RED metrics along with the spans they are based on. For more details, see [RED Metrics](trace_data_details.html#red-metrics).
+Tanzu Observability stores the RED metrics along with the spans they are based on. For more details, see [RED Metrics](trace_data_details.html#red-metrics).
{% include note.html content="The level of detail for the RED metrics is affected by any sampling that is done by your 3rd party distributed tracing system. See [Trace Sampling and RED Metrics from an Integration](#trace-sampling-and-red-metrics-from-an-integration), below." %}
@@ -250,11 +250,11 @@ Follow these steps:
## Alternatives to Integrations
-If using the Jaeger or Zipkin integration doesn't make sense in your environment, you can still use Operations for Applications with those systems.
+If using the Jaeger or Zipkin integration doesn't make sense in your environment, you can still use Tanzu Observability with those systems.
### Send Raw Trace Data
-We don't support an integration for your distributed tracing system, or if you are using your own proprietary tracing system, you can use a sender SDK to send raw trace data to Operations for Applications. With a sender SDK, you can write code that obtains the component values from your spans, and assembles those values into the [Operations for Applications span format](trace_data_details.html#operations-for-applications-span-format). The sender SDK also lets you configure your application to send the trace data to a Wavefront proxy or directly to Operations for Applications.
+We don't support an integration for your distributed tracing system, or if you are using your own proprietary tracing system, you can use a sender SDK to send raw trace data to Tanzu Observability. With a sender SDK, you can write code that obtains the component values from your spans, and assembles those values into the [Tanzu Observability span format](trace_data_details.html#tanzu-observability-span-format). The sender SDK also lets you configure your application to send the trace data to a Wavefront proxy or directly to Tanzu Observability.
For SDK setup details, see the [Sender SDK](wavefront_sdks.html#sdks-for-sending-raw-data) for your programming language.
@@ -262,7 +262,7 @@ For SDK setup details, see the [Sender SDK](wavefront_sdks.html#sdks-for-sending
### Use the Wavefront OpenCensus Go Exporter
-If you have instrumented your Go application with OpenCensus, you can use the [Wavefront OpenCensus Go Exporter](https://opencensus.io/exporters/supported-exporters/go/wavefront/) to push metrics, histograms, and traces into Operations for Applications. This exporter is built on the [Sender SDK](wavefront_sdks.html#sdks-for-sending-raw-data) for Go.
+If you have instrumented your Go application with OpenCensus, you can use the [Wavefront OpenCensus Go Exporter](https://opencensus.io/exporters/supported-exporters/go/wavefront/) to push metrics, histograms, and traces into Tanzu Observability. This exporter is built on the [Sender SDK](wavefront_sdks.html#sdks-for-sending-raw-data) for Go.
diff --git a/pages/doc/upgrade-and-purchase.md b/pages/doc/upgrade-and-purchase.md
index bd82cb11b..9c33511f8 100644
--- a/pages/doc/upgrade-and-purchase.md
+++ b/pages/doc/upgrade-and-purchase.md
@@ -28,7 +28,7 @@ Billing depends on the amount of data, measured in points per second (PPS), that
## Upgrade a Trial Service Instance on VMware Cloud Services
-{% include note.html content="To upgrade from a trial version, you must hold the [**Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) in the VMware Cloud organization running the service as well as at least one [Tanzu Observability service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance. If your enterprise domain is federated, to access the organization billing account, you must have a VMware account linked to your corporate account." %}
+{% include note.html content="To upgrade from a trial version, you must hold the [**Organization Owner** role](csp_getting_started.html#whats-a-vmware-cloud-organization-role) in the VMware Cloud organization running the service as well as at least one [Tanzu Observability service role](csp_users_roles.html#tanzu-observabilitys-service-roles-built-in) for the service instance. If your enterprise domain is federated, to access the organization billing account, you must have a VMware account linked to your corporate account." %}
1. Log in to your service instance.
1. On the banner showing you how many days have left from your trial period, click **Upgrade**.
diff --git a/pages/doc/wavefront_data_format.md b/pages/doc/wavefront_data_format.md
index c150315d5..7fd69bce3 100644
--- a/pages/doc/wavefront_data_format.md
+++ b/pages/doc/wavefront_data_format.md
@@ -149,7 +149,7 @@ Most of our discussion of the histogram and span data formats is on the pages li
### Span Data Format Syntax
-[The span format](trace_data_details.html#operations-for-applications-span-format) supports several predefined span tags.
+[The span format](trace_data_details.html#tanzu-observability-span-format) supports several predefined span tags.
```
source=
diff --git a/pages/doc/wavefront_data_naming.md b/pages/doc/wavefront_data_naming.md
index 4244a493c..f194283f3 100644
--- a/pages/doc/wavefront_data_naming.md
+++ b/pages/doc/wavefront_data_naming.md
@@ -1,14 +1,14 @@
---
-title: Wavefront Data Best Practices
+title: Tanzu Observability Data Best Practices
keywords: data
tags: [data, best practice]
sidebar: doc_sidebar
permalink: wavefront_data_naming.html
-summary: Best practices for naming data sent to Wavefront.
+summary: Best practices for naming data sent to VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications).
---
You can organize your data schema into metric names, source names, and point, alert, event, and source tags.
-Wavefront doesn't place any restrictions on naming. However, you benefit from following best practices when you name Wavefront objects. See [Wavefront Data Format](wavefront_data_format.html#operations-for-applications-data-format-fields) for details on valid characters for metric names and other names.
+Tanzu Observability doesn't place any restrictions on naming. However, you benefit from following best practices when you name Tanzu Observability objects. See [Tanzu Observability Data Format](wavefront_data_format.html) for details on valid characters for metric names and other names.
## Metric Names Best Practices
@@ -21,9 +21,9 @@ Don't include a timestamp in the metric name.
## Source Names Best Practices
-Source names should reflect a unique source that is emitting metrics. Wavefront assumes that source names are unique.
+Source names should reflect a unique source that is emitting metrics. Tanzu Observability assumes that source names are unique.
-For example, if you have the same machine name in different data centers, and don't separate the two machines when sending data to Wavefront (for example, by prefixing the source names with the datacenter), you can get confusing query results. Time series might oscillate between different values seemingly randomly, or you might see unexpected averaging of points between multiple sources.
+For example, if you have the same machine name in different data centers, and don't separate the two machines when sending data to Tanzu Observability (for example, by prefixing the source names with the datacenter), you can get confusing query results. Time series might oscillate between different values seemingly randomly, or you might see unexpected averaging of points between multiple sources.
When it's not clear which name to use as the source name, use the most unique value for a source name. For higher-level pre-aggregated data, for example, a datacenter-wide metric like power usage, use the name of the datacenter as the name of the source.
@@ -45,13 +45,13 @@ Tag names can contain alphanumeric (a-z, A-Z, 0-9), dash (-), underscore (_), an
### History
-Wavefront does not retain the history of alert, event, and source tags. For example, the machine `web004.pax.wavefront.com` might have the source tags `java-17`, `build-24`, and `dc-pax`. If you remove the `build-24` tag from `web004.pax.wavefront.com` and replace it with `build-25`, queries filtered by `build-24` no longer match `web004.pax.wavefront.com.` In other words, only current alert, event, and source tags affect queries because these tags are tied only to those objects, not to data.
+Tanzu Observability does not retain the history of alert, event, and source tags. For example, the machine `web004.pax.wavefront.com` might have the source tags `java-17`, `build-24`, and `dc-pax`. If you remove the `build-24` tag from `web004.pax.wavefront.com` and replace it with `build-25`, queries filtered by `build-24` no longer match `web004.pax.wavefront.com.` In other words, only current alert, event, and source tags affect queries because these tags are tied only to those objects, not to data.
For more information on tags, see [Organizing with Tags](tags_overview.html).
## Other Data Best Practices
-* [Wavefront and Cardinality](cardinality.html) has an introduction with a video.
+* [Tanzu Observability and Cardinality](cardinality.html) has an introduction with a video.
* [Optimizing the Data Shape to Improve Performance](optimize_data_shape.html) is an in-depth discussion with examples.
* [Common Time Limits and Best Practices](wavefront_limits.html) shows limits, for example, when a query times out.
* [Troubleshooting Missing Data](missing_data_troubleshooting.html) explains, for example, how you can toggle the Obsolete Metrics flag to see old data.
diff --git a/pages/doc/wavefront_obsolescence_policy.md b/pages/doc/wavefront_obsolescence_policy.md
index 8215604c6..5ecf8e772 100644
--- a/pages/doc/wavefront_obsolescence_policy.md
+++ b/pages/doc/wavefront_obsolescence_policy.md
@@ -189,5 +189,5 @@ Starting September 20, 2023, all **new trial** instances of Tanzu Observability
In October, 2023, we start to incrementally [onboard](csp_migration.html) all **original** subscriptions, which use Tanzu Observability authentication and authorization, to VMware Cloud services.
-{% include warning.html content="The Tanzu Observability 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 Tanzu Observability API tokens with VMware Cloud Services access tokens](csp_migration.html#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token), including [the Tanzu Observability API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy)." %}
+{% include warning.html content="The Tanzu Observability 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 Tanzu Observability API tokens with VMware Cloud Services access tokens](csp_migration.html#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token), including [the Tanzu Observability API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-tanzu-observability-api-token-of-a-wavefront-proxy)." %}
diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md
index d8841a7b2..8c9a0ddf0 100644
--- a/pages/doc/wavefront_release_notes.md
+++ b/pages/doc/wavefront_release_notes.md
@@ -34,7 +34,7 @@ Starting September 20, 2023, all **new trial** instances of Tanzu Observability
In October, 2023, we start to incrementally [**onboard**](csp_migration.html) all original subscriptions to VMware Cloud services. You will receive a notification in your Tanzu Observability UI with the date scheduled for your service onboarding to VMware Cloud services. Make sure that you get familiar with the VMware Cloud services platform and prepare for the onboarding. See [What Should I Do Before the Onboarding?](csp_migration.html#what-should-i-do-before-the-onboarding).
-{% include warning.html content="The Tanzu Observability 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 Tanzu Observability 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)." %}
+{% include warning.html content="The Tanzu Observability 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 Tanzu Observability API tokens with VMware Cloud Services access tokens](csp_migration.html#how-to-replace-a-tanzu-observability-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-tanzu-observability-api-token-of-a-wavefront-proxy)." %}
## 2024-07.x Release Notes
From c02ffec8c606655af54f6eb7f3fb309d3e66c8a3 Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Fri, 12 Apr 2024 12:06:55 +0300
Subject: [PATCH 19/26] fixes
---
pages/doc/csp_api_tokens.md | 2 +-
pages/doc/csp_invite-AoA-users_tutorial.md | 2 +-
pages/doc/csp_migration.md | 6 +++---
pages/doc/csp_users_account_managing.md | 2 +-
pages/doc/tracing_integrations.md | 2 +-
pages/doc/wavefront_obsolescence_policy.md | 2 +-
6 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/pages/doc/csp_api_tokens.md b/pages/doc/csp_api_tokens.md
index d5d181f41..bb55112c4 100644
--- a/pages/doc/csp_api_tokens.md
+++ b/pages/doc/csp_api_tokens.md
@@ -92,7 +92,7 @@ To generate and manage the API tokens for an existing **service account**:
As a user with the **Admin** service role, you can view and revoke the API tokens of any service account in your service instance.
-{% include warning.html content="If your original Tanzu Observability subscription was onboarded to VMware Cloud services, for backward compatibility, you might have some legacy Tanzu Observability API tokens that are associated with user accounts. It’s recommended that you incrementally [replace them with VMware Cloud services API tokens](csp_migration.html#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token)."%}
+{% include warning.html content="If your original Tanzu Observability subscription was onboarded to VMware Cloud services, for backward compatibility, you might have some legacy Tanzu Observability API tokens that are associated with user accounts. It’s recommended that you incrementally [replace them with VMware Cloud services API tokens](csp_migration.html#how-to-replace-a-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token)."%}
1. Log in to your service instance as an **Admin** user.
2. Click the gear icon on the toolbar and select **Accounts**.
diff --git a/pages/doc/csp_invite-AoA-users_tutorial.md b/pages/doc/csp_invite-AoA-users_tutorial.md
index 712280771..c1b37531c 100644
--- a/pages/doc/csp_invite-AoA-users_tutorial.md
+++ b/pages/doc/csp_invite-AoA-users_tutorial.md
@@ -61,7 +61,7 @@ We provide a number of built-in Tanzu Observability service roles.
- A corresponding service role for each [permission](csp_permissions_overview.html#tanzu-observability-permissions).
- Two special service roles - one that grants full administrative access to the service, and another one that grants read-only access to the service.
-For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#otanzu-observability-service-roles-built-in).
+For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#tanzu-observability-service-roles-built-in).
### Step 1: Enter the New User Details
diff --git a/pages/doc/csp_migration.md b/pages/doc/csp_migration.md
index 9c4da3aeb..21eef8c8a 100644
--- a/pages/doc/csp_migration.md
+++ b/pages/doc/csp_migration.md
@@ -266,7 +266,7 @@ For backward compatibility, all of your API tokens are **preserved** in Tanzu Ob
* The Tanzu Observability API tokens associated with user accounts are **no longer** editable. The users can still use, view, and revoke their Tanzu Observability API tokens until they expire, but they **cannot** generate new ones.
* The Tanzu Observability API tokens associated with service accounts are editable, because we still support them for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens).
-You should incrementally [replace](#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token) your Tanzu Observability API tokens with VMware Cloud services API tokens and server to server OAuth apps.
+You should incrementally [replace](#how-to-replace-a-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token) your Tanzu Observability API tokens with VMware Cloud services API tokens and server to server OAuth apps.
{% include tip.html content="From now on, all users must generate VMware Cloud services API tokens for their accounts and exchange them for access tokens. Users with the VMware Cloud **Organization Owner**, **Organization Administrator**, or **Organization Member** with **Developer** roles can create server to server OAuth apps and exchange the app credentials for access tokens."%}
@@ -407,9 +407,9 @@ You should incrementally [replace](#how-to-replace-the-tanzu-observability-api-t
During the process of onboarding your Tanzu Observability service to VMware Cloud services, all of the existing integrations are **preserved** and continue to operate using proxy authentication with Tanzu Observability API tokens.
-You should incrementally [replace](#how-to-replace-the-csp_migration.html-api-token-of-a-wavefront-proxy) the proxy tokens of your [integrations](integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens) that are updated to use proxy authentication with the more secure VMware Cloud services access token.
+You should incrementally [replace](#how-to-replace-the-tanzu-observability-api-token-of-a-wavefront-proxy) the proxy tokens of your [integrations](integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens) that are updated to use proxy authentication with the more secure VMware Cloud services access token.
-{% include tip.html content="From now on, the users with the **Proxies** and **Integrations** service roles can set up integrations in your Tanzu Observability service. New integrations must use proxy authentication with VMware Cloud services access tokens except for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-csp_migration.html-api-tokens) that still authenticate with Tanzu Observability API tokens."%}
+{% include tip.html content="From now on, the users with the **Proxies** and **Integrations** service roles can set up integrations in your Tanzu Observability service. New integrations must use proxy authentication with VMware Cloud services access tokens except for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens) that still authenticate with Tanzu Observability API tokens."%}
diff --git a/pages/doc/csp_users_account_managing.md b/pages/doc/csp_users_account_managing.md
index 284cd07b4..91a480ac2 100644
--- a/pages/doc/csp_users_account_managing.md
+++ b/pages/doc/csp_users_account_managing.md
@@ -58,7 +58,7 @@ To view your roles, see what access you have to services, and request additional
## Enable or Disable Super Admin Mode
-If you hold the [**Super Admin** service role](csp_users_roles.html#tanzu-observabilitys-service-roles-built-in), you can temporarily enable Super Admin mode and perform your Super Admin tasks.
+If you hold the [**Super Admin** service role](csp_users_roles.html#tanzu-observability-service-roles-built-in), you can temporarily enable Super Admin mode and perform your Super Admin tasks.
{% include note.html content="To avoid making unintentional changes in the system, after performing your current Super Admin tasks, disable the Super Admin mode." %}
diff --git a/pages/doc/tracing_integrations.md b/pages/doc/tracing_integrations.md
index 2b45cfcac..57f9d42a6 100644
--- a/pages/doc/tracing_integrations.md
+++ b/pages/doc/tracing_integrations.md
@@ -43,7 +43,7 @@ Each integration
Part of setting up the integration is to configure the Wavefront proxy to listen for the trace data on an integration-specific port.
-Using an integration is the simplest way - [but not the only way](#alternatives-to-integrations) - to send trace data to Tanzu Observabilityfrom a 3rd part tracing system.
+Using an integration is the simplest way - [but not the only way](#alternatives-to-integrations) - to send trace data to Tanzu Observability from a 3rd part tracing system.
## Trace Data from an Integration
diff --git a/pages/doc/wavefront_obsolescence_policy.md b/pages/doc/wavefront_obsolescence_policy.md
index 5ecf8e772..03be53819 100644
--- a/pages/doc/wavefront_obsolescence_policy.md
+++ b/pages/doc/wavefront_obsolescence_policy.md
@@ -189,5 +189,5 @@ Starting September 20, 2023, all **new trial** instances of Tanzu Observability
In October, 2023, we start to incrementally [onboard](csp_migration.html) all **original** subscriptions, which use Tanzu Observability authentication and authorization, to VMware Cloud services.
-{% include warning.html content="The Tanzu Observability 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 Tanzu Observability API tokens with VMware Cloud Services access tokens](csp_migration.html#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token), including [the Tanzu Observability API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-tanzu-observability-api-token-of-a-wavefront-proxy)." %}
+{% include warning.html content="The Tanzu Observability 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 Tanzu Observability API tokens with VMware Cloud Services access tokens](csp_migration.html#how-to-replace-a-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token), including [the Tanzu Observability API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-tanzu-observability-api-token-of-a-wavefront-proxy)." %}
From ec15e6a5b366be584cd3a2f76ca010251c6ff71e Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Mon, 15 Apr 2024 12:03:33 +0300
Subject: [PATCH 20/26] rebranding the Home doc page
---
_config.yml | 8 ++++----
_data/labels.yml | 4 ++--
_includes/topnav.html | 2 +-
index_choose_path.md | 2 +-
index_header.md | 4 ++--
5 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/_config.yml b/_config.yml
index 422ad50e5..3379b3fd1 100755
--- a/_config.yml
+++ b/_config.yml
@@ -3,10 +3,10 @@ repository: WavefrontHQ/docs
output: web
# this property is useful for conditional filtering of content that is separate from the PDF.
-topnav_title: VMware Aria Operations for Applications
+topnav_title: VMware Tanzu Observability
# this appears on the top navigation bar next to the home button
-site_title: VMware Aria Operations for Applications Documentation
+site_title: VMware Tanzu Observability Documentation
# this appears in the html browser tab for the site title (seen mostly by search engines, not users)
github_editme_path:
@@ -29,7 +29,7 @@ exclude:
- .gitignore
# these are the files and directories that jekyll will exclude from the build
-feedback_subject_line: VMware Aria Operations for Applications Documentation
+feedback_subject_line: VMware Tanzu Observability Documentation
plugins_dir:
- jekyll-sitemap
@@ -110,7 +110,7 @@ defaults:
sidebars:
- doc_sidebar
-description: "VMware Aria Operations for Applications documentation."
+description: "VMware Tanzu Observability documentation."
# the description is used in the feed.xml file
# needed for sitemap.xml file only
diff --git a/_data/labels.yml b/_data/labels.yml
index 30c321f16..08fe18bfe 100644
--- a/_data/labels.yml
+++ b/_data/labels.yml
@@ -13,6 +13,6 @@ release_notes: "Learn about the features added and updated in each release."
tutorials: "Quickly learn the basics of getting, displaying, and working with data."
videos: "View demonstrations of various features and use cases."
reference_page: "List of all query language functions (and some links to get you started)."
-integrations_list: "A script creates the doc page for each integration from the Operations for Applications UI."
-kubernetes: "Operations for Applications and Kubernetes info & videos."
+integrations_list: "A script creates the doc page for each integration from the Tanzu Observability UI."
+kubernetes: "Tanzu Observability and Kubernetes info & videos."
tracing: "Learn how to instrument applications for tracing and visualize the data."
diff --git a/_includes/topnav.html b/_includes/topnav.html
index 1c35b0c3c..1c52dcd38 100755
--- a/_includes/topnav.html
+++ b/_includes/topnav.html
@@ -10,7 +10,7 @@
--->
Note: The documentation on this site is about Operations for Applications, formerly known as Tanzu Observability by Wavefront. We're in the process of updating the product name, but in many places we still refer to it as Tanzu Observability or Wavefront.
+
Note: The documentation on this site is about Tanzu Observability, formerly known as Operations for Applications. We're in the process of updating the product name, but in many places we still refer to it as Operations for Applications or Wavefront.
(Formerly known as Tanzu Observability by Wavefront)
+
VMware Tanzu Observability
+
(Formerly known as VMware Aria Operations for Applications)
Welcome to our Documentation!
Explore using the hierarchy on the left.
From 32d44948ac52e6e8e315e5be031320074b1d5a9a Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Tue, 16 Apr 2024 17:47:29 +0300
Subject: [PATCH 21/26] Rebranding the Usage integration and dashboards
---
pages/doc/csp_supported_integrations.md | 2 +-
pages/doc/direct_ingestion.md | 2 +-
pages/doc/integrations_new_changed_2020.md | 8 ++++----
pages/doc/integrations_new_changed_2021.md | 12 +++++------
pages/doc/integrations_new_changed_2022.md | 16 +++++++--------
pages/doc/integrations_new_changed_2023.md | 8 ++++----
pages/doc/logging_faq.md | 6 +++---
pages/doc/missing_data_troubleshooting.md | 24 +++++++++++-----------
pages/doc/monitoring_overview.md | 2 +-
pages/doc/proxies_histograms.md | 2 +-
pages/doc/proxies_installing.md | 2 +-
pages/doc/proxies_preprocessor_rules.md | 4 ++--
pages/doc/proxies_troubleshooting.md | 4 ++--
13 files changed, 46 insertions(+), 46 deletions(-)
diff --git a/pages/doc/csp_supported_integrations.md b/pages/doc/csp_supported_integrations.md
index 1e51b1f02..21e192d48 100644
--- a/pages/doc/csp_supported_integrations.md
+++ b/pages/doc/csp_supported_integrations.md
@@ -487,5 +487,5 @@ The following integrations do not depend on the subscription type and work as ex
* [Webhooks](webhooks.html)
* [Graphite](graphite.html)
-* [Operations for Applications Usage Integration](wavefront_monitoring.html)
+* [Tanzu Observability Usage Integration](wavefront_monitoring.html)
diff --git a/pages/doc/direct_ingestion.md b/pages/doc/direct_ingestion.md
index f0b37ce72..4eb5ca69d 100644
--- a/pages/doc/direct_ingestion.md
+++ b/pages/doc/direct_ingestion.md
@@ -20,7 +20,7 @@ You can send data to VMware Tanzu Observability (formerly known as VMware Aria O
* **Prevent data loss, optimize network bandwidth** – The proxy buffers and manages data traffic. Even if there’s a connectivity problem, you don’t lose data points.
* **Simple firewall configuration** – The proxy receives metrics from many agents on different hosts and forwards those metrics to the Tanzu Observability service. You don’t need to open internet access for each of the agents.
* **Enrich or filter data** – You can set up the proxy preprocessor to filter data before it’s sent to the Tanzu Observability service.
- * **Examine bottlenecks** – Each proxy generates its own metrics. You can [learn about incoming and outgoing data](monitoring_proxies.html) in the individual proxy dashboards and the **Operations for Applications Service and Proxy Data** dashboard.
+ * **Examine bottlenecks** – Each proxy generates its own metrics. You can [learn about incoming and outgoing data](monitoring_proxies.html) in the individual proxy dashboards and the **Tanzu Observability Service and Proxy Data** dashboard.
diff --git a/pages/doc/integrations_new_changed_2020.md b/pages/doc/integrations_new_changed_2020.md
index 0c893a29a..6d0f232e5 100644
--- a/pages/doc/integrations_new_changed_2020.md
+++ b/pages/doc/integrations_new_changed_2020.md
@@ -26,10 +26,10 @@ Made improvements to the following integrations in October 2020 - December 2020:
* Spring Cloud Data Flow -- New preconfigured dashboard to monitor Native Kafka client
* Kubernetes -- New setup UI
* Slack -- URL unfurler
-* Operations for Applications Usage new dashboards:
- - **Operations for Applications Ingestion Policy Explorer** In environments where [ingestion policies](ingestion_policies.html) have been configured, shows usage for each user and ingestion policy.
+* Tanzu Observability Usage new dashboards:
+ - **Tanzu Observability Ingestion Policy Explorer** In environments where [ingestion policies](ingestion_policies.html) have been configured, shows usage for each user and ingestion policy.
- **Committed Rate and Monthly Usage (PPS P95)** dashboard shows Tanzu Observability monthly usage against committed rate.
- - **Operations for Applications Namespace Usage Explorer**: Tracks the number of metrics received for the first 3 levels of your metric namespace.
+ - **Tanzu Observability Namespace Usage Explorer**: Tracks the number of metrics received for the first 3 levels of your metric namespace.
* Google Cloud Platform (GCP) -- Fixed dashboard queries in Google Kubernetes Engine (GKE) dashboard
* Azure Storage -- Preconfigured dashboard now supports monitoring of the Classic storage type
@@ -69,7 +69,7 @@ Made improvements to the following integrations in October 2019 - October 2020:
Made significant improvements to the dashboards of the following integrations:
-* Operations for Applications Tutorial dashboards (upgrade for V2 UI)
+* Tanzu Observability Tutorial dashboards (upgrade for V2 UI)
* Pivotal Cloud Foundry dashboards
* Kubernetes dashboard
* vSphere dashboards
diff --git a/pages/doc/integrations_new_changed_2021.md b/pages/doc/integrations_new_changed_2021.md
index 5e0cd7c0c..ba8f6a6af 100644
--- a/pages/doc/integrations_new_changed_2021.md
+++ b/pages/doc/integrations_new_changed_2021.md
@@ -77,7 +77,7 @@ Made improvements to the following integrations and dashboards in September 2021
- Updated the query in the top 10 CPU charts of the **AWS: ECS (Fargate)** dashboard to show the correct values.
- Fixed bucket and region count mismatch issue in the **AWS: S3** dashboard.
-* Operations for Applications Tutorial -- Added the following list of new chart types and examples to the **Chart Types** dashboard:
+* Tanzu Observability Tutorial -- Added the following list of new chart types and examples to the **Chart Types** dashboard:
- Gauge
- Pie
- Node map
@@ -113,7 +113,7 @@ Made improvements to the following integrations and dashboards in July 2021:
* Project Pacific -- Renamed the integration from Project Pacific Integration to vSphere with Tanzu Integration.
* VMware Cloud PKS -- Removed the VMware Cloud PKS integration.
* OpenTelemetry -- Updated the steps for configuring the application to send trace data to Tanzu Observability using the trace exporter.
-* Operations for Applications Usage -- Added new charts to **Proxies Overview** section in the **Operations for Applications Service and Proxy Data** dashboard to show **Spans Sampled By Policies**.
+* Tanzu Observability Usage -- Added new charts to **Proxies Overview** section in the **Tanzu Observability Service and Proxy Data** dashboard to show **Spans Sampled By Policies**.
* Azure AD -- Added steps to configure Azure AD using Self-Service SAML.
* Data Platforms -- Added a new dashboard **Data Platform Blueprint2 - Kafka-Spark-Elasticsearch**.
* Kubernetes:
@@ -162,7 +162,7 @@ Made improvements to the following integrations and dashboards in June 2021:
Made improvements to the following integrations and dashboards in May 2021:
* AWS -- Updated the **AWS Summary** dashboard to use Delta Counters.
* Linux -- Updated the Linux integration to list all collected metrics.
-* Operations for Applications Usage:
+* Tanzu Observability Usage:
* The out of the box dashboards are updated to use new delta counters.
* The integration out of the box alerts are updated to use delta counters.
* Kubernetes:
@@ -210,7 +210,7 @@ Made improvements to the following integrations in March 2021:
* OneLogin -- Updates to the integration setup instructions
* vSphere -- Fixes to the out of the box dashboards
* RabbitMQ -- Fixes to the out of the box dashboards
-* Operations for Applications Usage -- Added new alerts to the integration
+* Tanzu Observability Usage -- Added new alerts to the integration
## December 2020 - February 2021
@@ -224,7 +224,7 @@ Made improvements to the following integrations and dashboards in December 2020
* Amazon Web Services Gateway -- New API gateway types
* Spring Cloud Data Flow -- Spring Cloud Data Flow and Spring Cloud Skipper version upgrade
* Microsoft Azure Storage -- New chart showing used capacity
-* Operations for Applications Usage:
+* Tanzu Observability Usage:
* Name changes to the dashboards
* Now includes an **Alerts** tab with predefined alerts
* Java
@@ -232,7 +232,7 @@ Made improvements to the following integrations and dashboards in December 2020
* AppDynamics -- Updates to the setup UI
* Kubernetes -- New out of the box dashboards
* OKTA -- Updates to the setup UI
-* Operations for Applications Tutorial
+* Tanzu Observability Tutorial
* Slack
* Amazon Web Services: Fargate dashboard
* Tanzu Kubernetes Grid Integrated Edition -- Updated to support Tanzu Kubernetes Grid Integrated Edition 1.10
diff --git a/pages/doc/integrations_new_changed_2022.md b/pages/doc/integrations_new_changed_2022.md
index 98f02d239..4cae622e3 100644
--- a/pages/doc/integrations_new_changed_2022.md
+++ b/pages/doc/integrations_new_changed_2022.md
@@ -97,13 +97,13 @@ Logs (Beta) Related Changes:
With the Initial Availability of our Logs (Beta) feature, we have made improvements to the following integrations:
* Linux Host -- Now contains Linux Logs Setup (Beta) instructions. If Logs (Beta) is enabled for you, you can set up your Linux integration to [send logs](logging_send_logs.html) to our service. For details on the Logs (Beta) feature, see [Get Started with Logs (Beta)](logging_overview.html). For detailed steps on setting up the Linux Host integration, see [Linux Logs Setup (Beta)](linux.html).
-* Operations for Applications Usage -- We added a Logs Stats section. It contains charts that track the amount of logs that are successfully delivered and successfully queried by our service. Also, the section shows charts that track the amount of logs that are received, queued, and blocked by the Wavefront proxy. [Read more](wavefront_monitoring.html#logs-stats).
+* Tanzu Observability Usage -- We added a Logs Stats section. It contains charts that track the amount of logs that are successfully delivered and successfully queried by our service. Also, the section shows charts that track the amount of logs that are received, queued, and blocked by the Wavefront proxy. [Read more](wavefront_monitoring.html#logs-stats).
We made improvements and bug fixes to the following integrations in October 2022:
-* Operations for Applications Usage:
+* Tanzu Observability Usage:
- Made significant improvements to the **Committed Rate vs Monthly Usage (PPS P95) for Billable** and **Usage (PPS) vs Remaining Balance (PPS P95) for Burndown** dashboards. You can use the data displayed on the dashboard that suits your commit contract. For example, if you have a billable commit contract, only the **Committed Rate vs Monthly Usage (PPS P95) for Billable** dashboard will contain charts populated with data. The **Usage (PPS) vs Remaining Balance (PPS P95) for Burndown** dashboard will be empty.
- - Made a minor fix to the **Operations for Applications Service and Proxy Data** dashboard.
+ - Made a minor fix to the **Tanzu Observability Service and Proxy Data** dashboard.
* Terraform Provider:
- We added data source support for alerts, dashboards, events, derived metrics, maintenance windows, and external links.
- Added support for checking frequency of Terraform Tanzu Observability Alert.
@@ -116,7 +116,7 @@ We made improvements and bug fixes to the following integrations in October 2022
* Java -- Fixed the links to the Jolokia 2 Agent documentation.
* Kubernetes -- Added a new system alert to the integration. You can now get notified when the Kubernetes observability status becomes unhealthy.
* Google Cloud Platform -- The **Google Dataproc** dashboard is now improved with information that you must create a derived metric if you see a delay in the loading of variables.
-* Operations for Applications Tutorial -- Made some minor fixes to the **Introduction** dashboard.
+* Tanzu Observability Tutorial -- Made some minor fixes to the **Introduction** dashboard.
## September 2022
@@ -125,7 +125,7 @@ We made improvements to the following integrations in September 2022:
* vSphere -- Made fixes to the **Cluster** dashboard. Updated the cluster variable to all charts in the **Virtual Machine Operations for a Data Center - 1 Hour** section.
* Elasticsearch -- Made a fix to the query of the chart that displays the number of nodes, and updated the descriptions of charts.
* Microsoft SQL Server -- Added proxy preprocessor rules in the Microsoft SQL Server setup instructions to avoid database read/write metrics getting dropped because of an extra quote (“) in a few point-tag keys.
-* Operations for Applications Usage -- Made minor updates to the Overview tab of the integration. The link to the service internal metrics is corrected.
+* Tanzu Observability Usage -- Made minor updates to the Overview tab of the integration. The link to the service internal metrics is corrected.
* Slack -- Updated the setup instructions and added information on how to troubleshoot the Slack URL Unfurler.
* Cassandra -- We updated the integration and now you can monitor Cassandra on Kubernetes.
* Tanzu Application Service -- We added three new dashboards for monitoring TAS services:
@@ -171,7 +171,7 @@ We made improvements to the following integrations in July 2022:
* Google Cloud Platform -- Added a **Google Cloud Bigtable** out-of-the-box dashboard which allows you to monitor the Google Cloud Bigtable service.
* Microsoft Azure -- Made fixes to the **Azure Cosmos DB** dashboard to avoid showing the NO DATA message on single-stat charts.
* Fluentd -- Improved the **Fluentd** dashboard and added two new sections to the dashboard: **Buffer** and **Fluentd Statistics**.
-* Operations for Applications Usage -- Made some fixes and standardized the **Operations for Applications Service and Proxy Data** dashboard.
+* Tanzu Observability Usage -- Made some fixes and standardized the **Tanzu Observability Service and Proxy Data** dashboard.
* Kubernetes -- Improved the Kubernetes Metrics Collector Troubleshooting dashboard to show correctly whether the desired number of Collector instances are ready.
## June 2022
@@ -209,7 +209,7 @@ We made improvements to the following integrations in June 2022:
* We improved the setup instructions with information on how to enable a Prometheus endpoint.
-* Operations for Applications Usage -- Updated the dashboard descriptions and made fixes to alerts.
+* Tanzu Observability Usage -- Updated the dashboard descriptions and made fixes to alerts.
## May 2022
@@ -270,7 +270,7 @@ We made improvements to the following integrations in March 2022:
* You can enable the control plane metrics with helm, or using manual configuration. To see a full list of supported control plane metrics, visit our [github repo](https://github.com/wavefrontHQ/observability-for-kubernetes/blob/main/docs/collector/metrics.md#control-plane-metrics).
-* Operations for Applications Usage
+* Tanzu Observability Usage
* Added two new system dashboards to the integration: **Committed rate vs Monthly Usage (PPS P95) Billable** and **Usage vs Remaining Balance (PPS P95) Burndown**.
* Added three new system alerts: **Percentage of Usage Scanned**, **Percentage of Usage Ingested**, and **Remaining Balance**.
diff --git a/pages/doc/integrations_new_changed_2023.md b/pages/doc/integrations_new_changed_2023.md
index 0923f8b69..e3b08ca34 100644
--- a/pages/doc/integrations_new_changed_2023.md
+++ b/pages/doc/integrations_new_changed_2023.md
@@ -60,7 +60,7 @@ Also, we made improvements to the following integrations in October 2023:
* 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.
+* Tanzu Observability Usage -- Enabled the **Include Obsolete Metrics** option for all charts in the **Tanzu Observability 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.
@@ -102,7 +102,7 @@ We made improvements to the following integrations in August 2023:
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.
+* Tanzu Observability 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.
@@ -126,7 +126,7 @@ We made improvements to the following integrations in July 2023:
* 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.
+* Tanzu Observability Usage -- Fixed issues in the predefined dashboards.
* Terraform Provider -- Fixed a discrepancy in the Terraform `resource_alert` provider resulting in erroneous Terraform change plan.
@@ -202,7 +202,7 @@ We made improvements to the following integrations in January 2023:
* 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 Observability 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
diff --git a/pages/doc/logging_faq.md b/pages/doc/logging_faq.md
index 65d09ca21..4b67f9385 100644
--- a/pages/doc/logging_faq.md
+++ b/pages/doc/logging_faq.md
@@ -80,9 +80,9 @@ Use the methods listed below to track the incoming log data and the number of lo
### See the Data on the Predefined Logs Stats Charts
1. Select **Dashboards** > **All Dashboards**.
-1. Search for **Operations for Applications Service and Proxy Data** in the search bar, and click the dashboard.
- 
-1. Examine the charts in the **Logs Stats** section of the [Operations for Applications Service and Proxy Data dashboard](wavefront_monitoring.html#operations-for-applications-service-and-proxy-data-dashboard) to get details about the logs you are sending.
+1. Search for **Tanzu Observability Service and Proxy Data** in the search bar, and click the dashboard.
+ 
+1. Examine the charts in the **Logs Stats** section of the [Tanzu Observability Service and Proxy Data dashboard](wavefront_monitoring.html#operations-for-applications-service-and-proxy-data-dashboard) to get details about the logs you are sending.
diff --git a/pages/doc/missing_data_troubleshooting.md b/pages/doc/missing_data_troubleshooting.md
index 78e5c3b54..aacaa6de6 100644
--- a/pages/doc/missing_data_troubleshooting.md
+++ b/pages/doc/missing_data_troubleshooting.md
@@ -204,7 +204,7 @@ Cloud integrations do not use a Wavefront proxy, but for many integrations, data
-There are several possible reasons for queues at the proxy. The [Monitoring Wavefront Proxies](monitoring_proxies.html) and the **Queuing Reasons** chart in the **Operations for Applications Service and Proxy Data** dashboard are especially helpful for identifying the cause for queuing, discussed next:
+There are several possible reasons for queues at the proxy. The [Monitoring Wavefront Proxies](monitoring_proxies.html) and the **Queuing Reasons** chart in the **Tanzu Observability Service and Proxy Data** dashboard are especially helpful for identifying the cause for queuing, discussed next:
* [Pushback from Backend](#proxy-queue-reasons-pushback-from-backend)
* [Proxy Rate Limit](#proxy-queue-reasons-proxy-rate-limit)
@@ -219,22 +219,22 @@ If the rate of data ingestion is higher than backend limit, the proxy queues dat
**Troubleshooting & Further Investigation**
-1. Look for pushback in the **Queuing Reasons** chart of the **Operations for Applications Service and Proxy Data** dashboard.
-2. Use the query in the **Data Ingestion Rate (Points)** chart of the **Operations for Applications Service and Proxy Data** dashboard to keep track of your ingestion rate. Ensure the ingestion rate is within contractual limits to avoid overages. While it's possible to ask Support to raise the backend limit such a change can result in overages.
+1. Look for pushback in the **Queuing Reasons** chart of the **Tanzu Observability Service and Proxy Data** dashboard.
+2. Use the query in the **Data Ingestion Rate (Points)** chart of the **Tanzu Observability Service and Proxy Data** dashboard to keep track of your ingestion rate. Ensure the ingestion rate is within contractual limits to avoid overages. While it's possible to ask Support to raise the backend limit such a change can result in overages.
#### Proxy Queue Reasons: Proxy Rate Limit
-If the proxy is configured with a rate limit, and the rate of data sent to the proxy is above the limit, the proxy starts queuing data. The **Proxy Rate Limiter Active** chart in the **Operations for Applications Service and Proxy Data** dashboard provides insight into whether data is coming in faster than the proxy rate limit supports.
+If the proxy is configured with a rate limit, and the rate of data sent to the proxy is above the limit, the proxy starts queuing data. The **Proxy Rate Limiter Active** chart in the **Tanzu Observability Service and Proxy Data** dashboard provides insight into whether data is coming in faster than the proxy rate limit supports.
**Troubleshooting & Further Investigation**
1. Confirm whether data is coming in faster than the proxy's rate limit configuration (`pushRateLimit`). If so, look into ways to reduce your data rate.
- 1. On the **Operations for Applications Service and Proxy Data dashboard** find the **Proxy Troubleshooting** section and examine the **Proxy Rate Limiter Active** chart to see whether the rate limiter is active on the different proxies in your environment.
+ 1. On the **Tanzu Observability Service and Proxy Data dashboard** find the **Proxy Troubleshooting** section and examine the **Proxy Rate Limiter Active** chart to see whether the rate limiter is active on the different proxies in your environment.
2. Confirm the `pushRateLimit` of each proxy by looking at the proxy configuration file or by querying `--proxyconfig.pushRateLimit`.
-2. Go to the **Received Points/Distributions/Spans Per Second** charts in the **Operations for Applications Service and Proxy Data** dashboard
+2. Go to the **Received Points/Distributions/Spans Per Second** charts in the **Tanzu Observability Service and Proxy Data** dashboard
1. Examine the ingest rate for the proxy that seems to have rate limit problems.
2. Use the Filter feature at the top of each dashboard or chart or specifying a specific source name in the underlying queries to filter for the proxy you are interested in.
@@ -249,7 +249,7 @@ Because rate limits are set assuming a steady rate, that burst of 60,000 PPS for
**Troubleshooting & Further Investigation**
-1. Explore the **Received Points/Distributions/Spans Max Burst Rate (top 20)** charts in the **Operations for Applications Service and Proxy Data** dashboard provides to understand the burstiness of your data rate. The queuing ability of the proxy normally helps smooth out the data rate through momentary queuing.
+1. Explore the **Received Points/Distributions/Spans Max Burst Rate (top 20)** charts in the **Tanzu Observability Service and Proxy Data** dashboard provides to understand the burstiness of your data rate. The queuing ability of the proxy normally helps smooth out the data rate through momentary queuing.
2. If you find that the proxy queues sustain and continue to grow, then the overall data ingest rate is too high.
3. Either reduce the ingest rate or request that the backend limit be raised (this could result in overages).
@@ -263,7 +263,7 @@ As the proxy processes data in the memory buffers, space is freed up for new inc
**Troubleshooting & Further Investigation**
-1. Find the **Queuing Reasons** chart in the **Operations for Applications Service and Proxy Data** dashboard and look for `bufferSize`.
+1. Find the **Queuing Reasons** chart in the **Tanzu Observability Service and Proxy Data** dashboard and look for `bufferSize`.
2. If you see problems, consider lowering the ingestion rate or distributing the load among several proxies.
3. In some situations, it might make sense to adjust the `pushMemoryBufferLimit` proxy property.
* Raising this value results in higher memory usage.
@@ -275,7 +275,7 @@ If network issues prevent or slow down requests from the proxy to the Tanzu Obse
**Troubleshooting & Further Investigation:**
-1. Go to the **Network Latency** chart in the **Proxy Troubleshooting** section of the **Operations for Applications Service and Proxy Data** dashboard. This chart tracks the amount of time from when the proxy sends out a data point to when it receives an acknowledgment from the backend.
+1. Go to the **Network Latency** chart in the **Proxy Troubleshooting** section of the **Tanzu Observability Service and Proxy Data** dashboard. This chart tracks the amount of time from when the proxy sends out a data point to when it receives an acknowledgment from the backend.
2. Ensure that this amount of time is in the range of hundreds of milliseconds. If the time reaches the range of seconds, check for network latency issues.
@@ -286,7 +286,7 @@ The proxy configuration property `memGuardFlushThreshold` is meant to protect ag
**Troubleshooting & Further Investigation:**
-1. Find the **Queueing Reasons** chart in the **Operations for Applications Service and Proxy Data** dashboard and examine the `memoryPressure` metric.
+1. Find the **Queueing Reasons** chart in the **Tanzu Observability Service and Proxy Data** dashboard and examine the `memoryPressure` metric.
2. If there's a problem, consider increasing memory limits for the host server.
@@ -297,7 +297,7 @@ If your data travels through a pipeline before reaching the Wavefront proxy or b
**Troubleshooting & Further Investigation**
-Examine the **Data Received Lag** charts in the **Proxy Troubleshooting** section of the **Operations for Applications Service and Proxy Data** dashboard.
+Examine the **Data Received Lag** charts in the **Proxy Troubleshooting** section of the **Tanzu Observability Service and Proxy Data** dashboard.
These charts can help if the data points are timestamped at or near the source of the data. The underlying metric used in these charts tracks the difference between the system time of the proxy host and the timestamp of data points. This difference can provide insight into how long it takes for a data point to traverse the data pipeline and reach the proxy.
@@ -314,7 +314,7 @@ Each time the service detects a new name, it generates a new ID. ID generation a
**Troubleshooting & Further Investigation**
-The **Operations for Applications Usage** integration includes several alerts that you can customize to be alerted when there is a high rate of new IDs.
+The **Tanzu Observability Usage** integration includes several alerts that you can customize to be alerted when there is a high rate of new IDs.
* A high rate of new IDs can happen when you start sending new data to Tanzu Observability.
* A high rate of new IDs could also indicate a **cardinality issue** with the data shape of the data you're sending to Tanzu Observability. For instance, if a timestamp was included as a point tag, a high number of unique point tags results. This can be a problem when you send the data to Tanzu Observability, but also causes problems later when you query the data. See [Data Naming Best Practices](wavefront_data_naming.html) for best practices.
diff --git a/pages/doc/monitoring_overview.md b/pages/doc/monitoring_overview.md
index ac22c1b71..bde18a842 100644
--- a/pages/doc/monitoring_overview.md
+++ b/pages/doc/monitoring_overview.md
@@ -51,7 +51,7 @@ Administrators (and often other team members) are interested in usage data at al
1. Users who install Wavefront proxies can examine the [proxy information](monitoring_proxies.html) on the out-of-the-box dashboards. Larger environments or production environments rely on a team of load-balanced proxies, as discussed by Clement Pang in [this video about proxies](https://vmwaretv.vmware.com/media/t/1_5wfjti3m).
Having usage data for the proxy helps administrators during installation and also helps with proxy sizing later.
-2. View the points flowing into the system from the [Overall Data Rate section](wavefront_monitoring.html#overall-data-rate) of the **Operations for Applications Service and Proxy Data** dashboard.
+2. View the points flowing into the system from the [Overall Data Rate section](wavefront_monitoring.html#overall-data-rate) of the **Tanzu Observability Service and Proxy Data** dashboard.
3. Create custom charts with internal metrics. Our system dashboard information is a great start, but you might benefit from other [internal metrics](wavefront-internal-metrics.html) and it's easy to create a dashboard with custom charts.
**Note**: We've include the internal metrics that are most useful in the documentation.
diff --git a/pages/doc/proxies_histograms.md b/pages/doc/proxies_histograms.md
index fae312707..de4c641df 100644
--- a/pages/doc/proxies_histograms.md
+++ b/pages/doc/proxies_histograms.md
@@ -265,4 +265,4 @@ The aggregation intervals do not overlap. If you are aggregating by the minute,
## Monitoring Histogram Points
-You can use `~histogram` metrics to monitor histogram ingestion. See the [Ingest Rate by Source](wavefront_monitoring.html#ingest-rate-by-source) section of the Operations for Applications Service and Proxy Data dashboard.
+You can use `~histogram` metrics to monitor histogram ingestion. See the [Ingest Rate by Source](wavefront_monitoring.html#ingest-rate-by-source) section of the Tanzu Observability Service and Proxy Data dashboard.
diff --git a/pages/doc/proxies_installing.md b/pages/doc/proxies_installing.md
index 6f6281304..75f5d46ad 100644
--- a/pages/doc/proxies_installing.md
+++ b/pages/doc/proxies_installing.md
@@ -29,7 +29,7 @@ In most cases, a Wavefront proxy must be running in your environment before metr
- Operating system and JRE - Wavefront proxy is a Java application and can run on operating systems supported by Java. Java 8, 9, 10 or 11 is required. See the requirements in the [Wavefront Proxy README file](https://github.com/wavefrontHQ/wavefront-proxy#requirements).
- Other - Maven
-{% include note.html content="The proxy uses disk space only for queue and buffering of metrics. The size of the buffer depends on the metrics size and the number of data points received and sent by the proxy. The individual proxy dashboards and the **Operations for Applications Service and Proxy Data** dashboard have several charts that allow you to examine proxy backlog size and related metrics. See [Monitoring Proxies](monitoring_proxies.html)." %}
+{% include note.html content="The proxy uses disk space only for queue and buffering of metrics. The size of the buffer depends on the metrics size and the number of data points received and sent by the proxy. The individual proxy dashboards and the **Tanzu Observability Service and Proxy Data** dashboard have several charts that allow you to examine proxy backlog size and related metrics. See [Monitoring Proxies](monitoring_proxies.html)." %}
diff --git a/pages/doc/proxies_preprocessor_rules.md b/pages/doc/proxies_preprocessor_rules.md
index a73d77f44..4eb157372 100644
--- a/pages/doc/proxies_preprocessor_rules.md
+++ b/pages/doc/proxies_preprocessor_rules.md
@@ -758,7 +758,7 @@ The following example illustrates using a `limitLength` for a point tag. The lim
```yaml
# Make sure that the limit that you are setting is not higher
- # than the default Operations for Applications limit.
+ # than the default Tanzu Observability limit.
################################################################
- rule : limit-point-tag-length
action : limitLength
@@ -1360,4 +1360,4 @@ To apply the Wavefront proxy preprocessor rules when certain conditions are met,
## Learn More!
-To monitor the time a proxy is spending with preprocessing rules, examine the [**Proxy Troubleshooting**](monitoring_proxies.html#proxy-troubleshooting) section on the **Operations for Applications Service and Proxy Data** dashboard.
+To monitor the time a proxy is spending with preprocessing rules, examine the [**Proxy Troubleshooting**](monitoring_proxies.html#proxy-troubleshooting) section on the **Tanzu Observability Service and Proxy Data** dashboard.
diff --git a/pages/doc/proxies_troubleshooting.md b/pages/doc/proxies_troubleshooting.md
index 2eeda6fa8..6a5697669 100644
--- a/pages/doc/proxies_troubleshooting.md
+++ b/pages/doc/proxies_troubleshooting.md
@@ -230,8 +230,8 @@ INFO [AbstractReportableEntityHandler:reject] [] blocked input: [WF-300 Ca
* Potential Resolution:
- 1. Log in to your service instance and navigate to the **Operations for Applications Usage** integration.
- 2. In the **Operations for Applications Service and Proxy Data** dashboard check if the proxy's queue and backlog are staying the same size or growing.
+ 1. Log in to your service instance and navigate to the **Tanzu Observability Usage** integration.
+ 2. In the **Tanzu Observability Service and Proxy Data** dashboard check if the proxy's queue and backlog are staying the same size or growing.
* If they're growing, then the attempted rate of ingest is higher than allowed by the backend limit. Either lower the rate of data that is at the proxies, or contact our Technical Support team to request a higher backend limit. If your overall rate of data ingestion is higher than your contract rate, you may incur overage charges.
* If the proxy's queue size is spiky (going up and coming down, close to 0), then the proxy is effectively smoothing out bursts in your rate of data ingestion. This is normal behavior and is not a cause for concern.
From de845567c1149434c9564e449a12f4ee96afe065 Mon Sep 17 00:00:00 2001
From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com>
Date: Mon, 22 Apr 2024 16:44:15 +0300
Subject: [PATCH 22/26] Migrated service status page
---
images/alias_name.png | Bin 17709 -> 13197 bytes
images/service_status.png | Bin 16339 -> 35458 bytes
images/status_subscribe.png | Bin 19759 -> 35042 bytes
pages/doc/service_status_page.md | 30 ++++++++++++++----------------
4 files changed, 14 insertions(+), 16 deletions(-)
diff --git a/images/alias_name.png b/images/alias_name.png
index 62a692fd7fc343691965f7897d6ced389d53e79d..933ce889cb5be610130f5ed58ddc886ce3bb0a44 100644
GIT binary patch
literal 13197
zcma)@1z1$!y0#aBG=kEN(uja`BPAd$NH<95&|QK80wU5OAq*kS&?Vj7Fay$!bPoK>
zbFOpF-uvHwtZQJnX61bGe$RWq4-slAa(LJj*Z=_FDagyb1>eU30EG$j0r*#PtZpgz
zhUF};>k0smI{*HlBs_ma34Vy-rl2f~v4uv0Ln3r_rFskibbx}4q^4K;KHSrQaB~&o
z&*lMl5E`a5TKf}qk5?t1uvru(*&Z2uDn2MHnJ#P9vg@hU+pR4@>Xnq#X+IhAt_oVFpxl?g|n%rG-ELtyT`eVTle{{_Os1^TAup}8C*s(*9IVHpFhge`HvNkrdyg_D(;#(V`r_jnwz+H`|Q|7
z&T6LQ+oV2gVSg|mJ#*`}dT~+BLthcL==C{P+UFnjfVOWDtGQ1cS-!`(R*HBZjDM;5
z&}UK?;|i&+LI;)wTPz1i*HS*DQt*hL`r>v_ImoF}NHFn0v$Q$xchf?fso#^~3Xe?t
zyfW2L+$}s&|D9yU+`RgeeQi$9oQ(fR^jw`!U+YX+)`T?>^t0*N`dqOl+rSHU6riBE
z&;e<3HlK&1St&HTp#BkHiNs~OIgFJ{qlIzkbJ>mUk@rgpXM|_7#H>osB;HlzPuQsH
zf5<7?hMG9Zr5M#W71fx&dK#+YJL739KRS39xEEQZmw@XqQhxYn+yA5L#d$vppmNUN
z-GSE&(I|af-rgDLH7%~l%z)u>){TQdBn
z(-YwWc}1|c?0K&+G7Oz4e;E@SEAEP;_?C8~$kw&IHuvpi-Yg1y_FhWW=#$Ex@%X}X
z{8pk13W^Rs3h@{#Rq@vZ7T~bc$rK9_6~}d^-sDv>)_%7TQjz;ssMT^Qjt8k|d2>@&
z|9Ri|*ndmmc%UhJdV=1@@o}$@uM;EG<3hf-eYo@h?78EXmJO|JrTof!#?VmqE{-n4
z-L1WA>y9_n4ljVV4;7;8&*JLLowf??6fTTZ6=hap92)OF=EyhJxtgim)kNC?fCQCz
zLWZ&5x!Gp}#LN`Dq{!jdtootPIC3yOMAr4e^*vEmd9~>6TLY`4{=0EbsjGEo6-fn2
zg?g#%UQP}S;M06p5uD&NoKlkEKy6AP=Z*Z2@sZX!3AeKj^M9H7|2=~Pf{#^?m=@ow
zW1as)VEB*Ss;mgTvQ6>GGW37l_2&VU2<_$RP|zLQO7txcYZ*XcQa;-p=LB4fQ2a4f
z%l|SRm>@yZlE^Q~cE)r&hJLv4?HlWlxRE=ZKZDxHuGf;%n?qzdm_VD!>Q39U)XHX6
z-ZVf}7mytJvxWgkev^$o`6!?FwsMyqGbg`j1IG90+G>2o`fp_GA8by6N{#AAoLlTE
zv9lN0KR!(?Dl63zfBow)1spA>^I0+yngZz8&`Wv`?68oX?pOCj1>E3R2sNVgvInE#
zqe_B@%d8LoGaSYSZeW>XG^-SFJ9BxA+M)V_4Hf7YEak446-b~-E|@I31tULx-UD%k
zv>>h$l-Q_u@S4&0pN$Q3w&0%P*ZDF>?9|*gkF`-QjYQ1PbKH}-BX?l=`Amcw6K!)<
zmc!VZ8XCUH7YeGXwPdCh$fyy`cczXiD)XV$uzNjd5%xU?jdA-)HxnnP04Mi~!DxuL
zViITW*!GhM1|E9zi(x}bet#1Si_=uf(2Fy2TmcgRr|%Nzy6+fOIg;e$42=Xm
zjj{q?$>`KoFa2SQ?;8&Li1BbZ^I-j?3_rs0%uQzt@
z`+vNxH^}s2G_`U5bf{UzDRG}uSP}QLKEGijKDIVLFW>RXxeDB2DB@8QB?AO~xV#*q
zwHGF(IoRHaBcQ!sb7ZhfJ6Nx>>lv0C8Ug^RY+7@S@a1}X
z=I7^Me+Y|@a;B2-KmHbu{(Qx3En!!CiCjYbbTbrg2=BndQyv<`KE~;tVtArpNIqPR?q!+?05o*aCUw
z?JXN7Tk-$}$f~N+V0fY%UHJeQwRZb%)1vP3l9coQb?!uNE(a=*o}NLmv!k!4*SpWp
z$KUU}zCq89R#Jk2e=Evt?YI(c#~dg$F*!>{Ni9v#IUiWE(BQu?y}#fHU3755}HxK5UZ~D)Q
z4LAgzi9YCYxep3LO3-3H!m7`J%t+8>-8*)=80hMQcg;i?dDnYmhdq1w^yPK!fQZL_
zQ$l*R2lBcDL%OP}vNy@?lZdUIZGh;dhNiuntLus9lAoQ42>~_j&D23z$4EG<1gaAz
zaZjl-%b>ifG0YN{*&-g2Gi=^dSKk;Pb(!GzFs7AKFuu>ijBG=^t7Clp>quEAmwn~J
z+UHZZN(~!Z`yUhAB=oN_(H;!MC8p}>VI65duo|hPvWdtkppUh(bj&X-v~e_j`Xqu2
zcU4G;cx{sq?WwKZ?!iIk8h?F$QR+`QMa8s^-vBT;I0UxxOI&mA6ofbe@9gYtp{BN~
z(}(p>EA7uJy}_vkx<00lWEJ*JttU6mz#{&H5Z^2E}v5@~r^41S|>odBNO
zm$^Q$c)dAn+>j8TD=z$5-BV$p3$5kBO^O?^Nf;tMyXE;@efgR
zR#uvvnz~toKmxYM_@`O>`rvRl9v&VO6O(y&bhGQt@Ff-pIF3b`X`)pyfNu$jG>^o-
zA-NQ_wP(g{Eu5Unl$bO$G|~iZ#-}=EE?8+G^-XmJf`SY`YHMqMR_|@n;-5OLIZJnB
zU7hg3s?nQt{r&w*v6B1@z-VS`IUSf0r==xOwzRcA>&!G?E0aI47BzGs5o?u7!dg
zXxU!fVX$9MpN3|_Y;0|g(!I#Hw-GHZU174%XMR2a=rCUqXi5_FcW?qg>({c<{BYA`
znP=+D*g#Ne%%k`|dt3WK`4O^1Zp7fC0b5*kO*J@kT6h9PfmbX9>B26@&F`LH9NeG)
zYH!~{b~+U*`ME>fVKDBL&%aE_T%-HUv%nce_i@ZhngC7mcXO0cSmZ@&et!NdI%`7g
zJ}8UERGTYuL!bor3c4HN2jM-0uNiH
zvROEvt12oJM#%U>u8`k|=*{UtZL2(l_;qLc+VZ20y`$+bvx@3!7!S`lF?QH5XH?*o
zzkhRKVPR+}YDf-dWKnVPbAh7LQb#+hw4}5PE_&DTwLUlDj9(_Ra|;`r8_jz!>k<;)
zy(4ZdDN)vatEtn*$2VqzmmZ9qvPA{RC@G`5RyH=|`oH!^VuOQ2%pa*eiw4uA5-}8O
zKH}hDj-e*SM*AQYmzkRQHC>5=ySBW%nu0ul|7T-yn&>S)a(nY&X;YDpk4HmWJ64eL
zZuru(cPxH@kAw5MoSNHRPMD|T()mS7VnzbY5>An=CMe)sBPBUID@x;C@;X|j4iYvr
zJvlikLtxP~aC!20bMOUw?+0>RS|jzpn*zZHHM%-y@k;2DThpqc!NF1^*q)-cr!1A7
zLml)IoDxFY95Jilsw}(%k@6EgYFcVb)z|r4QzPzr{H>rQT8(9#=0|r=SF4CC)0I&s
zy6o8bxd%9VTIFb~YwRK-=BZ+!Ni%Vy(#p}%VD}Lv-9mPhmiKg#67qqhY%~^+(Nct-
z6Lgg0+07_2e3g9~Maqd)A8*>vVoO`Uj
zm6q;U?uu%KH#gSgdwgB6xF_e~kdtLK7Fiq}ot)H^lauonErLR8-EV4mpel!Vwxnr8
z0Rqk&d-blFBFSG54>ryy(-2Fui<7*44#!r;evTIQw|m;U(G*>lOBn)o!;uMx4__n)
z{$9KS`<#-$WyFN*8w@7uv$pZO#b=*_B6?%<5LygvT#e!!c%#_!nX>T?i8swZJ%Z>=
z!?Lln>j<0~L!cmj3{<&LwYnY6bcc6e;gEu(2nFqNRF`fFJ~b6JZa6-)!F_b#Ddz~2
z)9a(xONG=O<=|18-;!v>{E}~1l5Q6}29faQF;EurZ!azUItl#e1o*#Y@c$`8{(Hcm
z{7w$;JwJY}9`RGeu0$Iwl9vhdeOz}cil3$eAloj5@2oknfbiL&}lXP7A
zuy$h|xItJ5zp6t8S!p)(#!$?#l7=EfWja1C)yPPXzt6u?iK%!+dkEjC
z&8!LlU{f$t=m<_KVH9xUwG*&g4*%>
zT=ZjO?ZKqh3>(gSZe3qr5shdYYkN&SgPbN7V-|vGtr>{2GI~j5labym+vxc8v-^r!
zc6WF8%FN2I-0OzP=owH|Luq)MvsZvh=5feP_cgj?RFG)@hk`JNg&JicoLD6`RKVKB
z2#LdwCJ6@6qT-^jj)=HZd4TScI6<8>mnQ%Htnh3~YKqukFMIEh6;}#uimyWbCD{7`
zD0jTVC0u0yu-xXlMc_%awk{$pMBy4O`)mxZuYe|b+PB{4d4P~_67Tn^ZV12T3N-~s
z%rWE`jM}!vb{w*I{TAHOpQGnxbJBlOfkUXNEH)S1iqrfy9r;?ZJIX7+R$gxDP>Q7W
z(Kxb1l57z7T5v-vhI!{H{qz1T{K##l2HG@1{ia0R^9XpAJ3-|YgUhsP>SK8w${QfN
z-aDpsLNYWnHl{wKRtu{wE-7hF`u5gHPkesb=OBd69nT$Ti?5j2u-1>J2{YS5HeS%=
zTlN1KFBH$*pdWmU_H?(fteAec0#@tlo+h6==H}*>nwA=WxY%`b{d(^6^w<>nd$9(V
zR=P7pXv4f7=?qrD;dQ)FXoWBGy62HmCSEhspJV$^X8(xj{=XvB{|5O&Z-1oS60@M;
zWk{M~1WrD}3%i4pQ&~Ly59;@CFUjeG@kM#8<6|lHsQz}_Pr1;<4#dAuLnCBY>Q}$$L+2Pi6O^*6GsX!cy|`2d$Nm
z{r-2ViLEr;DSHN9UTVwsONB=I{Qk))nUX9-0Fa{D5O|2sIbH-NcHpZO@%6){m#P5%
zdaHZ!^pCv!uhHIOTtt%U76r9AD?-*(-c7|=5x0?VeC06SKaE*cP*6Cap<(A&q$Bt=
zFC$Q9Y}|4zw!ZjLFvd6{>TqjI)4|+`AZ9i0@urWDPe26b%%~bC2ZwmT8cSrhc~5li
z4>A2(rxSck03bjc8yzL^S+rVg#Z2qOSo;Vdi0U#vyp8mmpMXutx+%QY^Ko)=`dGJW;B`5^OaS&GtZPEi!5#FmkU+^ke=Txyqg{F
zn=34>IahbBs$`%SgCh``=`SAxCJyFeF2_GE>jaOT!dEY+KFB!HI+bFP0$HFebuf=l
zN>eNaC9tN}+cyVhDVlm+niJ|!7PCrByxw1d+rfn<3xmNfsAnbY
zhW92+t)ydVrl+T0s}bdnC6?%9dacfHmmBxL834s22B33O<_?aaznS*_w?>uW;gMOP
znKHvwXF(Tj!e<<>^`a^Ayv)pct=hN-7Z+FlROHS$!jo%F?kYOu8XFr>fG$~CIegl=
zI7(!w=Yb5r#YY$m;4UyYv0UH+`EY&3;Ylr!MAud;4tt
z1MlD3sH&V)iwpGU60wplyU8>nE2~u;=%ki~KukbVw>sXMfYnhJ_&;
zcTo1I_vG|+pRyDc=JCM;eM|#>#k)p|hpN%7IScYqME6-Vs2+{pAaey-Lg;pOcR>~q
z{e8LJgiFVMnxVGOB57}J@8{5%ql3dQms?Pb{(2gL(`$f0mV%DKqROoPmi^V_k#M
z=g)iF+l7Ti`~m`26*@pr<@k6<_Qy(E%k7;VJ-z6?{r!YK3tOf9@bK_;dBw_11Oibx
zUim#xbTn`RghinnBQulZJH}hRs~K4MV2Jc~zP|$_LDk$|Y>fl;sO8^&PuV8_C@p=J
z;73nSPspS3;zfy3%ICuT^AM4qg&C_JQez`!`D76%#D|Dd+tB7ORAqfVxg{mqrMl}Y
zD-Qs0(Y=LSyV<+p0&Ua7DsHH6L$H(?b!gpL4hR82F6(2XMUIT7a+Ve8MQDbwSVgGy<+h6VcvzW
zP*nx=E0i+R`bq3*N1f-O)!IyW5s+`
z<-6$Fy0!@W>(6B6F~{F>B&d2iMl$&}Am&e2Qj{zk<*S_z@kii`nw%rCH37HPs$tx&
zEDtcz)LAfvO0y=^3?!GO=ca<6UL#^upuS2OkPDT!@4dt74DIdgZq|f-uCH4r{P1Zm
z`vw+@@2mF!08O%6)w$2-vb?Bhei#w_8mj-f+{^i}rJ!V}vl9(aGd6azwcS}>4$5K)
z$=TW23FQy{uasKMmx=*X%Devo@JelRaPenx@l9WLP4y28Fk{o;;X#w^J@OyL)@8>-
z56u>RyLYhj_4M{A`boGcxB}1yR=%*lYx3=59kJF41O;SCNr^_YXkTA!9}l4bCbs;2^E7y*N92jAr`MOy&&);;O+TNdR(_P5NQh=fAA06Xjlj
zfgL+cDy?H|Y^>h(CI&nO1~dHJL`PDK3Rt||jxg^5!J`XR(wjUmJ~8FzbJj`dQc&3Q
z-vsoFQT4p%o}2p6Ie3Z-0O6(@V$e*SSQd5`O&XkM01B|Rv+b>v0y&<=%6|2Vg@_Mi
zUU#*%u)Kty1hNDV2-f7^0HZU|t&RwUxSu@!_P20050E&5O*Jt;E{y0}x7pp=*(o(_
zbsSaO+1k<5)t#GLh!>j!b#4dV$AyK3cv_eL&dYsMp%=kO2_L1D_UTC~H$qUOfQ!k%
zU~lqo5&ypSW&Z3@_Z1m5DD=9_k&G9005we{uby6
z9I0J$T>KNDVZLf@XSZb2Lfdj5{Jqx6ZE`)xbLpMd%F4=H!*^ny8$Z7_f4X!*)k?@2Qbh#cwudI4}w3LQh(QszV+>1Cd9H5QZ?l;%GIOl%!(
zH%$&j&#z{(nkdLbFx}iej6T)9f=)C;z2lR3YO%s*2+KA_2UBaUQS?u)B;dZfMYI;g
z*s@xd)0t(h$lF!b3qPcTmSv(;Hki5_Cma6>;Ugj?$%CuhIgFdzM|=NB$*if_t9Mn<
zV?NuS&KRsdeYZQaH(wUJ8f#&)aJnBx!j~Dgi!05+QWDDY|S+1(6tYsXM9ZALkUcIc6qi
zPyuH!*(Vv&<|rvEX>>{*vbfYL81MkJHAYE-w12WdC1avg}_6D;fHkrF;7(
zV0=jA`E)4*=fl88;tkR|)iXNU+L~%mnZ%M^U3Ns!eOe%@o%Ag
zFnWA!3`yP)k{*xF!M0Ug(zmpAoK~B8WyJ;Nw~v~B#WpU9N8>4X8*p6du*GS;J4ONM16qfI
zvg1t6rE~iQ-XK}S3hU>we2}{_jT9vt)IH`N7owLf+pgcZF;q^3E^I3Fk#B&Z7GcIyB;f`dxpZTTy_Q`in
zq#Vj_X=}XQHf?yg2p`M`*Vos*J^35?^w;p22S5-VCQ#HmFV$61RZbO`lK7Mevrm!F
z_`|yVz>5V5HdgkSs~7W&?S32SZFh>WY8YavGOpt{i(;mS?OSy%#N@1-=qbzJGRFK4
zg>Pm@&=jb+`hJY7dIk(za61_^KLWBQwsE9LU^Ug^^7VmRJ)>WU6>%|knU=J|U%wtw
z9@0wH3gvLHwddZTDE7-`6VKz~<#uz1-0ruRNd*&t)q_#5m(MDTPmW4xK)#ptZgg>x
zJ!v2cC$hJ_=uHc#SEF5yPmhSIvDca*MAF0`z=D{6sHxt(ULotnI>fuNK#Wu5!lpLi
z%fPyjt`JHU0)BnPye4sIBVI35ABt#Hkd{X6C_gAIr3l~yUa`fItgYL*Rzoo^UEBnp
z#mU2N*6;)n?taG^jcco?7&h+`Zj0UofWYFf9%NPMD~)F^1Rwigp8zdoh3{Qjhmgyq
z&c`}wMg4&ur&M&sPy<^N!A1A+&IvhH?x|#YIk7u0R-(wL$E09=a7_Ukemi4Ha3VqwFJB?9@AI~H_HNH^WnFxG7%mjFrgMqv
zLX6eDC9X30<$MGFJebBY*e*E@@qCzd_w7LrmA-~+S84*-v=6T}$r~#y1>B4{CiC{GV2+N0lQN)yCM8Ww`$cFucyp8&QmLrADJb2f;u4q?$Te
zyCgQ5nMc+Bw_Ui9HU2j9HO1u;YDFx!7SGpT0YZbQGTBy&k-s~LO}otZ4S-Zo)LN{c@^8!iKt
z7EWm(BgfrkTrOv$?>ok);&)rw^nuMZQ#}XZqiXjq4yN!tM*GF}Gf*hp6fTGD309U2lMNCnaj
zcN>Mi2`yC6Iz>b7qO!QD;d#LuM-`6vzTSZWJ3?$$o1k%6
z@yyQd&P~#v=g*zsbqeo%gZj<2H7|4GyV>d+8zpKzHCc$jHFl(=wYa#rprBWRE~v}$
zDT}R@(>=0>rZ!}#d=bI<+RZSYG@9TSt=Z1>+O%z3I@9AEvu
zxyO14Mn)wzcl8uAGQA!Y7PkV*SLJVb5Oh
zxxuhg1gx{OrA5MLNYZl{2juZPJGRE>jG{D7
zZL`;4y5=Q{aNX_U!tFVVjD)PWMVgWwHyss#^~7U?HLy@**yz4mb$`ozYp-ME$nn=<
zGQq5BV_gnH5+kq#mT|NSI!b2YQ+UAE?rsz&jwcO|u1A<8T&sq6HbB
zKikEp#T^>%e|FKwDfsX?EF_fF$}KzOBAc=Wf*zp(r{5h$B^D;Md_9o=
zhKhvVk)wm5@AUkPpN~gcZ4&ZhJ*Vr}-@11E0GRUs8>a)>{{R>aWZSY}0OxvUZ7hC<
zia>4o=+xAzw&vHU`48=%Pfy?3Y3*+B(zEP{dVEf6yrJEnvA7xfqphJaVN!8xd1+3z
zu_BBjIrca)k-vt2{rx&BzlF60*slg8X|m7>RI3qN|H<*GsWS^-rJ+I5=H@4aPx=%|
zK_H@Xl-|$xn=Q@l-&ztPWZr5RA`7n6K^(-+kJG`W>clB>)1!eQZob*{sdiswKSmUh
z@~0e>f*2Qvhwu}zw4poe1uYGpDyt@oSuRw?0SU`0UT%Iz8=LKe?ZToJV?kQ)-?!f_
zUo3%KZEGx-kC&JIUKGVLFg7)f7~8Kpnhz|Pg0~r2`_ahnQ9~9EmN#~H@h7HyMVB~2
z=yFTsp5yDN6Ulz*p+*TeWr=*&T4w2JikRRj=ggkic0*r1G6$UlV(z2PC(ifhyKpec
z6O0i6Z(`KIu>T7cqHbo9xyOOa23
zRgl4AzjYdq<(ont^5p0T*mu3IoAe_Y+KI`@snG9mgMSf?6t*IL
zuzFl#S!ux3i}Se1Dwa6(Af5Ebisba-hLMQ-o+mFf%FXV(}U)WJ{u-j>Xo}
zae8VhdbKVlrc^5UdF;17Z#jjMk{5pB##hya6=Q8}L3!Dx@87@E)?b)Af@n{;d$@f|
zO872D>mnqsb>%dbIt3ac001n;1;5G?t!2c_0gW1YJAv;HH1a_+2p>PcO0r-@V0}eJ
zg$}!;#LigR59OI+8|ur++KHQI91ayrFZ{|rETdRT>EF<@CU(9!RFSf7bwKUi{IkmcNkAth<_w%U?
zC8nt8Xa^@JaKd_>-^Zq;r0vh1y)#f6{2KPl!NCFK6QCRL?EDPGGp_Z|wOTGZE|z9y
zrbg07obg``3Y$&WbPQWB7li}
z61#rUuko#fzRYPLLI%S3)WuPaAcPJ%;O^!=XYXMunGJdic&r|pk=2;)`$Wi8vRE8}
zm!2sz@;!o|X?xvV=L9;E{neckff9ydaB5>eT`fIf%f;EVL#OgPWSiUi&O6d)oM__fLuM6R^%A_Ui~o<(GNA2>+h5+f-yN;d5THn
zXhRv24{ec8@BvFC$_p9AQv@Oe6e5d{49^$(6=Bp2JLXFQ`-%pH>zfn}gK(f99
zYn+ieI3(yDwAoF3;cGZVc9dyTcGJy!_}}Lj7R>)+!}!)gE8gs{Dbah50lGa|n_CnX
zN*wG>th1PZ*|Gi~9PR&VmH#JomOe|E1AxDLl$Sd*3A+BvPXABG{5!w>|MLJZc!kDr
z0TwbI&vY**HzyJOBQHNME}W^i(9o{PF5HoDRE?}?7MzO~`Bsm3$X*Y_9!etd-t9$3
zMd3x`3OLPuO-d6mk>Y(o01EWt#IipbJ7?>g#vmKf;&=jsQH%c30F9#H>ypzdfk%;6
z%#GoxIOqzI^7E7OYXS|J7x_bD>Pgz{x(%lL*V@VbB!6|I3P;kCYW?Q+eiz?wFySR7
zCA~0CjnBx4k9S>O{?(Z_!`#@oe{V`Fv{0wUa_ey+kVyZ6v&*1`z#U7Q<@^vSDRg)m
zU;QtIlkh45WHheA9%x{CiA%}n!y9fofkc8H8gSuVe=8-4)Iy*t
zSUnGgkExKBgJ3>qYikPve;Z!C03(E2H9=0|j=3CxjGk>#QmsG+XfaFH*D0{Go}8Ly
z(=PWc-`v{z5)0nMhOe^vM>XgvD=42Gi-4x5eNllfh|H3%trs_i5v*%U;HajlCA*2(
zwAC`$Ds6zaxwQyg#_T|*sU8ji<{1f-ZcpDJWhRyblg%46<{{Fx#Q%TcCc^UC;
zm!`^`@wgsyE;5hv8hjpZ(4W#*F9sG=raRb|wkH4pG1F1JyL?C8npy^+zeNMpe
z3Wh$kY%)s|uB`OUHMe_&804)JsrHP^YPW;Wy}yLh63B|vYH!m-CnqK*Zq};yLF%El
zy!X&Ggo_A%dN>3kKp?0j13uW+cE3>Vt<^Tz-`@`!8vAU?al@Bz@5Pn^8eKYWz?7lL
zpL2ASd_F?#seIvmXXYO$@IU`^@~?9s_#R^<{?4u9qirAfuQY&ytcpyjlu5|{0;?C{
AK>z>%
literal 17709
zcmb4r1yGzpl;+@ryXzpq9fAiZxVyW%yF+kE@Zb{M-63djhv4q+&QA8~>b7e4>guNI
zAML;8`S<$uL@LUEMMfY%0002UQj%iI000CC{C*1v3x56<3`Gcjfp?VDasdEP`u|-J
z$@D1yzJzm?k`sqJfJ8%Lz+hT8KL7y808(PYs-Br=Szf+418+lu?ClCDK=M!>;8#Ga
z(j_c3Iy4rlqN-R&NyEH$WuZsHGati;GO_OopQ*!%zq2ws_88PnRFf8x
zYyVe~2vUZF)lt(+vsr(2$<~P^574C~Be1pfK?Wb_3||;W>iDgTY>i2UD6N
zu%hfiaQ^U|W+KA05Fi{Nw!MOhmYA|3cfsZ=j0sU-IVq^?;4=I;7jh3!^(XpNaSj-=vjVKb{NGpyMQ%1u5%j
ziiC2U0@HC4_A`S+0z(i}WhQlyy;y>dpiSM*VqVT$vEQEW``@9y)ja=jv;0d=%%#VL
ztzp1gx^N`c7SmJN-G+NZ+KT$&x%-9xx;#B?hN}|7B|Ghp;0xos#qZie7J?6UhtHo#
zWiZ};ZRH8di+(^GJaqe`khFCz*6QZ@r?C*;1bpWG+gbwEk4a(#fi69OTDmgXs3G4U
zV})ts!9VZM-^)jUIHoD$G<>{_@3G;8N#gbD<=bjk{QNp<$9FYyGRpcEg?Lr)cX9JV
zf!{z>8j9uR-pTT`Aj46@je3wUvi
zr->Decx+7-G9v%()K6tVmaIl+79n2s4{c{k?pwZ|KA23k7sW>0aIR-OP~x1qZkr3v
zxNz8itmEAZ_DXQH;r_%qfbE*hV8N^(x)(XX`5cI_8_M}ar9C>`QpbGxrvP>9NLR_cS^h9=AtmH+U6*00V#A6srp=$X
zioa2SJO!C(HK;k;AcD$3mD2zIkB~Ls>J!X@NT9hc4?6Km^MHoIh42uHU2=kKHVei^
zrZ-@%-R(D*52|5rzS&h+M1n~+wxJkJ{~tf^{E7NkPel=s?2r`@!4tFlD{o??Z>!el$-$x6SnPguLp~Fxm7fF96^=I-Z46KX4LAW2U
zl+FmmVz3H*IsPofDhq;9RNur9vkarLJ2F$a
z=h7juvuD5;^$CNRW@q}q`vRwp&RG_|i-)vSsM~HwqUSTMn3eamXiG{c(FtDsBC7RB
z>RXWu2hxEok8^PjKY;z)JjW`FIn?`W5LzFO=+IV$M|Qtmy!T?~8_w!o2*T?9Fo76_
zAL~n8Q3wr7YF*)kCVj&1JN$i=K^)+!L0amA^gDMlJpiEU+8K9M?rmh
zSF|HG0*^Hwl%<;@?z|0d*`sFM50AxyCA`LI?@dP}S{q|XSFFNczj94pngD_4YrHUB
zGBR>XIc~NaIHjeu@D+I`L;ay5VB4Wv0DuqzTb;T#_p+@LV$Wv}1*50z&v-s>S)QiZ
z5%6;7M^+zJ7RD{@_zImJeVD}vyZjFj2=(7gl2U&!BwvshD{@R6{!-IyZ)Sf+y{T4g
zI^rDDVPvd?XtB2S@x8hhskoh>9reSFP8q!j>OjS%C?*0BVRbg)Kcy41P|8nGn0(9s
zc;`%`u53Bf@3`O9J_J4W=?Y$1&4bZXG=(&QhlIWA~rO+%ufIOvBYvzD#B
za_i~_zXl5gO*-FPC;m(&z4^PfjlqF6h=DMjFMbv>cy!dr-Q)|GG8TX(0}zuxjIN#i
zWIQryPT_n}p!xkT0wWvTW|vo=D0Q--fdQb^j>UaJRu+GigpnL2e*n%Y4e}esd*aLe
z>C}Wx`~tpDEo<>Yb3(#;)^e`xBpuO$Airvrmhfj#r}}AQ$7I;O-8#+QafbK({qmh4qE;1#c7pU!v?>
zt(0840GpTk0;F1p-?f7BJ%VFTYwVA9nFm4?9W^(_8A+a9+2vJrWI209I*i
z2kW5}GClf4O!$%KeE^~YG`kHKG)DPR5gXep!q>GS$ntaVS>sA~R#HiT&43p5S^gJ)C(-nrw7l-!yXp(CY-k_a5R)B+^i2>ccfb
zbL;}t(AEg6U4QSK#O<)~DgDF586T`DuewJsqo>o8{%yN2uY_A|r^}$xV4;14s)sgF
z{wSBB&3<}|o3f9SeWAdo4GyBLJ%}dcBqCw|R!1Xpz3}Z*ef;%QD?GPxS59nD+k*~K
z9Au)lyVvwsUhj#%01@M7-{3s}O7|1ff@x+XpJ}@IvdP@(2}@MvKz=gk9z6-lx^_L(
znS@@*AN_RkwwS?6isf<&?My#>`>azvW^c4GDy1H_HxEA}X*Mw}FBqJzTUh_wH+;{{
z>Ki3>62d?tr-f4PRtJSwu$d@RIPFHf`ZjF3>N&4)6)#Ih&=@pAzRTY|g~)(w)O(TB
zyQ@>xD;i%2!GtDI1LYv#0}V*%zUB12uD9|uT{jh@59(Xl7#MU2JfGKf-q2AnX3C2E
zE7*?9K6kjZtlcUMk#BQ(NnzFU=F_}MiaRo0+c-RWZ_GuXYCOI9x5eQ+U8o4`@sKsU
z3ZVaj1OAn6x}g%A14Cy*vSVHv?FWMWO6aNTeVJ4{Pu!f_4*2-7yRSq0UmB;Q(f76^
zTSr-5d}gnvbOT&ZQM(O5#`5#~^u3i;zBs7nWBrvL8{cT1T~Bwa6W3;6-pi|%c(>X3
zIr5MJpyul=%HsvB^H@%k6DxdqVPjiqDpf;U
zG33UntFM1+KG1_3bKB&d?)hz0tlAK0_Em_HaIVfq!0IweW{9p9A~*DxgTqI?oKDk@
z;HWy4tSAE`IC90U!h~_jTI$e3SLEC7UV%;X7_#2ZdJz2G7OTUuU15ahm4X+y-2Fke
zV7D4IpHm?kearEB_=3BgwMS}nM}6`=QzsW&UEEXjz8ihp5)d`5bPRAF>Ip{N+zVB-{;Re`
zY-~F9e}ztbzgPp-9e!lN^f~oc=meynGH@Wq0IkxbO;|X-3=*^d9~AZPLmV!5f5xOU
zy9mc?lgW15(EW2M7@KTy2l@P__<)owutli+EXXg-$_B=8L~w@=mDEdxjazx^3dFe8
zY^-2JH@0&lJU5@kDRWbhM@1UZox%7HjADiZ8i^HnKx8v3SD}F}OkFmawX6U(no5}BJ3Yfr
z((OIIn17(@@8$)U0z6DHR;Wv$q9D$A>k^jQ>$D{g;-FvXCiH!IYWr{U1)6`e<$wYL
zS%BWn(|0;Ec|qr
zfEkJX*9$bd?R_SLv@kcs0oH1~EH$$W1plHeLcD9ArzMKVTGMOk)_%rFCn3@hXls7}
zv_>$=W}T0$I1o_ic}$K#gIEoVzU>siiH8&$X)oXzyJXXoNoHTuY?T`uZdHYcN}MPZ
z>bWTh#?fNiO?{7jYjUYIw~sl?)Mkx0YHED8R~>MKR5oA$+>RVeEi?!X=1OcBaz8rR
zSxA+DH;1`D5^SGGXs}*80MNh-0sb{STta804+sX;mcIPx2nbWtOtY3Oct~yo{wHC@
z9d}0f+~1l>fL{j^w@nYm!C)S)hFaGz>UN3u#!ESEV8
z9sxW-O)%O^d#@o22W1zPX$2X0y3oe%D=g~&hLNQ~`|25k0!{)*koR_(NQ8lr{ElIF
ztK%0IJMh}d}T@q>NB-qBf&o8u8
z8IJg0G)SnMrAnC?2m8CE<92%7^pZUsnXYANZCAqWR(c0IZHB8?hjcy?z2*a~+fv*7
zNtscPy*wu+_Qlt8%(QA4=o6Y45Qm&Lx#OhiedF42OdLCHSO&$O#rR#kD)_6L9x!e?
z_HwNCDtYJdpE^2u%d%T{ew*dXGI%*G-~6)Hi0pqVVcNJl1_TQ6MR<_jv9@w&hIhz6
zeq27>1qoO^Gu-le@Y-kc!U}e=V^g_g_gdVg_@ZgGh`6R{co8dsM9EEATcrbP(2qYf
z=n422#wpjM6t4sBYC26KwOOTQ;6Uit1iEvW`H-lgwh#mF~T&Fna=C0npuuYS}_h5eASC
zfAF9zx~M2C1=h;oqYJ#Nl+y~7RMpfXCHm89FhpWQT~HRC)SmOlLV;3SK^`3qE!G%$
zX%>-+J2HwEwi7CTl^0X?(7o5+mCNHdBiev}oVPO(5hKv%G0S}Ju1oHnW@c23Wu#V}ia^g*aNLwr*0f96G7TVc2e&&xhxN@4o$Ri*@|r@Dxpg7)J)
z?cno>&wL*oFuC$ww-9=uMeo?b^J#0uI$jJf5SVLMe7g9R%eDLJq^5!=G$P>lUJ5{S-CYNMjX$xABbZe20NTX-a
zb+V`c`3IdSy8I4u&zz*-@W-f!rUH05{b)K?{
zyzhuDk$20gDzRak1pkXYxK6V+k@3#JT6fztAq6~^@$^q3aTc_a
z=;V%i3j761$)s9aW@8kCyjR|Q$zNt6*RQ)erAc(vxR+f1xB?+)8haREqY)9s2GCnb
zEt8EazfOpyM=1D42ilk&uf;Du(tb8Jk5xfikrJ-kS?V
zqlz6-efnGDKDTNjO;El67R$GK=dT1lu+o(4&v#4dp@9dLK}KwYCo*mz0=(n@JKB+
zVH{N_PH<4dFyoY>|N1^`jD5$XS-pvD$nqQT=|-Z{_i+f8f&4-ax>I!4P1s?y%`@U4
zqUXjLAAO;aFsl3yG?d8xQ1k06+=*~UoTmHZSe
.
diff --git a/pages/doc/csp_users_roles.md b/pages/doc/csp_users_roles.md
index 5fba4575d..5478b18b3 100644
--- a/pages/doc/csp_users_roles.md
+++ b/pages/doc/csp_users_roles.md
@@ -41,7 +41,7 @@ The VMware Cloud Services Console **Roles** page lists all service roles and cus
### Tanzu Observability Service Roles (Built-in)
The VMware Cloud Services Console **Roles** page includes the following built-in Tanzu Observability service roles:
-- A corresponding Tanzu Observability service role for each [Tanzu Observability permission](csp_permissions_overview.html#operations-for-applications-permissions), that is, each of the following service roles has only one permission assigned:
+- A corresponding Tanzu Observability service role for each [Tanzu Observability permission](csp_permissions_overview.html#tanzu-observability-permissions), that is, each of the following service roles has only one permission assigned:
* **Admin**
* **Alerts**
@@ -87,7 +87,7 @@ The VMware Cloud Services Console **Roles** page includes the following built-in
### Create, Edit, or Delete a Custom Role
-Custom roles let you combine service permissions of your choice, for example, [Tanzu Observability permissions](csp_permissions_overview.html#operations-for-applications-permissions). A custom role can have permissions for one or multiple services in your organization. For example, you can have a custom role that grants administrative permissions for one service and read-only permissions for another service.
+Custom roles let you combine service permissions of your choice, for example, [Tanzu Observability permissions](csp_permissions_overview.html#tanzu-observability-permissions). A custom role can have permissions for one or multiple services in your organization. For example, you can have a custom role that grants administrative permissions for one service and read-only permissions for another service.
{% include important.html content="The Tanzu Observability permissions in a custom role apply to **all** Tanzu Observability service instances to which the target user account or server to server app has access. Therefore, to obtain the Tanzu Observability permissions from a custom role for a given Tanzu Observability service instance, the user account or server to server app assigned with that custom role must have at least one Operations to Applications service role for that service instance, for example, the **Viewer** service role."%}
@@ -115,7 +115,7 @@ For a [federated domain](csp_authentication.html#federated-domain-authentication
## Manage User Groups
-For efficient user management, you can create groups of users and assign roles to these groups. You can add new and existing users to a group. You can assign [service roles](#operations-for-applications-service-roles-built-in) and [custom roles](#create-edit-or-delete-a-custom-role) to a group.
+For efficient user management, you can create groups of users and assign roles to these groups. You can add new and existing users to a group. You can assign [service roles](#tanzu-observability-service-roles-built-in) and [custom roles](#create-edit-or-delete-a-custom-role) to a group.
See [How do I work with groups](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-0BD8A07B-C3C0-4220-8CD0-18FA070D3DAD.html) in the VMware Cloud services documentation.
diff --git a/pages/doc/documentation_getting_started.md b/pages/doc/documentation_getting_started.md
index 43962f0e2..c3ba2c7f0 100644
--- a/pages/doc/documentation_getting_started.md
+++ b/pages/doc/documentation_getting_started.md
@@ -81,7 +81,7 @@ Our documentation includes reference documentation for API, query language, and
@@ -153,7 +153,7 @@ Data protected by a metrics security policy rule can become invisible to users.
### Alert Notifications
-To protect metrics or RED metrics from inclusion in alert notifications, use the **Secure Metrics Details** check box. Operations for Applications looks at all metrics when determining when an alert status should change and shows them in alert notifications. When the check box is selected, [details are not shown](alerts_notifications.html#alert-notification-with-secured-metrics-details) in the notification.
+To protect metrics or RED metrics from inclusion in alert notifications, use the **Secure Metrics Details** check box. Tanzu Observability looks at all metrics when determining when an alert status should change and shows them in alert notifications. When the check box is selected, [details are not shown](alerts_notifications.html#alert-notification-with-secured-metrics-details) in the notification.
### Derived Metrics and Events
diff --git a/pages/doc/csp_server_to_server_apps.md b/pages/doc/csp_server_to_server_apps.md
index 906f658c0..4c82912bf 100644
--- a/pages/doc/csp_server_to_server_apps.md
+++ b/pages/doc/csp_server_to_server_apps.md
@@ -4,16 +4,16 @@ keywords: administration
tags: [administration]
sidebar: doc_sidebar
permalink: csp_server_to_server_apps.html
-summary: Create server to server apps and grant them access to VMware Aria Operations for Applications on VMware Cloud services.
+summary: Create server to server apps and grant them access to VMware Tanzu Observability on VMware Cloud services.
---
-{% include note.html content="Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage Service Accounts](service-accounts.html)."%}
+{% include note.html content="Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform. The content in this chapter is valid for VMware Cloud services subscriptions. For **original** subscriptions, see [Manage Service Accounts](service-accounts.html)."%}
-VMware Cloud services supports server to server apps that you can use to automate management of Operations for Applications objects, such as dashboards, alerts, etc. A server to server app can't perform the **UI operations** that all user accounts can [perform by default](csp_permissions_overview.html#default-tasks).
+VMware Cloud services supports server to server apps that you can use to automate management of Tanzu Observability objects, such as dashboards, alerts, etc. A server to server app can't perform the **UI operations** that all user accounts can [perform by default](csp_permissions_overview.html#default-tasks).
You can also use a server to server app for a [Wavefront proxy authentication](proxies_installing.html#proxy-authentication-types). For example, see our [Windows Host Integration Tutorial](windows_host_tutorial.html), which includes installing a Wavefront proxy with server to server OAuth app credentials.
-{% include note.html content="A server to server app must hold roles with certain [permissions](csp_permissions_overview.html#operations-for-applications-permissions) to perform tasks. For example, to run queries, a server to server app must hold the [**Metrics** service role](csp_users_roles.html#operations-for-applications-service-roles-built-in) or a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with the **Metrics** permission. To manage dashboards and alerts, the server to server app might need both roles with permissions and [access](csp_access.html)." %}
+{% include note.html content="A server to server app must hold roles with certain [permissions](csp_permissions_overview.html#tanzu-observability-permissions) to perform tasks. For example, to run queries, a server to server app must hold the [**Metrics** service role](csp_users_roles.html#tanzu-observability-service-roles-built-in) or a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with the **Metrics** permission. To manage dashboards and alerts, the server to server app might need both roles with permissions and [access](csp_access.html)." %}
## What Are Server to Server Apps?
@@ -25,29 +25,29 @@ Server to server apps are used for automating management tasks.
{% include note.html content="You must explicitly grant each server to server app only the role with the permission required for the task that’s being automated (least required privilege). Doing so, you ensure that permissions for server to server app are always very limited." %}
* A server to server app can be used in multiple organizations. The owner of a server to server app is the organization in which it was created.
-{% include important.html content="For each server to server app with access to an Operations for Applications service instance, we create a corresponding **internal service account** in that service instance and add it the **Service Accounts** internal system group. So that, when you configure [the access control security settings](csp_access.html#change-the-access-control-security-setting), [ingestion polices](ingestion_policies.html#step-1-specify-the-scope-and-pps-limit), or [metrics security rules](csp_metrics_security.html), the server to server apps that are assigned with Operations for Applications service roles are represented as service accounts together with the [service accounts](csp_service_accounts.html) created in Operations for Applications."%}
+{% include important.html content="For each server to server app with access to a Tanzu Observability service instance, we create a corresponding **internal service account** in that service instance and add it the **Service Accounts** internal system group. So that, when you configure [the access control security settings](csp_access.html#change-the-access-control-security-setting), [ingestion polices](ingestion_policies.html#step-1-specify-the-scope-and-pps-limit), or [metrics security rules](csp_metrics_security.html), the server to server apps that are assigned with Tanzu Observability service roles are represented as service accounts together with the [service accounts](csp_service_accounts.html) created in Tanzu Observability."%}
## How Server to Server Apps Work
{% include note.html content="To manage server to server apps, you must hold either the VMware Cloud **Organization Owner** role or any other organization role paired with the **Developer** additional role. See [What organization roles are available in VMware Cloud Services](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-C11D3AAC-267C-4F16-A0E3-3EDF286EBE53.html) in the VMware Cloud services documentation." %}
-If you build an application or tool that manages proxies or ingests data, then that tool must authenticate to the Operations for Applications REST API with a VMware Cloud services access token. Here's how it works:
+If you build an application or tool that manages proxies or ingests data, then that tool must authenticate to the Tanzu Observability REST API with a VMware Cloud services access token. Here's how it works:
1. Create a server to server app in VMware Cloud services. See [How to use OAuth 2.0 for server to server apps](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-327AE12A-85DB-474B-89B2-86651DF91C77.html) in the VMware Cloud services documentation.
-1. Assign the server to server app with one or more [Operations for Applications service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in) for the service instance.
+1. Assign the server to server app with one or more [Tanzu Observability service roles](csp_users_roles.html#tanzu-observability-service-roles-built-in) for the service instance.
{% include important.html content="Ensure that you assign the server to server app **only** with the roles and permissions that are needed. Do not assign all roles listed in the VMware Cloud Services Console." %}
- For example, to use a server to server app only for setting up the Operations for Applications integrations, assign only the **Proxies** service role to the app.
+ For example, to use a server to server app only for setting up the Tanzu Observability integrations, assign only the **Proxies** service role to the app.
- If you plan to assign the server to server app a custom role, you must assign that server to server app at least one Operations for Applications service role, for example **Viewer**.
+ If you plan to assign the server to server app a custom role, you must assign that server to server app at least one Tanzu Observability service role, for example **Viewer**.
-1. Optionally, assign the server to server app a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with an [Operations for Applications permission](csp_permissions_overview.html#operations-for-applications-permissions).
+1. Optionally, assign the server to server app a [custom role](csp_users_roles.html#create-edit-or-delete-a-custom-role) with an [Tanzu Observability permission](csp_permissions_overview.html#tanzu-observability-permissions).
- {% include important.html content="In a multi-tenant Operations for Applications environment, custom roles apply to **all** service instances (tenants) to which the server to server app has access, that is, for which the server to server app has at least one service role."%}
+ {% include important.html content="In a multi-tenant Tanzu Observability environment, custom roles apply to **all** service instances (tenants) to which the server to server app has access, that is, for which the server to server app has at least one service role."%}
1. Obtain the OAuth 2.0 client credentials of the server to server app and save them to a secure place.
-1. Add the app to your VMware Cloud organization running the Operations for Applications service.
+1. Add the app to your VMware Cloud organization running the Tanzu Observability service.
1. Configure your tool to pass the OAuth 2.0 client credentials to the REST API and exchange them to an access token. See [Make API Calls by Using a Server to Server App](using_wavefront_api.html#make-api-calls-by-using-a-server-to-server-app).
The access token is directly issued to your tool and it authenticates seamlessly to the API.
diff --git a/pages/doc/csp_sign_up_or_log_in.md b/pages/doc/csp_sign_up_or_log_in.md
index e2e24af67..5d9b56e4f 100644
--- a/pages/doc/csp_sign_up_or_log_in.md
+++ b/pages/doc/csp_sign_up_or_log_in.md
@@ -5,20 +5,20 @@ sidebar: doc_sidebar
permalink: csp_sign_up_or_log_in.html
summary: Learn how you can sign up and log in to your service instance if it's onboarded to VMware Cloud services.
---
-Starting July 3, 2023, VMware Aria Operations for Applications is a service on the VMware Cloud services platform.
+Starting July 3, 2023, VMware Tanzu Observability (formerly known as VMware Aria Operations for Applications) is a service on the VMware Cloud services platform.
-{% include note.html content="After July 3, 2023, we support two types of subscriptions: Operations for Applications subscriptions **onboarded** to VMware Cloud services and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services. We are in the process of incrementally [onboarding](csp_migration.html) original subscriptions to VMware Cloud services. For information about original and VMware Cloud services subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html). "%}
+{% include note.html content="After July 3, 2023, we support two types of subscriptions: Tanzu Observability subscriptions **onboarded** to VMware Cloud services and **original** subscriptions. Original subscriptions are the existing ones and they remain as is until onboarded to VMware Cloud services. We are in the process of incrementally [onboarding](csp_migration.html) original subscriptions to VMware Cloud services. For information about original and VMware Cloud services subscriptions and the differences between them, see [Subscription Types](subscriptions-differences.html). "%}
-When your Operations for Applications instance is onboarded to VMware Cloud services, you use a single [VMware Cloud services account](csp_getting_started.html#whats-a-vmware-cloud-services-account) to access your entire VMware Cloud services portfolio across hybrid and native public clouds, including Operations for Applications.
+When your Tanzu Observability instance is onboarded to VMware Cloud services, you use a single [VMware Cloud services account](csp_getting_started.html#whats-a-vmware-cloud-services-account) to access your entire VMware Cloud services portfolio across hybrid and native public clouds, including Tanzu Observability.
Here’s how the signup works:
-1. If you don't belong to the VMware Cloud organization in which the Operations for Applications service instance is running, you can be added to that organization in one the following ways:
+1. If you don't belong to the VMware Cloud organization in which the Tanzu Observability service instance is running, you can be added to that organization in one the following ways:
- A VMware Cloud **Organization Owner** or **Organization Administrator** adds you individually. See [How do I add users to my organization](https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-47AA313E-9DAC-447C-B6C8-DF71ED45B0D5.html) in the VMware Cloud services documentation.
- A VMware Cloud **Organization Owner** and **Enterprise Administrator** federate your corporate domain with VMware Cloud services. See [What is enterprise federation and how does it work](https://docs.vmware.com/en/VMware-Cloud-services/services/setting-up-enterprise-federation-cloud-services/GUID-76FAECB3-CFAA-461E-B9C9-2A49C39CD17F.html) in the VMware Cloud services documentation.
2. A VMware Cloud **Organization Owner** or **Organization Administrator** grants you access to the organization's resources with an [organization role](csp_getting_started.html#whats-a-vmware-cloud-organization-role).
-3. A VMware Cloud **Organization Owner** or **Organization Administrator** grants you access to the Operations for Applications service instance with an [Operations for Applications service role](csp_users_roles.html). In addition, they can grant you a custom role with Operations for Application permissions.
+3. A VMware Cloud **Organization Owner** or **Organization Administrator** grants you access to the Tanzu Observability service instance with an [Tanzu Observability service role](csp_users_roles.html). In addition, they can grant you a custom role with Operations for Application permissions.
- In a multi-tenancy environment, you can have different service and custom roles for the different Operations for Applications service instances (tenants).
+ In a multi-tenancy environment, you can have different service and custom roles for the different Tanzu Observability service instances (tenants).
4. After you’ve been added to an organization, you receive an email notification with information about the VMware Cloud organization to which you were added, your organization role, and any other roles. You can now [sign up](#sign-up-with-an-email-invitation) in the VMware Cloud Services Console.
{% include note.html content="The invitation link is valid for seven days."%}
@@ -26,9 +26,9 @@ Here’s how the signup works:
## Sign Up with an Email Invitation
-If you received an email notification with information that you are added to a VMware Cloud organization with Operations for Applications access, follow these steps:
+If you received an email notification with information that you are added to a VMware Cloud organization with Tanzu Observability access, follow these steps:
-1. Click the **VMware Aria Operations for Applications** link in your email notification.
+1. Click the **VMware Tanzu Observability** link in your email notification.
2. Authenticate yourself to VMware Cloud services.
- If your account is not federated, sign in with your VMware account credentials.
@@ -36,8 +36,8 @@ If you received an email notification with information that you are added to a V
- If your account is federated, sign in with your corporate credentials.
{% include note.html content="As a user of a federated account, you must create a VMware account only if you want to file a support ticket or perform billing and subscription-related operations."%}
-3. On the **Organization** tab of the **Services** page, locate the **VMware Aria Operations for Applications** tile from the list of the services available to the organization.
-4. In the **VMware Aria Operations for Applications** tile, click **Launch Service**.
+3. On the **Organization** tab of the **Services** page, locate the **VMware Tanzu Observability** tile from the list of the services available to the organization.
+4. In the **VMware Tanzu Observability** tile, click **Launch Service**.
+ 
@@ -81,7 +81,7 @@ You can export traces you view in the Traces Browser, save them locally as JSON
### Create a Sampling Policy
-Our intelligent sampling algorithm reduces the volume of ingested traces. The goals of intelligent sampling are to retain traces that are likely to be informative. But sometimes intelligent sampling discards traces that you want to keep. You can [create a sampling policy](trace_sampling_policies.html) to fine-tune intelligent sampling and let the Operations for Applications service know that you want to keep certain spans.
+Our intelligent sampling algorithm reduces the volume of ingested traces. The goals of intelligent sampling are to retain traces that are likely to be informative. But sometimes intelligent sampling discards traces that you want to keep. You can [create a sampling policy](trace_sampling_policies.html) to fine-tune intelligent sampling and let the Tanzu Observability service know that you want to keep certain spans.
diff --git a/pages/doc/tracing_service_dashboard.md b/pages/doc/tracing_service_dashboard.md
index e1f37707c..348465205 100644
--- a/pages/doc/tracing_service_dashboard.md
+++ b/pages/doc/tracing_service_dashboard.md
@@ -7,7 +7,7 @@ permalink: tracing_service_dashboard.html
summary: Identify potential hot spots of a service.
---
-VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) includes the Service Dashboard, which you can use to identify potential hot spots of a service, and then drill down to the Traces Browser.
+Tanzu Observability (formerly known as VMware Aria Operations for Applications) includes the Service Dashboard, which you can use to identify potential hot spots of a service, and then drill down to the Traces Browser.
## Explore the Default Service Dashboard
@@ -43,7 +43,7 @@ style="vertical-align:text-bottom;width:25px" alt="icon to click to get the link
* Select a region of the histogram chart and click **Search Traces** to view the traces for the selected duration.
* Click a bar on a TopK chart.
* Click the vertical ellipsis in the top right of any chart, click **Traces**, and click a service.
- {% include note.html content="If you don’t see **Traces**, check whether your metrics include `application` and `service point` tags.
)
-
+
Using the table view, you can:
* Examine the applications and services, or search for a particular application or service by applying filters.
diff --git a/pages/doc/wavefront_spring_boot.md b/pages/doc/wavefront_spring_boot.md
index 7cdff848a..324df7e23 100644
--- a/pages/doc/wavefront_spring_boot.md
+++ b/pages/doc/wavefront_spring_boot.md
@@ -4,7 +4,7 @@ keywords:
tags:
sidebar: doc_sidebar
permalink: wavefront_springboot.html
-summary: Examine Spring Boot 2 data in VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) dashboards and charts
+summary: Examine Spring Boot 2 data in Tanzu Observability (formerly known as VMware Aria Operations for Applications) dashboards and charts
---
Wavefront for Spring Boot allows you to quickly configure your environment, so Spring Boot 2 components send metrics, histograms, and traces/spans to our service.
@@ -57,8 +57,8 @@ This is the default dashboard you see when you run the Spring Boot initializer.
Getting started is easy. Here are some things to know before you start:
* **Ingestion Method**: Wavefront for Spring Boot sends data to our service via [direct ingestion](direct_ingestion.html) by default. You can [configure your application to send data via the Wavefront proxy](#proxy).
-* **Target**: Wavefront for Spring Boot sends data to the freemium instance by default. You can [configure your application to send data to your Operations for Applications instance](#step-2-optional-specify-your-operations-for-applications-instance).
-* **Account**: By default, the starter sends you to the Freemium instance, auto-negotiates an account, and saves the API token in the `~/.wavefront_freemium` file in your home directory. If you customize the starter to go to your Operations for Applications instance (see Step 2 below) you need to include an API token for that instance.
+* **Target**: Wavefront for Spring Boot sends data to the freemium instance by default. You can [configure your application to send data to your Tanzu Observability instance](#step-2-optional-specify-your-tanzu-observability-instance).
+* **Account**: By default, the starter sends you to the Freemium instance, auto-negotiates an account, and saves the API token in the `~/.wavefront_freemium` file in your home directory. If you customize the starter to go to your Tanzu Observability instance (see Step 2 below) you need to include an API token for that instance.
### Prerequisites for Wavefront Spring Boot Starter
@@ -307,17 +307,17 @@ dependencies {
-### Step 2 (Optional): Specify Your Operations for Applications Instance
+### Step 2 (Optional): Specify Your Tanzu Observability Instance
-By default, the Wavefront Spring Boot Starter creates an account for you and sends data to the Freemium instance. If you already have an Operations for Applications account, you can send data there instead by specifying the `uri` and `api-token` properties, as follows:
+By default, the Wavefront Spring Boot Starter creates an account for you and sends data to the Freemium instance. If you already have an Tanzu Observability account, you can send data there instead by specifying the `uri` and `api-token` properties, as follows:
```
management.metrics.export.wavefront.api-token=$API_Token
management.metrics.export.wavefront.uri=$wavefront_instance
```
-* `$API_Token` is a valid [API token for your Operations for Applications instance](users_account_managing.html#generate-an-api-token).
-* `$wavefront_instance` is the name of your Operations for Applications instance, for example, `https://example.wavefront.com`.
+* `$API_Token` is a valid [API token for your Tanzu Observability instance](users_account_managing.html#generate-an-api-token).
+* `$wavefront_instance` is the name of your Tanzu Observability instance, for example, `https://example.wavefront.com`.
### Step 3: View Your Data in Our Service
@@ -391,7 +391,7 @@ You can invite users and let them send data to the same cluster:
```
wavefront.freemium-account=true
```
- {% include tip.html content="If you don’t want Operations for Applications to auto-negotiate a freemium account for you, set the value to `false`."%}
+ {% include tip.html content="If you don’t want Tanzu Observability to auto-negotiate a freemium account for you, set the value to `false`."%}
1. Restart your application.
@@ -408,7 +408,7 @@ management.metrics.export.wavefront.uri=proxy://
+
-There are several possible reasons for queues at the proxy. The [Monitoring Wavefront Proxies](monitoring_proxies.html) and the **Queuing Reasons** chart in the **Operations for Applications Service and Proxy Data** dashboard are especially helpful for identifying the cause for queuing, discussed next:
+There are several possible reasons for queues at the proxy. The [Monitoring Wavefront Proxies](monitoring_proxies.html) and the **Queuing Reasons** chart in the **Tanzu Observability Service and Proxy Data** dashboard are especially helpful for identifying the cause for queuing, discussed next:
* [Pushback from Backend](#proxy-queue-reasons-pushback-from-backend)
* [Proxy Rate Limit](#proxy-queue-reasons-proxy-rate-limit)
@@ -219,22 +219,22 @@ If the rate of data ingestion is higher than backend limit, the proxy queues dat
**Troubleshooting & Further Investigation**
-1. Look for pushback in the **Queuing Reasons** chart of the **Operations for Applications Service and Proxy Data** dashboard.
-2. Use the query in the **Data Ingestion Rate (Points)** chart of the **Operations for Applications Service and Proxy Data** dashboard to keep track of your ingestion rate. Ensure the ingestion rate is within contractual limits to avoid overages. While it's possible to ask Support to raise the backend limit such a change can result in overages.
+1. Look for pushback in the **Queuing Reasons** chart of the **Tanzu Observability Service and Proxy Data** dashboard.
+2. Use the query in the **Data Ingestion Rate (Points)** chart of the **Tanzu Observability Service and Proxy Data** dashboard to keep track of your ingestion rate. Ensure the ingestion rate is within contractual limits to avoid overages. While it's possible to ask Support to raise the backend limit such a change can result in overages.
#### Proxy Queue Reasons: Proxy Rate Limit
-If the proxy is configured with a rate limit, and the rate of data sent to the proxy is above the limit, the proxy starts queuing data. The **Proxy Rate Limiter Active** chart in the **Operations for Applications Service and Proxy Data** dashboard provides insight into whether data is coming in faster than the proxy rate limit supports.
+If the proxy is configured with a rate limit, and the rate of data sent to the proxy is above the limit, the proxy starts queuing data. The **Proxy Rate Limiter Active** chart in the **Tanzu Observability Service and Proxy Data** dashboard provides insight into whether data is coming in faster than the proxy rate limit supports.
**Troubleshooting & Further Investigation**
1. Confirm whether data is coming in faster than the proxy's rate limit configuration (`pushRateLimit`). If so, look into ways to reduce your data rate.
- 1. On the **Operations for Applications Service and Proxy Data dashboard** find the **Proxy Troubleshooting** section and examine the **Proxy Rate Limiter Active** chart to see whether the rate limiter is active on the different proxies in your environment.
+ 1. On the **Tanzu Observability Service and Proxy Data dashboard** find the **Proxy Troubleshooting** section and examine the **Proxy Rate Limiter Active** chart to see whether the rate limiter is active on the different proxies in your environment.
2. Confirm the `pushRateLimit` of each proxy by looking at the proxy configuration file or by querying `--proxyconfig.pushRateLimit`.
-2. Go to the **Received Points/Distributions/Spans Per Second** charts in the **Operations for Applications Service and Proxy Data** dashboard
+2. Go to the **Received Points/Distributions/Spans Per Second** charts in the **Tanzu Observability Service and Proxy Data** dashboard
1. Examine the ingest rate for the proxy that seems to have rate limit problems.
2. Use the Filter feature at the top of each dashboard or chart or specifying a specific source name in the underlying queries to filter for the proxy you are interested in.
@@ -249,7 +249,7 @@ Because rate limits are set assuming a steady rate, that burst of 60,000 PPS for
**Troubleshooting & Further Investigation**
-1. Explore the **Received Points/Distributions/Spans Max Burst Rate (top 20)** charts in the **Operations for Applications Service and Proxy Data** dashboard provides to understand the burstiness of your data rate. The queuing ability of the proxy normally helps smooth out the data rate through momentary queuing.
+1. Explore the **Received Points/Distributions/Spans Max Burst Rate (top 20)** charts in the **Tanzu Observability Service and Proxy Data** dashboard provides to understand the burstiness of your data rate. The queuing ability of the proxy normally helps smooth out the data rate through momentary queuing.
2. If you find that the proxy queues sustain and continue to grow, then the overall data ingest rate is too high.
3. Either reduce the ingest rate or request that the backend limit be raised (this could result in overages).
@@ -263,7 +263,7 @@ As the proxy processes data in the memory buffers, space is freed up for new inc
**Troubleshooting & Further Investigation**
-1. Find the **Queuing Reasons** chart in the **Operations for Applications Service and Proxy Data** dashboard and look for `bufferSize`.
+1. Find the **Queuing Reasons** chart in the **Tanzu Observability Service and Proxy Data** dashboard and look for `bufferSize`.
2. If you see problems, consider lowering the ingestion rate or distributing the load among several proxies.
3. In some situations, it might make sense to adjust the `pushMemoryBufferLimit` proxy property.
* Raising this value results in higher memory usage.
@@ -275,7 +275,7 @@ If network issues prevent or slow down requests from the proxy to the Tanzu Obse
**Troubleshooting & Further Investigation:**
-1. Go to the **Network Latency** chart in the **Proxy Troubleshooting** section of the **Operations for Applications Service and Proxy Data** dashboard. This chart tracks the amount of time from when the proxy sends out a data point to when it receives an acknowledgment from the backend.
+1. Go to the **Network Latency** chart in the **Proxy Troubleshooting** section of the **Tanzu Observability Service and Proxy Data** dashboard. This chart tracks the amount of time from when the proxy sends out a data point to when it receives an acknowledgment from the backend.
2. Ensure that this amount of time is in the range of hundreds of milliseconds. If the time reaches the range of seconds, check for network latency issues.
@@ -286,7 +286,7 @@ The proxy configuration property `memGuardFlushThreshold` is meant to protect ag
**Troubleshooting & Further Investigation:**
-1. Find the **Queueing Reasons** chart in the **Operations for Applications Service and Proxy Data** dashboard and examine the `memoryPressure` metric.
+1. Find the **Queueing Reasons** chart in the **Tanzu Observability Service and Proxy Data** dashboard and examine the `memoryPressure` metric.
2. If there's a problem, consider increasing memory limits for the host server.
@@ -297,7 +297,7 @@ If your data travels through a pipeline before reaching the Wavefront proxy or b
**Troubleshooting & Further Investigation**
-Examine the **Data Received Lag** charts in the **Proxy Troubleshooting** section of the **Operations for Applications Service and Proxy Data** dashboard.
+Examine the **Data Received Lag** charts in the **Proxy Troubleshooting** section of the **Tanzu Observability Service and Proxy Data** dashboard.
These charts can help if the data points are timestamped at or near the source of the data. The underlying metric used in these charts tracks the difference between the system time of the proxy host and the timestamp of data points. This difference can provide insight into how long it takes for a data point to traverse the data pipeline and reach the proxy.
@@ -314,7 +314,7 @@ Each time the service detects a new name, it generates a new ID. ID generation a
**Troubleshooting & Further Investigation**
-The **Operations for Applications Usage** integration includes several alerts that you can customize to be alerted when there is a high rate of new IDs.
+The **Tanzu Observability Usage** integration includes several alerts that you can customize to be alerted when there is a high rate of new IDs.
* A high rate of new IDs can happen when you start sending new data to Tanzu Observability.
* A high rate of new IDs could also indicate a **cardinality issue** with the data shape of the data you're sending to Tanzu Observability. For instance, if a timestamp was included as a point tag, a high number of unique point tags results. This can be a problem when you send the data to Tanzu Observability, but also causes problems later when you query the data. See [Data Naming Best Practices](wavefront_data_naming.html) for best practices.
diff --git a/pages/doc/monitoring_overview.md b/pages/doc/monitoring_overview.md
index ac22c1b71..bde18a842 100644
--- a/pages/doc/monitoring_overview.md
+++ b/pages/doc/monitoring_overview.md
@@ -51,7 +51,7 @@ Administrators (and often other team members) are interested in usage data at al
1. Users who install Wavefront proxies can examine the [proxy information](monitoring_proxies.html) on the out-of-the-box dashboards. Larger environments or production environments rely on a team of load-balanced proxies, as discussed by Clement Pang in [this video about proxies](https://vmwaretv.vmware.com/media/t/1_5wfjti3m).
Having usage data for the proxy helps administrators during installation and also helps with proxy sizing later.
-2. View the points flowing into the system from the [Overall Data Rate section](wavefront_monitoring.html#overall-data-rate) of the **Operations for Applications Service and Proxy Data** dashboard.
+2. View the points flowing into the system from the [Overall Data Rate section](wavefront_monitoring.html#overall-data-rate) of the **Tanzu Observability Service and Proxy Data** dashboard.
3. Create custom charts with internal metrics. Our system dashboard information is a great start, but you might benefit from other [internal metrics](wavefront-internal-metrics.html) and it's easy to create a dashboard with custom charts.
**Note**: We've include the internal metrics that are most useful in the documentation.
diff --git a/pages/doc/proxies_histograms.md b/pages/doc/proxies_histograms.md
index fae312707..de4c641df 100644
--- a/pages/doc/proxies_histograms.md
+++ b/pages/doc/proxies_histograms.md
@@ -265,4 +265,4 @@ The aggregation intervals do not overlap. If you are aggregating by the minute,
## Monitoring Histogram Points
-You can use `~histogram` metrics to monitor histogram ingestion. See the [Ingest Rate by Source](wavefront_monitoring.html#ingest-rate-by-source) section of the Operations for Applications Service and Proxy Data dashboard.
+You can use `~histogram` metrics to monitor histogram ingestion. See the [Ingest Rate by Source](wavefront_monitoring.html#ingest-rate-by-source) section of the Tanzu Observability Service and Proxy Data dashboard.
diff --git a/pages/doc/proxies_installing.md b/pages/doc/proxies_installing.md
index 6f6281304..75f5d46ad 100644
--- a/pages/doc/proxies_installing.md
+++ b/pages/doc/proxies_installing.md
@@ -29,7 +29,7 @@ In most cases, a Wavefront proxy must be running in your environment before metr
- Operating system and JRE - Wavefront proxy is a Java application and can run on operating systems supported by Java. Java 8, 9, 10 or 11 is required. See the requirements in the [Wavefront Proxy README file](https://github.com/wavefrontHQ/wavefront-proxy#requirements).
- Other - Maven
-{% include note.html content="The proxy uses disk space only for queue and buffering of metrics. The size of the buffer depends on the metrics size and the number of data points received and sent by the proxy. The individual proxy dashboards and the **Operations for Applications Service and Proxy Data** dashboard have several charts that allow you to examine proxy backlog size and related metrics. See [Monitoring Proxies](monitoring_proxies.html)." %}
+{% include note.html content="The proxy uses disk space only for queue and buffering of metrics. The size of the buffer depends on the metrics size and the number of data points received and sent by the proxy. The individual proxy dashboards and the **Tanzu Observability Service and Proxy Data** dashboard have several charts that allow you to examine proxy backlog size and related metrics. See [Monitoring Proxies](monitoring_proxies.html)." %}