The library DOS itself if logs:DescribeLogGroups permissions is not set

[jgtestw]

Describe the bug

If the logs:DescribeLogGroups is not set, the library spams some api call. Could you please fix this, it should not do this just because the permission is not set.

Somewhat related is that it spams a log file if any error occurs (causing the computer to run out of disk space) . Again, this should not be happening.

Seems there are systemic issues with this library relating to not handling errors gracefully (correctly).

I guess I will just have to fix it myself, which I will do soon when I have time.

Regression Issue

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

Expected Behavior

No spam

Current Behavior

Spam

Reproduction Steps

Do not set logs:DescribeLogGroups

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

Latest

Targeted .NET Platform

.net 8

Operating System and version

Ecs

[peterrsongg]

Can you try turning off LogLibraryErrors in your config?

aws-logging-dotnet/src/AWS.Logger.Core/Core/AWSLoggerCore.cs

Lines 696 to 703 in 5bc6c91

	private void LogLibraryServiceError(Exception ex, string serviceUrl = null)
	{
	LogLibraryAlert?.Invoke(this, new LogLibraryEventArgs(ex) { ServiceUrl = serviceUrl ?? GetServiceUrl() });
	if (!string.IsNullOrEmpty(_config.LibraryLogFileName) && _config.LibraryLogErrors)
	{
	LogLibraryError(ex, _config.LibraryLogFileName);
	}
	}

[jgtestw]

@peterrsongg Yeah, that stops the library from creating a massive file on the system.

However, it doesn't stop the library from spamming the describlopgrups api. We actually received a call from AWS because they thought we were spamming them, but it was this library. So aws was spamming itself. And we got blamed for it lol.

We fixed the permissions, so its fine now, still, the library shouldn't spam just because a permission isn't set. Maybe call the api once every x minutes, instead of 100000 every minute, etc.