Seq Client for Windows Logins v1.1.3 - Improved support for OpsGenie and Jira integrations!

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 interactive user logs into a given server.

This works quite well with a Seq app like Seq.App.Opsgenie or Seq.App.Atlassian.Jira. Recently I've been engaged with the authors in making some updates to these applications and my own, to make them interoperate better. I plan to write about the JIra enhancements soon, but the net result is that apps such as Event Schedule can log properties that are automatically picked up by these apps, such as responder/assignee, tags, priority, and so on. This drives better integration with the upstream application, along with allowing for better structured properties and more detailed templates!

Seq Client for Windows Logins is a great candidate to provide these kind of properties to a Seq app. We want to raise a Jira ticket or an Opsgenie alert if a login happens, and the opportunity arises to allow Seq.Client.WindowsLogins to tell those apps who the ticket/alert should be assigned to, what tags and priority to use, etc.

Accordingly, I've now updated the service to include configuration items for the following properties:

  • ProjectKey
  • Responders
  • Priority
  • Tags
  • InitialTimeEstimate
  • RemainingTimeEstimate
  • DueDate

These are static configuration items within the Seq.Client.WindowsLogins.exe.config configuration file, and are not validated - whatever you set is what will be logged. If the property is not valid for the Opsgenie or Jira app, you may see a failure in the debug logs for those apps. 

I have also added the EventTimeLong and EventTimeShort properties. These are formatted strings of the EventTime property, as a convenience for inclusion in the Handlebars templates for both the Jira and OpsGenie apps.

An EventTime of 2021-07-29T09:58:42.3749981+10:00 will result in the following locale-dependent properties:

  • EventTimeLong - Thursday, 29 July 2021 9:58:42 AM
  • EventTimeShort - 29/07/2021 9:58:42 AM (for en-AU, but US would be 07/29/2021 9:58:42 AM)

and you can readily reference these as {{EventTimeLong}} or {{EventTimeShort}} in your templates, as with any property.

This provides more control over your integrations, while cutting down on the number of OpsGenie or Jira instances needed - you can easily set up signals that will pick up multiple applications with valid properties to drive a single app instance.

You can download Seq.Client.WindowsLogin v1.1.3 from the below fancy links!

Seq Client for Windows Logins Latest Version
Seq Client for Windows Logins Total Downloads




You may also like:

Detecting logins like a boss- the Seq Client for Windows Logins

The Journey Begins ... This was a journey that began with an existing, and really useful, Seq application. I've had some mileage in the past from the Seq.Client.EventLog service. I've used it to monitor the Windows Application event log for new logs from a specific source, send them to Seq,...

Passing Priority, Responder, and Tags from Seq to OpsGenie!

Building up the Seq app for OpsGenie Over the past few weeks, I've worked with Nicholas Blumhardt to enhance the Seq.App.OpsGenie application for Seq. Nicholas is the founder and CEO of Datalust, the company behind Seq, and is very active in the community - which is awesome, and has meant that...

Seq.Client.Log4j - Seq appender for Log4j 2

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...