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!
For reasons that seemed better at the time, I have some properties with a dot in the name. For example: @Properties["Request.StopWatch"] > 10000 Which works fine. However I do not know the syntax for SQL like queries, e.g.: select @Properties['Request.StopWatch'] from stream limit 1000
Posted by N Armer 3 years ago
I have now dozens of applications logged by Seq and I have created a lot of signals (some for using for apps (for sample e-mail on exception) and some for filter the events quickly.) It should be nice if we can have hierarchy in the signals. Not Something too complicated, but just a 2 levels hierarchy. Folders with inside some signals, and when we must select a signal (in an app instance config), the name of the signal should be "Folder - Signal". I think it's not necessary to have more levels. Regards Valentin
Posted by Valentin Bornand 3 years ago
Hey Nick. It's actually a bug report ;-) I just ran the latest installer (3.2.16) on a machine without Seq, and on the last step I mashed the button to browse to Seq. The installer closed and Explorer opened, but localhost:5341 did not. It's ok though I figured out the port number myself. Cheers Ben
Posted by Ben Scott 3 years ago
Hey, How can I provide durable logging by specifying a JSON file that's accessible by multiple threads? Now by default the bufferfile is only accessible by one thread, but my application can log from different threads using the same logging instance. Any idea on how to solve this problem? Thanks!
Posted by Stijn De Sloovere 3 years ago
Hey, When I enable durable logging and try to log an event, using Serilog, that exceeds the systems defined event size, the event is still logged to the JSON file and Serilogs SelfLog reports an error. That part is fine by me but then Serilog continuously tries to write the event to Seq which fails every time and therefor Serilog keeps posting the same message (" RequestEntityTooLarge: ....) to the SelfLog. I would expect that the serilog wouldn't keep on trying to log the oversized event in the JSON file to Seq. Is there any way to solve this? Thanks!
Posted by Stijn De Sloovere 3 years ago
Hello, I have a server with many applications, and I want to use Seq forwarder on it. My applications use api keys, but the seq server don't receive them, and if I put one in the seq forwarder configuration, all my events have the same key. I understand that the forwarder don't have the list of the api keys and cannot filter the requests, but it should forward the api keys to the seq server. The "applied properties", "filter", and "minimum level" are great and should be available even with the forwarder.
Posted by Valentin Bornand 3 years ago
We have been running Seq in a production manner for a few weeks and noticed that our retention policies never worked. As a test, we set an aggressive policy to delete all events after 1 day. Disk storage continues to grow, and the Diagnostics tab tells us we have something like 2.25 recorded days (depending on when we check). Eventually, we run out of disk space and get hosed. I have tried: - simple service restart - server reboot - deleting the entire data folder (Extents, AppData, Packages, etc) and doing service restart None of these things have worked. We are running on Windows Server 2012 R2 and the service runs as "Local System". Am I missing something? Is there anything I can do/run to help figure this out? Thank you!
Posted by Phil Johnson 3 years ago
I need to log REALLY BIG xml payloads (soap request/response messages). In general, most of them are not that big and log to Seq just fine. However, some of them are as large as 1.5MB and they are not logging. Looking at the ingestion log I see the message: Rejecting payload from "::1" due to oversized event; first 1024 chars of 1506249 Is there a way to increase the maximum event size?
Posted by Patrick Steele 3 years ago
Seq is exposed as localhost:5341, but I want it to be exposed as seq.domain.com. I'm running on a VM in azure. I tried adding it to the URI to the seq.json, but still couldn't access it (added to hosts file). I also tried doing a reverse proxy through IIS, also failed. Really want to get it to work :)
Posted by Dan Shapir 3 years ago
So I've setup a separate VM in azure and bound port 443 to seq, from my local machine I can write to it just fine since I've added my own CA to my machines trusted root cert store. Once I deploy to azure I can't log. I'm guessing it's since I'm using a self-signed cert and I can't install certs to the trusted root store for azure websites. And I really want my logging application to run in an azure website. To the question: is it possible to configure serilog to not validate the certificate chain? Perhaps point out my own request handler where I set the validation callback to always return true?
Posted by Ajden 3 years ago