AppSync has built-in logging integration with CloudWatch Logs (see here for more details on the logging options). You can set the Field resolver log level to NONE, ERROR or ALL. When the field resolver log level is set to NONE or ERROR, you don’t get a lot of value from the AppSync logs. For example, …
Many clients have asked me “how do I record custom metrics from Lambda?”. Generally speaking, you can either: Publish custom metrics synchronously – e.g. send them at the end of an invocation. Publish custom metrics asynchronously by writing them to stdout first and then extracting them from CloudWatch Logs. Problems with sending custom metrics synchronously …
Introducing a better way to record custom metrics Read More »
A while back I wrote about using DynamoDB TTL to implement ad-hoc scheduling. It generated some healthy debate and a few of you have mentioned alternatives including using Step Functions. So let’s take a look at some of these alternatives, starting with the simplest – using a cron job. We will assess this approach using the …
Using CloudWatch and Lambda to implement ad-hoc scheduling Read More »
First of all, I would like to thank all of you for following and reading my content. My post on centralised logging for AWS Lambda has been viewed more than 20K times by now, so it is clearly a challenge that many of you have run into. In the post, I outlined an approach of …
Centralised logging for AWS Lambda, REVISED (2018) Read More »
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 its own right, it only scratches the surface of what …
auto-create CloudWatch Alarms for APIs with Lambda Read More »
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 than the Lambda invocation costs cost of storage : CloudWatch Logs charges $0.03 …
part 1 : new challenges to observability part 2 : 1st party observability tools from AWS <- you are here part 3 : 3rd party observability tools part 4: the future of Serverless observability In part 1 we talked about the challenges serverless brings to the table. In this post, let’s look at 1st party tools from AWS …
Serverless observability, what can you use out of the box? Read More »
The common practice of using agents/daemons to buffer and batch send logs and metrics are no longer applicable in the world of serverless. Here are some tips to help you get the most out of your logging and monitoring infrastructure for your functions. This is part 2 of a 3-part mini series on managing your …
Tips and tricks for logging and monitoring AWS Lambda functions Read More »
[update 23/07/2018]: The approach outlined in this post works well when you start out, but you can run into concurrency related issues at scale. To see a better approach when running at scale, please see the revised version of this post here. CloudWatch Logs is hardly the ideal fit for all your logging needs, …
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 complexity with F#-powered DSLs from Yan Cui
By continuing to use the site, you agree to the use of cookies. more information
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.