Skip to content

Commit 491c4d9

Browse files
committed
release notes
1 parent dfb2f79 commit 491c4d9

File tree

2 files changed

+19
-3
lines changed

2 files changed

+19
-3
lines changed
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Convert to Anomaly Feature for Log Monitors (Monitors)
3+
image: https://www.sumologic.com/img/logo.svg
4+
keywords:
5+
- monitors
6+
- alerts
7+
hide_table_of_contents: true
8+
---
9+
10+
import useBaseUrl from '@docusaurus/useBaseUrl';
11+
12+
<a href="https://help.sumologic.com/release-notes-service/rss.xml"><img src={useBaseUrl('img/release-notes/rss-orange2.png')} alt="icon" width="50"/></a>
13+
14+
We’ve added the **Convert to Anomaly** option, allowing you to convert outlier monitors into anomaly-based monitors for more efficient data usage and reduced alert noise. Please note that this feature is only available for log monitors at this time. [Learn more](/docs/alerts/monitors/settings).

docs/alerts/monitors/settings.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,18 +56,20 @@ In addition to the details listed under [Monitor attributes](#monitor-attributes
5656
* **Alert Grouping**.
5757
* **Trigger Conditions**. Thresholds value that must met for monitor to trigger an alert. Applicable values include Critical, Warning, and Missing Data. These values are set when you create a monitor and can be based on a variety of metrics such as CPU usage, network latency, application response time.
5858

59+
5960
### Convert to Anomaly
6061

61-
:::note Log monitors only
62-
Metrics monitors not supported at this time.
62+
:::note Log monitors only
63+
Metrics monitors not supported at this time.
6364
:::
6465

65-
Outlier monitors are functionally similar to anomaly monitors, but tend to generate more noise. From a data usage perspective, anomaly monitors are more cost-effective.
66+
Outlier monitors are functionally similar to anomaly monitors, but they tend to generate more noise. From a data usage perspective, anomaly monitors are more cost-effective.
6667

6768
To reduce data usage and alert frequency, you can convert an existing outlier monitor to an anomaly-based monitor by clicking **Convert to Anomaly**. This action will open a monitor configuration window with the [detection method](/docs/alerts/monitors/create-monitor/#detection-method) preset to **Anomaly**, and you can adjust other settings as needed. You’ll then have the option to either disable the original outlier monitor or keep it active.<br/><img src={useBaseUrl('img/alerts/monitors/convert-to-anomaly.png')} alt="convert-to-anomaly" width="600"/>
6869

6970
For more guidance on optimizing scan costs when using Flex Pricing, refer to the [FAQ on optimizing scan costs for monitors](/docs/alerts/monitors/monitor-faq/#how-can-i-optimize-scan-costs-for-monitors-when-using-flex-pricing).
7071

72+
7173
### View in Log Search
7274

7375
The **View in Log Search** button opens a new **Log Search** page with the monitor’s query preloaded in the search field. You can run the query to compare the search results against the threshold values set in your monitor.

0 commit comments

Comments
 (0)