Asp net monitor
Let’s add a new class to hold the health-status data of each component. Response Class for Component-wise Health.In order to generate a more readable response that makes sense, let’s add a bunch of reponse classes.
But this is not quite a lot of helpful information. So, what is healthy? Here, Healthy means that our entire API Application is healthy. Out of the box, Health checks are quite basic without much of the bells and whistles. Let’s build the application and navigate to. That’s actually how simple it is to get the basic healthcheck up and running. This means that, if you navigate to localhost:xxx/health, you would get the health-check status. For now, we will use the endpoint at /health. Here we will have to specify the health-check endpoint path.
Not very much practical, yeah? How about pinging a single endpoint and retreiving the health status of all your components? Introducing Healthchecks for ASP.NET Core! Imagine having to ping each and every component to monitor it’s status. Traditionally, this is done by simply the pinging the specific resource using tools like Pingdom and Uptime.
Checking the health of your application components is quite vital for Microservices Architecture based Solutions, where you can have N number of sub-project / services. Usually, to monitor the uptime ( this is a term used to define the availability of a particular resource online ) of various components of a Solution like Database, APIs and so on, HealthChecks come in handy. Implementing Healthchecks in ASP.NET Core.