Skip to main content

StackDriver Integration with AWS Elastic Beanstalk

Introduction

In Today's era where application server spreads across hundreds of machines, log-aggregation has become mandatory tool. It provides centralised location for browsing / searching through your logs coming from all of the server instances. Google's stack driver is indeed quite stable log-aggregation tool.




After reading this blog you will be able to:
  • send your multi-server logs to centralised location ie stack driver
  • monitor / search logs in real time
  • re-use same config on different elastic beanstalk environments (prod vs non-prod)

This tutorial is divided into two chapters:

Comments

Popular posts from this blog

Going deep into the Instagram’s feed ranking algorithm

Going deep into the Instagram’s feed ranking algorithm Ranking algorithms means feed posts showing up based on what Instagram thinks you want to see and not just the newest posts first. Let's check the Instagram’s giant feed handling –   They never revealed how the feed algorithm worked until they called upon a group of reporters to their San-Francisco office and pulled the curtains off from the Instagram feed ranking algorithm. They explained the reporters that there were three factors where an individual’s engagement to the app is taken care of, the three being: -

Auto Scaling DynamoDB

Those of you who have worked with the DynamoDB long enough, will be aware of the tricky scaling policies of DynamoDB. It allows user to explicitly set requests per second (units per second, but for simplicity we will just say request per second). User can do so for read as well as write operations. Anytime user can increase or decrease the provision capacity from DynamoDB web console and it will reflect immediately. Sounds all good....... Or not? What if you set provisioned capacity to 50 req per second but load on the server crosses 100 req per second? Requests gets throttled!! Mostly times out. What's worse? This can cause requests getting queued up in your web server. Which can potentially bring your entire server down. What if you set provisioned capacity to 1000 req per second but load on the server is only 100 req per second through out the day? You lose your hard earned money for remaining 900 req per second. What if you set it to 1000 req per sec and then realis