Profiled Tracing for AWS Lambda Invocations
SUBSCRIBE TO OUR BLOG
Get our new blogs delivered straight to your inbox.
THANKS FOR SIGNING UP!
We’ll make sure to share the best materials crafted for you!
1 minute read
Profiled Tracing for AWS Lambda Invocations
Written by Burak Kantarcı
Product Manager @Thundra
Imagine a complex distributed system with lots of API calls, messaging transactions, and database operations. Having a complex system brings its own complex problems on observing the overall performance of resources used by the system.
Resource usage monitoring is a challenge in serverless applications. Unexpected time-consuming resources may affect your application’s performance, and time has never been so important on a single function call as ever. If you reduce the time usage, you save money.
Today, we announce Profiled Traces, as an improvement of how resource metrics are delivered to developers.
What is a Profiled Trace?
Profiled invocation represents the outline form of a traced invocation which includes detailed span data whereas profiled invocation consists of the essential information about your invocation. Thundra agent collects that information to visualize and analyze your resource usage as shown in the image below.
How to Use the Profiled Trace Graph?
You can click on the resource you would like to dive into and see the related resource usages. When you hover on the resource, you can see how much time that resource takes in total, on the bottom of the graph.
If you see a time-consuming resource, Bingo! You have a starting point for time usage optimization.
What is the Benefit for my Team?
The Resource Usage is beneficial for most of the software teams to optimize their applications in production or before releasing an update for production.
Bad resource utilization or consumption of applications leads to many undesired results. Firstly, you start spending more on needless resource usages or unnecessarily high resource usage durations. It can even lead to slow development cycles and exhaust developers.
Thundra APM aims to solve the time optimization problem with its lightweight, zero-overhead, and no code change requiring feature.
It is available for the free plan too! Signup for your Thundra account and start monitoring, debugging, troubleshooting your dev/test/staging/production environments.
Visit the documentation for more information, and don’t forget to follow us on Twitter. We’ll be glad to hear your feedback. You can reach out to us on our community slack, contact us page, or directly from the website chat.
SHARE
×
SUBSCRIBE TO OUR BLOG
Get our new blogs delivered straight to your inbox.
THANKS FOR SIGNING UP!
We’ll make sure to share the best materials crafted for you!
1 minute read
Profiled Tracing for AWS Lambda Invocations
Written by Burak Kantarcı
Product Manager @Thundra
Imagine a complex distributed system with lots of API calls, messaging transactions, and database operations. Having a complex system brings its own complex problems on observing the overall performance of resources used by the system.
Resource usage monitoring is a challenge in serverless applications. Unexpected time-consuming resources may affect your application’s performance, and time has never been so important on a single function call as ever. If you reduce the time usage, you save money.
Today, we announce Profiled Traces, as an improvement of how resource metrics are delivered to developers.
What is a Profiled Trace?
Profiled invocation represents the outline form of a traced invocation which includes detailed span data whereas profiled invocation consists of the essential information about your invocation. Thundra agent collects that information to visualize and analyze your resource usage as shown in the image below.
How to Use the Profiled Trace Graph?
You can click on the resource you would like to dive into and see the related resource usages. When you hover on the resource, you can see how much time that resource takes in total, on the bottom of the graph.
If you see a time-consuming resource, Bingo! You have a starting point for time usage optimization.
What is the Benefit for my Team?
The Resource Usage is beneficial for most of the software teams to optimize their applications in production or before releasing an update for production.
Bad resource utilization or consumption of applications leads to many undesired results. Firstly, you start spending more on needless resource usages or unnecessarily high resource usage durations. It can even lead to slow development cycles and exhaust developers.
Thundra APM aims to solve the time optimization problem with its lightweight, zero-overhead, and no code change requiring feature.
It is available for the free plan too! Signup for your Thundra account and start monitoring, debugging, troubleshooting your dev/test/staging/production environments.
Visit the documentation for more information, and don’t forget to follow us on Twitter. We’ll be glad to hear your feedback. You can reach out to us on our community slack, contact us page, or directly from the website chat.
SHARE
Imagine a complex distributed system with lots of API calls, messaging transactions, and database operations. Having a complex system brings its own complex problems on observing the overall performance of resources used by the system.
Resource usage monitoring is a challenge in serverless applications. Unexpected time-consuming resources may affect your application’s performance, and time has never been so important on a single function call as ever. If you reduce the time usage, you save money.
Today, we announce Profiled Traces, as an improvement of how resource metrics are delivered to developers.
What is a Profiled Trace?
Profiled invocation represents the outline form of a traced invocation which includes detailed span data whereas profiled invocation consists of the essential information about your invocation. Thundra agent collects that information to visualize and analyze your resource usage as shown in the image below.
How to Use the Profiled Trace Graph?
You can click on the resource you would like to dive into and see the related resource usages. When you hover on the resource, you can see how much time that resource takes in total, on the bottom of the graph.
If you see a time-consuming resource, Bingo! You have a starting point for time usage optimization.
What is the Benefit for my Team?
The Resource Usage is beneficial for most of the software teams to optimize their applications in production or before releasing an update for production.
Bad resource utilization or consumption of applications leads to many undesired results. Firstly, you start spending more on needless resource usages or unnecessarily high resource usage durations. It can even lead to slow development cycles and exhaust developers.
Thundra APM aims to solve the time optimization problem with its lightweight, zero-overhead, and no code change requiring feature.
It is available for the free plan too! Signup for your Thundra account and start monitoring, debugging, troubleshooting your dev/test/staging/production environments.
Visit the documentation for more information, and don’t forget to follow us on Twitter. We’ll be glad to hear your feedback. You can reach out to us on our community slack, contact us page, or directly from the website chat.
Imagine a complex distributed system with lots of API calls, messaging transactions, and database operations. Having a complex system brings its own complex problems on observing the overall performance of resources used by the system.
Resource usage monitoring is a challenge in serverless applications. Unexpected time-consuming resources may affect your application’s performance, and time has never been so important on a single function call as ever. If you reduce the time usage, you save money.
Today, we announce Profiled Traces, as an improvement of how resource metrics are delivered to developers.
What is a Profiled Trace?
Profiled invocation represents the outline form of a traced invocation which includes detailed span data whereas profiled invocation consists of the essential information about your invocation. Thundra agent collects that information to visualize and analyze your resource usage as shown in the image below.
How to Use the Profiled Trace Graph?
You can click on the resource you would like to dive into and see the related resource usages. When you hover on the resource, you can see how much time that resource takes in total, on the bottom of the graph.
If you see a time-consuming resource, Bingo! You have a starting point for time usage optimization.
What is the Benefit for my Team?
The Resource Usage is beneficial for most of the software teams to optimize their applications in production or before releasing an update for production.
Bad resource utilization or consumption of applications leads to many undesired results. Firstly, you start spending more on needless resource usages or unnecessarily high resource usage durations. It can even lead to slow development cycles and exhaust developers.
Thundra APM aims to solve the time optimization problem with its lightweight, zero-overhead, and no code change requiring feature.
It is available for the free plan too! Signup for your Thundra account and start monitoring, debugging, troubleshooting your dev/test/staging/production environments.
Visit the documentation for more information, and don’t forget to follow us on Twitter. We’ll be glad to hear your feedback. You can reach out to us on our community slack, contact us page, or directly from the website chat.
*** This is a Security Bloggers Network syndicated blog from Thundra blog authored by Burak Kantarcı. Read the original post at: https://blog.thundra.io/profiled-tracing-for-aws-lambda-invocations
