diff --git a/images/alert_firing.png b/images/alert_firing.png index 053ae7dc0..0d03efb86 100644 Binary files a/images/alert_firing.png and b/images/alert_firing.png differ diff --git a/images/alert_firing_severe.png b/images/alert_firing_severe.png index bd8abb087..47191fc1f 100644 Binary files a/images/alert_firing_severe.png and b/images/alert_firing_severe.png differ diff --git a/images/alert_tag_add.png b/images/alert_tag_add.png index 876d84ed1..fe605f360 100644 Binary files a/images/alert_tag_add.png and b/images/alert_tag_add.png differ diff --git a/images/alert_tag_path.png b/images/alert_tag_path.png index d417ad2c4..82c6be54e 100644 Binary files a/images/alert_tag_path.png and b/images/alert_tag_path.png differ diff --git a/images/alert_versions.png b/images/alert_versions.png index 714e81dcb..bf94eecda 100644 Binary files a/images/alert_versions.png and b/images/alert_versions.png differ diff --git a/images/alerts_filter.png b/images/alerts_filter.png index 17fa1de6a..534e8d6f6 100644 Binary files a/images/alerts_filter.png and b/images/alerts_filter.png differ diff --git a/images/delete_alert.png b/images/delete_alert.png index d791d27ee..718d21a4e 100644 Binary files a/images/delete_alert.png and b/images/delete_alert.png differ diff --git a/images/edit_alert.png b/images/edit_alert.png index c529c1248..fa9d6290c 100644 Binary files a/images/edit_alert.png and b/images/edit_alert.png differ diff --git a/images/select-deleted-alerts.png b/images/select-deleted-alerts.png index 3abb5d785..d5f11e57b 100644 Binary files a/images/select-deleted-alerts.png and b/images/select-deleted-alerts.png differ diff --git a/images/show_firings.png b/images/show_firings.png index 3bde5a1c2..5fad8af4e 100644 Binary files a/images/show_firings.png and b/images/show_firings.png differ diff --git a/pages/doc/alerts.md b/pages/doc/alerts.md index ce694f327..a64234423 100644 --- a/pages/doc/alerts.md +++ b/pages/doc/alerts.md @@ -207,13 +207,13 @@ For example, you could show alerts that are both FIRING and SEVERE. ### Step 3: Examine an Alert in Alerts Browser -For each alert, the Alerts Browser includes detailed information. For example, an alert that is firing looks like this: +You can expand each alert to view detailed information. For example, when you expand an alert that is firing, the detailed information looks like this: ![Annotated screenshot highlighting the UI elements which are described in the text below](images/alert_firing.png) Follow these steps for a tour: 1. Click the ellipsis icon to the left for a menu. -2. Click the chart icon next to the status for alert details. If the alert is firing, click to examine the alert in Alert Viewer. +2. Click the chart icon under the **State** column for alert details. If the alert is firing, click to examine the alert in Alert Viewer. 3. View the alert condition and points. 4. View details below the severity: - View the last affected series, including the affected sources and point tags. @@ -255,16 +255,13 @@ Alert version history shows: You can revert back to a past alert version or clone a past alert version.

. -alert history selected in menu +alert history selected in menu. - - - -### Step 5: Organize Related Alerts With Tags +### Step 5: Organize Related Alerts with Tags You can use alert tags to organize related alerts into categories. Alert tags are especially useful for setting up [maintenance windows](maintenance_windows_managing.html). You can: * [Search or filter](wavefront_searching.html) the list of alerts in the Alerts Browser to show only a category of alerts. @@ -272,21 +269,30 @@ You can use alert tags to organize related alerts into categories. Alert tags ar * [Reference a group of alert metrics](alerts_dependencies.html#referencing-alert-metrics) in a single expression. - - - - - - + + + + + +
-
-To add a new or existing alert tag at any time: -
    -
  • Set the Tags property when you create or edit the alert.
    • -
  • Click plus (+) at the bottom of the alert in the Alerts Browser.
    • -
  • Select one or more alerts in the Alerts Browser and click +Tag or -Tag
    • -
-

For example, you might assign tags like networkOps, underDevelopment, and eastCoast. All users can later search for one or more of these tags to find any other alerts that are in the same category or combination of categories.

-		Alerts Browser, + selected for single alert, Add Existing Tag and Create New Tag options
+
+ To add a new or existing alert tag at any time: +
    +
  • + Set the Tags property when you create or edit the alert. +
    • +
  • + In the Alerts Browser, expand to get the details view of an alert, and click plus (+) under Alert Tags. +
    • +
  • + Select one or more alerts in the Alerts Browser and click +Tag or -Tag +
    • +
+

For example, you might assign tags like networkOps, underDevelopment, and eastCoast. All users can later search for one or more of these tags to find any other alerts that are in the same category or combination of categories.

+ {% include note.html content="If you want to add a new tag in the revamped Alerts Browser, enter the name of the tag and click plus icon next to the new tag name. " %} + 		+ Alerts Browser, + selected for single alert, Add Existing Tag and Create New Tag options +
@@ -296,10 +302,10 @@ To add a new or existing alert tag at any time: ### Step 6: (Optional) Use Multi-Level Alert Tags If your environment has a nested set of categories, you can use alert tag paths. For example, suppose you have created a group of alerts that you use as demo examples, and: -* Within the demo group, some alerts monitor network activity, while others monitor request latency. -* Within each subgroup, some alerts monitor production applications, while others monitor development applications. +* Within the demo group, some alerts monitor network activity. +* Within each subgroup, some alerts monitor production applications. -To manage these alerts, you assign the tag paths `example.network.prod`, `example.network.dev`, `example.latency.prod`, and `example.latency.dev`. The Alerts Browser below shows the tag paths as a hierarchy under **Tag Paths** on the left. You can click **example** and then **network** to view all alerts that have a tag path that starts with `example.network`. +To manage these alerts, you assign the tag paths `example.network.prod` and `example.latency.prod`. The Alerts Browser below shows the tag paths as a hierarchy under **Tag Paths** on the left. You can click **example** and then **network** to view all alerts that have a tag path that starts with `example.network`. ![Alert tag path](images/alert_tag_path.png) diff --git a/pages/doc/alerts_delayed_data.md b/pages/doc/alerts_delayed_data.md index 9fef9c3fa..3fa43ba7a 100644 --- a/pages/doc/alerts_delayed_data.md +++ b/pages/doc/alerts_delayed_data.md @@ -86,7 +86,6 @@ You can use either of the following techniques (or both): * Use the `lag()` function in the alert condition. * Increase the length of the alert check time window. - ### Adjust the Alert Condition You can use the [`lag()`](ts_lag.html) function in an alert condition to shift the alert check time window back in time. Pick a time window that you think might be old enough to contain backfilled values. Without `lag()`, the alert check time window ends immediately before alert checking occurs, which is too soon for backfilling to occur. diff --git a/pages/doc/alerts_states_lifecycle.md b/pages/doc/alerts_states_lifecycle.md index 148292551..fb891e014 100644 --- a/pages/doc/alerts_states_lifecycle.md +++ b/pages/doc/alerts_states_lifecycle.md @@ -175,17 +175,15 @@ Alert checks are based on data that is summarized every minute. Consequently, i ### Viewing Firing Alerts -When you hover over **Alerting** on the toolbar, you can see how many alerts are firing. - - - +Click FIRING to filter the list of alerts. +
+
The filter bar at the left of the Alerts Browser shows the number of firing alerts by severity. For multi-threshold alerts, we list each alert only for the highest severity even if lower severity conditions are also met.

-Click FIRING to filter the list of alerts		Alerts in different states at the top, below the filter options with FIRING selected.Alerts in different states at the top, below the filter options with FIRING selected.
diff --git a/pages/doc/service_status_page.md b/pages/doc/service_status_page.md index bb2a98410..e1e846c0b 100644 --- a/pages/doc/service_status_page.md +++ b/pages/doc/service_status_page.md @@ -6,7 +6,7 @@ permalink: service_status_page.html summary: Monitor for incidents and maintenance on your service. --- -We publish the service operational status and maintenance schedules to the [VMware Cloud Services status page](https://status.broadcom.com/services/vmware-cloud-services). For confidentiality reasons, the individual customer clusters are listed with alias names. +We publish the Tanzu Observability (formerly known as VMware Aria Operations for Applications) service operational status and maintenance schedules to the [VMware Cloud Services page](https://status.broadcom.com/services/vmware-cloud-services) on the Broadcom Service Status portal. For confidentiality reasons, the individual customer clusters are listed with alias names. ## Find Your Cluster Alias Name @@ -14,7 +14,7 @@ We publish the service operational status and maintenance schedules to the [VMwa -To see the status of your Tanzu Observability (formerly known as VMware Aria Operations for Applications) service, you must get the alias name of your cluster. +To see the status of your Tanzu Observability service instance, you must get the alias name of your cluster.
  1. Log in to your service instance and click the gear icon on the toolbar.
  2. Under VMware Status Page, see your cluster alias name.
    3. diff --git a/pages/doc/wavefront_release_notes.md b/pages/doc/wavefront_release_notes.md index 35c91d632..fa5d91965 100644 --- a/pages/doc/wavefront_release_notes.md +++ b/pages/doc/wavefront_release_notes.md @@ -34,7 +34,14 @@ 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-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)." %} +{% 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)." %} + +## 2024-09.x Release Notes + +**Alerts Browser Improvements**: We improved the user experience of the **Alerts Browser**. To navigate to this page, select **Alerting > All Alerts**. + + ![An annotated screenshot of the Alerts Browser.](images/alert_firing.png) + ## 2024-07.x Release Notes @@ -57,7 +64,6 @@ In October, 2023, we start to incrementally [**onboard**](csp_migration.html) al - `~counter.global.namespace.*` - ## 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: