<?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 do I analyze web access logs in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/how-do-I-analyze-web-access-logs/m-p/476256#M122531</link>
    <description>&lt;P&gt;If it's SAS Logs then the SAS Environment Manager provides quite a bit for such tasks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For other logs: I agree with you that this is a problem which people must have solved already but whenever I actually need something specific I end up not finding anything pre-fabricated where amending the code for my specific use case wouldn't take me as long as writing new (and much simpler) code from scratch.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking at the log layout you've posted: That's so nicely structured that it shouldn't be too hard to parse out what you need.&lt;/P&gt;</description>
    <pubDate>Sun, 08 Jul 2018 03:55:03 GMT</pubDate>
    <dc:creator>Patrick</dc:creator>
    <dc:date>2018-07-08T03:55:03Z</dc:date>
    <item>
      <title>how do I analyze web access logs</title>
      <link>https://communities.sas.com/t5/SAS-Programming/how-do-I-analyze-web-access-logs/m-p/475182#M122173</link>
      <description>&lt;P&gt;We have some web logs that we need to analyze for site traffic. I know I could write some DATA step code to parse through these logs and pick out relevant data, but I'm sure there must be some code or macros that can do this already. An example of the raw log data is below:&lt;/P&gt;
&lt;P&gt;127.0.0.1 - - [13/Dec/2017:12:40:19 +0000] "GET /index.action HTTP/1.1" 401 58&lt;BR /&gt;127.0.0.1 - - [13/Dec/2017:12:40:24 +0000] "GET /login.action HTTP/1.1" 401 58&lt;BR /&gt;127.0.0.1 - - [13/Dec/2017:12:40:30 +0000] "GET /struts2-showcase/person/editPerson.action HTTP/1.1" 404 1033&lt;BR /&gt;127.0.0.1 - - [13/Dec/2017:12:40:36 +0000] "GET /struts2-showcase/showcase.action HTTP/1.1" 404 1015&lt;BR /&gt;127.0.0.1 - - [13/Dec/2017:12:40:41 +0000] "GET /struts-cookbook/processSimple.do HTTP/1.1" 404 1015&lt;BR /&gt;127.0.0.1 - - [13/Dec/2017:12:40:47 +0000] "GET /portal/client/cms/viewcmspage.action HTTP/1.1" 404 1023&lt;BR /&gt;127.0.0.1 - - [13/Dec/2017:12:40:53 +0000] "GET /admin/agent/default.action HTTP/1.1" 404 1003&lt;BR /&gt;127.0.0.1 - - [13/Dec/2017:12:40:58 +0000] "GET /index.do HTTP/1.1" 401 58&lt;BR /&gt;127.0.0.1 - - [13/Dec/2017:12:41:04 +0000] "GET /Dashboard.action HTTP/1.1" 401 58&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jul 2018 14:16:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/how-do-I-analyze-web-access-logs/m-p/475182#M122173</guid>
      <dc:creator>Robert</dc:creator>
      <dc:date>2018-07-03T14:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: how do I analyze web access logs</title>
      <link>https://communities.sas.com/t5/SAS-Programming/how-do-I-analyze-web-access-logs/m-p/476256#M122531</link>
      <description>&lt;P&gt;If it's SAS Logs then the SAS Environment Manager provides quite a bit for such tasks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For other logs: I agree with you that this is a problem which people must have solved already but whenever I actually need something specific I end up not finding anything pre-fabricated where amending the code for my specific use case wouldn't take me as long as writing new (and much simpler) code from scratch.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking at the log layout you've posted: That's so nicely structured that it shouldn't be too hard to parse out what you need.&lt;/P&gt;</description>
      <pubDate>Sun, 08 Jul 2018 03:55:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/how-do-I-analyze-web-access-logs/m-p/476256#M122531</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2018-07-08T03:55:03Z</dc:date>
    </item>
  </channel>
</rss>

