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
{{ message }}
This repository has been archived by the owner on Dec 8, 2018. It is now read-only.
app.UseHealthChecks("/health");app.UseHealthChecks("/health/detail",newHealthCheckOptions(){// This custom writer formats the detailed status as JSON.ResponseWriter=WriteResponse,});app.Run(async(context)=>{awaitcontext.Response.WriteAsync("Go to /health to see the health status");});
And that would work properly.
In preview 3 both routes return the default data and the response writer is ignored. You can test this in the CustomWriterStartup.cs file by adding the code above.
What is the proper way to expose more than one health check endpoint? Tags?
The text was updated successfully, but these errors were encountered:
I think your issue is the same as #511 this is using the .Map middleware primitive, so if these middleware were ordered in the opposite way, it would work as you expect.
I agree that this is surprising and bad, I think we will have change how this is implemented.
In preview 2 I was able to use
And that would work properly.
In preview 3 both routes return the default data and the response writer is ignored. You can test this in the CustomWriterStartup.cs file by adding the code above.
What is the proper way to expose more than one health check endpoint? Tags?
The text was updated successfully, but these errors were encountered: