The new version of Warden has been released. It’s a rather minor update concerning only core Warden package, however it includes a feature that I was asked for a quite some time - a possibility to dynamically reconfigure the already existing Warden instance.

The new version of Warden has been released. It’s not as big update, as the version 1.3.0, however it contais some minor updates towards making the Warden extensions available cross-platform. All of the packages (core, watchers and integrations) are ready to be installed via NuGet.

It’s been 2 months since the latest version of the Warden has been released as the NuGet packages. Although our focus (yes, I’m not the only one person anymore working on this project) has moved towards the development of so-called stack (brand new API, Website, Microservices etc.) I’m still actively developing the core library in order to make it even more useful than before.

Warden Spawn is a brand new repository within the Warden Stack that will let you configure the Warden instance of the Warden monitoring application using the human readable configuration files.

Thew new integration with the Cachet will let you to make use of these beautiful status pages along with the running instance of the Warden monitoring application. Cachet integration can be configured seamlessly within a few lines of code.

Thanks to the contribution from Mattias, Warden and all of it’s packages have been updated to the latest version of the framework which is .NET 4.6.1. and accordingly the cross-platform packages have been upgraded to use the NETCoreApp including DotNet 5.6 & DNX Core 5.0.

The new type of integration designed for either querying or saving the data into the MS SQL database has been released. MS SQL integration also provides storing the whole IWardenIteration object thanks to the available method SaveIterationAsync() and provided table schema, which means you can store all the data you need in your own MS SQL database just within a few lines of code.

Previously existing Port watcher has been extended with a new feature for sending a ping requests (including status description in response), therefore it has been refactored into the new Server watcher. Port is now an optional parameter, as from now on this watcher serves a more generic purpose.

Interval is a brand new functionality, that I’ve been asked to implement at least for a few times. By using intervals, you are able to specify a custom period for each particular Watcher (or all of them at once) after which the actual check (invoking ExecuteAsync() method) will happen.

Let me introduce a blog about the Warden where the most important information and updates will be posted in order to keep you informed what’s going on with the proejct.