Skip to content

Commit f3bb424

Browse files
authored
Merge branch 'main' into Mandiant-Threat-Intel
2 parents 778bbce + 5706cb5 commit f3bb424

33 files changed

+567
-209
lines changed

.github/CODEOWNERS

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# Default owners for everything in the repo.
2-
* @kimsauce @jpipkin1 @JV0812 @mafsumo
2+
* @kimsauce @jpipkin1 @JV0812 @mafsumo @amee-sumo
33

44
# Owners of all files in the `/docs` directory and its subdirectories.
5-
/docs/ @kimsauce @jpipkin1 @JV0812 @mafsumo
5+
/docs/ @kimsauce @jpipkin1 @JV0812 @mafsumo @amee-sumo
66

77
# Owners of all files in the `/docs/send-data/kubernetes` directory.
8-
/docs/send-data/kubernetes/ @SumoLogic/open-source-collection-team @kimsauce @jpipkin1 @JV0812 @mafsumo
8+
/docs/send-data/kubernetes/ @SumoLogic/open-source-collection-team @kimsauce @jpipkin1 @JV0812 @mafsumo @amee-sumo
99

1010
# Owners of all files in the `/docs/send-data/opentelemetry-collector` directory and its subdirectories.
11-
/docs/send-data/opentelemetry-collector/ @SumoLogic/open-source-collection-team @kimsauce @jpipkin1 @mafsumo @JV0812
11+
/docs/send-data/opentelemetry-collector/ @SumoLogic/open-source-collection-team @kimsauce @jpipkin1 @mafsumo @JV0812 @amee-sumo
1212

1313
# GitHub workflow owners
1414
/.github/workflows/ @SumoLogic/open-source-collection-team @kimsauce
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Trend Micro C2C Source (Collection)
3+
image: https://help.sumologic.com/img/sumo-square.png
4+
keywords:
5+
- collection
6+
- trend-micro
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're excited to announce the release of our new cloud-to-cloud source for Trend Micro. This source helps you to collect alert details from the Trend Micro platform, and ingest them into Sumo Logic for streamlined analysis. [Learn more](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/trend-micro-source).

cid-redirects.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2005,6 +2005,7 @@
20052005
"/cid/25618": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/cse-aws-ec-inventory-source",
20062006
"/cid/25619": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/cybereason-source",
20072007
"/cid/25779": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/mandiant-threat-intel-source",
2008+
"/cid/25719": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/trend-micro-source",
20082009
"/cid/25620": "/docs/integrations/security-threat-detection/duo-security",
20092010
"/cid/25621": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/microsoft-graph-security-api-source",
20102011
"/cid/25622": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/mimecast-source",

docs/alerts/monitors/create-monitor.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -370,7 +370,9 @@ If your data is coming from the [Amazon CloudWatch Source for Metrics](/docs/s
370370

371371
## Step 3. Notifications (optional)
372372

373-
Configure who gets notified when the monitor triggers an alert. When a trigger condition is met, you can send notifications to other people and services. Metrics monitors have an option to send notifications either as a group or separately. **Group Notifications** define whether you want single notifications per time series that match the Monitor query or you want group notifications where you receive a single notification for the entire Monitor. Log monitors always group notifications.
373+
Configure who gets notified when the monitor triggers an alert. When a trigger condition is met, you can send notifications to other people and services.
374+
375+
Notifications will be sent when the monitor is triggered as configured in the [Alert Grouping](/docs/alerts/monitors/alert-grouping/) section of the monitor.
374376

375377
<img src={useBaseUrl('img/alerts/monitors/new-monitor-notifications.png')} alt="Screenshot of the Notifications section in Sumo Logic's 'New Monitor' setup page. It includes an option to select the preferred notification time zone, set to (GMT-06:00) America/Chicago. Below is a section to configure connection types for notifications, with options for Critical, Alert, Recovery, Warning, and Missing Data. There is also a button to add a new notification." style={{border: '1px solid gray'}} width="800"/>
376378

docs/get-started/sign-up.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -145,11 +145,13 @@ Should you decide to cancel, you can do this through AWS Marketplace.
145145

146146
Your subscription will be cancelled immediately.
147147

148-
## Discover Sumo Logic with preloaded data
148+
### Kickstart your Sumo Logic experience with placeholder data
149149

150-
To help you get started quickly, preloaded placeholder data is available for trial users. This feature lets you jump in and explore Sumo Logic right away, with sample dashboards and data tailored to your needs.
150+
Get started with Sumo Logic effortlessly using **Kickstart Data**, preloaded placeholder data designed to help you explore and understand the platform’s capabilities. With Kickstart Data, you can dive in immediately and explore Sumo Logic's features without needing to set up your own data sources.
151151

152-
For more information on maximizing this feature, check out our [Quickstart Guide](/docs/get-started/quickstart).
152+
Experience the platform with sample dashboards and data tailored to your needs, allowing you to test searches, dashboards, and alerts right away.
153+
154+
Whether you're new to Sumo Logic or evaluating its features, Kickstart Data provides a hands-on way to experience the power of the platform. For more information, check out our [Quickstart Guide](/docs/get-started/quickstart).
153155

154156
## Resources
155157

docs/integrations/amazon-aws/application-load-balancer.md

Lines changed: 45 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
id: application-load-balancer
33
title: AWS Application Load Balancer
4-
description: The Sumo Logic App for AWS Elastic Load Balancing ULM - Application is a unified logs and metrics (ULM) App that gives you visibility into the health of your Application Load Balancer and target groups.
4+
description: The Sumo Logic app for AWS Elastic Load Balancing ULM - Application is a unified logs and metrics (ULM) app that gives you visibility into the health of your Application Load Balancer and target groups.
55
---
66

77
import useBaseUrl from '@docusaurus/useBaseUrl';
@@ -10,7 +10,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
1010

1111
The AWS Application Load Balancer functions at the application layer, receives requests, evaluates the listener rules in priority order to determine which rule to apply, and then selects a target from the target group.
1212

13-
The Sumo Logic App for AWS Application Load Balancing uses logs and metrics to give you visibility into the health of your Application Load Balancer and target groups. Use the pre-configured dashboards to understand the latency, request and host status, threat intel, and HTTP backend codes by availability zone and target group.
13+
The Sumo Logic app for AWS Application Load Balancing uses logs and metrics to give you visibility into the health of your Application Load Balancer and target groups. Use the pre-configured dashboards to understand the latency, request and host status, threat intel, and HTTP backend codes by availability zone and target group.
1414

1515
## Log types
1616

@@ -105,7 +105,7 @@ import Aws3 from '../../reuse/apps/create-aws-s3-source.md';
105105

106106
### Field Extraction Rule(s)
107107

108-
Create Field Extraction Rule for AWS Application Load Balancer Access Logs. Learn how to create Field Extraction Rule [here](/docs/manage/field-extractions/create-field-extraction-rule).
108+
Create Field Extraction Rule (FER) for AWS Application Load Balancer Access Logs. Learn how to create Field Extraction Rule [here](/docs/manage/field-extractions/create-field-extraction-rule).
109109

110110
```sql
111111
Rule Name: AwsObservabilityAlbAccessLogsFER
@@ -117,15 +117,35 @@ Scope (Specific Data): account=* region=* (http or https or h2 or grpcs or ws or
117117
parse "* * * * * * * * * * * * \"*\" \"*\" * * * \"*\"" as Type, DateTime, loadbalancer, Client, Target, RequestProcessingTime, TargetProcessingTime, ResponseProcessingTime, ElbStatusCode, TargetStatusCode, ReceivedBytes, SentBytes, Request, UserAgent, SslCipher, SslProtocol, TargetGroupArn, TraceId | tolowercase(loadbalancer) as loadbalancer | fields loadbalancer
118118
```
119119

120-
## Installing the AWS Application Load Balancer App
120+
#### Create/Update Field Extraction Rule(s) for Application Load Balancer CloudTrail logs
121+
122+
```sql
123+
Rule Name: AwsObservabilityALBCloudTrailLogsFER
124+
Applied at: Ingest Time
125+
Scope (Specific Data): account=* eventSource eventName "elasticloadbalancing.amazonaws.com" "2015-12-01"
126+
```
127+
128+
```sql title="Parse Expression"
129+
json "eventSource", "awsRegion", "recipientAccountId", "requestParameters.name", "requestParameters.type", "requestParameters.loadBalancerArn", "apiVersion" as event_source, region, accountid, loadbalancer, loadbalancertype, loadbalancerarn, api_version nodrop
130+
|"" as namespace
131+
| where event_source = "elasticloadbalancing.amazonaws.com" and api_version matches "2015-12-01"
132+
| parse field=loadbalancerarn ":loadbalancer/*/*/*" as balancertype, loadbalancer, f1 nodrop
133+
| if(loadbalancertype matches "network", "aws/nlb", if(balancertype matches "net", "aws/nlb", namespace)) as namespace
134+
| if(loadbalancertype matches "application", "aws/applicationelb", if(balancertype matches "app", "aws/applicationelb", namespace)) as namespace
135+
| where namespace="aws/applicationelb" or isEmpty(namespace)
136+
| toLowerCase(loadbalancer) as loadbalancer
137+
| fields region, namespace, loadbalancer, accountid
138+
```
139+
140+
## Installing the AWS Application Load Balancer app
121141

122142
Now that you have set up collection for AWS Application Load Balancer, install the Sumo Logic App to use the pre-configured searches and dashboards that provide visibility into your environment for real-time analysis of overall usage.
123143

124144
import AppInstall from '../../reuse/apps/app-install.md';
125145

126146
<AppInstall/>
127147

128-
## Viewing AWS Application Load Balancer Dashboards
148+
## Viewing AWS Application Load Balancer dashboards
129149

130150
### Overview
131151

@@ -137,7 +157,7 @@ Use this dashboard to:
137157
* Monitor trends for load balancers errors, 4XX, and 5XX errors, as well as healthy and unhealthy hosts.
138158
* Monitor the current state across all load balancers through active connections, new connections, target connection errors, and rejected connections.
139159

140-
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load-Balancer-Overview.png')} alt="AWS Application Load Balancer dashboard" />
160+
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load-Balancer-Overview.png')} alt="AWS Application Load Balancer dashboard" style={{border: '1px solid gray'}} width="800"/>
141161

142162
### Response Analysis
143163

@@ -147,7 +167,7 @@ Use this dashboard to:
147167
* Monitor incoming client locations for all 5XX, 4XX, and 3XX error responses.
148168
* Quickly correlate error responses using load balancer access logs and AWS CloudWatch metrics to determine the possible cause for failures and decide corrective actions.
149169

150-
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load_Balancer-Response_Analysis.png')} alt="AWS Application Load Balancer dashboard" />
170+
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load_Balancer-Response_Analysis.png')} alt="AWS Application Load Balancer dashboard" style={{border: '1px solid gray'}} width="800"/>
151171

152172
### Target Group Response Analysis
153173

@@ -157,7 +177,7 @@ Use this dashboard to:
157177
* Monitor trends of all response codes for your target groups by LoadBalancer, Target Group, and availability zones.
158178
* Correlate response code trends across load balancer access logs and CloudWatch metrics to determine the root cause for failures.
159179

160-
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load_Balancer-Target_Group_Response_Analysis.png')} alt="AWS Application Load Balancer dashboard" />
180+
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load_Balancer-Target_Group_Response_Analysis.png')} alt="AWS Application Load Balancer dashboard" style={{border: '1px solid gray'}} width="800"/>
161181

162182
### Latency Overview
163183

@@ -167,7 +187,7 @@ Use this dashboard to:
167187
* Monitor response times by load balancer, target group, and availability zone.
168188
* Monitor client latency and processing times for target groups.
169189

170-
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load_Balancer-Latency_Overview.png')} alt="AWS Application Load Balancer dashboard" />
190+
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load_Balancer-Latency_Overview.png')} alt="AWS Application Load Balancer dashboard" style={{border: '1px solid gray'}} width="800"/>
171191

172192
### Latency Details
173193

@@ -176,7 +196,7 @@ The **AWS Application Load Balancer - Latency Details** dashboard provides insig
176196
Use this dashboard to:
177197
* Troubleshoot load balancer performance through detailed views across client, request processing, and response time latencies.
178198

179-
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application_Load_Balancer-Latency_Details.png')} alt="AWS Application Load Balancer dashboard" />
199+
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application_Load_Balancer-Latency_Details.png')} alt="AWS Application Load Balancer dashboard" style={{border: '1px solid gray'}} width="800"/>
180200

181201
### Connection and Host Status
182202

@@ -186,7 +206,7 @@ Use this dashboard to:
186206
* Monitor active connections, new connections, rejected connections, and connection errors for the load balancer.
187207
* Monitor healthy and unhealthy host counts by the load balancer, target group, and availability zone across your infrastructure.
188208

189-
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load_Balancer-Connections_and_Host_Status.png')} alt="AWS Application Load Balancer dashboard" />
209+
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load_Balancer-Connections_and_Host_Status.png')} alt="AWS Application Load Balancer dashboard" style={{border: '1px solid gray'}} width="800"/>
190210

191211
### Requests and Processed Bytes
192212

@@ -196,7 +216,7 @@ Use this dashboard to:
196216
* Monitor client request load, network traffic, and processed bytes to determine how to best configure load balancers for optimal performance.
197217
* Determine how to best allocate backend resources and target groups based on load.
198218

199-
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application_Load_Balancer-Requests_and_Processed_Bytes.png')} alt="AWS Application Load Balancer dashboard" />
219+
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application_Load_Balancer-Requests_and_Processed_Bytes.png')} alt="AWS Application Load Balancer dashboard" style={{border: '1px solid gray'}} width="800"/>
200220

201221
### Threat Intel
202222

@@ -206,4 +226,16 @@ Use this dashboard to:
206226
* Identify known malicious IPs that access your load-balancers and use firewall access control lists to prevent them from sending you traffic going forward.
207227
* Monitor the malicious confidence level for all incoming malicious IP addresses the threats.
208228

209-
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application_Load_Balancer-Threat_Intel.png')} alt="AWS Application Load Balancer dashboard" />
229+
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application_Load_Balancer-Threat_Intel.png')} alt="AWS Application Load Balancer dashboard" style={{border: '1px solid gray'}} width="800"/>
230+
231+
### CloudTrail Audit
232+
233+
The **AWS Application Load Balancer - CloudTrail Audit** dashboard provides a comprehensive overview of AWS Application Load Balancer activities through CloudTrail audit logs. It visualizes successful and failed events globally, event trends, error details, and user activities, offering insights into load balancer performance, security, and usage patterns.
234+
235+
Use this dashboard to:
236+
* Monitor the geographical distribution of successful and failed load balancer events, allowing for quick identification of regions with high activity or potential issues.
237+
* Track the overall success rate of load balancer events and analyze trends over time, helping to identify any sudden changes or patterns in performance.
238+
* Investigate specific error events, including their details, frequency, and associated users, enabling faster troubleshooting and resolution of issues.
239+
* Identify the most common error types and the users experiencing the highest failure rates, facilitating targeted improvements and user support.
240+
241+
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Application-Load-Balancer-CloudTrail-Audit.png')} alt="AWS Application Load Balancer dashboard" style={{border: '1px solid gray'}} width="800"/>

0 commit comments

Comments
 (0)