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!
I could really use the functionality that would allow us to show the context of events around a single event in the log. For instance, I would like to easily show 10 minutes before and after an error event I have found. Is there a quick way to do this?
Posted by Ryan Adler 3 years ago
I have a local server of Seq, and a remote server where the app is deployed. I usually have to track the same signals in both servers, and I constantly find myself copying signals from each other manually. I'd like to be able to sync them as a batch, or import/export a set of them at once. Thanks in advance.
Posted by Lucio 3 years ago
Is there a way to see scopes in seq? e.g. ``` public class Program { static ILogger Logger { get; } = ApplicationLogging.CreateLogger<Program>(); public static void Main(string[] args = null) { ApplicationLogging.LoggerFactory.AddConsole(true); Logger.LogInformation( "This is a test of the emergency broadcast system."); using (Logger.BeginScopeImpl(nameof(Main))) { Logger.LogInformation("Begin using controller"); Controller controller = new Controller(); controller.Initialize(); Logger.LogInformation("End using controller"); } Logger.Log(LogLevel.Information, 0, "Shutting Down...", null, null); } } ```
Posted by Cengiz Ilerler 3 years ago
I know I can configure Seq to delete events of certain type. However what I would like to understand is it a good idea to use seq as permanent store of a certain type of message. My use case is audit log. I want to write my system log messages like Debug, Info, etc to Seq. However I also want to write DB audit messages for example if a certain table column was updated I want to retain its old value in Seq. I can do it from a implementation point of view but my questions are Is it a good Idea to do so? Can I create a retention policy which will never delete audit events but may delete all the other events?
Posted by Mudassar Jafer 3 years ago
Hi, What is mean by The free single-user license is enabled out-of-the-box. Does it mean that it's free for single user for lifetime or only for 30 days? What about the developer licence for single user and 5 users? Looking forward to your reply. Thanks, Sushil Kumar
Posted by Sushil Kumar 3 years ago
Seq server is been terminated randomly (once a week/month) with this error: "Application: seq.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF5D3A38E (000007FEF5B20000) with exit code 80131506." It seems that has to do with garbage collection dysfunction (see http://stackoverflow.com/questions/4367664/application-crashes-with-internal-error-in-the-net-runtime) The configuration of the server that hosts Seq is 20GB RAM, 4CPUs under VMware virtualization. Is this a known issue?
Posted by Nick Meggoudis 3 years ago
Hi, Just upgraded to Windows Server 2016 ... everything is running ... well ... almost ... I get this error when the server have been rebooted ... seems the service takes to long to return from the start method when booted. This is from the Event Log. * The Seq service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. * A timeout was reached (30000 milliseconds) while waiting for the Seq service to connect. If I then after the server have been running a little tries to start it again ... it runs. I know this is something in the start method you are using that takes to long to start on a fresh boot. Should be easy to fix I guess ... Let me know if you need more information ...
Posted by Mikael Syska 3 years ago
I have a spot in my code where I user Serilog to log some information about a DB call -- namely, the SQL being used and the parameter values. The parameter names and values are logged "as-is" -- i.e the parameters all start with an "@" sign. Here's a sample JSON of one of the log messages: { "@t": "2016-10-12T19:22:48.6078145Z", "@mt": "Sample Message", "@m": "Sample Message", "@i": "de16d090", "@@field": "15", "SQL": "select * from table where field = @field", "Application": "Test" } I'm finding that I can't query on the fields that start with an "@". For example, I wanted to find all queries on a particular table with a certain parameter value: `Contains(SQL, "table") && @field == "15"` Doesn't return anything. I've also tried `@@field == "15"` but that doesn't work either.
Posted by Patrick Steele 3 years ago
I've used the "Theme" settings and some CSS to make a visual differentiation between multiple SEQ instances but the browser title is still simply "Seq". If I have a bunch of browsers tabs open, all I see is "Seq". I couldn't find anywhere in the UI where the page title was configurable. I'd like to have something like "Seq - DEV" and "Seq - PROD". Is this currently possible? Thanks.
Posted by Patrick Steele 3 years ago
I've somehow managed to end up with two signals with the same name. Only one shows up in the events view, but both show up when adding an app. I've managed to rename the visible one so I can tell them apart, but it's bugging me that I have the phantom one in the dropdown list for setting up apps. Any idea how I can get rid of it? Cheers, Dan.
Posted by Dan Woolstencroft 3 years ago
From the seq log: 2016-09-29 16:30:35.412 +03:00 [Error] Error serving "http://localhost:5341/api/events/raw" (token: "72f948f32ac7444ea33d97448b5f33b7") Newtonsoft.Json.JsonReaderException: Input string '1.7976931348623157E+308' is not a valid decimal. Path 'Properties.OpenOrderEvent.Order.PercentOffset', line 1, position 1070. at Newtonsoft.Json.JsonTextReader.ParseNumber() at Newtonsoft.Json.JsonTextReader.ParseValue() at Newtonsoft.Json.JsonTextReader.Read() at Seq.MemoryEncoding.Serializer.ReadProperty(JsonTextReader json, List`1 properties, List`1 values, SharedAssets sharedAssets) at Seq.MemoryEncoding.Serializer.ReadObject(JsonTextReader json, SharedAssets shared) at Seq.MemoryEncoding.Serializer.ReadValue(JsonTextReader json, SharedAssets sharedAssets) at Seq.MemoryEncoding.Serializer.ReadProperty(JsonTextReader json, List`1 properties, List`1 values, SharedAssets sharedAssets) at Seq.MemoryEncoding.Serializer.ReadObject(JsonTextReader json, SharedAssets shared) at Seq.MemoryEncoding.Serializer.ReadValue(JsonTextReader json, SharedAssets sharedAssets) at Seq.MemoryEncoding.Serializer.ReadProperty(JsonTextReader json, List`1 properties, List`1 values, SharedAssets sharedAssets) at Seq.MemoryEncoding.Serializer.ReadObject(JsonTextReader json, SharedAssets shared) at Seq.MemoryEncoding.Serializer.ReadValue(JsonTextReader json, SharedAssets sharedAssets) at Seq.MemoryEncoding.Serializer.ReadProperty(JsonTextReader json, List`1 properties, List`1 values, SharedAssets sharedAssets) at Seq.MemoryEncoding.Serializer.ReadObject(JsonTextReader json, SharedAssets shared) at Seq.Server.Features.Filtering.FilterEntry.Includes(StorageEventCreationData evt) at Seq.Server.Web.Api.Events.RawEventsModule.Ingest() at Nancy.Routing.Route.<>c__DisplayClass4.<Wrap>b__3(Object parameters, CancellationToken context) The class trying to be serialized: public class Order { public double PercentOffset { get; set; } ... }
Posted by Bob Costas 3 years ago
I have the following set: After Delete 60 days All events Storage The event store is arranged in segments from 2015-10-18 to 2016-10-04. Out of 352.75 recorded days, 43.375 days totalling 481367 events are cached in RAM. The fast user will see that 352 is way more than 60 ... so why are all these events still on the disk ... I can see they are not in the memory ... but still ... overtime I will run out of space. Nothing to see in the Logs folder ... This is what I have in the "Extents" folder. C:\ProgramData\Seq\Extents -- 0,00 MB C:\ProgramData\Seq\Extents\2015-10-14_2015-10-21 -- 38,02 MB C:\ProgramData\Seq\Extents\2015-10-21_2015-10-28 -- 52,02 MB C:\ProgramData\Seq\Extents\2015-10-28_2015-11-04 -- 96,02 MB C:\ProgramData\Seq\Extents\2015-11-04_2015-11-11 -- 91,02 MB C:\ProgramData\Seq\Extents\2015-11-11_2015-11-18 -- 90,02 MB C:\ProgramData\Seq\Extents\2015-11-18_2015-11-25 -- 90,02 MB C:\ProgramData\Seq\Extents\2015-11-25_2015-12-02 -- 111,02 MB C:\ProgramData\Seq\Extents\2015-12-02_2015-12-09 -- 134,02 MB C:\ProgramData\Seq\Extents\2015-12-09_2015-12-16 -- 128,02 MB C:\ProgramData\Seq\Extents\2015-12-16_2015-12-23 -- 83,02 MB C:\ProgramData\Seq\Extents\2015-12-23_2015-12-30 -- 64,02 MB C:\ProgramData\Seq\Extents\2015-12-30_2016-01-06 -- 97,02 MB C:\ProgramData\Seq\Extents\2016-01-06_2016-01-13 -- 105,02 MB C:\ProgramData\Seq\Extents\2016-01-13_2016-01-20 -- 98,02 MB C:\ProgramData\Seq\Extents\2016-01-20_2016-01-27 -- 116,02 MB C:\ProgramData\Seq\Extents\2016-01-27_2016-02-03 -- 117,02 MB C:\ProgramData\Seq\Extents\2016-02-03_2016-02-10 -- 116,02 MB C:\ProgramData\Seq\Extents\2016-02-10_2016-02-17 -- 100,02 MB C:\ProgramData\Seq\Extents\2016-02-17_2016-02-24 -- 111,02 MB C:\ProgramData\Seq\Extents\2016-02-24_2016-03-02 -- 111,02 MB C:\ProgramData\Seq\Extents\2016-03-02_2016-03-09 -- 110,02 MB C:\ProgramData\Seq\Extents\2016-03-09_2016-03-16 -- 113,02 MB C:\ProgramData\Seq\Extents\2016-03-16_2016-03-23 -- 90,02 MB C:\ProgramData\Seq\Extents\2016-03-23_2016-03-30 -- 85,02 MB C:\ProgramData\Seq\Extents\2016-03-30_2016-04-06 -- 91,02 MB C:\ProgramData\Seq\Extents\2016-04-06_2016-04-13 -- 89,02 MB C:\ProgramData\Seq\Extents\2016-04-13_2016-04-20 -- 92,02 MB C:\ProgramData\Seq\Extents\2016-04-20_2016-04-27 -- 112,02 MB C:\ProgramData\Seq\Extents\2016-04-27_2016-05-04 -- 100,02 MB C:\ProgramData\Seq\Extents\2016-05-04_2016-05-11 -- 92,02 MB C:\ProgramData\Seq\Extents\2016-05-11_2016-05-18 -- 89,02 MB C:\ProgramData\Seq\Extents\2016-05-18_2016-05-25 -- 106,02 MB C:\ProgramData\Seq\Extents\2016-05-25_2016-06-01 -- 62,02 MB C:\ProgramData\Seq\Extents\2016-06-01_2016-06-08 -- 97,02 MB C:\ProgramData\Seq\Extents\2016-06-08_2016-06-15 -- 138,02 MB C:\ProgramData\Seq\Extents\2016-06-15_2016-06-22 -- 107,02 MB C:\ProgramData\Seq\Extents\2016-06-22_2016-06-29 -- 105,02 MB C:\ProgramData\Seq\Extents\2016-06-29_2016-07-06 -- 341,09 MB C:\ProgramData\Seq\Extents\2016-07-06_2016-07-13 -- 193,02 MB C:\ProgramData\Seq\Extents\2016-07-13_2016-07-20 -- 843,09 MB C:\ProgramData\Seq\Extents\2016-07-20_2016-07-27 -- 778,15 MB C:\ProgramData\Seq\Extents\2016-07-27_2016-08-03 -- 1.116,09 MB C:\ProgramData\Seq\Extents\2016-08-03_2016-08-10 -- 1.080,09 MB C:\ProgramData\Seq\Extents\2016-08-10_2016-08-17 -- 1.046,09 MB C:\ProgramData\Seq\Extents\2016-08-17_2016-08-24 -- 1.921,09 MB C:\ProgramData\Seq\Extents\2016-08-24_2016-08-31 -- 727,09 MB C:\ProgramData\Seq\Extents\2016-08-31_2016-09-07 -- 425,09 MB C:\ProgramData\Seq\Extents\2016-09-07_2016-09-14 -- 274,02 MB C:\ProgramData\Seq\Extents\2016-09-14_2016-09-21 -- 323,02 MB C:\ProgramData\Seq\Extents\2016-09-21_2016-09-28 -- 223,02 MB C:\ProgramData\Seq\Extents\2016-09-28_2016-10-05 -- 43,02 MB
Posted by Mikael Syska 3 years ago
Hi, We often times use the {@..} syntax when logging to log the json structure of an object. However I don't seem to be able to run a Contains query on it. No matter what I pass to the contains search it never finds anything, is this expected? Thanks, Cathal
Posted by Cathal Golden 3 years ago