In a previous post we discussed how to auto-subscribe a CloudWatch Log Group to a Lambda function using CloudWatch Events. So that we don’t need a manual process to ensure all Lambda logs would go to our log aggregation service. Whilst this is useful in i[...]

It’s common practice to set log level to WARNING for production due to traffic volume. This is because we have to consider various cost factors: cost of logging : CloudWatch Logs charges $0.50 per GB ingested. In my experience, this is often much higher t[...]

Tweet Here’s the recorded live stream of the F# DSLs session I did at the F# |> Bristol user group last night. (apologies for the first few mins where I forgot to share my screen to the Hangout…) and here’s the slides to go with the talk: Tame cloud compl[...]

Tweet Learn you to tame complex APIs with F#-powered DSLs from Yan Cui Tweet

On application monitoring In the Gamesys social team, our view on application monitoring is such that anything that runs in production needs to be monitored extensively all the time – every service entry point, IO operations or CPU intensive tasks. Sure, [...]

If you have done any DevOps work on Amazon Web Services (AWS) then you should be familiar with Amazon CloudWatch, a service for tracking and viewing metrics (CPU, network in/out, etc.) about the various AWS services that you consume, or better still, cust[...]