Version 4.0.1 causes logging to fail

[Pyrhos]

Describe the bug

After package upgrade from version 4.0.0 to 4.0.1, logging continues to work for a short period, then stops entirely. Both Network TX and CPU load skyrocket, presumably from repeated attempts at sending logs. Logging does not recover until another deployment is made, at which point the same pattern manifests.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Logging continues to work indefinitely as before.

Current Behavior

A reduced amount of logs get through for up to 2 hours after a deployment finishes. Due to reliance on this form of logging exclusively, there is no other logs I can provide as to the cause of the issue - environmental logs show nothing of note.

Reverting to 4.0.0 without any other changes fixes the issue.

Reproduction Steps

public static void ConfigureLogging(this WebApplicationBuilder builder)
{
    var services = builder.Services;
    var configuration = builder.Configuration;
    var logGroup = "LogGroup";
    var awsOptions = configuration.GetAWSOptions();


    //Note that both environments exhibit the same behavior
    var environment = "Release";
    switch (environment)
    {
        case "Debug":
            services.AddSerilog(s => SetupLogger(s, logGroup, awsOptions)
                .WriteTo.Console(
                    new MessageTemplateTextFormatter(
                        "[{Timestamp:HH:mm:ss} {Level:u3}] [Id:{CorrelationId}, IdentityId:{IdentityId}] [{SourceContext:l}] {Message:lj}{NewLine}{Exception}")));
            break;
        case "Release":
            services.AddSerilog(s => SetupLogger(s, logGroup, awsOptions));
            break;
    }
}

private static LoggerConfiguration SetupLogger(LoggerConfiguration config, string logGroup, AWSOptions awsOptions) =>
    config
        .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
        .MinimumLevel.Override("Microsoft.Extensions", LogEventLevel.Information)
        .MinimumLevel.Override("Microsoft.AspNetCore.Server.Kestrel", LogEventLevel.Information)
        .MinimumLevel.Override("Hangfire", LogEventLevel.Warning)
        .MinimumLevel.Override("Microsoft.EntityFrameworkCore", LogEventLevel.Warning)
        .Enrich.FromLogContext()
        .Enrich.WithMachineName()
        .Destructure.JsonNetTypes()
        .MinimumLevel.Information()
        .WriteTo.AWSSeriLog(
            new AWSLoggerConfig
            {
                LogGroup = logGroup,
                Credentials = awsOptions.Credentials,
                Region = awsOptions.Region.SystemName,
            },
            textFormatter: new RenderedCompactJsonFormatter(),
            restrictedToMinimumLevel: LogEventLevel.Information);

Possible Solution

No response

Additional Information/Context

Reproducible on AWS ECS and AWS Apprunner

AWS .NET SDK and/or Package version used

AWS.Logger.SeriLog 4.0.1
AWSSDK.Core 4.0.1
Serilog 4.3.0
Destructurama.JsonNet 4.0.2

Targeted .NET Platform

.NET 9

Operating System and version

Ubuntu

[normj]

Thanks for reporting the issue. Looks like the change for how we compute the user agent made in 4.0.1 has a bug where the value being added to the user agent string is being duplicated for each request. Which is why it works for awhile but then the user agent grows to big and then fails.

I'll work on getting a fix out quickly.

[normj]

PR addressing the issue is out. We have also unlisted the NuGet package versions that went in the release that have this issue.

[normj]

Version 4.0.2 of AWS.Logger.SeriLog along with the other logging libraries has been released fixing the issue. Thanks again for reporting the issue and sorry for the inconvience.

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.