Serilog can generate properties with numeric names ("0", "1", "2", ...), i.e. when logging standard .NET format strings. These can't be expressed in queries as they are interpreted as numeric literals.

I.e. %TEMP%\seq-{Date}.log

Distinguishing the log file according to the listening port or other instance-specific configuration is probably the way to go.

When looking at a log event, support pushing J to move to the next log event (i.e. collapse the current one, expand the next one) and K to move back to the previous.

Allow users to save a search and have it trigger a webhook when the search matches. This would be critical for having errors post to a company chatroom or hit up Pagerduty, for example.

But this is all I have configured:

...

and restarting Seq service didn't clear them.

Once an event is found, or if it is saved via a link, make it possible to drop filters and view that event in the context of the rest of the stream, possibly applying different filters to see what events came before and/or after it.

I import my debug logs into Seq, but I don't want to see those by default unless I explicitly look for them. It would be great to be able to set up a filter as my default, either by saving it on the server or by storing it in a cookie.

Rendering the message server-side we currently convert embedded structured objects into JSON; this doesn't present as nicely as Serilog's built-in formatting, let's use that.

Allowing an automatic export, either to text file or something else, would let me keep long-term historic logs.

Due to, I assume, serialization of a specific type, sometimes JSON properties are rendered as array indexes with no discernible meaning. I'm posting an example of some MassTransit probing log output via its InMemoryDiagnosticsProbe.

I also had this issue with a custom type, but some simple restructuring of the type eliminated the serialization issue. I'll post more details if I can dig the code history out.

E.g. based on http://nblumhardt.com/2014/01/seq-apps/ "sliding window" example

When attempting to export from the log, the Exception field does not have a button to mark for export nor does it automatically export.

Loading them from packages extracted to the filesystem would have the advantage of PDB support, over the current in-memory byte[] loading.

Building against a different version of either of these shouldn't prevent app loading.

• AD
• User-provided

From: #7

Not a military man here -- it'd be nice to have an option for standard time. E.g. 12:45:00PM

Hi guys, thanks for your project, amazing tool.
In our project we use only MongoDB, and any information about support MongoDB?

Allow multiple retention policies to be configured. The basic idea is that noisy events (e.g. debug logs) can be retained for a day or two, information/error events for a long (perhaps indefinite period).

• Query and/or view specified
• Retention time

To accompany this:

• Preserved events

Support automatically loading more feed items automatically when 3/4 of the height of the page has loaded.

Nor is it simple to select property values; the overlay hosting the tool buttons covers the right column of event information preventing mouse interactions.

Maybe allow a special mode of just copy/paste deployment with PDBs so that Attach to could be used to debug plugins?

No one likes installing things by hand these days ;) .... a simple NUPKG for our favourite automated deployment tool would be handy for a lot of folks.

E.g. Deploy.ps1 would uninstall the existing instance and invoke seq.exe install to set up a new one based on variables specified in the project.

I want to add other properties like Exception via the Serilog sink for Seq: I want these properties to appear in the data for the log entry but not in the message.

My particular use case is that I want to expose the result JSON from a RESTful web service when it responds with a 500 error code, for additional diagnostic information.

The following fails .WriteTo.Seq("http://localhost:5341", minimumLevel: LogEventLevel.Verbose) with a The best overload for 'Seq' does not have a parameter named 'minmumLevel'

Whats about to support web sockets for udp view logs? I know that seq have opportunity to enable page reload, but it would be more convenient (for udp view) to receive logs with sockets.

Either through ScriptCS/Roslyn (ideal) and/or uploaded assemblies, provide a way to fire custom code when events matching a query are detected.

• Guaranteed once-only execution
• Gentler than Rx to program against
• Reprocessing or configurable policy for failures
• Local debugging

• Init() method for reactors
• Persistence
• Restart instances when the app itself is upgraded
• Strongly typed event data
• Dispatching to multiple handler methods
• Dispatching to multiple in-process reactors
• Spawn()
• Quit()
• Link out to query for events raised by an app instance
• Link from event properties to the apps/instances that created them
• Rx-centric implementation option/API
• Direct logging back to the stream, side-stepping the network stack
• Simpler sharing - metadata describing properties, name, finding the main reactor type
• Validation of supplied properties

Attached a screenshot for this. Minor, but passing along.

With a filter active but no view, using Require -> View correctly prompts for a name and creates a new view, but the name is lost somehow.

Renaming the view with rename works fine.

Installing multiple instances of the Windows service requires unique service names.

If possible and in the proper way, a 'tailing' feature would be great. Either non or filter-based would be ideal. Being able to specify a refresh interval would also be very nice.

The inline view within message text is fine at a quick glance, but the detail view (after expanding an event) needs to be displayed more clearly. Syntax-highlighted JSON is probably the best option.

I think it would be great to create chocolatey package for seq.
It makes easier to manage and install it on servers (for example with boxstarter.org)

If you try to send events with no properties through the built-in email reactor it fails with a null reference exception.

I thinkthis has to do with the reactor assuming that the event .Data.Properties dictionary will not be null but if you send something like Log.Information("Website is down"); it is.

For pure convenience, it would be very handy to have existing filters and views accessible while one is active. You could possibly make the existing UI that indicates the active filter/view to be a drop down listing the existing ones.

Allow users to save a search and have it trigger a webhook when the search matches. This would be critical for having errors post to a company chatroom or hit up Pagerduty, for example.

In the log details text don't surround the details in the bootstrap label class as it makes the details more difficult to read.

Split out of #44.

Nor is it simple to select property values; the overlay hosting the tool buttons covers the right column of event information preventing mouse interactions.

When an event type gets added to a query/view, store with the query or view the message template text that corresponds to the event type.

Then, display the message template as a tooltip or elsewhere that the hash value appears.

For increased ease of use, it would be nice to allow the 'header' and 'tools' to be anchored while the log scrolls.

For the filtering and querying of data within Seq it would be help to have some sort of query language, perhaps seqql

In lieu of indexing, materialized views will allow matching events to be identified asynchronously/as they arrive. Searches can run over the persisted list of matching events, reducing search time.

A count of events-since-viewing might be maintained for users watching the view.

As it says on the box.

For my application's Verbose level logs, I really just want to retain them for 4 hours; I generate so many of them that it makes no sense to retain them longer.

At the moment instead, I just don't send them to Seq, but I would really love to be able to do so.

I realize you're in process with all of this... But, I'm just hacking away at a YouTrack exception issue creator. But I can't get it working with dependencies:

Setup:

Thanks.