Make use of the stack trace

You can become a serverless blackbelt. Enrol in my course Learn you some Lambda best practice for great good! and learn best practices for performance, cost, security, resilience, observability and scalability. By the end of this course, you should be able to make informed decisions on which AWS service to use with Lambda and how to build highly scalable, resilient and cost efficient serverless applications.

As you’re debugging and stepping through your code in Visual Studio, you will no doubt have come across the Call Stack window in Visual Studio:

image

You can get access to the same stack trace information using the StackTrace and StackFrame class and this opens up some interesting possibilities. For instance, you can have a Log method which can work out the caller method name as suggested in this blog post.

You can find the caller method using the following code:

StackFrame frame = new StackFrame(1);
MethodBase method = frame.GetMethod();

With information about the caller method in hand you can even do interesting things such as restricting a method so it’s only callable from particular class or method:

if (method.DeclaringType != typeof(MyClass) || !method.Name.Equals("Mymethod"))
{
    throw new Exception();
}

Limitations

There are some important limitations you need to consider when using the Stack Track, these are discussed in more details in the second post I’ve included in the ‘References’ section. In short, it’s not guaranteed to give you the result you’d expect as result of compiler optimization when you make a Release build. And you require information from the source file such as the line number, etc. you will need to generate the symbols (.pdb file) and make sure it’s included in the release package.

References:

Getting the Current Stack Trace

Caveats about System.Diagnostics.StackTrace

JIT Optimization: Inlining

Liked this article? Support me on Patreon and get direct help from me via a private Slack channel or 1-2-1 mentoring.
Subscribe to my newsletter


Hi, I’m Yan. I’m an AWS Serverless Hero and the author of Production-Ready Serverless.

I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.

Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.

Hire me.


Check out my new podcast Real-World Serverless where I talk with engineers who are building amazing things with serverless technologies and discuss the real-world use cases and challenges they face. If you’re interested in what people are actually doing with serverless and what it’s really like to be working with serverless day-to-day, then this is the podcast for you.


Check out my new course, Learn you some Lambda best practice for great good! In this course, you will learn best practices for working with AWS Lambda in terms of performance, cost, security, scalability, resilience and observability. We will also cover latest features from re:Invent 2019 such as Provisioned Concurrency and Lambda Destinations. Enrol now and start learning!


Check out my video course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. There is something for everyone from beginners to more advanced users looking for design patterns and best practices. Enrol now and start learning!


Are you working with Serverless and looking for expert training to level-up your skills? Or are you looking for a solid foundation to start from? Look no further, register for my Production-Ready Serverless workshop to learn how to build production-grade Serverless applications!

Find a workshop near you