<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logging on Evan Hoffman</title><link>https://evan.wtf/tags/logging/</link><description>Recent content in Logging on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Wed, 29 Oct 2014 14:11:40 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/logging/index.xml" rel="self" type="application/rss+xml"/><item><title>How (the hell) do you set up Splunk Cloud on Linux?</title><link>https://evan.wtf/2014/10/29/how-the-hell-do-you-set-up-splunk-cloud-on-linux/</link><pubDate>Wed, 29 Oct 2014 14:11:40 +0000</pubDate><guid>https://evan.wtf/2014/10/29/how-the-hell-do-you-set-up-splunk-cloud-on-linux/</guid><description>&lt;p&gt;This took me way longer than I would&amp;rsquo;ve thought, mostly due to horrible documentation. Here&amp;rsquo;s my TL;DR version:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Sign up for &lt;a href="http://www.splunk.com/getsplunk/cloudtrial"&gt;Splunk Cloud&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;Download and install the forwarder binary from &lt;a href="http://www.splunk.com/download/universalforwarder"&gt;here&lt;/a&gt;.- Log in &lt;a href="https://www.splunk.com/page/cloudtrial_status"&gt;here&lt;/a&gt; and note the URL of your Splunk instance:&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;&lt;a href="https://evan.wtf/wp-content/uploads/2014/10/splunk_cloud.png"&gt;&lt;img src="https://evan.wtf/wp-content/uploads/2014/10/splunk_cloud.png" alt="splunk_cloud"&gt;&lt;/a&gt;&#10;In the above picture, assume the URL is &lt;strong&gt;&lt;a href="https://prd-p-jxxxxxxxx.splunk6.splunktrial.com"&gt;https://prd-p-jxxxxxxxx.splunk6.splunktrial.com&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Make sure your instances can connect to port tcp/9997 on your input host. Your input host is the hostname from above with &amp;ldquo;input-&amp;rdquo; prepended to it. So in our example, the input host is &lt;strong&gt;input-prd-p-jxxxxxxxx.splunk6.splunktrial.com&lt;/strong&gt;. To ensure you can connect, try &lt;code&gt;telnet input-prd-p-jxxxxxxxx.splunk6.splunktrial.com 9997&lt;/code&gt;. If it can&amp;rsquo;t connect you may need to adjust your firewall rules / Security groups to allow outbound tcp/9997&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Below are the actual commands I used to get data into our Splunk Cloud trial instance:&lt;/p&gt;</description></item><item><title>Logging RT username in Apache access_log</title><link>https://evan.wtf/2011/08/08/logging-rt-username-in-apache-access_log/</link><pubDate>Mon, 08 Aug 2011 17:34:18 +0000</pubDate><guid>https://evan.wtf/2011/08/08/logging-rt-username-in-apache-access_log/</guid><description>&lt;p&gt;&lt;a href="http://bestpractical.com/rt/"&gt;RT&lt;/a&gt; has its own internal accounting &amp;amp; tracking system for logging activity, but I was interested in even more granular stuff, like seeing who looked at which tickets. I figured it wouldn&amp;rsquo;t be that hard to log this in Apache. Well, I was kind of right, in that it wasn&amp;rsquo;t &amp;ldquo;hard,&amp;rdquo; but it took me a long time to find the right place to do it. I did finally get it though.&lt;/p&gt;</description></item></channel></rss>