Hi, 1) The "no code changes" means that, no code change is required by you. Because Thundra makes it for you automatically. This is not the new approach for ex

Hi, 1) The "no code changes" means that, no code change is required by you. Because Thundra makes it for you automatically. This is not the new approach for existing APM and instrumentation tools but new for AWS Lambda which makes Thundra unique (and first) here at the moment. Additionally, Thundra can make method level CPU profiling without instrumenting the user code. It is supported by Java at the moment but we will support it for other languages Node.js, Go, Python soon. 2) "No overhead" means that almost no overhead. As far as we measured it is just a few microseconds in average (note that it is not milliseconds) for executing our interceptors and printing trace data to console. In respect to publishing monitor data outside of container synchronously, publishing them over CloudWatch logs asynchronously can be considered as no overhead in practice