Go to All Forums

Extending Support for AWS Elastic Load Balancer - Classic (ELB) and Simple Notification Service (SNS).

From what we have learned, gaining insight into your dynamic AWS cloud environment is a complex business, where monitoring your cloud server instances (EC2) alone, can only get you so far. So in accordance, we are taking our first steps by enhancing our AWS infrastructure monitoring with an improved CloudWatch integration. Announcing public beta for two new AWS services - Classic Load Balancer (ELB) and Simple Notification Service (SNS), with this new support you can measure and monitor critical performance metrics of services which power you distributed application in the cloud.

AWS ELB monitoring (Classic Load Balancer)
Should I add or remove instances or should I enable AutoScaling policy? Analyze request activity trend and load balancer latency to make the correct decision to the above question. Various key metrics of Classic load balancer supported by Site24x7 are:
  • HealthyHostCount and UnHealthyHostCount
  • BackendConnectionErrors
  • Request count
  • Latency
  • SurgeQueueLength
  • SpilloverCount
  • ELB 4XX Errors, ELB 5XX Errors.




AWS SNS monitoring (Simple Notification Service)
A single notification from a CloudWatch alarm can scale in or scale out an AutoScaling group. AWS SNS, your messenger service publishes thousands of such notifications across various SNS topics every day. Monitor to ensure the notification published by your CloudWatch Alarm and applications reaches your Subscribed end point. The various SNS metrics monitored by Site24x7 are:
  • Number of messages published
  • Publish size
  • Number of notifications delivered or failed
  • Details about subscription status and subscribers.

Licensing
Each Elastic Load Balancer or SNS topic discovered will be treated as a basic monitor. No charges will be applicable for evaluating during Beta testing, monitoring charges will only be levied when the feature goes GA.

IAM Policy Update
Update the IAM permission policy to include ELB and SNS and start monitoring. This can be done either by pasting the custom policy document JSON as an inline policy or by extending ReadOnly Access to ELB and SNS service via managed policy in the AWS IAM console. If you have already assigned complete ReadOnly access then you can sit back.

To know more about IAM policy update and the metrics we support for AWS ELB and SNS, visit our documentation.

Like I said this is just the first step, a whole lot more is coming up, so stay tuned!

Post about your monitoring experiences on our forums, ask questions, and get in touch with our support if you want to report any issue you are facing.

Update 

The ELB and SNS support for AWS monitoring is released for general availability, and is currently available for all Site24x7 customers with a paid or evaluation account. We'd like to thank all our customers who took part during the beta phase and provided us with valuable feedback.

As promised, we'll continue our efforts in making our AWS monitoring capabilities more versatile and robust. Any product enhancements or feature request from your side will go a long way in helping us achieve this. So please get in touch with our support and do let us know.

Sneak peek: Support for Application type Elastic load balancer and DynamoDB tables are on the way!



Like (3) Reply
Replies (0)