https://redmine.openinfosecfoundation.org/https://redmine.openinfosecfoundation.org/favicon.ico?17011170022018-11-12T18:07:33ZOpen Information Security FoundationSuricata - Feature #2671: Add Log level to suricata.log when using JSON typehttps://redmine.openinfosecfoundation.org/issues/2671?journal_id=104092018-11-12T18:07:33ZEric Urban
<ul></ul><p>It is true that error level messages do have extra info added, so it would be possible to alert on errors. However, it seems nice to have the log level always available.</p>
<p>An example of an error event:<br /><pre>
{"timestamp":"2018-11-12T12:02:39.566766-0600","event_type":"engine","engine":{"error_code":43,"error":"SC_ERR_NO_RULES_LOADED","message":"Loading signatures failed."}}
</pre></p>
<p>It still seems to me it would be appropriate to have something like:<br /><pre>
{"timestamp":"2018-11-12T12:02:39.566766-0600","log_level":"Error","event_type":"engine","engine":{"error_code":43,"error":"SC_ERR_NO_RULES_LOADED","message":"Loading signatures failed."}}
</pre></p> Suricata - Feature #2671: Add Log level to suricata.log when using JSON typehttps://redmine.openinfosecfoundation.org/issues/2671?journal_id=105862018-12-03T17:26:09ZEric Urban
<ul></ul><p><a class="external" href="https://github.com/OISF/suricata/pull/3563">https://github.com/OISF/suricata/pull/3563</a></p> Suricata - Feature #2671: Add Log level to suricata.log when using JSON typehttps://redmine.openinfosecfoundation.org/issues/2671?journal_id=105892018-12-04T08:51:14ZVictor Julienvictor@inliniac.net
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Target version</strong> set to <i>4.1.1</i></li></ul>