Continuous Monitoring

Overview

We leveraged Platform as a Service (PaaS) cloud model for hosting the application on Amazon Elastic Beanstalk. Utilizing a PaaS model comes with following benefits

  1. Higher level of abstraction compared to OS/infrastructure as a service (IaaS) based models
  2. Built in mechanisms for scaling, monitoring and healing
  3. Cost effeciences
  4. Faster time to market

Our continuous monitoring model consists of following elements 1. Healthcheck, notification and scaling configurations 2. Monitoring platform generated metrics 3. Logging and monitoring system and environment changes 4. Running analysis scripts/jobs on logs saved to Amazon S3 (tbd)

We also use google analytics to get information on site access.

Google analytics console


Google analytics console

The following screenshots provide an overview of the healthcheck and monitoring configuration and metrics

AWS CloudTrail keeps an audit logs of all the API calls to the AWS cloud platform. These logs provide a record of how, when and by whom cloud platform configuration changes were effected.

CloudTrail logs viewable in the console


CloudTrail logs viewable in the console

CloudTrail logs stored in S3


CloudTrail logs stored in S3

Application platform alarms - 1


Application platform alarms - 1

Application platform alarms - 2


Application platform alarms - 2

Platform health events


Platform health events

Platform health


Platform health

Platform logs can be downloaded from console


Platform logs can be downloaded from console

Platform logs contents


Platform logs contents

Application platform metrics - 1


Application platform metrics - 1

Application platform metrics - 2


Application platform metrics - 2

Email notification configuration


Email notification configuration

Email notification on platform change


Email notification on platform change

Load balancer logs saved to S3 - 1


Load balancer logs saved to S3 - 1

Load balancer logs saved to S3 - 2


Load balancer logs saved to S3 - 2