Don't Skip Proactive Server(less)-side Monitoring
November 21, 2018

Don't Skip Proactive Server(less)-side Monitoring

Kyle Reichelt | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Amazon CloudWatch

We use Amazon Cloudwatch in a variety of ways, from monitoring the performance and validation success/failures of our ETL (extract, transform, and load) processes, our Lambda Services, our EC2 instances, our RDS instances, as well as our Redshift instance. Certainly we're using Amazon Cloudwatch to monitor day-to-day server-side activities, but the really impressive capabilities lie in its ability to both diagnose issue, as well as to trigger automated remediation.
  • Lambda process monitoring, particularly useful when you're relying on third-party services.
  • Active monitoring RDS (set thresholds so we know before a database runs out of space)
  • Auto-requisitioning of additional resources
  • It saves time pouring through log files, providing us non-engineers with a nice clean, intuitive interface
  • It helps us maximize "up-time" by allowing us to stay ahead of third-party service downtime
Well suited if:
  • Your organization is married to the AWS ecosystem
  • You tech stack is reliant on third-party services
  • You use Splunk as your log aggregator (integrates well)
  • You prefer to be proactive about health of your tech stack
Not particularly suited if:
  • You don't use AWS
  • You like to fly by the seat of your pants