I've previously said that I really like Handlebars implementations in other Seq apps, and I felt that there were opportunities to incorporate these into apps like Event Timeout. One of the things to be cautious of here, though, is that we might already be passing a Handlebars template as part...
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...
One of the really useful things with Seq.App.Opsgenie was that Nick Blumhardt had integrated Handlebars templates to the app, using Handlebars.NET. I liked it so much that, when I contributed to Ali Özgür's excellent Seq.App.Atlassian.Jira project, I carried it over. There's a few oddities in the JIRA REST API, and...
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...
Reporting all the things Seq Reporter is the command-line client that can be used to schedule reporting from your Seq structured logs. It drives a number of daily and monthly reports for us and overall, it works well. We just set our query config and time range, schedule it, and...
Grr ... Bugses. We hates them precious. There's nothing worse than code that doesn't quite work as intended. Well, that's not quite true. If you have 3 products with common code that doesn't work as intended, that's probably worse. Anyway, I noticed that Event Schedule fired prematurely on the last...
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,...