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
@@ -192,7 +192,8 @@
192
192
"fguimond",
193
193
"rmeyer-legato",
194
194
"jagan2221",
195
-
"pankaj101A"
195
+
"pankaj101A",
196
+
"prajalb"
196
197
],
197
198
"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-service/2025-10-15-manage.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,3 @@ hide_table_of_contents: true
11
11
We're excited to annouce the new **AutoPause** feature for Scheduled Views, designed to enhance system performance and optimize resource usage.
12
12
13
13
With AutoPause, any Scheduled View that remains inactive for 90 consecutive days (that is, not queried or referenced) will be automatically flagged and paused. To ensure you're informed ahead of time, Scheduled View owners and active account administrators will receive email and in-app notifications 21 days and 7 days before the scheduled pause. If no action is taken, the view will be automatically paused on the 90th day, followed by a final alert. [Learn more](/docs/manage/scheduled-views/pause-disable-scheduled-views/).
14
-
15
-
:::note
16
-
This feature is currently available only for Canada (Central), Asia Pacific (Tokyo), and Asia Pacific (Seoul) regions.
We're excited to announce the release of our new cloud-to-cloud source for Varonis. This source securely collects alerts from the Varonis platform and sends them to Sumo Logic for streamlined analysis. [Learn more](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/varonis-source).
12
+
We're excited to announce the release of our new cloud-to-cloud source for Varonis Alerts. This source securely collects alerts from the Varonis platform and sends them to Sumo Logic for streamlined analysis. [Learn more](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/varonis-source).
Copy file name to clipboardExpand all lines: docs/integrations/microsoft-azure/azure-app-service-plan.md
-13Lines changed: 0 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,19 +39,6 @@ import MetricsSource from '../../reuse/metrics-source.md';
39
39
40
40
<MetricsSource/>
41
41
42
-
### Configure logs collection
43
-
44
-
#### Diagnostic logs
45
-
46
-
In this section, you will configure a pipeline for shipping diagnostic logs from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) to an Event Hub.
47
-
48
-
1. To set up the Azure Event Hubs source in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
49
-
2. To create the **Diagnostic setting** in the Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform the steps below for each Azure Functions that you want to monitor.
50
-
1. Choose `Stream to an event hub` as the destination.
51
-
1. Select `AllMetrics`.
52
-
1. Use the Event Hub namespace and Event Hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-App-Service-Plan-Configure-Diagnostic-Metrics.png')} alt="Azure App Service Plan Tag Location" style={{border: '1px solid gray'}} width="800" />
53
-
3. Tag the location field in the source with right location value.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Location.png')} alt="Azure Storage Tag Location" style={{border: '1px solid gray'}} width="400" />
54
-
55
42
#### Activity logs (optional)
56
43
57
44
import ActivityLogs from '../../reuse/apps/azure-activity-logs.md';
Copy file name to clipboardExpand all lines: docs/integrations/microsoft-azure/azure-cosmos-db.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,10 +29,8 @@ For Azure Cosmos DB, you can collect the following logs and metrics:
29
29
30
30
***Resource logs**. To learn more about the different resource log category types and schemas collected for Azure Cosmos DB, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/monitor-reference#resource-logs).
31
31
32
-
***Platform Metrics for Azure Cosmos DB**. For more information on supported metrics and dimensions, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/monitor-reference#metrics). These metrics are available in the following namespaces:
33
-
*`Microsoft.DocumentDB/applicationGateways`
34
-
*`Microsoft.DocumentDB/cassandraClusters`
35
-
*`Microsoft.DocumentDB/mongoClusters`
32
+
***Platform Metrics for Azure Cosmos DB**. For more information on supported metrics and dimensions, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/monitor-reference#metrics). These metrics are available within the namespace `Microsoft.DocumentDB/DatabaseAccounts`
33
+
36
34
***Activity logs**. Provides insight into any subscription-level or management group level events that have occurred in the Azure. To learn more, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log-schema).
Copy file name to clipboardExpand all lines: docs/security/index.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
@@ -11,7 +11,7 @@ Sumo Logic security solutions support the entire spectrum of security use cases,
11
11
***[Logs for Security](/docs/security/additional-security-features/)**<br/>Provides enhanced insight for security analysts into threat activity via logs. Collect security log and event data from your infrastructure and applications, on-premises and in-cloud. Analyze your security data with pre-built and custom dashboards, out-of-the-box security apps, and robust queries.
12
12
***Threat detection, investigation, and response**<br/>After you have collected logs for security, you can use them with the following solutions for threat detection, investigation, and response:
13
13
***[Cloud SIEM](/docs/cse/)**<br/>Gives SOC (security operations center) analysts prioritized and contextualized actionable threats with automated security workflows. Out-of-the-box automated detection reduces manual work, saving valuable resource time and enabling your team to be more effective by allowing them to focus on higher-value security functions.
14
-
***[Cloud SOAR](/docs/cloud-soar/)**<br/>Fully automates triage, investigation, and remediation of threats for any security professional. The open integrations framework allows you to connect to a multitude of third-party applications. The platform provides full incident response lifecycle management with machine learning and threat hunting, accelerating mean time to respond (MTTR). |
14
+
***[Cloud SOAR](/docs/cloud-soar/)**<br/>Fully automates triage, investigation, and remediation of threats for any security professional. The open integrations framework allows you to connect to a multitude of third-party applications. The platform provides full incident response lifecycle management with machine learning and threat hunting, accelerating mean time to respond (MTTR).
0 commit comments