Polly
Serilog
Our great sponsors
Polly | Serilog | |
---|---|---|
52 | 55 | |
12,991 | 6,938 | |
1.4% | 1.4% | |
9.8 | 7.0 | |
4 days ago | 5 days ago | |
C# | C# | |
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Polly
-
The Retry Pattern and Retry Storm Anti-pattern
In our applications, we should wrap all requests to remote services in code that implements a retry policy that follows one of the strategies I listed earlier. If you are a .NET developer like myself, you may be familiar with the Polly library. Golang has a library called Retry, and there are numerous third-party libraries for Python and Java.
-
Http calls on mobile, what is the preferred way / best practice
Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?
-
[Question] HttpClient does not recover from error
D'Oh! Sorry, not PolySharp. I meant Polly. Too many similarly-named libraries!
-
I thought "Availability Groups" would be 100% "seamless"
Everywhere I've worked with AGs, we've worked with the application team to add retry logic to help make things a bit more seamless to end users. There are libraries out there that can make this pretty easy - Polly is one that I've used a few times, but there are others.
-
Do you really need "microservices"?
Fallacy 1: The network is reliable. If system 2 works perfectly well, but is not accessible for service 1 due to network issues, service 2 is still unavailable. This is why timeouts, service breakers and retry policies exist. A great tool for .NET to handle common network issues is Polly, but even when using a tool like this, the network is still not completely reliable.
-
Only "exit 1" if VISIBLE errors are thrown during script invocation, ignoring try/catch blocks
I see. Then I don't have any better idea right now, but I do want to suggest that if your script is mostly API calls and you want to be able to deal with failures then take a look at the polly library: https://github.com/App-vNext/Polly
-
Getting back into C# after a hiatus, any good reading material recommendations to get back up to speed? Been using Kotlin recently, and got quite a lot of experience in engineering.
Runs in containers nicely, has good integration with Kafka, RabbitMQ, gRPC, etc. for Microservices communication. Implements resiliency patterns you'd want in Microservices via Polly. Has a decent Dependency Injection framework built in by default.
-
What your hidden nuget gems ?
It's in no way hidden. But I use Polly all the time.
-
Message Queueing
Depending if the sender or the reciever is down, you can also try Polly http://www.thepollyproject.org/
- How To Implement Retries Without Cluttering Your Code
Serilog
-
Logging in .NET 8 with Serilog and Seq
To learn more about Serilog, you can visit the documentation on their GitHub project. To learn more about Seq, you can visit the documentation on their website.
-
Microsoft Entity Framework Core 8 samples
These projects use dependency injection for connections and have no logging although they are ready to log to the console via SeriLog setup in Program.cs.
-
Logging - How to configure Log Content?
See here: https://github.com/serilog/serilog/wiki/Configuration-Basics e.g.
-
Using toast notifications in Windows Forms
Captured in public static void OnActivated() and note Log is SeriLog.
-
How to set up Serilog "Enrichers"?
"Serilog": { "Using": [ "Serilog.Sinks.File" ], "Enrich": [ "WithHttpRequestId", "WithExceptionDetails", "WithClientIp" ], "MinimumLevel": { "Default": "Information" }, "WriteTo": [ { "Name": "File", "Args": { "path": "../../../../../Logs/MyApp/MyApp-.log", "rollingInterval": "Day", "retainedFileCountLimit": "7", "outputTemplate": "[{Timestamp:yyyy-MM-dd HH:mm:ss.fff zzz} {CorrelationId} {Level:u3}] {Username} {Message:lj}{NewLine}{Exception} {Properties:lj}{NewLine}" } } ] } 👆 I got the enricher names from serilog's wiki. The idea was to log the HTTPRequestId, ClientIp, and automagically log the details of every exception thrown (without having to do _logger.LogError(...)). However I don't see those details in the logs. In Program.cs: ``` var logger = new LoggerConfiguration() .ReadFrom.Configuration(builder.Configuration) .Enrich.FromLogContext() .CreateLogger();
- How to log to an Excel file?
-
How can I fix logger maximum destructuring reached error when using Serilog C#?
You could also write a custom destructuring policy, assuming it's a flurl-specific public exception type and you only need certain properties of it. You'd implement IDestructuringPolicy and then add it to the configuration:
- getting started with loggin
-
A command line tool that converts GraphQL schemas to Karate API tests
Serilog for logging
-
question about TargetFrameworks/multitargetting (new style SDK) csprojs... via serilog example
I've cloned https://github.com/serilog/serilog and I'm not sure what's going on with the multitargetting in the tests? Does this (below) mean, if the dev's OS is windows, then target framework 462 or 471? What should I do on my laptop, which only has the net6 and fw48 sdk installed?
What are some alternatives?
MediatR - Simple, unambitious mediator implementation in .NET
NLog - NLog - Advanced and Structured Logging for Various .NET Platforms
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
Log4Net - Apache Log4net is a versatile, feature-rich, efficient logging API and backend for .NET
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
ELMAH - Error Logging Modules & Handlers for ASP.NET
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
Sentry - Sentry SDK for .NET
Refit - The automatic type-safe REST library for .NET Core, Xamarin and .NET. Heavily inspired by Square's Retrofit library, Refit turns your REST API into a live interface.
opentelemetry-specification - Specifications for OpenTelemetry
Flurl.Http - Fluent URL builder and testable HTTP client for .NET
Semantic Logging Application Block (SLAB) - Supporting semantic/structured logging for .NET