Skip to main content
Sumo Logic

Install the AWS Elastic Load Balancing App and view the Dashboards

Install the Sumo Logic App

Now that you have set up collection for AWS ELB, install the Sumo Logic App for AWS Elastic Load Balancing to use the preconfigured searches and dashboards to analyze your data. 

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. To install the app, click Add to Library and 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. See Welcome to the New Library for information on working with the library in the new UI.

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. 

What if data isn't displaying in all Panels?

Amazon S3 buckets are scanned for new files according to the Scan Interval you set when configuring the S3 Source used for AWS Elastic Load Balancing logs. Even if you set a shorter Scan Interval, say five minutes, if no new files are found, the Scan Interval is automatically doubled, up to 24 hours (you can read more in Set the S3 Source Scan Interval). If the Scan Interval increases, it means that a Panel set to a 60-minute time range may not find any data to display, because no files have uploaded to Sumo Logic. This isn't to say that no data is being collected from your S3 bucket; you can confirm that data is being collected on the Status page.

Additionally, you can change the time range of a Panel. Even though these Panels have been preconfigured, they can be edited just like any other Panel. You'll find instructions in Changing the time range of a Panel.

Dashboards

The Sumo Logic App for AWS Elastic Load Balancing helps you monitor the overall health of your ELB deployment. Dashboards keep an eye on errors being generated by back-end applications as well as errors generated from ELB instances.

Overview

aws_elb_overview.png

Requests by Geolocation. Uses a geolocation query to display a map of the IP addresses used by clients accessing your apps for the last three hours.

Requests and Data Volume. Displays the data being sent and received by client IP in a pie chart for the last three hours.

Requests by Load Balancer. Displays a bar chart of how many requests are hitting a load balancer for the last three hours.

4XX and 5XX Status Codes by Backend Instance and ELB. Charts the number of 4XX and 5XX status codes for each backend instance and ELB in a bar chart over the last 24 hours.

Latency by Load Balancer. Displays the latency of each load balancer in AWS in a stacked column chart for the last three hours.

Latency Analysis

aws_elb_latency_analysis_700x350.png

Latency by Top 20 Paths. Displays the process time of the busiest 20 paths in your deployment.

Latency by Top 20 Clients. Displays the process time of the top 20 IP addresses in your deployment.

Latency by Domain. Displays the latency of each domain in your EC2 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.

Requests Analysis

aws_elb_request.png

Requests by Geolocation. Uses a geolocation query to display a map of the IP addresses used by clients accessing your apps for the last three hours.

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 three hours.

Total Requests by Load Balancer. Show the requests per load balancer over time in a bar chart for the last three hours.

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 24 hours.

Status Codes Analysis

aws_elb_analysis_700x376.png

Backend Instance and Load Balancer 4XX Status Codes by Path. Displays the time an error occurred, along with the associated path.

Backend Instance and Load Balancer 4XX Status Codes by Domain. Displays the time of an error, along with the domain, the load balancer associated with the domain, and the error code.

Backend Instance and Load Balancer 4XX Status Codes by Client. Shows the time an error occurred, the IP that generated the error, the load balancer associated with the UP, and the number of errors that have occurred.

Backend Instance and Load Balancer 5XX Status Codes by Path. Shows the time error(s) occurred on a specific path, along with the load balancer and backed instance associated with the path.

Backend Instance and Load Balancer 5XX Status Codes by Domain. Shows the time error(s) occurred in a domain, along with the load balancer and backed instance associated with domain.

Backend Instance and Load Balancer 5XX Status Codes by Client. Shows the time error(s) occurred at an IP, along with the load balancer and backed instance associated with the client IP.