🩺 for Healthchecks
See original GitHub issueHello @carloscuesta 😎!
- Emoji: 🩺
- Code:
:stethoscope:
- Description: When healthchecks have been added or updated.
I already submitted PR #667 for this.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Monitoring ASP.NET Core Application Health ... - Kevin W. Griffin
NET Core, a new feature was introduced called Health Checks. This is a backend component which can regularly poll your services to see...
Read more >Checking the Health of Your ASP.NET Core APIs
How Do Health Checks Work? To know if an API is running in a healthy way or not, we use a health check...
Read more >Implementing resilient applications with API Gateway (Health ...
👉🏼 Health checks are exposed by a microservice as HTTP/HTTPS endpoints. Then enable a health check managing functionality at the API Gateway ...
Read more >🩺 Health checks | Permit.io - OPToggles
Health Checks. OPToggles exposes several endpoints for health checks by external services: /health/live Returns 200 as long as OPToggles runs.
Read more >GUINEA PIG HEALTH CHECKS 🩺 - YouTube
This video shows you the exact process I use to do my guinea pig health checks !PET CARE BINDER (DIGITAL): ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for your feedback!
I agree it’s a very backendish thing.
It’s not uncommon to have multiple health checks or adding more checks over time. Usually there is one common endpoint, which is only created once; that’s right. But there might actually be more than one check that is run when calling the health check endpoint. Think of, for example:
So I wouldn’t say it’s a “once a in project lifetime” commit emoji as basically a lot of features could come with their own health check that needs to be written and registered. For these commit emoji would imho be useful.
I’m personally not a huge fan of commits that you only use once in the project, and I don’t see this being used more than once 🤔