What has changed? What are some tips and tricks?

Wavefront users have asked for a more streamlined alert creation experience, and we’re rolling it out to all users.

  • Going forward, all alerts will appear in the new alert GUI.
  • Under the covers, alerts work the same. But we’re including this FAQ to help current alert users.

What Are the Main Improvements?

The team has talked to customers and we’ve addressed a significant number of requests. We now have a streamlined design and better notifications.

Create and Edit Alerts More Easily

Straightforward stepper for Create Alert and Edit Alert flows.
  1. Chart shows alert metrics and thresholds. Format the chart for insight into your data.
  2. Multi-query option supports using query results as variables in the condition query.
  3. Simple Start Testing and Stop Testing button.
create alert

Help Alert Recipients

If you have information that helps alert recipients find and resolve the causes for the alert, specify them in the Contents section:

  • Runbook: A URL or a wiki page, or another document that helps the alert recipient resolve the alert.
  • Triage Dashboard(s): Start typing to select from dashboards on your Wavefront instance that have useful information and pass in information. See How Can I Pass a Value to a Triage Dashboard
  • Additional Information: Any other information that is useful to the alert recipient. This field supports Markdown. Click Preview to preview the Markdown output.

Preview Notifications

You can now preview alert notifications directly from the Create Alert and Edit Alert workflow.

FAQs for the New Alert Experience

Can I pick the alert GUI version?

A: No. All alerts are updated to the new alert GUI.

Do I have to change my API requests?

A: No. The existing API still works. To take advantage of the new multi-query request format, use the useMultiQuery option in the POST of /api-docs/ui/#!/Alert/createAlert

FAQs for Alert Migration

How Can I Set a Display Expression?

A: For alerts that return 0 or 1, it makes sense to include information about the query, not just the query result, in the alert notification. Until now you set a display expression explicitly. With the new alert GUI, all non-hidden queries are included in the notification.

In the example below:

  • The alert condition query is variance(${A}) > 2.
  • The display expression is ts(~sample.cpu.loadavg.1m, source=app-1*).

selected query is variance(${A})>2 but non-hidden query is ts(~sample.cpu.loadavg.1m, source=app-1*)

Where Is Included Obsolete Metrics?

A: Include Obsolete Metrics is now in the same place for charts on dashboards and charts for alerts.

  • Before, Include Obsolete Metrics was under Advanced, at the bottom of the page.
  • With the new alert GUI, Include Obsolete Metrics is under Data. Just as for charts in dashboards, you click the Advanced tab to turn on Include Obsolete Metrics.

Where Is Backtesting?

A: Instead of backtesting, you can now use the Test Condition and Stop Testing button as part of the alert create/edit flow.

What happens if I save an previously created alert?

After the migration, alerts are converted the new format with multi-queries. The alert behavior does not change.

What’s the alert condition?

A: The alert condition is the selected query. This query can include the result of other queries as variables. Notifications show the condition if it’s not hidden, but you can hide the condition and create a different query to show in notifications.

How will the chart images in notification emails look now that there’s no display expression?

The chart image will show all the series from all the visible queries.

I’m using a Boolean condition but I’m asked to specify a threshold

If you use a simple condition that returns 0 or 1, the Conditions section prompts you to specify a single severity and no threshold.

However, if you use a more complicated condition that returns 0 or 1, the condition asks you to specify a severity. If you specify a 0 for the severity that you want to use in the notification, the alert works as expected.

In Data, boolean query with AND conjoined conditions. In Conditions,and severity 0.

My alert fired for a non-zero value, and now it no longer works

With the old alert experience, it was possible to specify a query ts(...). An alert for this query fired for any non-zero value, positive or negative.

With the new alert experience, you can explicitly specify ts(...) !=0 to trigger such an alert.