-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bonus Chapter - Implementing a Health Check API #8
Comments
Are you able to call the actual endpoint and get a response? |
I’m not entirely sure that I understand the question. Here is what I see:
From: Mark J. Price ***@***.***>
Sent: Thursday, December 29, 2022 07:54
To: markjprice/cs11dotnet7 ***@***.***>
Cc: BobMolloy ***@***.***>; Author ***@***.***>
Subject: Re: [markjprice/cs11dotnet7] Bonus Chapter - Implementing a Health Check API (Issue #8)
Are you able to call the actual endpoint and get a response?
—
Reply to this email directly, view it on GitHub <#8 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABY45SDUVGZV23BIYY2QUNDWPWCVDANCNFSM6AAAAAATCVK6HE> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/ABY45SDQ7G4RQQO6SZSPBTTWPWCVDA5CNFSM6AAAAAATCVK6HGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSRP5JOE.gif> Message ID: ***@***.*** ***@***.***> >
|
There is nothing shown. Please try replying in GitHub and add the screenshot. |
Okay, so just before the Implementing advanced features for web services section that is online only was the client HTTP section. I assume you were therefore able to call the the actual endpoint and get a response, for example, the HTTP client could call: GET https://localhost:5002/api/customers/?country=UK and the response was returned. Therefore the endpoint is working. If you then added the package for health checks and the Web API service is returning 503 Unhealthy then it's is "lying" in some way. After getting 503, try changing the address box to: https://localhost:5002/api/customers/?country=UK and see what response you get and please screenshot that. |
Yes, so the endpoint is actually healthy but the Microsoft health check thinks that it not. I don't know why. I'll see if I can research why that might be. |
Page 2, Bullet 7
Every time I run this, I receive the output "Unhealthy" and a 503 status code.
The text was updated successfully, but these errors were encountered: