<?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: Indexing FreeRadius Accounting Logs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303698#M57340</link>
    <description>&lt;P&gt;From the FreeRadius Wiki it looks like you can't change the separated lines to a single line.  Here is a web page that gives the information on what you CAN do:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://wiki.freeradius.org/config/Logging"&gt;FreeRadius Config/Logging&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;So it looks like  you will have to accomplish that through the transforms and props configs. But, is that what you want to do? What would that accomplish? Are you just having problems with the event and parsing, because I would think that you could still do all that and just leave the data on multiple lines.&lt;/P&gt;</description>
    <pubDate>Thu, 30 Mar 2017 17:22:34 GMT</pubDate>
    <dc:creator>cpetterborg</dc:creator>
    <dc:date>2017-03-30T17:22:34Z</dc:date>
    <item>
      <title>Indexing FreeRadius Accounting Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303693#M57335</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am indexing FreeRadius Accounting logs from &lt;CODE&gt;/var/log/radius/radacct/&lt;/CODE&gt; directory.&lt;BR /&gt;
Below is an image of a sample log in Splunk:&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/2709i0CD31A989DCEC41E/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Issues/Requests:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;The log splits before the &lt;CODE&gt;TimeStamp = &amp;lt; &amp;gt;&lt;/CODE&gt;field in the log, creating two logs on Splunk instead of one (shown in a red box in the image)&lt;/LI&gt;
&lt;LI&gt;How can I change the &lt;CODE&gt;host=&lt;/CODE&gt; on Splunk to map to field &lt;CODE&gt;"Tunnel-Server-Auth-Id:0"&lt;/CODE&gt; in the log itself, so it can be searched via hostname?&lt;/LI&gt;
&lt;LI&gt;Is there a way for the log to have a single space between each field, instead of a new line?&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Thanks! I'd love input on these and am absolutely open to reading through links/documentation anyone shares to find the answer.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2017 20:59:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303693#M57335</guid>
      <dc:creator>mhassan24</dc:creator>
      <dc:date>2017-03-28T20:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing FreeRadius Accounting Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303694#M57336</link>
      <description>&lt;P&gt;1- Looks like you just have to set up your &lt;CODE&gt;props.conf&lt;/CODE&gt; so that the timestamp is ignored, or the "Fri..." is ignored as the date by defining what the data should look like, AND you should do the event breaker as well, which I would set to something like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;^\w\w\w\s\w\w\w\s\d\d\s\d\d:
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;2- &lt;CODE&gt;props.conf&lt;/CODE&gt; and &lt;CODE&gt;transforms.conf&lt;/CODE&gt; is the way that I would do it, but there may be an easier way. &lt;EM&gt;Anyone else want to chime in here?&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;3- That would be the way the log is created, or you might be able to do it again in &lt;CODE&gt;props.conf&lt;/CODE&gt; and &lt;CODE&gt;transforms.conf&lt;/CODE&gt;. I don't know how to make the radius log format be different. &lt;/P&gt;

&lt;P&gt;if you want to know more about the props.conf and transforms.conf ways, comment here to let me know and I'll add some more, or others can help out with it too. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; #1 should be easy enough to do if you have access. Do you have access to the props.conf on the indexers, or are you using cloud?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2017 21:20:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303694#M57336</guid>
      <dc:creator>cpetterborg</dc:creator>
      <dc:date>2017-03-28T21:20:52Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing FreeRadius Accounting Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303695#M57337</link>
      <description>&lt;P&gt;En el props.conf debes de poner el formato que desees poner&lt;/P&gt;

&lt;P&gt;Translation: In the props.conf you have to put the format that you want to put&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2017 21:24:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303695#M57337</guid>
      <dc:creator>medveleyenet</dc:creator>
      <dc:date>2017-03-28T21:24:14Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing FreeRadius Accounting Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303696#M57338</link>
      <description>&lt;P&gt;Thanks! I do recognize where I might change it, along with &lt;CODE&gt;transforms.conf&lt;/CODE&gt;, but I was hoping for a more definitive reading or guide to understand my particular problem.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2017 01:13:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303696#M57338</guid>
      <dc:creator>mhassan24</dc:creator>
      <dc:date>2017-03-29T01:13:07Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing FreeRadius Accounting Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303697#M57339</link>
      <description>&lt;P&gt;Thanks cpetterborg!&lt;/P&gt;

&lt;P&gt;Still stuck on 3) unfortunately. IF you stumble upon something, please do share!&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 16:53:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303697#M57339</guid>
      <dc:creator>mhassan24</dc:creator>
      <dc:date>2017-03-30T16:53:13Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing FreeRadius Accounting Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303698#M57340</link>
      <description>&lt;P&gt;From the FreeRadius Wiki it looks like you can't change the separated lines to a single line.  Here is a web page that gives the information on what you CAN do:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://wiki.freeradius.org/config/Logging"&gt;FreeRadius Config/Logging&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;So it looks like  you will have to accomplish that through the transforms and props configs. But, is that what you want to do? What would that accomplish? Are you just having problems with the event and parsing, because I would think that you could still do all that and just leave the data on multiple lines.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 17:22:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-FreeRadius-Accounting-Logs/m-p/303698#M57340</guid>
      <dc:creator>cpetterborg</dc:creator>
      <dc:date>2017-03-30T17:22:34Z</dc:date>
    </item>
  </channel>
</rss>

