Welcome to the Seq documentation hub. You'll find comprehensive guides and documentation to help you start working with Seq as quickly as possible, as well as support if you get stuck. Let's jump right in!
docker-compose.yml ```yml version: "2" services: seq: image: 'datalust/seq:5.1.3004' restart: always container_name: seq_log_server environment: ACCEPT_EULA: Y BASE_URI: ${BASE_URI}:${HOST_HTTP_PORT} SEQ_API_CANONICALURI: ${SEQ_API_CANONICALURI}:${HOST_HTTP_PORT} volumes: - $HOST_PATH_TO_SEQ:/data - ./settings.seqbac:/settings.seqbac ports: - $HOST_HTTP_PORT:80 - $HOST_INGESTION_PORT:5341 ``` Example of one that doesn't show ui. ```bash -bash-4.2$ docker-compose up Creating network "seq_default" with the default driver Creating seq_log_server Attaching to seq_log_server seq_log_server | ──────────────────────────────────────── seq_log_server | Seq ♦ Machine data, for humans. seq_log_server | ─────────── © 2019 Datalust Pty Ltd ──── seq_log_server | seq_log_server | Running as server; press Ctrl+C to exit. seq_log_server | seq_log_server | [23:22:31 INF] Seq "5.1.3004" running on OS "Linux 3.10.0-1062.9.1.el7.x86_64 #1 SMP Fri Dec 6 15:49:49 UTC 2019" seq_log_server | [23:22:32 INF] Seq listening on ["http://localhost/", "http://localhost:5341/"] seq_log_server | [23:22:32 INF] Seq using canonical URI "REDACTED" seq_log_server | [23:22:32 INF] Opening document store "/data/Documents/documents.lmdb" seq_log_server | [23:22:32 INF] Opening event store at "/data/Extents" seq_log_server | [23:22:32 INF] Available storage engines in order of preference are ["FLARE"] seq_log_server | [23:22:32 INF] Cache warm-up is required seq_log_server | [23:22:32 INF] Storage subsystem available seq_log_server | [23:22:32 INF] Started "Seq.Apps.GenericHost" process 150 for "appinstance-139" seq_log_server | [23:22:32 INF] Started "Seq.Apps.GenericHost" process 156 for "appinstance-315" seq_log_server | [23:22:32 INF] Started "Seq.Apps.GenericHost" process 161 for "appinstance-346" seq_log_server | [23:22:32 INF] Started "Seq.Apps.GenericHost" process 163 for "appinstance-364" seq_log_server | [23:22:32 INF] Started "Seq.Apps.GenericHost" process 166 for "appinstance-381" seq_log_server | [23:22:32 INF] Started "Seq.Apps.GenericHost" process 168 for "appinstance-394" seq_log_server | [23:22:40 INF] Deduplication buffer renewed on reaching {"Schemata": 99, "Strings": 103401} seq_log_server | [23:22:49 INF] Deduplication buffer renewed on reaching {"Schemata": 184, "Strings": 104604} seq_log_server | [23:22:59 INF] Deduplication buffer renewed on reaching {"Schemata": 193, "Strings": 109754} seq_log_server | [23:23:07 INF] Deduplication buffer renewed on reaching {"Schemata": 197, "Strings": 104219} seq_log_server | [23:23:18 INF] Deduplication buffer renewed on reaching {"Schemata": 194, "Strings": 107967} ``` Example of one that works ```bash -bash-4.2$ docker-compose logs -f Attaching to seq_log_server seq_log_server | ──────────────────────────────────────── seq_log_server | Seq ♦ Machine data, for humans. seq_log_server | ─────────── © 2019 Datalust Pty Ltd ──── seq_log_server | seq_log_server | Running as server; press Ctrl+C to exit. seq_log_server | seq_log_server | [23:38:52 INF] Seq "5.1.3004" running on OS "Linux 3.10.0-1062.9.1.el7.x86_64 #1 SMP Fri Dec 6 15:49:49 UTC 2019" seq_log_server | [23:38:53 INF] Seq listening on ["http://localhost/", "http://localhost:5341/"] seq_log_server | [23:38:53 INF] Seq using canonical URI "REDACTED" seq_log_server | [23:38:53 INF] Opening document store "/data/Documents/documents.lmdb" seq_log_server | [23:38:53 INF] Opening event store at "/data/Extents" seq_log_server | [23:38:53 INF] Available storage engines in order of preference are ["FLARE"] seq_log_server | [23:38:53 INF] Cache warm-up is required seq_log_server | [23:38:53 INF] Storage subsystem available seq_log_server | [23:38:53 INF] Started "Seq.Apps.GenericHost" process 141 for "appinstance-139" seq_log_server | [23:38:53 INF] Started "Seq.Apps.GenericHost" process 146 for "appinstance-315" seq_log_server | [23:38:53 INF] Started "Seq.Apps.GenericHost" process 148 for "appinstance-346" seq_log_server | [23:38:53 INF] Started "Seq.Apps.GenericHost" process 158 for "appinstance-364" seq_log_server | [23:38:53 INF] Started "Seq.Apps.GenericHost" process 161 for "appinstance-381" seq_log_server | [23:38:53 INF] Started "Seq.Apps.GenericHost" process 164 for "appinstance-394" seq_log_server | [23:39:02 INF] Deduplication buffer renewed on reaching {"Schemata": 99, "Strings": 103401} seq_log_server | [23:39:12 INF] Deduplication buffer renewed on reaching {"Schemata": 184, "Strings": 104602} seq_log_server | [23:39:21 INF] Deduplication buffer renewed on reaching {"Schemata": 193, "Strings": 109751} seq_log_server | [23:39:29 INF] Deduplication buffer renewed on reaching {"Schemata": 197, "Strings": 104220} ``` NOTE: This happened after I had to move the docker-compose.yml file from one directory to another. Before I did this I stopped and removed the old container. I left the volume because I wanted to keep my logs.
Posted by Shane Swayney about a year ago
Hi, We have a project where the major part will be done in C# and a small part will be in C++. For C# the Serilog logging to Seq works great. But I would also like to integrate some logging from the C++ part. Are there already workings solution to log to Seq from C++? Thanks and best regards, Andrea
Posted by Andrea about a year ago
I called Log debug like this: _logger.LogDebug("Requesting Combined Pdf", requestToLog); I expected to see my requestToLog object in seq, but it wasn't there. If call LogDebug Like this: _logger.LogDebug("Requesting Combined Pdf {requestToLog}", requestToLog); It does show up in seq in both the message an in the seq event properties. Is there some extra step I need to take to get the log params to show up without adding them to the message?
Posted by Dan Davis about a year ago
Is there a way to configure the seq sink in a way that it buffers a number of log messages that will be send to the seq server if an error is logged. The Idea behind this request is to reduce traffic by only sending some debug messages, when errors happen. Example: try { Log.Debug("SQL Statement {sql}", sql); // execute SQL } catch (exception ex) { Log.Error(ex, "Error Executing Sql"); } In this example the Seq Sinks should buffer the Debug log message and send it to the server, if Log.Error is called.
Posted by Volkmar about a year ago
Hello, I have been using Seq 5.1 without any problems for quite a long time. I was very happy to read on your blog that you improved performance of 2020.1 so I tried to upgrade in hopes to see better performance. But instead I have seen lot of failing queries, failing ingestions and at the end also complete crash of Seq. I tried to look into logs and I have found lot of OutOfMemory exceptions. Now, to continue using Seq, I had to downgrade to 5.1 - unfortunately no data is visible there anymore :( (If I use 2020.1 I see it, so I guess the data format between these two is incompatible). Oh, not to forget, I'm using docker distribution, and I have configured --memory-limit.
Posted by David K. about a year ago
I'm not sure if someone attempted to activate an authenticator or what happened, but we are now in a state where only one individual being able to access seq, and that's via AD authentication. We didn't have this problem before. An individual was able to access the site without having to log in. What do I need to do to revert the Seq instance back into single user mode without losing data?
Posted by Dennis Judd about a year ago
Hi, Im trying to understand how data gets stored once it arrives into the server. does it get written to disk first and than moved to RAM? or is it the other way around where the data first gets stored into RAM, and once the configured capacity is reached it than flushes the data to disk?
Posted by Shiko about a year ago
Why does SEQCLI allow the same API key and token to be created more than once? Is there a way to force it to error if the keyname (title) or token already exists? example: seqcli apikey create --title carltest --token carltest12345678 results in apikey-62 carltest seqcli apikey create --title carltest --token carltest12345679 results in apikey-68 carltest seqcli apikey create --title carltest --token carltest12345679 results in apikey-69 carltest
Posted by Carl about a year ago
Hi, I use the Seq.Syslog.Input to get and ingest syslog events from 3rd party to our log system on Seq. I was glad to see how fast and easy is its integration. However, it supports only UDP which is considered to be lossy and unreliable. How far are we from support for syslog on TCP? is it planned for the near future? regards Amitai
Posted by Amitai Shaveh about a year ago
Hi there. I've setup Seq with my trial license and from what I can tell I have everything configured. I added my license in the UI and it says its valid. I was able to run the bind-ssl command and set the listenUris. I know it works to some degree because I'm able to access https://localhost and it complains that the cert doesn't match the URL which I would expect. I'm using an Azure VM so I've added firewall exceptions in the Azure portal and in the Windows firewall. I'm certain my firewall exceptions are ok because I did the same for ICMP traffic to see if I could ping the server and that works.
Posted by Troy Hughes about a year ago
Hi. I'm using NLog with the Seq target and I was surprised to discover that the NLog target ignores `{"MinimumLevelAccepted":"Information"}` responses sent out by the server. It was going to be one of the most compelling features of Seq that I could dynamically control logging level of clients apps per API Key on the server side. And, according to Wireshark, the server is doing its job. However, the NLog target does not seem to take any notice of the hints being sent out by the server. Is this something that just hasn't been implemented, or is there something else I need to configure?
Posted by Tim Long about a year ago
I upgraded Seq 4.2 to seq 2020.1. After installation and configuring seq from Administration. I am facing following Error. Seq is unavailable. Failed to initialize storage: An exception was thrown while activating seq.server.Data.Permalinks.Migrations.PermalinkExternalToEmbeddedEvents Can you please guide me how to upgrade seq. I am planning to upgrade to my critical machine, but if this is happening, I am afraid I can loose my existing logs.
Posted by Kamran Asim about a year ago
I'm on my way to move our Seq to a new server and I'm trying to figure out which system requirements that we need, I read in the documentation that "1 GB RAM per 1.5 million retained events" is a good starting point. Where to I view how many retained events we have? Thanks in advance.
Posted by J Jansson about a year ago
We have had a problem with seq over the last few versions and it's getting worse. Every now and then, the Seq interface stops responding and we can't access it for several minutes. Once we manage to get back in it seems that ingestion has been working fine all along. We're currently running 2020.1 on ubuntu but this problem has been with us for several months. At first we thought it was our server that was underpowered or something related to our hosting provider. But we have changed to a different provider and beefed up the server significantly. We have fiddled with memory configuration to no avail. Not really sure how to attack the problem at this point.
Posted by Kristoffer Lindvall about a year ago