UI Client Help Needed about aspnetcore.diagnostics.healthchecks

[unaizorrilla]

Hi @nullptr1108

I've created a sample with UI and HealthZ on the same project here https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/tree/master/samples/HealthChecks.UIAndApi can you checkout? this explain how solve your issues?

[nullptr1108]

Unai - Thank you for your quick reply to this issue. I will put together a small repro solution and then add it into this commentary.

[unaizorrilla]

Checkout the new sample

[nullptr1108]

@unaizorrilla - I did check out the sample that you added which I think is a little different than the use case that I currently am trying to work through. I have put together a repro solution at https://github.com/nullptr1108/Repro-HeathChecksUI which follows the pattern that I am trying to implement across a larger project. Hopefully this will shed some light on what I am trying to accomplish

[unaizorrilla]

Let me some time to check this

[CarlosLanderas]

One question @nullptr1108. Why are you adding the UI in the svc.target project that is only meant to register HealthChecks when you have a separate UI monitor project that is already registering the UI?

[nullptr1108]

@CarlosLanderas - Based on what I was seeing that project allowed for the response writer that was needed in the Svc.Target project to reply back in a way that the monitor can consume it. Does this reference need to be removed?

[CarlosLanderas]

You can remove the UI assembly and the AddHealthecksUI, UseHealthChecksUI from the SVC.target as only the health-ui path with the UIResponse Writer is needed for that service to be monitored by the other project you have 👍. You can read additional info on the README.md

[nullptr1108]

@CarlosLanderas - I removed the references that you indicated in your message and the behavior remains. It seems to me that the UI client in the monitor application is not able to see the target api that it is supposed to be monitoring. I dont see any errors that are being thrown through the execution in the containers.

[CarlosLanderas]

Are you using localhost in UI project appsettings configured HealthChecks? Because if you use localhost that's not gonna work. You have to assign the container name

[nullptr1108]

@CarlosLanderas - That took care of the issue that I was having, which is kind of an embarrassing oversight on my part. When I put the URI as http://svc.target:80 everything works as I would expect it to. When I try https://svc.target:443 it does not seem to work though. Is there a limitation or additional configuration for https?

[CarlosLanderas]

Yes, volumes have to be configured so an HTTPS certificate can be used. You can check more here. I close the issue as we found the problem. Thanks

https://mikewilliams.io/net-core-2-1-and-docker-how-to-get-docker-to-recognize-a-local-ssl-certificate-6e637e1e8800