Issues, design discussions and feature roadmap for the Seq log server
Switch branches/tags
Nothing to show
Clone or download
Latest commit 03b1ab5 Sep 3, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
rfcs
0000-template.md
CODE_OF_CONDUCT.md
CONTRIBUTING.md Minimal CONTRIBUTING.md Jan 10, 2018
README.md

README.md

Seq Join the chat at https://gitter.im/datalust/seq Read Documentation

Welcome to the hub for issues, design discussions and the feature roadmap for Seq.

What is Seq?

Seq is a log server designed to speed up diagnostics in complex, asynchronous and distrubuted applications. It has a strong focus on structured logging, the idea that log events should carry important information in first-class properties.

Bugs and feature requests

If you think you may have found a bug in Seq, this is the place to report it. You can search existing issues or raise a new issue here.

Please also feel free to suggest features here. We will endeavor to consider and respond to every request we receive.

Documentation and support

The Seq online documentation has information on all aspects of Seq - it's a great place to start if you are configuring or using Seq for the first time.

If you need help with Serilog.Sinks.Seq, the Troubleshooting section of the sink documentation has some useful steps for tracking down common issues.

For more information or help with Seq, please feel free to visit our support forum or email support@getseq.net.

Feature roadmap

We maintain feature milestones to provide an outline of what to expect in upcoming releases.

Design discussions

For Seq 5.0 onwards, we have adopted an RFC ('request for comment') process so that design discussions for larger features can happen in the open, with full community involvement.

Accepted RFCs are recorded under /rfcs in this repository, while new proposals are discussed via pull requests.

To propose a feature, please create an issue to discuss it with the Seq development team. We will create RFCs and PRs where necessary.