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...
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...
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...
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...
Lurgle.Dates, EventX Trilogy, Seq Reporter, and Seq.App.Atlassian.Jira updated - Improved date expressions and line breaks
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...
Updates to Event Timeout, Event Threshold, and Event Schedule for Seq ... and introducing Lurgle.Dates!
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...
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...
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...
Browse all Topics
- Event Schedule
- Event Threshold
- Event Timeout
- EventX Trilogy
- File Transfer
- Outlook Profiler
- Public Holidays
- Remote Desktop
- Shell scripts
- Structured logging
- Terminal Server
- Unit Tests
- Windows Logins