Posts in "Open source"

Free SSL by Let’s Encrypt – IIS setup

I’ve heard about this group/movement which provides a free access to the SSL/TLS certificates and have decided to check it out since I want the Warden project to be secured, especially the Web Panel where some sensitive data might be stored. Actually, I still can’t believe that it was so easy to do, basically just a single click (no kidding).
Allow me present you the Let’s Encrypt and explain how easy it is, to make it work with IIS.

Continue reading

Warden screencast #1 – introduction and app example

Do you remember when a few days ago, I’ve made a promise to post come cool stuff in the next days? Well, here it goes – my first video tutorial ever in which I describe the Warden project and create a sample console application. I do realize that this recording is far from being perfect, yet I’m happy with the outcome anyway because I’ve managed to record this video using free, open source tools without a special audio recording microphone etc. – just a regular headset Superlux HMC631. The screencast can be found in the post details.

Continue reading

Warden goes Azure and gets a logo

Big updates related to the Warden project are coming this and the upcoming week.
The first release (1.0.0) has just been published to the NuGet and additionally the Web Panel is almost completed.
Not only the web interface will be available as a part of the repository, but also, it will be running in the Azure cloud in case you’d like to play with it or store your monitoring data without a need to provide own, hosting environment.
And there is one more good news – Warden is getting a brand new logo.

Continue reading

Measure your CPU & RAM usage with performance watcher

The latest, 6th watcher, has been recently added to the Warden library. It’s probably the simplest one, but it doesn’t mean it’s barely useful. The performance watcher has been created in order to measure the CPU & RAM usage, simple as that. Sounds interesting? If that’s the case, you might find the whole note useful then.

Continue reading

Warden Web Panel – UI prototype

In my latest post, I’ve stated that one day I’d like to provide some kind of UI for the users, that would visualize what’s going on in their system that is being monitored by the Warden.
As you may have noticed, this special day has come quite fast.
In this post, I’ll present the first prototype of the web interface design (that took me just a couple of minutes to complete).

Continue reading

Warden migration to .NET Core

Big changes related to the Warden project – it has been totally rewritten to the new .NET Core in order to support cross-platform capabilities (at least in a future).
The functionality per se (including API) didn’t change, yet from now on you can use Warden with the new DNX runtime.
If you’re interested in the migration process, a current status of this update (including the supported parts of the project) and what are the next goals – take a look at the whole post.

Continue reading

Warden – extensions, integrations, NuGet

Quite recently I’ve started working on new features for the Warden project and published the first prelease version to the NuGet (along with other packages that are meant to be additional plugins). In this post, I will discuss the available extensions that are basically responsible for making the fluent API even more fluent and the integrations that are a totally new thing, implemented as separate plugins (similarly to the watchers), which provide a quick access to the external services that can be part of the Warden (e.g. the SendGrid).

Continue reading

Sentry project renamed to Warden (#100 commit anniversary)

Eventually, I’ve decided to change the name of my library called Sentry to the Warden. Why? Mostly due to the fact that there’s already a big service called Sentry and I don’t want to use the same name. To be honest, I was aware of that fact since the inception of my project, yet I’ve decided not to do anything about it. What has changed my mind? Mostly other user comments that maybe it would be wise to rename the project – so I did.

The new repository can be found here but it turned out that GitHub manages the repository renaming quite nicely, so the old link will redirect you to the new one as well.