<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to parse Radius log files into splunk? What the configuration required for props and transforms in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47289#M8982</link>
    <description>&lt;P&gt;alenseb,&lt;BR /&gt;
You should avoid the use of SHOULD_LINEMERGE = true and any break_before or break_after parameters. They're not required to do linebreaking correctly in almost all cases. Here's what should work for you:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;[radius]&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;BR /&gt;
TIME_FORMAT = %A %B %d %H:%M:%S %Y&lt;BR /&gt;
TIME_PREFIX = ^&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 40&lt;BR /&gt;
LINE_BREAKER = ([\r\n]+)\w{3}\s+\w{3}\s+\d{1,2}\s+\d{2}:\d{2}:\d{2}\s+\d{4}&lt;BR /&gt;
TRUNCATE = 99999&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
    <pubDate>Tue, 29 Sep 2020 13:31:15 GMT</pubDate>
    <dc:creator>beatus</dc:creator>
    <dc:date>2020-09-29T13:31:15Z</dc:date>
    <item>
      <title>How to parse Radius log files into splunk? What the configuration required for props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47286#M8979</link>
      <description>&lt;P&gt;Following is the Radius log file format that i have got. Now i need only few of the fields from each instance. Also you can see that 2 instances are separated by a blank line.&lt;BR /&gt;
So can anyone help with the configuration of prop.conf and transfroms.conf to get the desired output.&lt;/P&gt;

&lt;P&gt;Tue Aug  7 00:00:00 2012&lt;BR /&gt;
        User-Name = "xxxxxxxx"&lt;BR /&gt;
        NAS-Port = xxxxxxxx&lt;BR /&gt;
        NAS-IP-Address = xxxxxxxxu&lt;BR /&gt;
        Framed-IP-Address = xxxxxxxx&lt;BR /&gt;
        Filter-Id = " xxxxxxxx "&lt;BR /&gt;
        Class = " xxxxxxxx "&lt;BR /&gt;
        NAS-Identifier = " xxxxxxxx "&lt;BR /&gt;
        Acct-Status-Type = xxxxxxxx&lt;BR /&gt;
        Acct-Delay-Time = 0&lt;BR /&gt;
        Acct-Session-Id = " xxxxxxxx "&lt;BR /&gt;
        Acct-Authentic = RADIUS&lt;BR /&gt;
        Event-Timestamp = 1344286800&lt;BR /&gt;
        NAS-Port-Type = Ethernet&lt;BR /&gt;
        Calling-Station-Id = " xxxxxxxx "&lt;BR /&gt;
        NAS-Port-Id = " xxxxxxxx "&lt;BR /&gt;
        Service-Type = Framed-User&lt;BR /&gt;
        Framed-Protocol = PPP&lt;BR /&gt;
        Acct-Link-Count = 0&lt;BR /&gt;
        RB-Agent-Circuit-Id = " xxxxxxxx "&lt;BR /&gt;
        DSLForum-Agent-Circuit-Id = " xxxxxxxx "&lt;BR /&gt;
        DSLForum-Access-Loop-Encapsulation = ""&lt;BR /&gt;
        Timestamp = 1344286800&lt;BR /&gt;
        OSC-Service-Identifier = "DSLUsers"&lt;BR /&gt;
        Proxy-State = OSC-Extended-Id=40682&lt;BR /&gt;
        Timestamp = 1344286800&lt;/P&gt;

&lt;P&gt;Tue Aug  7 00:00:00 2012&lt;BR /&gt;
        User-Name = " xxxxxxxx "&lt;BR /&gt;
        NAS-Port = xxxxxxxx&lt;BR /&gt;
        NAS-IP-Address = xxxxxxxx&lt;BR /&gt;
        Framed-IP-Address = xxxxxxxx&lt;BR /&gt;
        Class = "44620232:04:"&lt;BR /&gt;
        NAS-Identifier = " xxxxxxxx "&lt;BR /&gt;
        Acct-Status-Type = Stop&lt;BR /&gt;
        Acct-Delay-Time = 0&lt;BR /&gt;
        Acct-Input-Octets = 6021&lt;BR /&gt;
        Acct-Output-Octets = 323749&lt;BR /&gt;
        Acct-Session-Id = " xxxxxxxx "&lt;BR /&gt;
        Acct-Authentic = RADIUS&lt;BR /&gt;
        Acct-Session-Time = 1348&lt;BR /&gt;
        Acct-Input-Packets = 53&lt;BR /&gt;
        Acct-Output-Packets = 3187&lt;BR /&gt;
        Acct-Terminate-Cause = User-Request&lt;BR /&gt;
        Acct-Input-Gigawords = 0&lt;BR /&gt;
        Acct-Output-Gigawords = 0&lt;BR /&gt;
        Event-Timestamp = 1344286800&lt;BR /&gt;
        NAS-Port-Type = Ethernet&lt;BR /&gt;
        Calling-Station-Id = " xxxxxxxx "&lt;BR /&gt;
        NAS-Port-Id = " xxxxxxxx "&lt;BR /&gt;
        Service-Type = Framed-User&lt;BR /&gt;
        Framed-Protocol = PPP&lt;BR /&gt;
        Acct-Link-Count = 0&lt;BR /&gt;
        Timestamp = 1344286800&lt;BR /&gt;
        OSC-Service-Identifier = "DSLUsers"&lt;BR /&gt;
        Proxy-State = OSC-Extended-Id=24386&lt;BR /&gt;
        Timestamp = 1344286800&lt;/P&gt;

&lt;P&gt;Thanks!!&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2012 11:10:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47286#M8979</guid>
      <dc:creator>alenseb</dc:creator>
      <dc:date>2012-08-30T11:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to parse Radius log files into splunk? What the configuration required for props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47287#M8980</link>
      <description>&lt;P&gt;I think all you need is props.conf - and frankly, I think that the Splunk default settings would work just fine.&lt;BR /&gt;
Splunk will automatically extract all the fields, as they are in name=value format. But here is a stanza for props.conf that should work as well. Note that this assumes that you set sourcetype=radius in the inputs.conf&lt;BR /&gt;&lt;BR /&gt;
And these props.conf entries belong on the indexer (or wherever the events are being parsed).&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[radius]
SHOULD_LINEMERGE = true
BREAK_ONLY_BEFORE_DATE = true
TIME_FORMAT = %A %B %d %H:%M:%S %Y
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 03 Sep 2012 00:13:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47287#M8980</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2012-09-03T00:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to parse Radius log files into splunk? What the configuration required for props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47288#M8981</link>
      <description>&lt;P&gt;Thanks for the input!!&lt;/P&gt;

&lt;P&gt;You can also try the following code, It works as well&lt;/P&gt;

&lt;P&gt;SHOULD_LINEMERGE = true &lt;BR /&gt;
REPORT-vievents = vievents_extractions&lt;BR /&gt;
BREAK_ONLY_BEFORE = ^(Sun|Mon|Tue|Wed|Thu|Fri|Sat)&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 12:22:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47288#M8981</guid>
      <dc:creator>alenseb</dc:creator>
      <dc:date>2020-09-28T12:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to parse Radius log files into splunk? What the configuration required for props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47289#M8982</link>
      <description>&lt;P&gt;alenseb,&lt;BR /&gt;
You should avoid the use of SHOULD_LINEMERGE = true and any break_before or break_after parameters. They're not required to do linebreaking correctly in almost all cases. Here's what should work for you:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;[radius]&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;BR /&gt;
TIME_FORMAT = %A %B %d %H:%M:%S %Y&lt;BR /&gt;
TIME_PREFIX = ^&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 40&lt;BR /&gt;
LINE_BREAKER = ([\r\n]+)\w{3}\s+\w{3}\s+\d{1,2}\s+\d{2}:\d{2}:\d{2}\s+\d{4}&lt;BR /&gt;
TRUNCATE = 99999&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:31:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47289#M8982</guid>
      <dc:creator>beatus</dc:creator>
      <dc:date>2020-09-29T13:31:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to parse Radius log files into splunk? What the configuration required for props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47290#M8983</link>
      <description>&lt;P&gt;Thanks That WORKS &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Apr 2017 00:08:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-parse-Radius-log-files-into-splunk-What-the-configuration/m-p/47290#M8983</guid>
      <dc:creator>sudoritz</dc:creator>
      <dc:date>2017-04-04T00:08:16Z</dc:date>
    </item>
  </channel>
</rss>

