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,...
I haven't had a lot of time lately to work on the various apps and libraries I've created or contributed to, but a vulnerability in SSH.NET needed attention in Lurgle.Transfer. This vulnerability was noted here, and required an update to dependencies. That's done now, with all other dependencies updated. The...
Email+ (aka HTML Email) I have had some pull requests open for a while for Seq.App.EmailPlus, which are quite large in scope and degree of change. This is because they are transformational in nature - adding fallback mailhosts, delivery using DNS resolution, fine-grained TLS control, enhanced logging, and adding a...
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...
Lurgle.Transfer now supports SMB; Lurgle.Alerting, Lurgle.Dates, Lurgle.Logging, EventX Trilogy, and other apps updated!
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...
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...
I've already written up a couple of posts about using Seq.Input.MSSQL, but I wanted to share one more. If you use termservers (Remote Desktop Session Host) in your environment, integrated with a Remote Desktop Connection Broker, you can do something pretty funky - logging new logins and disconnects to Seq!...
Following on from my last post about using Seq.Input.MSSQL to read Endpoint Protection table entries as Seq logs, I wanted to share something that has really made a huge difference for us - turning the SQL Agent job tables into Seq logs! This was actually the first full MSSQL Input...
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,...
Among a bunch of stars in the Seq ecosystem, Seq.Input.MSSQL has to be one of the most ambitious and coolest. This Seq input app allows you to turn just about anything with a timestamp in a SQL database into Seq logs - which in turn can power your monitoring and...
Browse all Topics
- data breach
- Event Schedule
- Event Threshold
- Event Timeout
- EventX Trilogy
- File Transfer
- Mailbox Reporter
- NLB Manager
- Outlook Profiler
- Public Holidays
- Remote Desktop
- Shell scripts
- Structured logging
- Terminal Server
- Unit Tests
- Windows Logins