I've been working on new updates to the EventX Trilogy - Event Timeout, Event Threshold, and Event Schedule - which I will blog about in more detail, but I wanted to put a quick note out about an issue that may occur when you update to Event Timeout v1.5.1 and...
After the last update to Seq.Client.WindowsLogins, in which I cursed the very existence of EventLog().EntryWritten, the Seq Client for Windows Logins has proven to be extremely reliable, and we've been really happy with it. It does exactly what it's supposed to do - it logs events to Seq when an...
Ok, so we got through the date token and calculation updates. Now, I finally get to use this meme for something: We continue on with our march through turning Event Schedule for Seq into its own distinct and unique entity that works with other apps to provide a useful automation...
After posting the last release of Event Schedule earlier today, I gave some more consideration to the implications of how the date calculations work. The problem, as touched on in the post, is that not all date calculations are equal. If, on the first of January 2022, I expect that...
Yesterday's releases for Event Schedule introduced the ability to include simple date tokens in the Scheduled log message, Scheduled log description, and Scheduled log tags fields. These were based entirely on returning the current day, month, or year - but what if you want to reference last month, next month,...
Event Schedule is a bit of a different beast from the Event Timeout and Event Threshold apps. It's an app that will (for example) allow you to automatically create Jira tickets every month via a Seq log entry. This means that it can have difference needs from the other apps...
I've released a minor update to Seq.App.EventTimeout. While creating a new app that shares common functionality (more on that later!), I came across some edge cases for the handling of holidays. These cases should not "usually" have happened, and were only exposed by running a holiday test case near the...
Update After the original post, I tackled another item I'd been meaning to look at - being able to configure proxy settings for the Serilog Seq sink. Lurgle.Logging v1.2.3 now includes additional optional configurations for the Seq sink's proxy. This is particularly useful for console apps like Seq Reporter, to...
Lurgle Update Time! I've released an update to Lurgle.Alerting, the premier Lurgle Alerting library for Lurgling your Alerts! This release is about updating some of the older code that was brought into the library: FluentEmail largely suppresses exceptions when there are send failures. Lurgle was simply returning the FluentEmail.Core.Models.SendResponse.Successful bool...
I've released a small update to Lurgle.Alerting which adds automatic determination of the attachment content type using the MimeMapping library. I've raised the version to v1.2.0 to align with Lurgle.Logging's current releases. This specifically addresses an issue when sending attachments with MailKit as the SMTP sender. The FluentEmail implementation was...
Lurgle approach compared to Serilog Following on from the v1.2.0 multi-threaded correlation release, I thought about whether we could further improve how we interface with Lurgle.Logging. The general approach was to maintain a static interface to logging that would allow us to capture key properties for logging, that would provide nicely...
Multi-threaded correlation ids were not a thing Following on from my work on Seq.Client.WindowsLogins and the subsequent realisation that EventLog's EntryWritten event handler is bad and should feel bad, I contemplated whether I could apply some of my efforts to solve another issue that had been bugging me. Lurgle.Logging was...