Sumo Logic App for AWS Elastic Load Balance

The Sumo Logic app for AWS Elastic Load Balancer - Application ingests the logs stored in an S3 bucket, giving you the visibility to see the overall health of your Application Load Balancer and Target Groups. Use the Sumo Logic App to analyze the raw Application Load Balancer data to investigate the availability of the applications running behind Application Load Balancers. Or correlate the Application Load Balancing data with other data sets to get a broader understanding of the fault tolerance of your applications across multiple AWS Availability Zones.

NoteFor information on collecting unified logs and metrics for AWS Elastic Load Balancer Application, see the AWS Elastic Load Balancing ULM Application.

Log Types

The Application Load Balancer Access Log introduces two new fields in addition to the fields contained in Classic ELB Access log:

• Type - This is the type of request or connection (HTTP, HTTPS, H2, ws, wss)
• Target_group_arn - This is the Amazon Resource Name (ARN) of the target group

The logs are stored in a .gzip format in the specified S3 bucket and contain these fields in this order:

type, timestamp, elb, client:port, target:port, request_processing_time, target_processing_time, response_processing_time, elb_status_code, target_status_code, received_bytes, sent_bytes, request, user_agent, ssl_cipher, ssl_protocol, target_group_arn, trace_id

For more details on the ALB Access log, see the AWS documentation.

Collecting Logs for the AWS Elastic Load Balancer Application

Before you begin

In this step, you'll configure an AWS Elastic Load Balancing source to receive logs. When you create an AWS Source, you associate it with a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use, or create a new Hosted Collector. For instructions, see Configure a Hosted Collector. Before you can begin to use the Sumo Logic App for Application Load Balancing, complete the following steps:

1. Grant Sumo Logic access to an Amazon S3 bucket.
2. Enable Application Load Balancer logging in AWS.
3. Confirm that logs are being delivered to the Amazon S3 bucket.

Rules

• If you're editing the Collection should begin date on a Source the new date must be after the current Collection should begin date.

• Sumo Logic supports log files (S3 objects) that do NOT change after they are uploaded to S3. Support is not provided if your logging approach relies on updating files stored in an S3 bucket. S3 does not have a concept of updating existing files, you can only overwrite an existing file. When this overwrite happens, S3 considers it as a new file object, or a new version of the file, and that file object gets its own unique version ID.

• Sumo Logic scans an S3 bucket based on the path expression supplied, or receives an SNS notification when a new file object is created. As part of this, we receive a file name (key) and the object's ID. It's compared against a list of file objects already ingested. If a matching file ID is not found the contents of the file are ingested in full.

• When you overwrite a file in S3, the file object gets a new version ID and as a result, Sumo Logic sees it as a new file and ingests all of it. If with each version you post to S3 you are simply adding to the end of the file, then this will lead to duplicate messages ingested, one message for each version of the file you created in S3.

• Glacier objects will not be collected and are ignored.

• If you're using SNS you need to create a separate topic and subscription for each Source.

S3 Event Notifications Integration

The Sumo Logic S3 integration combines scan-based discovery and event based discovery into a unified integration that gives you the ability to maintain a low-latency integration for new content and provide assurances that no data was missed or dropped. When you enable event based notifications S3 will automatically publish new files to Amazon Simple Notification Service (SNS) topics which Sumo Logic can be subscribed. This notifies Sumo Logic immediately when new files are added to your S3 bucket so we can collect it. For more information about SNS, see the Amazon SNS product detail page.

Enabling event based notifications is an S3 bucket-level operation that subscribes to an SNS topic. An SNS topic is an access point that Sumo Logic can dynamically subscribe to in order to receive event notifications. When creating a Source that collects from an S3 bucket Sumo assigns an endpoint URL to the Source. The URL is for you to use in the AWS subscription to the SNS topic so AWS notifies Sumo when there are new files. See Configuring Amazon S3 Event Notifications for more information.

You can adjust the configuration of when and how AWS handles communication attempts with Sumo Logic. See Setting Amazon SNS Delivery Retry Policies for details.

Create an AWS Source

1. In Sumo Logic select Manage Data > Collection > Collection.

2. On the Collectors page, click Add Source next to a Hosted** **Collector, either an existing Hosted Collector, or one you have created for this purpose.

3. Select AWS Elastic Load Balancing as the source type.

4. Enter a name for the new Source. A description is optional.

5. Select an S3 region or keep the default value of Others. The S3 region must match the appropriate S3 bucket created in your Amazon account.

   note

   Selecting an AWS GovCloud region means your data will be leaving a FedRAMP-high environment. Use responsibly to avoid information spillage. See Collection from AWS GovCloud for details.

6. For Bucket Name, enter the exact name of your organization's S3 bucket. Be sure to double-check the name as it appears in AWS, for example:

7. For Path Expression, enter the wildcard pattern that matches the S3 objects you'd like to collect. You can use one wildcard (*) in this string. Recursive path expressions use a single wildcard and do NOT use a leading forward slash. See About Amazon Path Expressions for details.

8. Collection should begin. Choose or enter how far back you'd like to begin collecting historical logs. You can either:

   * Choose a predefined value from dropdown list, ranging from "Now" to “72 hours ago” to “All Time”, or
   * Enter a relative value. To enter a relative value, click the **Collection should begin** field and press the delete key on your keyboard to clear the field. Then, enter a relative time expression, for example `-1w`. You can define when you want collection to begin in terms of months (M), weeks (w), days (d), hours (h), and minutes (m).

   If you paused the Source and want to skip some data when you resume, update the Collection should begin setting to a time after it was paused.

9. For Source Category, enter any string to tag the output collected from this Source. (Category metadata is stored in a searchable field called _sourceCategory.)

10. Fields. Click the +Add Field link to add custom log metadata Fields.

    • Define the fields you want to associate, each field needs a name (key) and value.

• A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema.

• An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the Fields table schema. In this case, an option to automatically add or enable the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema or is disabled it is ignored, known as dropped.

11. For AWS Access you have two Access Method options. Select Role-based access or Key access based on the AWS authentication you are providing. Role-based access is preferred, this was completed in the prerequisite step Grant Sumo Logic access to an AWS Product.
    • For Role-based access enter** **the Role ARN that was provided by AWS after creating the role.
    • For Key access enter the Access Key ID and Secret Access Key. See AWS Access Key ID and AWS Secret Access Key for details.
12. Log File Discovery. You have the option to set up Amazon Simple Notification Service (SNS) to notify Sumo Logic of new items in your S3 bucket. A scan interval is required and automatically applied to detect log files.

Sumo Logic highly recommends using an SNS Subscription Endpoint for its ability to maintain low-latency collection. This is essential to support up-to-date Alerts.

* **Scan Interval. **Sumo Logic will periodically scan your S3 bucket for new items in addition to SNS notifications. **Automatic** is recommended to not incur additional AWS charges. This sets the scan interval based on if subscribed to an SNS topic endpoint and how often new files are detected over time.

If the Source is not subscribed to an SNS topic and set to Automatic the scan interval is 5 minutes. You may enter a set frequency to scan your S3 bucket for new data. To learn more about Scan Interval considerations, see About setting the S3 Scan Interval.

* **SNS Subscription Endpoint **(**Highly Recommended**). New files will be collected by Sumo Logic as soon as the notification is received. This will provide faster collection versus having to wait for the next scan to detect the new file.
    3. To set up the subscription you need to get an endpoint URL from Sumo to provide to AWS. This process will save your Source and begin scanning your S3 bucket when the endpoint URL is generated. Click on **Create URL** and use the provided endpoint URL when creating your subscription in step C.

Set up SNS in AWS (Highly Recommended)

The following steps use the AWS SNS Console. You may instead use AWS CloudFormation. Follow the instructions to use CloudFormation to set up an SNS Subscription Endpoint.

1. Go to Services > Simple Notification Service and click Create Topic. Enter a Topic name and click Create topic. Copy the provided Topic ARN, you’ll need this for the next step.

Make sure that the topic and the bucket are in the same region. 2. Again go to Services > Simple Notification Service and click Create Subscription. Paste the Topic ARN from step B above. Select HTTPS as the protocol and enter the Endpoint URL provided while creating the S3 source in Sumo Logic. Click Create subscription and a confirmation request will be sent to Sumo Logic. The request will be automatically confirmed by Sumo Logic. 3. Select the Topic created in step B and navigate to Actions > Edit Topic Policy. Use the following policy template, replace the SNS-topic-ARN and bucket-name placeholders in the Resource section of the JSON policy with your actual SNS topic ARN and S3 bucket name: \

{
    "Version": "2008-10-17",
    "Statement": [{
        "Effect": "Allow",
        "Principal": {
            "AWS": "*"
        },
        "Action": [
            "SNS:Publish"
        ],
        "Resource": "SNS-topic-ARN",
        "Condition": {
            "ArnLike": {
                "aws:SourceArn": "arn:aws:s3:*:*:bucket-name"
            }
        }
    }]
}

4. Go to Services > S3 and select the bucket to which you want to attach the notifications. Navigate to Properties > Events > Add Notification. Enter a Name for the event notification. In the Events section select All object create events. In the Send to section (notification destination) select SNS Topic. An SNS section becomes available, select the name of the topic you created in step B from the dropdown. Click Save.

Complete setup in Sumo

1. Set any of the following under Advanced:

• Enable Timestamp Parsing. This option is selected by default. If it's deselected, no timestamp information is parsed at all.
  • Time Zone. There are two options for Time Zone. You can use the time zone present in your log files, and then choose an option in case time zone information is missing from a log message. Or, you can have Sumo Logic completely disregard any time zone information present in logs by forcing a time zone. It's very important to have the proper time zone set, no matter which option you choose. If the time zone of logs can't be determined, Sumo Logic assigns logs UTC; if the rest of your logs are from another time zone your search results will be affected.
  • Timestamp Format. By default, Sumo Logic will automatically detect the timestamp format of your logs. However, you can manually specify a timestamp format for a Source. See Timestamps, Time Zones, Time Ranges, and Date Formats for more information.
• Enable Multiline Processing. See Collecting Multiline Logs for details on multiline processing and its options. This is enabled by default. Use this option if you're working with multiline messages (for example, log4J or exception stack traces). Deselect this option if you want to avoid unnecessary processing when collecting single-message-per-line files (for example, Linux system.log). Choose one of the following:
  • Infer Boundaries. Enable when you want Sumo Logic to automatically attempt to determine which lines belong to the same message. If you deselect the Infer Boundaries option, you will need to enter a regular expression in the Boundary Regex field to use for detecting the entire first line of multiline messages.
  • Boundary Regex. You can specify the boundary between messages using a regular expression. Enter a regular expression that matches the entire first line of every multiline message in your log files.

1. Create any Processing Rules you'd like for the AWS Source.
2. When you are finished configuring the Source click Save.

SNS with one bucket and multiple Sources

When collecting from one AWS S3 bucket with multiple Sumo Sources you need to create a separate topic and subscription for each Source. Subscriptions and Sumo Sources should both map to only one endpoint. If you were to have multiple subscriptions Sumo would collect your objects multiple times.

Each topic needs a separate filter (prefix/suffix) so that collection does not overlap. For example, the following image shows a bucket configured with two notifications that have filters (prefix/suffix) set to notify Sumo separately about new objects in different folders.

Update Source to use S3 Event Notifications

There is a community supported script available that configures event based object discovery on existing AWS Sources.

1. In Sumo Logic select Manage Data > Collection > Collection.
2. On the Collection page navigate to your Source and click Edit. Scroll down to Log File Discovery and note the Endpoint URL provided, you will use this in step 10.C when creating your subscription.
3. Complete steps 10.B through 10.E for configuring SNS Notifications.

Troubleshoot S3 Event Notifications

In the web interface under Log File Discovery, it shows a red exclamation mark with "Sumo Logic has not received a validation request from AWS".

Steps to troubleshoot:

1. Refresh the Source’s page to view the latest status of the subscription in the SNS Subscription section by clicking Cancel, then Edit on the Source in the Collection tab.
2. Verify you have enabled sending Notifications from your S3 bucket to the appropriate SNS topic. This is done in step 10.E.
3. If you didn’t use CloudFormation check that the SNS topic has a confirmed subscription to the URL in AWS console. A "Pending Confirmation" state likely means that you entered the wrong URL while creating the subscription.

In the web interface under Log File Discovery it shows a green check with "Sumo Logic has received an AWS validation request at this endpoint." but you still have high latencies.

The green check confirms that the endpoint was used correctly, but it does not mean Sumo is receiving notifications successfully.

Steps to troubleshoot:

1. AWS writes CloudTrail and S3 Audit Logs to S3 with a latency of a few minutes. If you’re seeing latencies of around 10 minutes for these Sources it is likely because AWS is writing them to S3 later than expected.
2. Verify you have enabled sending Notifications from your S3 bucket to the appropriate SNS topic. This is done in step 10.

Installing the AWS ELB Application

Now that you have set up collection for AWS ELB, install the Sumo Logic App for AWS Elastic Load Balancer to use the pre-configured searches and dashboards that provide visibility into your environment.

To install the app:

Locate and install the app you need from the App Catalog. If you want to see a preview of the dashboards included with the app before installing, click Preview Dashboards.

1. From the App Catalog, search for and select the app.
2. Select the version of the service you're using and click Add to Library. Version selection is applicable only to a few apps currently. For more information, see the Install the Apps from the Library.
3. To install the app, complete the following fields.
   1. App Name. You can retain the existing name, or enter a name of your choice for the app.

   2. Data Source. Select either of these options for the data source.

      • Choose Source Category, and select a source category from the list.

      • Choose Enter a Custom Data Filter, and enter a custom source category beginning with an underscore. Example: (_sourceCategory=MyCategory).

   3. Advanced. Select the Location in Library (the default is the Personal folder in the library), or click New Folder to add a new folder.
4. Click Add to Library.

Once an app is installed, it will appear in your Personal folder, or other folder that you specified. From here, you can share it with your organization.

Panels will start to fill automatically. It's important to note that each panel slowly fills with data matching the time range query and received since the panel was created. Results won't immediately be available, but with a bit of time, you'll see full graphs and maps.

Viewing AWS ELB Dashboards

Application Overview

• Requests by Geolocation. Uses a geolocation query to display a map of the IP addresses used by clients accessing your apps for the last fifteen minutes.
• Browsers and Operating Systems. Reports the breakdown of the client’s browser by operating system in a stacked column chart for the last fifteen minutes.
• Requests by SSL Protocol and Cipher. Reports the breakdown of ciphers used by protocol in a stacked column chart for the last fifteen minutes.
• Requests by Load Balancer. Displays a bar chart of how many requests are hitting a load balancer for the last fifteen minutes.
• Data Sent and Received in MB. Displays the data being sent and received by client IP in a pie chart for the last fifteen minutes.
• Target Group Utilization. Counts the requests by target group in the last fifteen minutes.
• 4XX and 5XX Status Codes by Backend Instance and ALB. Charts the number of 4XX and 5XX status codes for each backend instance and ALB in a bar chart over the last fifteen minutes.
• Average Req and Response Time by ELB. Displays the latency of each load balancer in AWS in a stacked column chart for the last fifteen minutes.
• Average Target Processing Time by Target Group. Displays the average target processing time for each target group.

Latency Analysis

• Total Process Time Latency 90th, 95 pct. Shows the 90th and 95th percentile trend as an average across your deployment.
• Latency by Protocol. Shows the average latency by protocol across your deployment.
• Latency by Target Group. Shows the average latency by Target Group across your deployment.
• Latency by Domain. Displays the latency of each domain in your EC2 deployment.
• Target Processing Time by Target Group. Bar chart of max, average, and min processing times for each target group.
• Average Target Processing Time by Target Group. Line chart of mean processing time by target group.
• Latency by Top 20 Clients. Displays the process time of the top 20 IP addresses in your deployment.
• Latency by Top 20 Backend Instances. This Panel focuses solely on the back end of your AWS EC2 deployment, keeping watch over the processing time of the 20 busiest instances.
• Latency by Top 20 Paths. Displays the process time of the busiest 20 paths in your deployment.

Request Analysis

• Requests by Geolocation. Uses a geolocation query to display a map of the IP addresses used by clients accessing your apps for the last fifteen minutes.
• Requests by Target Group Over Time. Shows the trend of requests by Target Group over time for the last fifteen minutes.
• Requests by Protocol Over Time. Shows the trend of requests by protocol over time for the last fifteen minutes.
• Requests by Load Balancer Over Time. Displays a line chart of how many requests are hitting a load balancer on a timeline over the last fifteen minutes.
• Total Requests by Load Balancer. Show the requests per load balancer over time in a bar chart for the last fifteen minutes.
• Total Requests and Data Volume. Displays the data being sent and received by client IP in a line chart on a timeline for the last fifteen minutes.

Status Code Analysis

• ELB Status Over Time. Displays a bar chart representing the application status over a specified time period.
• Target Status Over Time. Displays a bar chart representing the status of the target over a specified time period.
• 4XX ELB Status by Location. Charts the number and geographic location of 4XX ELB errors.
• 5XX ELB Status by Location. Charts the number and geographic location of 5XX ELB errors.
• 5XX Target Status by Location. Charts the number and geographic locations of errors for 5XX targets.
• 4XX Target Status by Location. Charts the number and geographic locations of errors for 4XX targets.
• Target Status by Target Group. Shows a bar chart comparing errors by target group: 4XX and 5XX.
• ELB Status by ELB Server. Shows a bar chart comparing errors on each server by target: 4XX and 5XX.
• Target Status by Domain. Shows the number of errors that occurred in a domain by target: 4XX and 5XX.
• Target Status by URI. Shows the number of errors for each Uniform Resource Identifier (URI): 4XX and 5XX.

Failed Dispatch Monitoring

• Failed Dispatches Client Geolocation. Uses geolocation to map IP addresses for clients with failed dispatches.
• Failed Dispatch Outlier. Shows the number of failed dispatches, the threshold for “normal” failures and identifies any outliers outside that threshold.
• Failed Dispatches by Backend. Identifies the failed dispatches by backend time sliced by 30 minutes over a 24 hour period.
• Failed Dispatches by Target Group. Identifies the failed dispatches by target group time sliced by 30 minutes over a 24 hour period.
• Failed Dispatches by Client. Aggregation table of clients and the number of their failures for the last 24 hours.
• Failed Dispatches Count. Total number of failed dispatches.
• Failed Dispatches by URI. Aggregation table of the top ten URIs with dispatches failed.
• Failed Dispatches by Host. Identifies the failed dispatches by host domain time sliced by 30 minutes over a 24 hour period.