You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/alerts/monitors/create-monitor.md
+31-1Lines changed: 31 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@ description: Learn how to create a Sumo Logic monitor.
5
5
---
6
6
7
7
import useBaseUrl from '@docusaurus/useBaseUrl';
8
+
import Iframe from 'react-iframe';
8
9
9
10
This guide will walk you through the steps of creating a monitor in Sumo Logic, from setting up trigger conditions to configuring advanced settings, notifications, and playbooks.
10
11
@@ -87,7 +88,7 @@ Set specific threshold conditions for well-defined KPIs with constant thresholds
87
88
88
89
#### Anomaly
89
90
90
-
Leverage machine learning to identify unusual behavior and suspicious patterns by establishing baselines for normal activity. This [*AI-driven alerting*](https://www.youtube.com/watch?v=nMRoYb1YCfg) system uses historical data to minimize false positives and alerts you to deviations.
91
+
Leverage machine learning to identify unusual behavior and suspicious patterns by establishing baselines for normal activity. This *AI-driven alerting* system uses historical data to minimize false positives and alerts you to deviations.
91
92
92
93
***Model-driven detection**. Machine learning models create accurate baselines, eliminating guesswork and noise.
93
94
***AutoML**. The system self-tunes with seasonality detection, minimizing user intervention and adjusting for recurring patterns to reduce false positives.
@@ -96,6 +97,35 @@ Leverage machine learning to identify unusual behavior and suspicious patterns b
96
97
***Auto-diagnosis and recovery**. The Automation Service handles diagnosis and resolution, closing the loop from alert to recovery.
97
98
***Customizable detection**. Use advanced rules like "Cluster anomalies" to detect multiple data points exceeding thresholds within a set timeframe.
If you want to trigger alerts on outlier direction rather than anomaly detection, select **Anomaly** and enable **Use Outlier**. This detects unusual changes or spikes in a time series of a key indicator. Use this detection method when you are alerting on KPIs that don't have well-defined constant thresholds for what's good and bad. You want the monitor to automatically detect and alert on unusual changes or spikes on the alerting query. For example, application KPIs like page request, throughput, and latency. <br/><img src={useBaseUrl('img/alerts/monitors/monitor-detector-types-for-anomaly.png')} alt="Screenshot of the Monitor Type and Detection Method options in Sumo Logic's 'New Monitor' setup page. Logs is selected as the Monitor Type, and Anomaly is selected as the Detection Method. There is an option to use Outlier detection, which is currently toggled off." width="300"/>
Copy file name to clipboardExpand all lines: docs/alerts/monitors/use-playbooks-with-monitors.md
+26-12Lines changed: 26 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@ description: Learn how to use Automation Service playbooks with monitors.
6
6
---
7
7
8
8
import useBaseUrl from '@docusaurus/useBaseUrl';
9
+
import Iframe from 'react-iframe';
9
10
10
11
This article describes how to configure automated playbooks in monitors. An *automated playbook* is a [playbook in the Automation Service](/docs/platform-services/automation-service/automation-service-playbooks/), and is a predefined set of actions and conditional statements that run in an automated workflow to respond to an event. For example, suppose that a monitor detects suspicious behavior that could indicate a security problem. When the monitor sends the alert, it could also run an automated playbook to respond to the event.
11
12
@@ -83,21 +84,34 @@ An anomaly monitor is triggered when unusual conditions are detected. Anomaly mo
83
84
Weekly seasonality detection is turned off by default to optimize performance. [Contact Sumo Logic Customer Support](https://support.sumologic.com/support/s/contactsupport) to activate it for specific monitors. (*Weekly seasonality detection* is the optimization of baseline calculations to account for the variations of data flow that can occur in a work week.)
84
85
:::
85
86
87
+
:::sumo Micro Lesson
86
88
Watch this micro lesson to learn about anomaly monitors.
Copy file name to clipboardExpand all lines: docs/apm/traces/quickstart.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,12 +21,26 @@ You can access Traces if your Sumo Logic service package has been upgraded to in
21
21
[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access Traces, go to the **Home** screen and select **Traces**.
22
22
23
23
[**New UI**](/docs/get-started/sumo-logic-ui/). To access Traces, in the main Sumo Logic menu, select **Observability**, and then under **Application Monitoring**, select **Transaction Traces**. You can also click the **Go To...** menu at the top of the screen and select **Transaction Traces**.
24
-
25
24
26
-
## Micro Lesson
25
+
## Micro lesson
26
+
27
+
:::sumo Micro Lesson
27
28
28
29
This micro lesson can help you get started with Tracing.
Trace data is visualized through filtered trace lists and icicle charts allowing you to find and troubleshoot faulty transactions easily. See how easy it is to [view and investigate traces](view-and-investigate-traces.md).
Copy file name to clipboardExpand all lines: docs/apm/traces/spans.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,19 @@ import Iframe from 'react-iframe';
31
31
32
32
This micro lesson provides an overview of Span Analytics, and describes the term Span in the distributed tracing and the benefits of Span Analytics. It also explains how to perform Span Analytics in Sumo Logic UI.
Copy file name to clipboardExpand all lines: docs/cloud-soar/incidents-triage.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,22 @@ Incidents are events that require investigation and remediation. Incidents are a
28
28
29
29
[**New UI**](/docs/cloud-soar/overview#new-ui). To access incidents, in the main Sumo Logic menu select **Cloud SOAR > Incidents**. You can also click the **Go To...** menu at the top of the screen and select **Incidents**.
30
30
31
+
:::sumo Micro Lesson
31
32
Watch this micro lesson to learn more about incidents in Cloud SOAR.
The **Incidents** screen lists all Cloud SOAR incidents. Clicking on any of the incident IDs will open the incident. You can configure what incidents are displayed by creating queries against available incident data and saving them as incident filters.
@@ -317,8 +333,23 @@ To explore entities:
317
333
318
334
Cloud SOAR's **Dashboards** section highlights the most important pieces of data to the user or investigator who is logged into the platform. This data is presented through the use of multiple widgets that you can add, remove, and customize to include all data relevant to your job functions and duties.
319
335
336
+
:::sumo Micro Lesson
337
+
320
338
Watch the following micro lesson to learn about dashboards.
Copy file name to clipboardExpand all lines: docs/cloud-soar/legacy/legacy-global-functions-menu.md
-14Lines changed: 0 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,20 +41,6 @@ CBR solves new problems by adapting previously successful solutions to similar p
41
41
42
42
ARK assists operators during investigations in two main areas: Automatically suggesting/prompting next actions/tasks in Playbooks (until version 5) and Correlation/ Deduplication of similar threats into 1 unique incident.
0 commit comments