{"id":1604,"date":"2018-10-01T10:33:18","date_gmt":"2018-10-01T10:33:18","guid":{"rendered":"http:\/\/wiki.thomasandsofia.com\/?p=1604"},"modified":"2018-12-02T00:10:51","modified_gmt":"2018-12-02T00:10:51","slug":"monitoring-and-alerting-for-aws-elb","status":"publish","type":"post","link":"https:\/\/wiki.thomasandsofia.com\/?p=1604","title":{"rendered":"Monitoring and Alerting for AWS ELB"},"content":{"rendered":"<p><a href=\"http:\/\/wiki.thomasandsofia.com\/2018\/08\/31\/aws-cloudwatch-masterclass\/\">Main Menu<\/a><\/p>\n<h1>Section Menu<\/h1>\n<ul>\n<li><a href=\"#IntroductiontoMonitoringandAlertingforAWSELB\">Introduction to Monitoring and Alerting for AWS ELB<\/a><\/li>\n<li><a href=\"#DeployAWSELB\">Deploy AWS ELB<\/a><\/li>\n<li><a href=\"#AWSELBMetrics\">AWS ELB Metrics<\/a><\/li>\n<li><a href=\"#MonitorAWSELBMetrics\">Monitor AWS ELB Metrics<\/a><\/li>\n<li><a href=\"#Quiz\">Quiz<\/a><\/li>\n<\/ul>\n<p><a name=\"IntroductiontoMonitoringandAlertingforAWSELB\"><\/a><\/p>\n<h1>Introduction to Monitoring and Alerting for AWS ELB<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/aws-monitoring-alerting-with-aws-cloudwatch-and-aws-sns\/learn\/v4\/t\/lecture\/7082832?start=0\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/aws-monitoring-alerting-with-aws-cloudwatch-and-aws-sns\/learn\/v4\/t\/lecture\/7082832?start=0<\/a><\/p>\n<ul>\n<li>ELB: Elastic Load Balancer\n<ul>\n<li>ELBs automatically load balances incoming traffic across multiple EC2 instances<\/li>\n<li>Enables us to achieve fault tolerance and transparent scalability for our applications<\/li>\n<li>Enables us to add compute capacity to our cloud infrastucture<\/li>\n<li>Seamlessly provides the required amount of load balancing capacity required to route application traffic.<\/li>\n<\/ul>\n<\/li>\n<li>Load balancers are the entry point for most of our applications which are accessed over remote networks by users.\n<ul>\n<li>Availability, performance and correct functioning of the Load balancer is crucial.<\/li>\n<\/ul>\n<\/li>\n<li>Multiple key metrics should be monitored and thresholds should be set to ensure highle available and better serving Load Balancers<\/li>\n<\/ul>\n<p><a name=\"DeployAWSELB\"><\/a><\/p>\n<h1>Deploy AWS ELB<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/aws-monitoring-alerting-with-aws-cloudwatch-and-aws-sns\/learn\/v4\/t\/lecture\/7082834?start=0\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/aws-monitoring-alerting-with-aws-cloudwatch-and-aws-sns\/learn\/v4\/t\/lecture\/7082834?start=0<\/a><\/p>\n<ul>\n<li>Ec2 &gt; Load Balancers &gt; [Create Load Balancer] &gt; Select Load Balancer type (Classic)\n<ul>\n<li>Name: awsalertelb<\/li>\n<li>Select VPC<\/li>\n<\/ul>\n<\/li>\n<li>Configure health check\n<ul>\n<li>Ping Protocol: http (looks for 200 code from web page<\/li>\n<li>Ping Port: 80 (should match protocol port)<\/li>\n<li>Ping Path: \/index.html (could be php page that connects to a database. if that fails, then send failure code)<\/li>\n<li>Advanced Details\n<ul>\n<li>Response timeout: How long the ELB will wait for a reply.<\/li>\n<li>Interval: How long to wait after an instance fails the Response Timeout before trying it again.<\/li>\n<li>Unhealthty threshold: How many cycles (response timeout and interval) must fail before marking it as &#8216;Down&#8217;<\/li>\n<li>Healthy threshold: How many cycles before marking it at &#8216;Up&#8217;<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><a name=\"AWSELBMetrics\"><\/a><\/p>\n<h1>AWS ELB Metrics<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/aws-monitoring-alerting-with-aws-cloudwatch-and-aws-sns\/learn\/v4\/t\/lecture\/7082836?start=0\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/aws-monitoring-alerting-with-aws-cloudwatch-and-aws-sns\/learn\/v4\/t\/lecture\/7082836?start=0<\/a><\/p>\n<h2>Key Metrics<\/h2>\n<ul>\n<li>Backend Connection Errors\n<ul>\n<li>Number of unsuccessful connections between the ELB and the registered VM<\/li>\n<li>Example: An attempt is made to connect to the ELB and unable to establish a successful connection.\u00a0 This will increment the value of this metric by 1.<\/li>\n<li>Failures here mean there are errors causing latency<\/li>\n<\/ul>\n<\/li>\n<li>Latency\n<ul>\n<li>Time it takes to receive a response from the backend VM<\/li>\n<li>Use the average historic values and plot them against the maximum values to get a better insight about the application performance.\n<ul>\n<li>This will show if there is a specific period of slow responses.<\/li>\n<li>Can observe if only a few requests are taking longer than usual.\n<ul>\n<li>This can lead to many useful insights which can lead to either performance tuning of specific pages or queries.<\/li>\n<li>This can also alert regarding some configuration issues that are causing slowdowns in the application.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Surge Queue Length\n<ul>\n<li>Signifies the total number of requests that are waiting to be routed by the load balancer.\n<ul>\n<li>The ELB queues a request if it is unable to establish a connection with a healthy instance<\/li>\n<li>max queue size 1024. additional requests are rejected<\/li>\n<li>this value should be close to 0<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Spill over count\n<ul>\n<li>counts the number of dropped requests<\/li>\n<li>Should be 0!<\/li>\n<\/ul>\n<\/li>\n<li>http responses (5xx, 4xx, 2xx)\n<ul>\n<li>Count of each code?<\/li>\n<\/ul>\n<\/li>\n<li>Request count\n<ul>\n<li>number of requests received<\/li>\n<\/ul>\n<\/li>\n<li>Healthy host count<\/li>\n<li>Unhealthy host count<\/li>\n<\/ul>\n<h1>Monitor AWS ELB Metrics<\/h1>\n<ul>\n<li>EC2 &gt; Load Balancers &gt; Select load balancer &gt; Monitoring tab\n<ul>\n<li>5xx: server error<\/li>\n<li>4xx: Protocol level\n<ul>\n<li>bad request<\/li>\n<li>file not found<\/li>\n<\/ul>\n<\/li>\n<li>2xx: Server OK<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><a name=\"Quiz\"><\/a><\/p>\n<h1>Quiz<\/h1>\n<p>https:\/\/www.udemy.com\/aws-monitoring-alerting-with-aws-cloudwatch-and-aws-sns\/learn\/v4\/t\/quiz\/358942<\/p>\n<h4>ELB stands for Effective Load Balancer<\/h4>\n<ul>\n<li><strong>True<\/strong><\/li>\n<li>False<\/li>\n<\/ul>\n<h4>The backend connection errors are<\/h4>\n<ul>\n<li>Number of unsuccessful connections<\/li>\n<li>Number of successful connections<\/li>\n<li><strong>Number of unsuccessful connections to the ELB<\/strong><\/li>\n<li>Number of successful connections to the ELB<\/li>\n<\/ul>\n<h4>Backend connection errors are the number of unsuccessful connections between the ELB and registered instances.<\/h4>\n<p>If the surge queue length is ful, then the request gets dropped. These dropped requests are called &#8216;Spillover&#8217;<\/p>\n<ul>\n<li><strong>True<\/strong><\/li>\n<li>False<\/li>\n<\/ul>\n<h4>_______ monitors the health of registered targets and routes traffic only to the healthy targets<\/h4>\n<ul>\n<li>RDS<\/li>\n<li><strong>ELB<\/strong><\/li>\n<li>SNS<\/li>\n<li>EC2<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Main Menu Section Menu Introduction to Monitoring and Alerting for AWS ELB Deploy AWS ELB AWS ELB Metrics Monitor AWS ELB Metrics Quiz Introduction to Monitoring and Alerting for AWS ELB https:\/\/www.udemy.com\/aws-monitoring-alerting-with-aws-cloudwatch-and-aws-sns\/learn\/v4\/t\/lecture\/7082832?start=0 ELB: Elastic Load Balancer ELBs automatically load balances incoming traffic across multiple EC2 instances Enables us to achieve fault tolerance and transparent scalability ..<\/p>\n<div class=\"clear-fix\"><\/div>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/?p=1604\" title=\"read more...\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18,39],"tags":[],"class_list":["post-1604","post","type-post","status-publish","format-standard","hentry","category-amazon-web-services-aws","category-cloudwatch"],"_links":{"self":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/1604","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1604"}],"version-history":[{"count":11,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/1604\/revisions"}],"predecessor-version":[{"id":1622,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/1604\/revisions\/1622"}],"wp:attachment":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1604"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1604"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1604"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}