I've been slack in maintenance and haven't had new feature ideas as I've been somewhat abstracted from development in my current role. Nonetheless, I have gone through and updated dependencies for all apps and libraries that make sense to update. The goal here is to keep things current, although I...
It's been a while since I've added functionality to Lurgle libraries, but I played around with adding AWS Cloudwatch support to Lurgle.Logging. This affords further opportunities to use Lurgle.Logging as a common logging library with all its 'baked in' benefits. To do this, I leveraged the 'official' AWS.Logger.Serilog sink. Puzzlingly,...
Lurgle.Logging until now has supported just the File, Windows Event Log, Seq, and Console log types. It was always the intent to extend this to other log types to support the overall intent of Lurgle - accelerating and enhancing structured logging in your projects by leveraging the excellent work of...
Update bonanza! I've recently worked to update dependencies in almost all of my apps, so there are quite a few new versions to check out. Many of these depend on one or more of the Lurgle libraries, so it's logical that when I update the libraries, I also update the...
Standardising transfers I mentioned some time back that I had developed an internal app for critical file transfers. It's quite a useful application that has developed over time to support most of our critical file transfers. The functionality that it uses has been predominantly based around SFTP transfers using SSH.NET,...
I've recently been contributing some code to the Seq Email+ (Seq.App.HtmlEmail) repo to allow for enhanced capabilities, such as delivering email using DNS (by querying the MX record for domains) and using fallback mail hosts, along with adding To/CC/BCC and other options. These additions will, if merged, make for a...
I have had a fair bit of mileage from Seq.Client.EventLog. It's a great little service that was quite reliable for the simple usages that I initially had. When it came to monitoring for user logins, my first port of call was here - I wound up needing to fork the...
While I was investigating a case where Event Schedule for Seq had duplicate multi-log events occurring, I noticed a Daylight Savings Time issue with the unit tests, which was evident due to an upcoming DST changeover here in Australia. It was readily apparent, of course, that with their shared DNA,...
We've started to really make use of the newest member of the "EventX Trilogy" to trigger scheduled events. It's really useful to be able to trigger monthly scheduled events for IT maintenance tasks, especially tied to a Seq.App.Atlassian.Jira instance that raises the ticket at the right priority, with the right...
A while back I updated Lurgle.Logging to support new logging patterns. I've sat on it for a while, but some aspects of this weren't as well thought through as they could have been. Specifically, the idea of passing: Log.Error(ex, "Oh no! An error! {Message}", Logging.NewCorrelationId(), args: ex.Message); Log.Error(ex, "Oh no!...
A quick post on app updates - both my own and others. Over the past week, I realised that when adding Jira date expression parsing to the codebase for the Jira app, I missed out on parsing "w" (weeks), which then was also missed in Lurgle.Dates and by extension the...
You would realise by now that I'm quite a fan of Seq. It's hard not to be, when you can download a free single user license and get started with a trial, a POC, or designing your monitoring and infrastructure. The growth in open source apps for Seq over the...