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. ![histogram types](images/histogram_types.png) (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. [tsExpression](query_language_reference.html#query-expressions) -Ordinary histogram distribution that we'll convert to an Operations for Applications histogram. +Ordinary histogram distribution that we'll convert to a Tanzu Observability histogram. metrics|sources|sourceTags|pointTags|<pointTagKey> 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 ![GCP bucket data](images/gcp_bucket_data.png) -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. ![frequency histo](images/frequency_histo_p95.png) ## 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.