Logging and Monitoring

Last Updated: Tuesday, 01 January 2017 02:43AM v091bh12

We have developed a combination of standard processes and proprietary technologies to collect, aggregate and process heterogeneous data sources (server application logs, ELB/ALB logs, S3 usage logs, CloutTrail/CloudWatch) that enable us to proactively detect traffic anomalies and prevent possible application failure or service disruption.

REOL Services currently employs custom avail. agents, SENSU, Graphana, ELK stack and other third-party tools to gain visibility into client processes and performance levels.

Application States are collected from both internal and external Amazon CloudWatch metrics sources to gauge service health and automate resource provisioning (service group auto-scale or Terraform initiated), depending on outage scope.

The following log categories are collected and preserved (if applicable) by REOL Services.

AWS Infrastructure Logging

- AWS CloudTrail
- AWS VPC Flow Logs 
- AWS Inspector / Trusted Advisor

AWS Service Logging

- AWS S3
- AWS ELB Logs
- AWS CloudFront (FED consumption)
- AWS Lambda runtime Logs
- AWS IAM Credential usage Reports

REOL Service Agent Metrics

- Kernel messanging
- Security, wtpm, lastlogs, who
- Webserver logs (any variant)
- SYSLOGs/Messages
- Peformance metrics

We also automate event discovery (CloudTrail > CloudWatch > SNS/Lambda) for failures reported by AWS Inspector service