<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/">
<channel>
<title>LogFusion RSS: Columns parsing method for journalctl</title>
<atom:link href="https://www.logfusion.ca/Discussions/RSS/?TopicID=018b7027-8b55-7756-a86e-6b5da7703621" rel="self" type="application/rss+xml" />
<link>https://www.logfusion.ca/Discussions/RSS/?TopicID=018b7027-8b55-7756-a86e-6b5da7703621</link>
<description>LogFusion RSS: Columns parsing method for journalctl</description>
<lastBuildDate>Thu, 30 Apr 2026 16:37:01 GMT</lastBuildDate>
<language>en</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>https://www.logfusion.ca/Discussions/RSS/?TopicID=018b7027-8b55-7756-a86e-6b5da7703621</generator>
<item>
<title>RE: Columns parsing method for journalctl</title>
<link>https://www.logfusion.ca/Discussions/View/columns-parsing-method-for-journalctl/?ID=018b7027-8b55-7756-a86e-6b5da7703621#3</link>
<pubDate>Sat, 28 Oct 2023 12:21:03 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.logfusion.ca/Discussions/View/columns-parsing-method-for-journalctl/?ID=018b7027-8b55-7756-a86e-6b5da7703621#3</guid>
<category>LogFusion</category>
<description><![CDATA[Hi and thank you for the answer.
Yes, this feature would be really great. The issue with basic separation is that not many traces use them this way. What would be something worth considering, is separating based on the number of characters, as traces headers often have a fixed number of these.
...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hi and thank you for the answer. <br/>
Yes, this feature would be really great. The issue with basic separation is that not many traces use them this way. What would be something worth considering, is separating based on the number of characters, as traces headers often have a fixed number of these.<br/>
<br/>
But regex would probably take care of that too, thank you!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Columns parsing method for journalctl</title>
<link>https://www.logfusion.ca/Discussions/View/columns-parsing-method-for-journalctl/?ID=018b7027-8b55-7756-a86e-6b5da7703621#2</link>
<pubDate>Fri, 27 Oct 2023 19:03:11 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.logfusion.ca/Discussions/View/columns-parsing-method-for-journalctl/?ID=018b7027-8b55-7756-a86e-6b5da7703621#2</guid>
<category>LogFusion</category>
<description><![CDATA[The column parser is really basic, it basically just looks for the separator character(s) you specify and then does a split on that. This journalctl log line isn't really great for that because it's just using spaces, and as you mentioned, some of the fields you want to break out into columns hav...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
The column parser is really basic, it basically just looks for the separator character(s) you specify and then does a split on that. This journalctl log line isn't really great for that because it's just using spaces, and as you mentioned, some of the fields you want to break out into columns have spaces in them as well.<br/>
<br/>
I think to do this LogFusion would need to support RegEx for column separators. I'm not sure how feasible that is to add, but I've put it on our feature request list <img src="https://www.logfusion.ca/MediaCommon/SVGs/FontAwesome/face-smile.light.svg" alt=":)" style="box-sizing:border-box;position:relative;overflow:hidden;vertical-align:middle !important;width:16px;height:16px;" HelpButtonData=":)" HelpButtonDataAlign="BelowMiddle" /><br/>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>Columns parsing method for journalctl</title>
<link>https://www.logfusion.ca/Discussions/View/columns-parsing-method-for-journalctl/?ID=018b7027-8b55-7756-a86e-6b5da7703621</link>
<pubDate>Fri, 27 Oct 2023 08:02:02 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.logfusion.ca/Discussions/View/columns-parsing-method-for-journalctl/?ID=018b7027-8b55-7756-a86e-6b5da7703621</guid>
<category>LogFusion</category>
<description><![CDATA[Hello,
I own a Logfusion licence for a while now, but each time I tried to use it, I somehow wasn;t able to figure out how to configure the parsing for the created columns... I was wondering whether someone more proficcient would know how to create a config for journalctl log parsing, where the ...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hello,<br/>
I own a Logfusion licence for a while now, but each time I tried to use it, I somehow wasn;t able to figure out how to configure the parsing for the created columns... I was wondering whether someone more proficcient would know how to create a config for journalctl log parsing, where the following columns are made:<br/>
<br/>
Date and time.<br/>
Host.<br/>
Log source.<br/>
Log message.<br/>
<br/>
Exemplary log line:<br/>
<br/>
Aug 15 00 55:36 abc xyz[301]: EID=24, ComponentIndex=1, Offset=6714368, Length=4096<br/>
<br/>
The separations are made with spaces, which are also included in the date.<br/>
I would appreciate all help.
</div>
]]></content:encoded>
</item>
</channel>
</rss>