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: .clabot
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -190,7 +190,8 @@
190
190
"samiura",
191
191
"naveenrama",
192
192
"fguimond",
193
-
"rmeyer-legato"
193
+
"rmeyer-legato",
194
+
"jagan2221"
194
195
],
195
196
"message": "Thank you for your contribution! As this is an open source project, we require contributors to sign our Contributor License Agreement and do not have yours on file. To proceed with your PR, please [sign your name here](https://forms.gle/YgLddrckeJaCdZYA6) and we will add you to our approved list of contributors.",
Copy file name to clipboardExpand all lines: blog-csoar/2024/12-31.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -320,7 +320,7 @@ The Python upgrade impacts a total of 38 integrations. These integrations will r
320
320
321
321
Please be aware that with this update, the output from certain actions may no longer be displayed as expected if they were customized in your current setup. This is an important consideration for your workflows, and we recommend reviewing any customizations you have in place.
322
322
323
-
To facilitate a smooth transition, we have prepared a straightforward guide to assist you in updating your integrations. This guide outlines the steps you need to take to ensure your integrations work seamlessly with Python 3.12. <ahref="https://help.sumologic.com/files/updating-app-central-integrations.pdf"target="_blank">Click here for the "Updating App Central Integrations" guide</a>.
323
+
To facilitate a smooth transition, we have prepared a straightforward guide to assist you in updating your integrations. This guide outlines the steps you need to take to ensure your integrations work seamlessly with Python 3.12. <ahref="/files/updating-app-central-integrations.pdf"target="_blank">Click here for the "Updating App Central Integrations" guide</a>.
324
324
325
325
Below is the full list of integrations that will be affected by the Python upgrade. Please review this list to determine which integrations in your environment will require attention.
We're excited to introduce the new AWS IAM Users app for Sumo Logic. This app helps you monitor and analyze user-related data, enabling you to optimize security practices and ensure compliance within your AWS account. [Learn more](/docs/integrations/saas-cloud/aws-iam-users/).
We're excited to introduce the new **OneLogin - User Inventory** dashboard to the existing OneLogin app for Sumo Logic. This dashboard offers a centralized view of user account lifecycle and activity within the OneLogin environment. [Learn more](/docs/integrations/saml/onelogin/#user-inventory).
We're excited to announce the ability to run a log search queries directly within a selected child org under a parent org. Additionally, you can now fetch data from the selected child org and seamlessly view the associated dashboards, thereby enabling more granular monitoring and insights.
13
+
14
+
This enhancement streamlines workflows across multi-org environments and makes it easier to dive into org-specific insights while staying connected at the parent org level.
15
+
16
+
[Learn more - Log Search Across Child Orgs](/docs/search/search-across-child-orgs) <br/>
17
+
[Learn more - Create a Dashboard for Child Orgs](/docs/dashboards/dashboard-child-orgs)
Copy file name to clipboardExpand all lines: docs/alerts/monitors/alert-grouping.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Alert grouping works for both logs and metrics monitors.
20
20
21
21
### Metrics
22
22
23
-
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**.
23
+
1.[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**. <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
24
24
2. Click **Add a New monitor**.
25
25
3. Select **Metrics** as the type of monitor.
26
26
4. Enter your metrics query, then select your desired alert grouping option.
@@ -32,7 +32,7 @@ Alert grouping works for both logs and metrics monitors.
32
32
33
33
### Logs
34
34
35
-
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**.
35
+
1.[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**. <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
36
36
2. Click **Add a New monitor**.
37
37
3. Select **Logs** as the type of monitor.
38
38
4. Enter your logs query, then select your desired alert grouping option:
Copy file name to clipboardExpand all lines: docs/alerts/monitors/create-monitor.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ There are several ways to create a new monitor, depending on where you are in Su
19
19
20
20
### From Monitors
21
21
22
-
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**.
22
+
1.[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**. <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
23
23
1. Click **Add** > **New Monitor**, and the **New Monitor** dialog box will appear.
24
24
25
25
<!-- These options are not appearing
@@ -47,8 +47,8 @@ Creating a monitor based on the threshold values defined in the Metrics page can
47
47
To create a monitor from the [Metrics Search](/docs/metrics/metrics-queries/metrics-explorer/), follow the steps below:
48
48
49
49
1. Open the **Metrics Search**:
50
-
*[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). From Sumo Logic home, click **Metrics**.<br/><img src={useBaseUrl('img/alerts/monitors/home-metrics.png')} alt="Screenshot of the Sumo Logic home page with rectangle around the Metrics icon" style={{border: '1px solid gray'}} width="200"/>
51
50
*[**New UI**](/docs/get-started/sumo-logic-ui). Click the **Go To...** menu at the top of the screen and select **Metrics Search**.
51
+
*[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). From Sumo Logic home, click **Metrics**.<br/><img src={useBaseUrl('img/alerts/monitors/home-metrics.png')} alt="Screenshot of the Sumo Logic home page with rectangle around the Metrics icon" style={{border: '1px solid gray'}} width="200"/>
52
52
1. On the **Metrics Search** page:
53
53
1. Enter a metrics query.<br/><img src={useBaseUrl('img/alerts/query-metrics-explorer-view.png')} alt="Metrics explorer query" style={{border: '1px solid gray'}} width="800"/>
54
54
1. In the **Thresholds** section, define the critical and warning thresholds for your metrics query.<br/><img src={useBaseUrl('img/alerts/thresholdonly-metrics-explorer-view.png')} alt="Screenshot of the Metrics Search in Sumo Logic, displaying a line chart for node memory utilization over time. The chart shows the memory utilization metric from 17:42:12 to 17:57:12 on 21/02/2023. The right side of the screen includes a thresholds panel with critical and warning thresholds set to 500000000 and 80, respectively. The 'Fill remaining area as green' option is toggled off." style={{border: '1px solid gray'}} width="800"/>
Copy file name to clipboardExpand all lines: docs/alerts/monitors/muting-schedules.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ If fine-grained permissions are enabled for your account, you'll need the **Mana
20
20
21
21
To set a muting schedule:
22
22
23
-
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Muting Schedules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Muting Schedules**. You can also click the **Go To...** menu at the top of the screen and select **Muting Schedules**.
23
+
1.[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Muting Schedules**. You can also click the **Go To...** menu at the top of the screen and select **Muting Schedules**. <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Muting Schedules**.
24
24
1. Click **Add** > **New Schedule**.
25
25
1. Define your **Schedule Configuration** using the provided UI or [*RRule*](https://freetools.textmagic.com/rrule-generator), a syntax that allows you to specify schedule recurrence rules for calendar dates programmatically.
26
26
1. Define your **Scope**, where you associate one or more monitors with this schedule.
@@ -29,7 +29,7 @@ To set a muting schedule:
29
29
### Validate muting schedule
30
30
31
31
To confirm that your muting schedule has been applied successfully:
32
-
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**.
32
+
1.[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**.<br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
33
33
1. Find your monitor in the list and check the **Status** column, where you should see the muted indicator.
@@ -42,6 +42,6 @@ Optionally, you can apply a muting schedule to an entire alert group, rather tha
42
42
43
43
Once you've set up an alert group and a muting schedule, here's how how to link them together:
44
44
45
-
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**.
45
+
1.[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Monitoring > Monitors**. You can also click the **Go To...** menu at the top of the screen and select **Monitors**. <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**.
46
46
1. Select the alert group variable you want to mute. In this example, we'll choose `region`.<br/><img src={useBaseUrl('img/alerts/mute-sched-alert-groups1.png')} alt="mute-sched-alert-groups1.png" style={{border: '1px solid gray'}} width="500"/>
47
47
1. Under **(1) Trigger Conditions**, find the alert group you want to use. In this example, we've set up the condition so that if the `region` is `us-east-1`, alerts will be muted every third Saturday.<br/><img src={useBaseUrl('img/alerts/mute-sched-alert-groups2.png')} alt="mute-sched-alert-groups2.png" style={{border: '1px solid gray'}} width="500" />
0 commit comments