Update - The specific cause of the below problem was subsequently identified as Event Timeout recently reaching 100 Nuget versions, which meant that that the new versions were on the next page of results. The Seq implementation of Nuget wasn't handling paged results correctly. Many thanks to Joel Verhagen from...
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...
EventX Trilogy With the work that I've done on my Seq apps (specifically Event Timeout and Event Threshold), I've managed to build quite a robust and versatile date and time system which can be set for some complex scenarios. The properties built into these apps are extensive, with an ability...
A lot of scripting can be involved in running an IT operation. While your business applications may be logging to Seq, is it any less important that you have visibility of key scripts? What happens when they fail and endanger your critical SLAs? At a fundamental level, logging is really...
"Tell us when events fall below a threshold, between X and Y times..." Seq has an innate ability to alert based on a simple count of events in a signal, using dashboard widgets with alerts. We use that for a number of alerts, including detection of possible upstream outages -...
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...
I've been working to build a Seq appender for Log4j 2, which will allow Java applications that use Log4j to send events to Seq. While I've been previously been able to configure Log4net instances to send to Seq using Seq.Client.Log4net and Log4net.Async, there seems to be a lack of an...
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