Seq Apps

Since structured events are so easy to process, you naturally want to start reacting to them. It might be as simple as sending an email to operations when an integration point is slow, or to the support team if a site crashes during a particular transaction.

Seq Apps integrate with collaboration platforms like Slack or Microsoft Teams, pass errors to systems like issue trackers, or interact with different kinds of devices like pagers. With a little more code, Seq apps can find patterns, detect trends or track an event’s frequency.

Input apps are used to extend Seq to support new log sources like queuing systems, and protocols like GELF and Syslog.

Apps are managed from Settings > Apps in the Seq UI.

To get started you'll need to find some apps to install.

Finding Seq Apps

There are several Seq Apps available on the public NuGet feed. You can search for the seq-app NuGet tag to list apps developed both by the makers of Seq and other users.

🚧

Seq apps are plug-ins that run with full access in the Seq process. It's important to only install apps from sources you trust.

To install an app, you need its package id - the title shown on the package's page, like Seq.App.EmailPlus.

Installing and Configuring the Email+ App

This app supports simple formatted email with {{Handlebars}} templates for rendering event properties into the subject and body.

Installing the Package

The package id of this app is Seq.App.EmailPlus. In Seq, go to settings > Apps and select Install from NuGet.

You'll be presented with a dialog requesting the package id. Type it in, and press Install.

After a short wait, the app will appear in the Apps list. To use the app, configure it by creating an instance.

App instances

To the right of the app's name in the app list, select the link titled Start a new instance.... This will present a configuration page where settings can be applied to the app.

Here’s how configuration for the Email+ app looks:

The top section is where the instance is given a name, and the source of events is configured. Un-ticking the Only send events manually box will let you choose a signal to run the app on.

Further down, in the Settings section, you see some pretty typical fields for configuring email.

Allowing setting overrides

Each setting in an app instance has a button on the right-hand-side to allow or disallow manual invocations and alerts to override the setting value:

If a setting allows overrides, the value set on the app instance is used as a default for that setting when the instance is invoked.

🚧

If a setting supports overrides then its value will be visible to any user when configuring alerts or sending events to the app. Password fields are an exception and are never visible.

Sending events to app instances

Once the app is saved, you can send events to it using the Send to app menu on an event's detail view:

See the section on Signals to learn how to create filters that can be used to select events for the app automatically. Supported settings on the app can be overridden before the event is sent:

Behind a web proxy

To install apps from a NuGet feed when a web proxy is in use, the proxy details must be recorded in the NuGet.config file at:

C:\Windows\System32\config\systemprofile\AppData\Roaming\NuGet\NuGet.config

If Seq is running under an account other than Local System, replace systemprofile in the path with the account name.

The HTTP_PROXY and HTTPS_PROXY values are set as follows:

<config>
  <add key="HTTP_PROXY" value="http://xxx.xxx.xxx.xxx:nn" />
  <add key="HTTPS_PROXY" value="http://xxx.xxx.xxx.xxx:nn" />
</config>

After configuring the proxy, restart Seq so that the settings take effect.