From a7095238d867676c323349cb6554d46113dd30cd Mon Sep 17 00:00:00 2001 From: shavidissa Date: Mon, 12 Feb 2024 11:27:09 -0800 Subject: [PATCH 01/11] minor change to start the build --- pages/doc/metric_types.md | 1 - 1 file changed, 1 deletion(-) diff --git a/pages/doc/metric_types.md b/pages/doc/metric_types.md index 43821cbd6..defc5596f 100644 --- a/pages/doc/metric_types.md +++ b/pages/doc/metric_types.md @@ -86,7 +86,6 @@ To have the Operations for Applications service treat a metric as a delta counte [Using Delta Counters](delta_counters.html#using-delta-counters) gives details and best practices. - ## 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. From 5a414eb6e883a81a6bfc6589d881dbb6e071a9f8 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Tue, 19 Mar 2024 18:17:52 +0200 Subject: [PATCH 02/11] Internal metrics are ephemeral --- pages/doc/metric_types.md | 3 ++- pages/doc/metrics_managing.md | 4 ++-- pages/doc/wavefront_internal_metrics.md | 2 ++ pages/doc/wavefront_release_notes.md | 5 +++++ 4 files changed, 11 insertions(+), 3 deletions(-) diff --git a/pages/doc/metric_types.md b/pages/doc/metric_types.md index fe1e34cf5..d6edcf040 100644 --- a/pages/doc/metric_types.md +++ b/pages/doc/metric_types.md @@ -71,11 +71,12 @@ With the 2024-05 release, we introduce **ephemeral** metrics, which have a short Persistent -18 months of data retention. By default, all metrics and counters are persistent. Metrics are convertible to ephemeral. +18 months of data retention. By default, all ingested metrics are persistent but are convertible to ephemeral. Counters are persistent and not convertible. Ephemeral 28 days of data retention. Suitable for metrics that are relevant for a short time and that have high cardinality, such as the Kubernetes metrics (kubernetes.). +

By default, only the internal metrics are ephemeral and they are not convertible to persistent.

Converting metrics from persistent to ephemeral improves the query performance and reduces the cardinality.

diff --git a/pages/doc/metrics_managing.md b/pages/doc/metrics_managing.md index 97463ea5e..38927ad6f 100644 --- a/pages/doc/metrics_managing.md +++ b/pages/doc/metrics_managing.md @@ -106,7 +106,7 @@ On the Metrics Browser, you can: * Filter by name or source. * Hide and redisplay individual metrics or metrics namespaces to unclutter your page. * View the metric type in terms of retention period - persistent or ephemeral. -* Convert persistent metrics to ephemeral and the reverse. +* Convert persistent metrics to ephemeral and the reverse. Internal metrics are ephemeral and not convertible. * Create a chart or dashboard for an individual metric or for the current set of metrics. * View the sources and point tags for an individual metric. @@ -164,7 +164,7 @@ With the 2024-05 release, we introduce **ephemeral** metrics, which have short [ Converting persistent metrics to ephemeral can significantly improve the [query performance](query_language_performance.html) and reduce the [cardinality](cardinality.html). -{% include note.html content="To change the retention period of a metric or metrics namespace, you must be a Super Admin user with [enabled Super Admin mode](users_account_managing.html#enable-or-disable-super-admin-mode)." %} +{% include note.html content="To change the retention period of a metric or metrics namespace, you must be a Super Admin user with [enabled Super Admin mode](users_account_managing.html#enable-or-disable-super-admin-mode). Internal metrics are ephemeral and not convertible to persistent." %} {% include important.html content="Converting a persistent metric to ephemeral **permanently deletes** the data points of this metric that are older than 28 days." %} diff --git a/pages/doc/wavefront_internal_metrics.md b/pages/doc/wavefront_internal_metrics.md index 96089a780..a1c8ea36c 100644 --- a/pages/doc/wavefront_internal_metrics.md +++ b/pages/doc/wavefront_internal_metrics.md @@ -12,6 +12,8 @@ You can: * Clone and modify one of the Operations for Applications Usage integration dashboards. * Create your own dashboard, query these metrics in charts, and create alerts for some of these metrics. +{% include note.html content="The internal metrics are [**ephemeral**](metric_types.html#metric-types-per-retention-period) and not convertible to persistent." %} + ## Internal Metrics Overview We collect the following sets of metrics. diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md index aa3ccd34c..4da5fa17c 100644 --- a/pages/doc/wavefront_release_notes.md +++ b/pages/doc/wavefront_release_notes.md @@ -36,6 +36,11 @@ In October, 2023, we start to incrementally [**onboard**](csp_migration.html) al {% include warning.html content="The Operations for Applications authentication and authorization will be **deprecated** in the future. Therefore, after onboarding to VMware Cloud services, **replace** [your service accounts with server to server apps](csp_migration.html#how-to-replace-a-service-account-with-a-server-to-server-app) and [your Operations for Applications API tokens with VMware Cloud Services access tokens](csp_migration.html#how-to-replace-an-operations-for-applications-api-token-with-a-vmware-cloud-services-access-token), including [the Operations for Application API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy)." %} +## 2024-07.x Release Notes + +* **Ephemeral Internal Metrics**: All [internal metrics](wavefront-internal-metrics.html) are now [ephemeral](metric_types.html#metric-types-per-retention-period), so that they are retained for 28 days. Internal metrics are not convertible to persistent. + + ## 2024-05.x Release Notes * **New Ephemeral Metric Type**: With this release, we introduce ephemeral metrics, which have a short retention period. Ephemeral metrics are retained for 28 days, whereas persistent (default) metrics are retained for 18 months. For details, see [Metric Types per Retention Period](metric_types.html#metric-types-per-retention-period). From 98e4423b90aa21105b3d0466c350274bed99d1d4 Mon Sep 17 00:00:00 2001 From: shavidissa Date: Fri, 22 Mar 2024 10:15:20 -0700 Subject: [PATCH 03/11] update the doc --- pages/doc/wavefront_spring_boot3_tutorial.md | 118 ++++++++++--------- 1 file changed, 60 insertions(+), 58 deletions(-) diff --git a/pages/doc/wavefront_spring_boot3_tutorial.md b/pages/doc/wavefront_spring_boot3_tutorial.md index e43bd8529..ec3ca2103 100644 --- a/pages/doc/wavefront_spring_boot3_tutorial.md +++ b/pages/doc/wavefront_spring_boot3_tutorial.md @@ -30,65 +30,67 @@ In this tutorial, you use Wavefront for Spring Boot that uses Spring Boot 3 with ## Configure the Petclinic Application -1. Import the Wavefront for Spring Boot Bill of Materials (BOM) to your project. Add the following code to the `pom.xml` file (replace VERSION with the current version). - {{site.data.alerts.tip}} -

Make sure that the Wavefront for Spring Boot dependency is compatible with the Spring Boot release version. See System Requirements to get the correct dependency version. -
- For example, if you are using Spring Boot release version 3.0.1, the VERSION must be 3.0.1. -

- {{site.data.alerts.end}} - ```xml - - +1. Add the following configurations to the `pom.xml` file in the sample petclinic application: + + 1. Import the Wavefront for Spring Boot Bill of Materials (BOM) to your project. Replace VERSION with the current version. + {{site.data.alerts.tip}} +

Make sure that the Wavefront for Spring Boot dependency is compatible with the Spring Boot release version. See System Requirements to get the correct dependency version. +
+ For example, if you are using Spring Boot release version 3.0.1, the VERSION must be 3.0.1. +

+ {{site.data.alerts.end}} + ```xml + + + + com.wavefront + wavefront-spring-boot-bom + VERSION + pom + import + + + + ``` + + 1. Add the `wavefront-spring-boot-starter` and `micrometer-registry-wavefront` dependencies. + ```xml com.wavefront - wavefront-spring-boot-bom - VERSION - pom - import + wavefront-spring-boot-starter - - - ``` - -1. Open the sample petclinic application using an IDE and add the `wavefront-spring-boot-starter` and `micrometer-registry-wavefront` to the `pom.xml` file's ``. - ```xml - - com.wavefront - wavefront-spring-boot-starter - - - io.micrometer - micrometer-registry-wavefront - runtime - - ``` + + io.micrometer + micrometer-registry-wavefront + runtime + + ``` -1. Add the following dependencies to your pom.xml to send trace data to Wavefront. - ```xml - - io.micrometer - micrometer-tracing-bridge-brave - - - io.micrometer - micrometer-tracing-reporter-wavefront - runtime - - ``` + 1. Add the `micrometer-tracing-bridge-brave` and `micrometer-tracing-reporter-wavefront` dependencies to send trace data to our service. + ```xml + + io.micrometer + micrometer-tracing-bridge-brave + + + io.micrometer + micrometer-tracing-reporter-wavefront + runtime + + ``` -1. Add the `Datasource Micrometer` dependency to intercept and log JDBC SQL queries. You can intercept most Connection, Statement, and ResultSet methods invocations using the Datasource Micrometer dependency. - {{site.data.alerts.tip}} -

Check the Datasource Micrometer releases and enter the latest version in place of VERSION.

- {{site.data.alerts.end}} - ```xml - - net.ttddyy.observation - datasource-micrometer-spring-boot - VERSION - runtime - - ``` + 1. Add the `datasource-micrometer-spring-boot` dependency to intercept and log JDBC SQL queries. You can intercept most Connection, Statement, and ResultSet methods invocations using the Datasource Micrometer dependency. + {{site.data.alerts.tip}} +

Check the Datasource Micrometer releases and enter the latest version in place of VERSION.

+ {{site.data.alerts.end}} + ```xml + + net.ttddyy.observation + datasource-micrometer-spring-boot + VERSION + runtime + + ``` 1. Add the following configurations to the `application.properties` file so that your: * Application is named `spring-demo`. @@ -102,17 +104,17 @@ In this tutorial, you use Wavefront for Spring Boot that uses Spring Boot 3 with ## Send Data to Our Service -1. Restart the application and navigate to [http://localhost:8080](http://localhost:8080/). +1. Restart the application. -1. Generate telemetry data from the petclinic user interface. +1. Navigate to [http://localhost:8080](http://localhost:8080/) and generate telemetry data from the petclinic user interface. For example: 1. Add an Owner and a Pet via the User Interface. 1. Click **VETERINARIANS** to list vets in the database. 1. Click **ERROR** to trigger errors. -1. Click the one-time use link to access the Wavefront for Spring Boot Service Dashboard and view data. +1. Copy the one-time use link that was printed on your terminal when you restarted your application to access the Wavefront for Spring Boot Service Dashboard and view data. {% include tip.html content = "Make sure to save the one-time use link so you can access the same dashboard each time you restart your application."%} - Example: + Example output on your terminal: ``` To share this account, make sure the following is added to your configuration: From 67cb2dd9f657cbb856f250b0b6f695f776125a6e Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Wed, 27 Mar 2024 15:12:16 +0200 Subject: [PATCH 04/11] adding a link to the new workbook TAS OTel for Spring Boot Application --- pages/doc/integrations_custom_app_metrics_howto.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pages/doc/integrations_custom_app_metrics_howto.md b/pages/doc/integrations_custom_app_metrics_howto.md index 97a58d16a..d253504cc 100644 --- a/pages/doc/integrations_custom_app_metrics_howto.md +++ b/pages/doc/integrations_custom_app_metrics_howto.md @@ -55,6 +55,8 @@ Spring Boot is commonly used to build apps running on TAS. Spring Boot Actuator supports both push and pull models, with the only difference typically being configuration changes. In that case, it becomes relatively easy to switch from push to pull or vice-versa. +See also the VMware Tanzu solutions workbook [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). + ### Wavefront Proxy Load All additional custom app metrics increase the load on the Wavefront proxy. You might have to increase the count of Wavefront proxies and to deploy an IaaS load balancer to balance traffic across proxy instances. From 30a9754504db1034aa0056e3d919291997b83c36 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Wed, 27 Mar 2024 16:39:41 +0200 Subject: [PATCH 05/11] adding a link to the new workbook TAS OTel for Spring Boot Application --- pages/doc/wavefront_spring_boot3_tutorial.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pages/doc/wavefront_spring_boot3_tutorial.md b/pages/doc/wavefront_spring_boot3_tutorial.md index ec3ca2103..644b885e9 100644 --- a/pages/doc/wavefront_spring_boot3_tutorial.md +++ b/pages/doc/wavefront_spring_boot3_tutorial.md @@ -10,6 +10,8 @@ In this tutorial, you use Wavefront for Spring Boot that uses Spring Boot 3 with {% include tip.html content="Want to start your project from scratch using [https://start.spring.io/](https://start.spring.io/)? Follow the [Observability with Spring](https://spring.io/guides/gs/tanzu-observability/) tutorial." %} +See also the VMware Tanzu solutions workbook [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). + ## Prerequisites * Spring Boot 3.0.0 or later. From 2abefa18aa186acd168f623d4747b185b3632957 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Thu, 28 Mar 2024 19:23:54 +0200 Subject: [PATCH 06/11] peer review --- pages/doc/wavefront_spring_boot3_tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/doc/wavefront_spring_boot3_tutorial.md b/pages/doc/wavefront_spring_boot3_tutorial.md index 644b885e9..b037e3640 100644 --- a/pages/doc/wavefront_spring_boot3_tutorial.md +++ b/pages/doc/wavefront_spring_boot3_tutorial.md @@ -10,7 +10,7 @@ In this tutorial, you use Wavefront for Spring Boot that uses Spring Boot 3 with {% include tip.html content="Want to start your project from scratch using [https://start.spring.io/](https://start.spring.io/)? Follow the [Observability with Spring](https://spring.io/guides/gs/tanzu-observability/) tutorial." %} -See also the VMware Tanzu solutions workbook [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). +If you are also using the Tanzu Application Service (TAS), see the VMware Tanzu solutions workbook [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). ## Prerequisites From 6751addb659312614297671f4a60e9603ffa484e Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Thu, 28 Mar 2024 21:33:22 +0200 Subject: [PATCH 07/11] peer review --- pages/doc/integrations_custom_app_metrics_howto.md | 2 +- pages/doc/wavefront_spring_boot3_tutorial.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/doc/integrations_custom_app_metrics_howto.md b/pages/doc/integrations_custom_app_metrics_howto.md index d253504cc..d4ac1e583 100644 --- a/pages/doc/integrations_custom_app_metrics_howto.md +++ b/pages/doc/integrations_custom_app_metrics_howto.md @@ -55,7 +55,7 @@ Spring Boot is commonly used to build apps running on TAS. Spring Boot Actuator supports both push and pull models, with the only difference typically being configuration changes. In that case, it becomes relatively easy to switch from push to pull or vice-versa. -See also the VMware Tanzu solutions workbook [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). +To use a VMware Tanzu solutions workbook, see [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). ### Wavefront Proxy Load diff --git a/pages/doc/wavefront_spring_boot3_tutorial.md b/pages/doc/wavefront_spring_boot3_tutorial.md index b037e3640..85215a2f5 100644 --- a/pages/doc/wavefront_spring_boot3_tutorial.md +++ b/pages/doc/wavefront_spring_boot3_tutorial.md @@ -10,7 +10,7 @@ In this tutorial, you use Wavefront for Spring Boot that uses Spring Boot 3 with {% include tip.html content="Want to start your project from scratch using [https://start.spring.io/](https://start.spring.io/)? Follow the [Observability with Spring](https://spring.io/guides/gs/tanzu-observability/) tutorial." %} -If you are also using the Tanzu Application Service (TAS), see the VMware Tanzu solutions workbook [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). +If you are also using the Tanzu Application Service (TAS), see the VMware Tanzu solutions workbook on [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). ## Prerequisites From 51d9126d1f33f03350c97a5a43bbcd09cd395650 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Mon, 1 Apr 2024 15:02:53 +0300 Subject: [PATCH 08/11] moving the links to the workbook --- pages/doc/integrations_custom_app_metrics_howto.md | 4 +--- pages/doc/wavefront_spring_boot3.md | 2 ++ pages/doc/wavefront_spring_boot3_tutorial.md | 2 -- 3 files changed, 3 insertions(+), 5 deletions(-) diff --git a/pages/doc/integrations_custom_app_metrics_howto.md b/pages/doc/integrations_custom_app_metrics_howto.md index d4ac1e583..d2ef8c89e 100644 --- a/pages/doc/integrations_custom_app_metrics_howto.md +++ b/pages/doc/integrations_custom_app_metrics_howto.md @@ -51,12 +51,10 @@ The supported way to do this using the Tanzu Observability by Wavefront Nozzle i ### Spring Boot -Spring Boot is commonly used to build apps running on TAS. +Spring Boot is commonly used to build apps running on TAS. To use a VMware Tanzu solutions workbook, see [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). Spring Boot Actuator supports both push and pull models, with the only difference typically being configuration changes. In that case, it becomes relatively easy to switch from push to pull or vice-versa. -To use a VMware Tanzu solutions workbook, see [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). - ### Wavefront Proxy Load All additional custom app metrics increase the load on the Wavefront proxy. You might have to increase the count of Wavefront proxies and to deploy an IaaS load balancer to balance traffic across proxy instances. diff --git a/pages/doc/wavefront_spring_boot3.md b/pages/doc/wavefront_spring_boot3.md index 0a1b9bce5..b99db5345 100644 --- a/pages/doc/wavefront_spring_boot3.md +++ b/pages/doc/wavefront_spring_boot3.md @@ -27,6 +27,8 @@ You can send data from your Spring Boot applications into our service using the - **Customer or Free Trial User**: Customers or free trial users can modify the default Wavefront Spring Boot Starter to send data to their cluster. You can sign up for a [free 30-day trial here](https://tanzu.vmware.com/observability). * **Wavefront Spring Boot Integration**: Customers and free trial users can access the Wavefront Spring Boot integration directly from their clusters. +If your Spring Boot applications are running on Tanzu Application Service (TAS), see the VMware Tanzu solutions workbook on [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). + ## Dashboards After you complete the setup, you can examine the data in our dashboards. diff --git a/pages/doc/wavefront_spring_boot3_tutorial.md b/pages/doc/wavefront_spring_boot3_tutorial.md index 85215a2f5..ec3ca2103 100644 --- a/pages/doc/wavefront_spring_boot3_tutorial.md +++ b/pages/doc/wavefront_spring_boot3_tutorial.md @@ -10,8 +10,6 @@ In this tutorial, you use Wavefront for Spring Boot that uses Spring Boot 3 with {% include tip.html content="Want to start your project from scratch using [https://start.spring.io/](https://start.spring.io/)? Follow the [Observability with Spring](https://spring.io/guides/gs/tanzu-observability/) tutorial." %} -If you are also using the Tanzu Application Service (TAS), see the VMware Tanzu solutions workbook on [Instrumenting TAS OpenTelemetry for Spring Boot Application](https://docs.vmware.com/en/VMware-Tanzu-Reference-Architecture/services/tanzu-solutions-workbooks/solution-workbooks-TAS-OpenTelemetry-SpringBoot-TO.html). - ## Prerequisites * Spring Boot 3.0.0 or later. From 0871e985cdc34aad94c1ac312722deac5643255d Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Wed, 3 Apr 2024 23:03:21 +0300 Subject: [PATCH 09/11] Not all internal metrics are ephemeral --- pages/doc/metric_types.md | 2 +- pages/doc/metrics_managing.md | 4 ++-- pages/doc/wavefront_internal_metrics.md | 5 ++++- pages/doc/wavefront_release_notes.md | 5 ++++- 4 files changed, 11 insertions(+), 5 deletions(-) diff --git a/pages/doc/metric_types.md b/pages/doc/metric_types.md index 3b6e9a880..90f04867e 100644 --- a/pages/doc/metric_types.md +++ b/pages/doc/metric_types.md @@ -76,7 +76,7 @@ With the 2024-05 release, we introduce **ephemeral** metrics, which have a short Ephemeral 28 days of data retention. Suitable for metrics that are relevant for a short time and that have high cardinality, such as the Kubernetes metrics (kubernetes.). -

By default, only the internal metrics are ephemeral and they are not convertible to persistent.

+

By default, most of the internal metrics are ephemeral and they are not convertible to persistent.

Converting metrics from persistent to ephemeral improves the query performance and reduces the cardinality.

diff --git a/pages/doc/metrics_managing.md b/pages/doc/metrics_managing.md index 38927ad6f..761c7d634 100644 --- a/pages/doc/metrics_managing.md +++ b/pages/doc/metrics_managing.md @@ -106,7 +106,7 @@ On the Metrics Browser, you can: * Filter by name or source. * Hide and redisplay individual metrics or metrics namespaces to unclutter your page. * View the metric type in terms of retention period - persistent or ephemeral. -* Convert persistent metrics to ephemeral and the reverse. Internal metrics are ephemeral and not convertible. +* Convert persistent metrics to ephemeral and the reverse. Most of the internal metrics are ephemeral and not convertible. * Create a chart or dashboard for an individual metric or for the current set of metrics. * View the sources and point tags for an individual metric. @@ -164,7 +164,7 @@ With the 2024-05 release, we introduce **ephemeral** metrics, which have short [ Converting persistent metrics to ephemeral can significantly improve the [query performance](query_language_performance.html) and reduce the [cardinality](cardinality.html). -{% include note.html content="To change the retention period of a metric or metrics namespace, you must be a Super Admin user with [enabled Super Admin mode](users_account_managing.html#enable-or-disable-super-admin-mode). Internal metrics are ephemeral and not convertible to persistent." %} +{% include note.html content="To change the retention period of a metric or metrics namespace, you must be a Super Admin user with [enabled Super Admin mode](users_account_managing.html#enable-or-disable-super-admin-mode). Most of the internal metrics are ephemeral and not convertible to persistent." %} {% include important.html content="Converting a persistent metric to ephemeral **permanently deletes** the data points of this metric that are older than 28 days." %} diff --git a/pages/doc/wavefront_internal_metrics.md b/pages/doc/wavefront_internal_metrics.md index a1c8ea36c..de43a50ab 100644 --- a/pages/doc/wavefront_internal_metrics.md +++ b/pages/doc/wavefront_internal_metrics.md @@ -12,7 +12,10 @@ You can: * Clone and modify one of the Operations for Applications Usage integration dashboards. * Create your own dashboard, query these metrics in charts, and create alerts for some of these metrics. -{% include note.html content="The internal metrics are [**ephemeral**](metric_types.html#metric-types-per-retention-period) and not convertible to persistent." %} +Most of the internal metrics are [**ephemeral**](metric_types.html#metric-types-per-retention-period) and not convertible to persistent. Exceptions are the following internal metrics, which are persistent: +``` +~collector.*points.reported, ~externalservices.*.points, ~derived-metrics.points.reported, ~collector.*histograms.reported, ~derived-histograms.histograms.reported, ~collector.*spans.reported, ~query.metrics_scanned, ~proxy.points.*.received, ~proxy.histograms.*.received, ~proxy.spans.*.received, ~proxy.spanLogs.*.received, ~proxy.build.version, ~metric.global.namespace.*, ~histogram.global.namespace.*, ~counter.global.namespace.* +``` ## Internal Metrics Overview diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md index 4da5fa17c..8b2abd148 100644 --- a/pages/doc/wavefront_release_notes.md +++ b/pages/doc/wavefront_release_notes.md @@ -38,7 +38,10 @@ In October, 2023, we start to incrementally [**onboard**](csp_migration.html) al ## 2024-07.x Release Notes -* **Ephemeral Internal Metrics**: All [internal metrics](wavefront-internal-metrics.html) are now [ephemeral](metric_types.html#metric-types-per-retention-period), so that they are retained for 28 days. Internal metrics are not convertible to persistent. +**Ephemeral Internal Metrics**: Most of the [internal metrics](wavefront-internal-metrics.html) are now [ephemeral](metric_types.html#metric-types-per-retention-period) and not convertible to persistent. Exceptions are the following internal metrics, which remain persistent: +``` +~collector.*points.reported, ~externalservices.*.points, ~derived-metrics.points.reported, ~collector.*histograms.reported, ~derived-histograms.histograms.reported, ~collector.*spans.reported, ~query.metrics_scanned, ~proxy.points.*.received, ~proxy.histograms.*.received, ~proxy.spans.*.received, ~proxy.spanLogs.*.received, ~proxy.build.version, ~metric.global.namespace.*, ~histogram.global.namespace.*, ~counter.global.namespace.* +``` ## 2024-05.x Release Notes From 7886dbf037ccf3da3fbdf8a54d0ee09c224cad04 Mon Sep 17 00:00:00 2001 From: mmihaylovam <85890011+mmihaylovam@users.noreply.github.com> Date: Thu, 4 Apr 2024 08:12:25 +0300 Subject: [PATCH 10/11] unordered list of the persistent internal metrics --- pages/doc/wavefront_internal_metrics.md | 18 +++++++++++++++--- pages/doc/wavefront_release_notes.md | 20 +++++++++++++++++--- 2 files changed, 32 insertions(+), 6 deletions(-) diff --git a/pages/doc/wavefront_internal_metrics.md b/pages/doc/wavefront_internal_metrics.md index de43a50ab..5c2042bd4 100644 --- a/pages/doc/wavefront_internal_metrics.md +++ b/pages/doc/wavefront_internal_metrics.md @@ -13,9 +13,21 @@ You can: * Create your own dashboard, query these metrics in charts, and create alerts for some of these metrics. Most of the internal metrics are [**ephemeral**](metric_types.html#metric-types-per-retention-period) and not convertible to persistent. Exceptions are the following internal metrics, which are persistent: -``` -~collector.*points.reported, ~externalservices.*.points, ~derived-metrics.points.reported, ~collector.*histograms.reported, ~derived-histograms.histograms.reported, ~collector.*spans.reported, ~query.metrics_scanned, ~proxy.points.*.received, ~proxy.histograms.*.received, ~proxy.spans.*.received, ~proxy.spanLogs.*.received, ~proxy.build.version, ~metric.global.namespace.*, ~histogram.global.namespace.*, ~counter.global.namespace.* -``` +- `~collector.*points.reported` +- `~externalservices.*.points` +- `~derived-metrics.points.reported` +- `~collector.*histograms.reported` +- `~derived-histograms.histograms.reported` +- `~collector.*spans.reported` +- `~query.metrics_scanned` +- `~proxy.points.*.received` +- `~proxy.histograms.*.received` +- `~proxy.spans.*.received` +- `~proxy.spanLogs.*.received` +- `~proxy.build.version` +- `~metric.global.namespace.*` +- `~histogram.global.namespace.*` +- `~counter.global.namespace.*` ## Internal Metrics Overview diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md index 8b2abd148..92d18dbbc 100644 --- a/pages/doc/wavefront_release_notes.md +++ b/pages/doc/wavefront_release_notes.md @@ -39,9 +39,23 @@ In October, 2023, we start to incrementally [**onboard**](csp_migration.html) al ## 2024-07.x Release Notes **Ephemeral Internal Metrics**: Most of the [internal metrics](wavefront-internal-metrics.html) are now [ephemeral](metric_types.html#metric-types-per-retention-period) and not convertible to persistent. Exceptions are the following internal metrics, which remain persistent: -``` -~collector.*points.reported, ~externalservices.*.points, ~derived-metrics.points.reported, ~collector.*histograms.reported, ~derived-histograms.histograms.reported, ~collector.*spans.reported, ~query.metrics_scanned, ~proxy.points.*.received, ~proxy.histograms.*.received, ~proxy.spans.*.received, ~proxy.spanLogs.*.received, ~proxy.build.version, ~metric.global.namespace.*, ~histogram.global.namespace.*, ~counter.global.namespace.* -``` + +- `~collector.*points.reported` +- `~externalservices.*.points` +- `~derived-metrics.points.reported` +- `~collector.*histograms.reported` +- `~derived-histograms.histograms.reported` +- `~collector.*spans.reported` +- `~query.metrics_scanned` +- `~proxy.points.*.received` +- `~proxy.histograms.*.received` +- `~proxy.spans.*.received` +- `~proxy.spanLogs.*.received` +- `~proxy.build.version` +- `~metric.global.namespace.*` +- `~histogram.global.namespace.*` +- `~counter.global.namespace.*` + ## 2024-05.x Release Notes From 1eb7633b7ad759b9a6ce6d4c8e14a645783bc8b4 Mon Sep 17 00:00:00 2001 From: shavidissa Date: Thu, 4 Apr 2024 15:21:29 -0700 Subject: [PATCH 11/11] Comment out the data retention section from the docs --- pages/doc/metric_types.md | 6 +++--- pages/doc/metrics_managing.md | 2 +- pages/doc/missing_data_troubleshooting.md | 6 ++++++ pages/doc/terms_of_service.md | 11 ++++++++--- pages/doc/wavefront_pricing.md | 4 +++- pages/doc/wavefront_spring_boot_faq.md | 2 +- 6 files changed, 22 insertions(+), 9 deletions(-) diff --git a/pages/doc/metric_types.md b/pages/doc/metric_types.md index 90f04867e..de50cd907 100644 --- a/pages/doc/metric_types.md +++ b/pages/doc/metric_types.md @@ -16,9 +16,7 @@ summary: Learn about gauges, counters, delta counters, histograms, and spans. {% include tip.html content="Wavefront co-founder Clement Pang wrote [a Medium article](https://medium.com/@clementpang/thoughts-from-the-front-line-why-wavefront-3d807e2106f) that explains different metric types and why they are so powerful." %} -## Summary of Metric Types - -### Metric Types per Data Type +## Metric Types per Data Type The following table gives an overview of metric types. We introduce each type in more detail below. @@ -60,6 +58,7 @@ The following table gives an overview of metric types. We introduce each type in + ## Gauges diff --git a/pages/doc/metrics_managing.md b/pages/doc/metrics_managing.md index 761c7d634..f1642ab20 100644 --- a/pages/doc/metrics_managing.md +++ b/pages/doc/metrics_managing.md @@ -160,7 +160,7 @@ The selected metrics and metric prefixes appear again as long as they are not ob ### Change the Retention Period of Metrics -With the 2024-05 release, we introduce **ephemeral** metrics, which have short [retention period](terms_of_service.html#data-retention). By default, all ingested metrics are persistent but are convertible to ephemeral. +With the 2024-05 release, we introduce **ephemeral** metrics, which have short retention period. By default, all ingested metrics are persistent but are convertible to ephemeral. Converting persistent metrics to ephemeral can significantly improve the [query performance](query_language_performance.html) and reduce the [cardinality](cardinality.html). diff --git a/pages/doc/missing_data_troubleshooting.md b/pages/doc/missing_data_troubleshooting.md index eb6f277ea..c72ee3ff6 100644 --- a/pages/doc/missing_data_troubleshooting.md +++ b/pages/doc/missing_data_troubleshooting.md @@ -7,8 +7,14 @@ 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. 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. + ## Terms of Service Your Terms of Service are different depending on when you became a customer. + If you became a customer on or after August 17, 2017: diff --git a/pages/doc/wavefront_pricing.md b/pages/doc/wavefront_pricing.md index 4509b1b62..274f3dccf 100644 --- a/pages/doc/wavefront_pricing.md +++ b/pages/doc/wavefront_pricing.md @@ -26,7 +26,7 @@ For spans, the pricing structure is as follows: ![Metrics 1pps and Histograms 7pps are the basis, distributed tracing is 22 PPS if intelligent sampling is turned off](images/pricing_model_1.png) - + + ## Learn More * [Improve PPS and Prevent Overage](wavefront_usage_info.html) diff --git a/pages/doc/wavefront_spring_boot_faq.md b/pages/doc/wavefront_spring_boot_faq.md index c3dbeb0a5..7cbba406a 100644 --- a/pages/doc/wavefront_spring_boot_faq.md +++ b/pages/doc/wavefront_spring_boot_faq.md @@ -36,7 +36,7 @@ Follow these steps: While this is subject to changes at any time, we currently retain 5 days of data and offer no SLA on our free cluster. Freemium accounts that are are inactive for 3 days are automatically deleted. -Production clusters currently offer 18 months of full-resolution (no downsampling) data retention for persistent metrics, 28 days for ephemeral metrics, 6 months for histograms, and 7 days for spans. We also have a 99.95% uptime guarantee, as well as High Availability (HA) and Disaster Recovery (DR) options. + ## Why Do I Not See a Link to Access the Free Service on Start-Up?