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

 

 

Comments

You may also like:

Setting Jira Priority and Labels with OpsGenie Edge Connector

The default OpsGenie integration with Jira Service Management has a puzzling omission when it comes to their OpsGenie Edge Connector integration - it doesn't send Priority or Tags. This means that tags won't pass through as labels, and the priority will be at the default. My ideal is that the...

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

Speaking broadly - at least for an always-online server - the logon types of interest are 2 (Interactive) and 10 (Remote Interactive). In order to pick these up, we need to get up close and personal with the event log to extract the event log properties. Doing this quickly turned...