-
Notifications
You must be signed in to change notification settings - Fork 520
using the ASP.NET Core HealthChecks library for the liveness/readiness sample #523
Conversation
docs/recipes/probes.md
Outdated
.AddCheck("someReadinessCheck", new MyGenericCheck(_statusDictionary, "someReadinessCheck"), failureStatus: HealthStatus.Unhealthy, tags: new[] { "readiness" }); | ||
``` | ||
|
||
(Starting .NET 5, the HealthChecks library ships together with ASP.NET Core) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this package has been shipping since 2.2. I'm not sure if we are shipping the HealthChecks library with ASP.NET Core though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you're right. I saw that the HealthChecks library moved to the aspnetcore
repository after .NET 5, but it has been and still part of the extensions library.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor nits, but overall looks great. I'd like to take a spin with this entire experience locally.
Again thanks for the contribution.
Thanks for the doc! I think we should leave the readiness check and liveness check as fake checks that don't change as a result of an http request. It's fine in a sample but I would leave it out of the doc since it's not exactly what you would do in practice. |
@davidfowl I removed the whole talk about the |
LGTM, thanks! |
As discussed in #502