Other Views: By Month | By Category | By Tag Cloud
In this series, we are looking at some of my favorite VS Code extensions.
Extensions in VS Code are invaluable to speed up your work and make you more productive.
In this post, we will look at the GitHub Pull Request and Issues extension that allows you to stay where you are writing your code and manage your GitHub pull requests and issues right from VS Code
In this series, we are looking at some of my favorite VS Code extensions.
Extensions in VS Code are invaluable to speed up your work and make you more productive.
In this post, we will look at Angular2 Switcher which provides shortcuts to switch between the TypeScript, StyleSheet, Spec, and Html files for your Angular files.
In this series, we are taking a look at some of my favorite VS Code extensions.
Extension in VS Code are invaluable to speed up your work and make you more productive.
In this post, we are going to look at Markdown Lint which provides Markdown/CommonMark linting and style checking for markdown files.
Markdownlint has make my markdown output much more predictable and easier for others dev to follow.
In this series, we are taking a look at some of my favorite VS Code extensions.
Extension in VS Code are invaluable to speed up your work and make you more productive.
In this post, we are going to look at Path Intellisense which autocompletes file names.
In this series, we are taking a look at some of my favorite VS Code extensions.
Extension in VS Code are invaluable to speed up your work and make you more productive.
In this post, we are going to look at Fold Plus which enables you to quickly expand or collapse sections within a file.
Extension in VS Code are invaluable to speed up your work and make you more productive. In this series, we are taking a look at some of my favorite VS Code extensions.
In this post, we are going to look at Add Only to quickly add or remove a .Only to your tests.
In the previous post in the series, we have implemented our health checks that return a json response and allow us to selectively run the health checks based on tags.
In this post, we are going to build on the previous post and update our endpoint mappings to use a generic endpoint builder so that we only have our filters and json response code in a single place.
In part 1 we create our basic ASP.NET Core health check and then in part 2 we changed from plain text “Healthy” or “Unhealthy” to a json response that let us know the stauts of each health check.
In our previous post, we have only have a single health check so it has been ok to have all health checks run when we hit our health check endpoint. However, if we had multiple health checks we are going to want to be able to run them by themselves as well as run the whole suite.
In this post, we will are going to add the ability to selectively run our health checks and create endpoints that will run either a set of health checks or all of the health checks.
In our previous post, we added a simple health check to our ASP.NET Core application. Although we only added a single health check, you can add multiple health checks and have multiple run as once. Regardless if you run a single or multiple health checks, the implementation out of the box, just returns a “Healthy” or “Unhealthy” string, which is not overall helpful to know which component actually failed.
In this post, we are going to update our health check response to return a json record that will let us know the status of each health check that is run as well as the overall health status of the application.
{
"status": "Healthy",
"duration": "00:00:00.0066738",
"info":
[
{
"key": "ExampleHealthCheckAsync",
"description": "Health Msg Here.",
"duration": "00:00:00.0010113",
"status": "Healthy",
"data": {}
}
]
}
If your ASP.NET Core application communicates with any 3rd party systems, it is beneficial to have health checks to determine if your connection to the 3rd party system is healthy, degraded, or unhealthy.
With ASP.NET Core, Microsoft references Microsoft.AspNetCore.Diagnostics.HealthChecks package implicitly for ASP.NET Core apps. This means that everything you need architecture wise is available and you just need to create your actual health check code.