You are here

Integrations

AWS - ELB CloudWatch

Download version    6.0    5.x

Included in Opsview Monitor 5.x
Included in Opsview Monitor 6.0
check_circle
Opsview Supported

AWS - ELB CloudWatch Opspack

Elastic Load Balancing automatically distributes incoming application traffic across multiple Amazon EC2 instances. It enables you to achieve fault tolerance in your applications, seamlessly providing the required amount of load balancing capacity needed to route application traffic and is part of Opsview Monitor's continuing support for AWS Monitoring.

What Can You Monitor

With our Opsview Monitor AWS ELB Opspack, you can easily and affordably monitor Amazon Web Services ELB (Elastic Load Balancing). Our Opspack provides detailed monitoring with various metrics across your AWS cloud including latency, healthy hosts counts and backend connection errors.

Service Checks

Service Check Description
AWS/ELB.BackendConnectionErrors The number of connections that were not successfully established
AWS/ELB.HealthyHostCount The number of healthy instances registered with your load balancer
AWS/ELB.HTTPCode_Backend The number of HTTP response codes generated by registered instances
AWS/ELB.HTTPCode_ELB The number of HTTP response codes of each code from the load balancer
AWS/ELB.Latency The time elapsed, in seconds, after the request leaves the load balancer until the headers of the response are received
AWS/ELB.RequestCount The number of requests completed or connections made during the specified interval
AWS/ELB.SpilloverCount The total number of requests that were rejected because the surge queue is full
AWS/ELB.SurgeQueueLength The total number of requests that are pending routing
AWS/ELB.UnHealthyHostCount The number of unhealthy instances registered with your load balancer

AWS - ELB CloudWatch Opspack

Elastic Load Balancing automatically distributes incoming application traffic across multiple Amazon EC2 instances. It enables you to achieve fault tolerance in your applications, seamlessly providing the required amount of load balancing capacity needed to route application traffic and is part of Opsview Monitor's continuing support for AWS Monitoring.

What Can You Monitor

With our Opsview Monitor AWS ELB Opspack, you can easily and affordably monitor Amazon Web Services ELB (Elastic Load Balancing). Our Opspack provides detailed monitoring with various metrics across your AWS cloud including latency, healthy hosts counts and backend connection errors.

Note: This Opspack knows when it was last run, so when testing the results in the troubleshoot section, you will need to wait a couple minutes each time you recheck the results. The time frame that is searched for is based around the last time the Opspack ran, so running it too quickly will result in no data being found and the service check going into an unknown

Service Checks

Service Check Description
AWS/ELB.BackendConnectionErrors The number of connections that were not successfully established
AWS/ELB.HealthyHostCount The number of healthy instances registered with your load balancer
AWS/ELB.HTTPCode_Backend The number of HTTP response codes generated by registered instances
AWS/ELB.HTTPCode_ELB The number of HTTP response codes of each code from the load balancer
AWS/ELB.Latency The time elapsed, in seconds, after the request leaves the load balancer until the headers of the response are received
AWS/ELB.RequestCount The number of requests completed or connections made during the specified interval
AWS/ELB.SpilloverCount The total number of requests that were rejected because the surge queue is full
AWS/ELB.SurgeQueueLength The total number of requests that are pending routing
AWS/ELB.UnHealthyHostCount The number of unhealthy instances registered with your load balancer

Notes

This Opspack knows when it was last run, so when testing the results in the troubleshoot section, you will need to wait a couple minutes each time you recheck the results. The time frame that is searched for is based around the last time the Opspack ran, so running it too quickly will result in no data being found and the service check going into an unknown.

Prerequisites

There are two ways of adding your authentication credentials to the host. We recommend adding the access key and secret key directly using the variable 'AWS_CLOUDWATCH_AUTHENTICATION'. You can also add the access key and secret key to a file (default /usr/local/nagios/etc/aws_credentials.cfg) in the following format:

[default]
aws_access_key_id = "Your Access Key Id"
aws_secret_access_key = "Your Secret Key Id"

Setup and Configuration

Step 1: Add the host template and the 'Cloud - AWS - ELB CloudWatch' Opspack to the host running the ELB software.

Add host template

Step 2: Add and configure the host variables tab, add in 'AWS_CLOUDWATCH_AUTHENTICATION' with either the file location or the access key and secret key depending on your preferred way of supplying the access credential. Add the region you hosted in (default eu-west-1). Then add and configure the 'AWS_ELB_LOAD_BALANCER_NAME' by adding the loadbalance instance.

Add variable

Step 3: Reload and view the ELB statistics

View output

Prerequisites

To be able to monitor AWS CloudWatch services you need to add your AWS credentials to your Opsview Monitor server.

We recommend adding your AWS Access Key ID and AWS Secret Key ID to the default location:

/opt/opsview/monitoringscripts/etc/plugins/cloud-aws/aws_credentials.cfg

This credentials file should be in the following format:

[default]
aws_access_key_id = "Your Access Key Id"
aws_secret_access_key = "Your Secret Key Id"

If you are not using the default path, you will then need to assign your path to the variable: AWS_CLOUDWATCH_AUTHENTICATION.

Setup and Configuration

To configure and utilize this Opspack, you need to add the 'Cloud - AWS - ELB CloudWatch' Opspack to your Opsview Monitor system

Step 1: Add the host template

Add host template

Step 2: Add and configure the variables for the host

  • AWS_CLOUDWATCH_AUTHENTICATION - Contains either the file location created earlier (recommended method) or add the Access Key and Secret Key directly to this variable's values.

  • Override the Region value if you are not using the default

Add credentials variable

  • AWS_ELB_LOAD_BALANCER_NAME - Load Balancer name from AWS

Add variable

Step 3: Reload and view the ELB statistics

View output

v1.1-opsview-5

ODI-393 AWS/ELB no longer returning critical when no data point on 'error count' checks

Update Opspack for version 1.1

v1.0-opsview-5

ODI-309 - AWS Cloudwatch Opspacks

Initial release for AWS Cloudwatch Opspacks

v2.0-opsview-6

ODI-1154 Release Opspacks for Opsview Monitor 6.0

            Initial release of Opspack to work with Opsview Monitor 6.0