Bug: XRay Tracing not showing on Lambda timeouts

[JohnHarkendorff]

Expected Behaviour

Tracing segments are shown when a Lambda times out

Current Behaviour

No tracing segments are shown

Code snippet

using System;
using System.Threading.Tasks;
using System.Collections.Generic;
using System.Net;
using System.Threading.Tasks;
using Amazon.Lambda.APIGatewayEvents;
using Amazon.Lambda.Core;
using Amazon.S3;
using AWS.Lambda.Powertools.Logging;
using AWS.Lambda.Powertools.Tracing;
using Microsoft.Extensions.DependencyInjection;

[assembly: LambdaSerializer(typeof(Amazon.Lambda.Serialization.SystemTextJson.DefaultLambdaJsonSerializer))]
namespace SecondaryQualityLambda
{
    public class Function
    {
        public Function()
        {
        }

        [Logging(ClearState = true)]
        [Tracing(CaptureMode = TracingCaptureMode.ResponseAndError)]
        public async Task<APIGatewayProxyResponse> Handler(APIGatewayProxyRequest request)
        {
            // Set a 5 second timeout on the Lambda
            await Task.Delay(10000);
            return new APIGatewayProxyResponse
            {
                 StatusCode = (int)HttpStatusCode.OK,
            };
        }
    }
}

Possible Solution

No response

Steps to Reproduce

1. Create a Lambda with a 5-second timeout and Tracing enable
2. Upload code to the Lambda that pauses for 10 seconds
3. Execute the Lambda

Would expect, in the code provided, to see ## Handler in the traces, but instead only see "Invocation".

AWS Lambda Powertools for .NET version

latest

AWS Lambda function runtime

dotnet6

Debugging logs

No response

[hjgraca]

@JohnHarkendorff thanks for reporting. Will get back to you as soon as we can repro

[heitorlessa]

That’s expected behaviour for any language, because the “container” gets recycled and app traces aren’t sent to the X-Ray daemon running within Lambda sidecar “container”. That’s an existing feature request for the Lambda service we can +1 if you can shoot us an email from your corporate address. We also asked Lambda for a guaranteed mechanism for cleanup within process (no extensions), as they would solve it too and enable other use cases - there is an undocumented workaround today[1] for a guaranteed 500ms timeout handler, but can’t rely on that contract for now on X-Ray SDK because there isn't a mechanism to flush traces to X-Ray Daemon. Until then, Lambda Extension is the only solution but that comes with a set of caveats too. [1] https://gist.github.com/heitorlessa/4aad06c39a1d520ff8c42adc72b0bcd5

…

On Sat, 15 Apr 2023 at 18:41, Henrique Graca ***@***.***> wrote: @JohnHarkendorff <https://github.com/JohnHarkendorff> thanks for reporting. Will get back to you as soon as we can repro — Reply to this email directly, view it on GitHub <#245 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZPQBGIMPUQOW6LYE7ZLH3XBLFTFANCNFSM6AAAAAAW62R7JQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[hjgraca]

@JohnHarkendorff also refer to the existing issues aws/aws-xray-sdk-dotnet#265. and aws/aws-xray-sdk-node#446 (comment).

Like @heitorlessa mentioned there can be a possibility by using extensions. I will investigate if there is a way in .NET to do something similar to what Heitor did for python.