You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have well maintained OTEL providers for just every service and package in my application, save for the most obvious one AWS. The published SDK relies on far outdated AWS packages so we've had to fork & maintain our own just to track SQS & S3 operations on the worlds biggest & most widely used cloud. While I get that everyone at AWS is busy with things, the idea that AWS observability on dotnet is so outdated is a really bad look. It implies that dotnet developers are third-class citizens on the only cloud they might consider beyond Azure.
The text was updated successfully, but these errors were encountered:
I have well maintained OTEL providers for just every service and package in my application, save for the most obvious one AWS. The published SDK relies on far outdated AWS packages so we've had to fork & maintain our own just to track SQS & S3 operations on the worlds biggest & most widely used cloud. While I get that everyone at AWS is busy with things, the idea that AWS observability on dotnet is so outdated is a really bad look. It implies that dotnet developers are third-class citizens on the only cloud they might consider beyond Azure.
The text was updated successfully, but these errors were encountered: