<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://wiki.loggly.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://wiki.loggly.com/feed.php">
        <title>Loggly Wiki</title>
        <description></description>
        <link>http://wiki.loggly.com/</link>
        <image rdf:resource="http://wiki.loggly.com/lib/tpl/vector/images/favicon.ico" />
       <dc:date>2012-05-17T07:10:57+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://wiki.loggly.com/addnewdevicetoinput?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/administration_apis?rev=1297365123&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/adrollstory?rev=1302745924&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/airport?rev=1307303152&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/alertbirds?rev=1327712879&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/alertbirdsvideo?rev=1315956241&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/apachelogging?rev=1335994877&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/api-documentation?rev=1287691653&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/apidocumentation?rev=1311214335&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/apidocumention?rev=1336496603&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/app47story?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/authentication?rev=1311195064&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/bebostory?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/bookmarklet?rev=1308355980&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/ciscopixlogging?rev=1287717421&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/clouddeployment?rev=1289941848&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/compare_screenshot?rev=1306974115&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/concurrentstory?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/creating_custom_commands?rev=1334268261&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/devic_apis?rev=1307147118&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/device_management?rev=1307412024&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/dotnetlogging?rev=1294726337&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/event_log_server?rev=1308680015&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/externalresources?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/faq?rev=1291750629&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/gameserverlogging?rev=1307747597&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/generalcodeguidelines?rev=1307148183&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/gettinglogsintologgly?rev=1307990860&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/gettingstarted?rev=1307400404&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/gistplugin?rev=1310590518&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/hadoop?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/heroku?rev=1334077090&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/hoover_config_inputs?rev=1311099972&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/hoover_create_inputs?rev=1311185058&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/hoover_facets?rev=1311094648&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/hoover_get_input_by_name?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/hoover_inputs?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/hooverguide?rev=1324590437&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/input_apis?rev=1319132354&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/input_pics?rev=1311374781&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/inputbasics?rev=1330551797&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/inputsexplained?rev=1311366720&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/javascriptlogging?rev=1307377262&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/languagespecific?rev=1319217508&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/live_tail?rev=1330987150&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/log4j?rev=1320432385&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/logging-configurations?rev=1287711888&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/logging-in-your-code?rev=1287711565&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/loggingconfiguration?rev=1311360647&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/loggingfromcode?rev=1307374129&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/loggingjargon?rev=1336426437&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/logglyshell?rev=1321301292&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/logshipper?rev=1320973968&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/logstash?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/lucenerev?rev=1308245563&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/mysqllogging?rev=1307746111&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/nginxlogging?rev=1316714868&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/nodelogging.md?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/nodelogging?rev=1297539033&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/oauth?rev=1323904734&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/osxlogging?rev=1311360529&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/overviewscreencast?rev=1327368387&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/pagesweneed?rev=1310428967&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/phplogging?rev=1331064285&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/pixellogging?rev=1312417796&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/postgresqllogging?rev=1307748892&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/powershell?rev=1307142283&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/pricing?rev=1331701793&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/productbrochure?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/python_js?rev=1308689156&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/pythonlogging?rev=1312995922&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/pythonsdk?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/releases?rev=1317157528&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/responsecodes?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/retrieve_events?rev=1293920578&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/rsysloginstallation?rev=1336881575&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/rubylogging?rev=1307145274&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/s3archive?rev=1319218109&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/s3bucketaccess?rev=1333012486&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/savedsearch?rev=1326405327&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/search_404?rev=1306970958&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/searchbasics?rev=1331067227&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/searchguide?rev=1296557894&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/securetransport?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/send_events?rev=1333757143&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/shellcommands?rev=1335483142&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/siloamsprings?rev=1308703657&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/snare?rev=1307659962&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/start?rev=1333468137&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/startsendingdata?rev=1307148385&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/syslog514?rev=1287709534&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/syslognginstallation?rev=1320688409&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/thefaq?rev=1294775637&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/thelogglyshell?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/thewiki?rev=1297538627&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/timestamps?rev=1287700726&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/trackingpixel?rev=1319070950&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/troubleshooting?rev=1307374408&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/ventrilologging?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/verslystory?rev=1319155289&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/videos?rev=1299305703&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/vrslystory?rev=1306967741&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/windowslogging?rev=1326144407&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.loggly.com/wordpress?rev=1319155289&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://wiki.loggly.com/lib/tpl/vector/images/favicon.ico">
        <title>Loggly Wiki</title>
        <link>http://wiki.loggly.com/</link>
        <url>http://wiki.loggly.com/lib/tpl/vector/images/favicon.ico</url>
    </image>
    <item rdf:about="http://wiki.loggly.com/addnewdevicetoinput?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>addnewdevicetoinput</title>
        <link>http://wiki.loggly.com/addnewdevicetoinput?rev=1319155289&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://wiki.loggly.com/administration_apis?rev=1297365123&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-02-10T19:12:03+00:00</dc:date>
        <title>administration_apis</title>
        <link>http://wiki.loggly.com/administration_apis?rev=1297365123&amp;do=diff</link>
        <description>Administration APIs

Admin methods provide a way to manage the objects associated with your Loggly account, including users, inputs, and devices.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/adrollstory?rev=1302745924&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-04-14T01:52:04+00:00</dc:date>
        <title>adrollstory</title>
        <link>http://wiki.loggly.com/adrollstory?rev=1302745924&amp;do=diff</link>
        <description>Adroll Shares Their Logging Story

Valentino Volonghi, Senior Scalability Director at Adroll chats with Kord Campbell about how Adroll logs, and how they use Loggly to do debugging, alerting and troubleshooting with Loggly.  You can follow Adroll and Valentino on Twitter.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/airport?rev=1307303152&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-05T19:45:52+00:00</dc:date>
        <title>airport</title>
        <link>http://wiki.loggly.com/airport?rev=1307303152&amp;do=diff</link>
        <description>Logging from Apple Airport Devices

Apple's AirPort and AirPort Extreme devices are local area wireless networking products based on the IEEE 802.11 standard (also known as Wi-Fi).

Both the Extreme and the Express will log messages about various networking tasks they perform.  The devices support a simple versions of syslog, and will only forward on port 514 UDP.  Airports limit the destination address to be in the form of IP addresses only.  You may NOT use named addresses like logs.loggly.com…</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/alertbirds?rev=1327712879&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-28T01:07:59+00:00</dc:date>
        <title>alertbirds</title>
        <link>http://wiki.loggly.com/alertbirds?rev=1327712879&amp;do=diff</link>
        <description>Alert Birds


Alert Birds is Loggly's alerting and monitoring app. It also serves as the reference app for developers to start working with the Loggly logging platform.  We'll get into what that means for app developers in a little bit, but first, let's cover the basics of what Alert Birds does.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/alertbirdsvideo?rev=1315956241&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-09-13T23:24:01+00:00</dc:date>
        <title>alertbirdsvideo</title>
        <link>http://wiki.loggly.com/alertbirdsvideo?rev=1315956241&amp;do=diff</link>
        <description>Alert Birds Demo Video

Kord Campbell runs through the new Alert Birds alerting application for Loggly.  If you've been dying for alerting, check it out now!</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/apachelogging?rev=1335994877&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-05-02T21:41:17+00:00</dc:date>
        <title>apachelogging</title>
        <link>http://wiki.loggly.com/apachelogging?rev=1335994877&amp;do=diff</link>
        <description>How you send log messages to Loggly from Apache will depend on how you are shipping your logs to loggly.  You can always send your logs using the API, but your best bet will be to send your logs using syslog.

Sending Access &amp; Error Logs to Loggly via Rsyslog

Rsyslog has the ability to monitor files including our beloved Apache2 and Error and Access Logs.  The following gist is a rsyslog.conf file that separates apache2/access.log &amp; apache2/error.log into two designated Loggly ports as well a a…</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/api-documentation?rev=1287691653&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-21T20:07:33+00:00</dc:date>
        <title>api-documentation</title>
        <link>http://wiki.loggly.com/api-documentation?rev=1287691653&amp;do=diff</link>
        <description>apidocumentation&lt;strong&gt;You will be redirected to  in approximately 3 seconds.&lt;/strong&gt;&lt;script&gt;url=&quot;/apidocumentation&quot;;setTimeout(&quot;location.href=url&quot;,3000);&lt;/script&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/apidocumentation?rev=1311214335&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-21T02:12:15+00:00</dc:date>
        <title>apidocumentation</title>
        <link>http://wiki.loggly.com/apidocumentation?rev=1311214335&amp;do=diff</link>
        <description>apidocumention&lt;strong&gt;You will be redirected to  in approximately 3 seconds.&lt;/strong&gt;&lt;script&gt;url=&quot;/apidocumention&quot;;setTimeout(&quot;location.href=url&quot;,3000);&lt;/script&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/apidocumention?rev=1336496603&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-05-08T17:03:23+00:00</dc:date>
        <title>apidocumention</title>
        <link>http://wiki.loggly.com/apidocumention?rev=1336496603&amp;do=diff</link>
        <description>Wanting to utilize your Loggly information outside of the Dashboard? You can access your information from Loggly via Loggly's API which allows you to:

	*  Send and Retrieve Events
	*  Add, View or Delete inputs
	*  Add, View, or Delete devices

Loggly's API allows for easy access to your log data.  Creating and utilizing data for use in application development and deployment without having to mess around with the dashboard.  If you're in need of a python API check out Python Logging and Hoover</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/app47story?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>app47story</title>
        <link>http://wiki.loggly.com/app47story?rev=1319155289&amp;do=diff</link>
        <description>App47 Shares Their Logging Story

Chris Schroeder, CEO of App47, talks to Kord about how App47 is embedding Loggly into their offering to provide advanced troubleshooting and analytics for mobile developers.  You can follow App47 and Chris on Twitter.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/authentication?rev=1311195064&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-20T20:51:04+00:00</dc:date>
        <title>authentication</title>
        <link>http://wiki.loggly.com/authentication?rev=1311195064&amp;do=diff</link>
        <description>Hoovmarklet: Authenticating with Oauth

Using Oauth, we can create a safer login system that allows the user to authorize or cancel applications. The idea behind oauth is a 3 way handshake between request token, oauth verifier, and access token. In the app Hoovmarklet, uses oauth to allow the user to authorize the application that allows the user to send log files to Loggly of every site the user visits.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/bebostory?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>bebostory</title>
        <link>http://wiki.loggly.com/bebostory?rev=1319155289&amp;do=diff</link>
        <description>Bebo Shares Their Logging Story

Aren Sanderson, Operations Architect for Bebo, chats with Kord Campbell about how Bebo is changing their infrastructure, manages logs, and how they use Loggly to do debugging, alerting and operational troubleshooting with Loggly.  You can follow Bebo and Aren on Twitter.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/bookmarklet?rev=1308355980&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-18T00:13:00+00:00</dc:date>
        <title>bookmarklet</title>
        <link>http://wiki.loggly.com/bookmarklet?rev=1308355980&amp;do=diff</link>
        <description>Want to bookmark links (like you would with del.icio.us) using Loggly?

Set up an HTTP input, then grab your API key. 

Create a Bookmarklet

Each time you click on the bookmarklet, it will record the URL of the site you are on to the Loggly input you created.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/ciscopixlogging?rev=1287717421&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-22T03:17:01+00:00</dc:date>
        <title>ciscopixlogging</title>
        <link>http://wiki.loggly.com/ciscopixlogging?rev=1287717421&amp;do=diff</link>
        <description>logging on
logging trap debugging
logging history debugging
logging host [interface] &lt;loggly_ip&gt;
If you have a newer PIX/ASA, you can use this:

 logging host [interface] &lt;loggly_ip&gt; [protocol/port]

Tons of more details here: &lt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00805a2e04.shtml&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/clouddeployment?rev=1289941848&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-11-16T21:10:48+00:00</dc:date>
        <title>clouddeployment</title>
        <link>http://wiki.loggly.com/clouddeployment?rev=1289941848&amp;do=diff</link>
        <description>Cloud Deployments

TBD

If you are using Puppet, here are some scripts that you might want to use: 

&lt;https://github.com/till/easybib-cookbooks/blob/master/loggly/templates/default/loggly.sh.erb&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/compare_screenshot?rev=1306974115&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-02T00:21:55+00:00</dc:date>
        <title>compare_screenshot</title>
        <link>http://wiki.loggly.com/compare_screenshot?rev=1306974115&amp;do=diff</link>
        <description>&quot;Compare&quot; &amp; Contrast



Using the 'compare' shell command:

Here is a screen shot comparing different web browsers that have shown up in some log files 

Example:
compare mozilla , chrome , ie
Try it out!</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/concurrentstory?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>concurrentstory</title>
        <link>http://wiki.loggly.com/concurrentstory?rev=1319155289&amp;do=diff</link>
        <description>Concurrent Shares Their Logging Story

Chris Wensel, CEO of Concurrent chats with Kord Campbell about how to best use Hadoop and Cascading for processing logs, and talks about the new roles we're seeing in business analytics around application logs is growning.  You can follow Concurrent, Cascading and Chris on Twitter.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/creating_custom_commands?rev=1334268261&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-12T22:04:21+00:00</dc:date>
        <title>creating_custom_commands</title>
        <link>http://wiki.loggly.com/creating_custom_commands?rev=1334268261&amp;do=diff</link>
        <description>Creating Custom Commands

It takes all kinds to make a world...So with that in mind we bring to your attention an amazing way to release your inner javascript: Custom Commands

To create and run your own commands in Loggly isn't too bad if you've got a plan.  No matter what your javascript is up to you'll definitely need to use some specific parameters to get your custom command off the ground. But first....a tad bit of info:
The Loggly Terminal is always an awesome resource (With great power co…</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/devic_apis?rev=1307147118&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-04T00:25:18+00:00</dc:date>
        <title>devic_apis</title>
        <link>http://wiki.loggly.com/devic_apis?rev=1307147118&amp;do=diff</link>
        <description>Devices APIs

Methods to manage devices associated with your Loggly account.

Devices
/devices/[id]/
HTTP GET

Provides an device or list of devices for an account.

Sample Query
curl -u [user]:[pass] 'http://[subdomain].loggly.com/api/devices/'

JSON Output
[
  {
      &quot;name&quot;: &quot;&quot;, 
      &quot;ip&quot;: &quot;24.4.108.196&quot;, 
      &quot;input&quot;: [
          {
              &quot;name&quot;: &quot;zoto&quot;, 
              &quot;id&quot;: 248
          }, 
          {
              &quot;name&quot;: &quot;test&quot;, 
              &quot;id&quot;: 501
          }
      ], 
…</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/device_management?rev=1307412024&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-07T02:00:24+00:00</dc:date>
        <title>device_management</title>
        <link>http://wiki.loggly.com/device_management?rev=1307412024&amp;do=diff</link>
        <description>Device Management

So What's Happening Down Here??

----------



For the most part if the lower part of your dashboard is looking like this nothing is going on.   

You can even log from your code and track events from  JavaScript, Python, Ruby, and many more.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/dotnetlogging?rev=1294726337&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-11T06:12:17+00:00</dc:date>
        <title>dotnetlogging</title>
        <link>http://wiki.loggly.com/dotnetlogging?rev=1294726337&amp;do=diff</link>
        <description>.NET

Karl Seguin has written a nice little .NET driver which is housed on Github: &lt;https://github.com/karlseguin/loggly-csharp&gt;.  The driver allows you to use HTTP/HTTPS inputs to send events into Loggly.  After you send in events, you can search for them.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/event_log_server?rev=1308680015&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-21T18:13:35+00:00</dc:date>
        <title>event_log_server</title>
        <link>http://wiki.loggly.com/event_log_server?rev=1308680015&amp;do=diff</link>
        <description>One of Loggly's many uses is as an event log server in the cloud. 

Most of the time, event logs are stored in a file on a computer's hard drive - but here at Loggly, we store event logs in the cloud. Loggly currently supports a number of event log servers for input, including syslog, rsyslog, syslog-ng, as well as server event logging directly from code, such as Javascript, Python, Ruby, .NET/C#, Java, and AppEngine.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/externalresources?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>externalresources</title>
        <link>http://wiki.loggly.com/externalresources?rev=1319155289&amp;do=diff</link>
        <description>&lt;http://www.syslog.org/&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/faq?rev=1291750629&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-12-07T19:37:09+00:00</dc:date>
        <title>faq</title>
        <link>http://wiki.loggly.com/faq?rev=1291750629&amp;do=diff</link>
        <description>thefaq&lt;strong&gt;You will be redirected to  in approximately 3 seconds.&lt;/strong&gt;&lt;script&gt;url=&quot;/thefaq&quot;;setTimeout(&quot;location.href=url&quot;,3000);&lt;/script&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/gameserverlogging?rev=1307747597&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-10T23:13:17+00:00</dc:date>
        <title>gameserverlogging</title>
        <link>http://wiki.loggly.com/gameserverlogging?rev=1307747597&amp;do=diff</link>
        <description>Ability to upload logs from game servers - there are quite a few large game server hosts that would likely love the ability to search/graph data from their logs (and many of them host hundreds of servers, which means loggly is the perfect tool for them to use for aggregation).</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/generalcodeguidelines?rev=1307148183&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-04T00:43:03+00:00</dc:date>
        <title>generalcodeguidelines</title>
        <link>http://wiki.loggly.com/generalcodeguidelines?rev=1307148183&amp;do=diff</link>
        <description>Logging Format Recommendations

We recommend that you send messages in key-value format, such as:
2010-12-12T09:23:01.262+00:00 localhost loggly: severity=INFO,user=api_api,object=input,action=read,status=success,input_id=None
You can then search for events matching certain values for their respective keys:</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/gettinglogsintologgly?rev=1307990860&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-13T18:47:40+00:00</dc:date>
        <title>gettinglogsintologgly</title>
        <link>http://wiki.loggly.com/gettinglogsintologgly?rev=1307990860&amp;do=diff</link>
        <description>Getting Logs into Loggly

Do you have a log file you want to ship to Loggly? First create an HTTP input on your account, then follow the instructions below for your environment type.

From a Linux or Mac Environment

Use the following command to send the log to Loggly:</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/gettingstarted?rev=1307400404&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-06T22:46:44+00:00</dc:date>
        <title>gettingstarted</title>
        <link>http://wiki.loggly.com/gettingstarted?rev=1307400404&amp;do=diff</link>
        <description>Getting Started Using Loggly

In this first of a series video, Kord Campbell, CEO and co-founder of Loggly, steps you through setting up an account, configuring a regular ol' syslog server on OSX to send Loggly data, and doing some simple searches and troubleshooting.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/gistplugin?rev=1310590518&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-13T20:55:18+00:00</dc:date>
        <title>gistplugin</title>
        <link>http://wiki.loggly.com/gistplugin?rev=1310590518&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://wiki.loggly.com/hadoop?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>hadoop</title>
        <link>http://wiki.loggly.com/hadoop?rev=1319155289&amp;do=diff</link>
        <description>Log analytics with Hadoop and Hive
Introduction
Get interactive SQL query access to months of log archives (using Hadoop and Hive), in 5-10 minutes, without any hardware or software.

How It Works
This article covers how to:

load logs into a SQL-compatible system for ad-hoc analysis (Hive), accessible from your terminal
extract important message-specific fields into separate columns, so they can be used in SQL queries. For example, the message “Request for /foo from 1.2.3.4 in 42 ms” could beco…</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/heroku?rev=1334077090&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-10T16:58:10+00:00</dc:date>
        <title>heroku</title>
        <link>http://wiki.loggly.com/heroku?rev=1334077090&amp;do=diff</link>
        <description>Loggly is a cloud-based log management service. Our goal is to provide you with a quick, easy, and fun way to store, retain, and search your log files and application events in near-realtime. 

We're really happy that we can now offer our services to Heroku users.  With one command in the Heroku Toolbelt you can start sending your log files to us!</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/hoover_config_inputs?rev=1311099972&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-19T18:26:12+00:00</dc:date>
        <title>hoover_config_inputs</title>
        <link>http://wiki.loggly.com/hoover_config_inputs?rev=1311099972&amp;do=diff</link>
        <description>To call the Configure Inputs function just type:
  hoover.config_inputs()
Here's a Gist of how you might use config_inputs:


More Insight

The Configuring Inputs method in hoover allows you to log to a specific input by integrating the logging module which is in the standard python library.  Logging within python is a really useful feature (Logging and Python) that can be worth so much when you're aiming for efficiency, getting rid of bugs, or just plain writing some code.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/hoover_create_inputs?rev=1311185058&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-20T18:04:18+00:00</dc:date>
        <title>hoover_create_inputs</title>
        <link>http://wiki.loggly.com/hoover_create_inputs?rev=1311185058&amp;do=diff</link>
        <description>Creating Inputs With Hoover

If you need to create an input it is important that you have three things: 

	*  The name you want for your new input
	*  Which connection service your input will be using. Inputs Explained 
	*  A description for your new input</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/hoover_facets?rev=1311094648&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-19T16:57:28+00:00</dc:date>
        <title>hoover_facets</title>
        <link>http://wiki.loggly.com/hoover_facets?rev=1311094648&amp;do=diff</link>
        <description>A facet (at least as far as Hoover's concerned) is either a date, ip, or input name.  The way you call facets is by first creating a LogglySession('&lt;subdomain&gt;', '&lt;user_name&gt;', '&lt;password&gt;') and assigning its object to a variable.   
  i = hoover.LogglySession('&lt;subdomain&gt;', '&lt;user_name&gt;', '&lt;password&gt;')
Once you're session is in a variable you'll use</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/hoover_get_input_by_name?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>hoover_get_input_by_name</title>
        <link>http://wiki.loggly.com/hoover_get_input_by_name?rev=1319155289&amp;do=diff</link>
        <description>Get Input By Name

Here is a short example of some code (Gist):</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/hoover_inputs?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>hoover_inputs</title>
        <link>http://wiki.loggly.com/hoover_inputs?rev=1319155289&amp;do=diff</link>
        <description>Hoover's Input Function</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/hooverguide?rev=1324590437&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-22T21:47:17+00:00</dc:date>
        <title>hooverguide</title>
        <link>http://wiki.loggly.com/hooverguide?rev=1324590437&amp;do=diff</link>
        <description>Using Hoover

Hoover is a python library that allows you to log directly from your python code. 

Installing Hoover

Easy Install will be the “easiest” way to get things started (Using -U for the most up to date version) an alternative is to head over to the the GitHub or  Pypi to download the package.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/input_apis?rev=1319132354&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-20T17:39:14+00:00</dc:date>
        <title>input_apis</title>
        <link>http://wiki.loggly.com/input_apis?rev=1319132354&amp;do=diff</link>
        <description>This page is deprecated.   Please see: &lt;http://wiki.loggly.com/apidocumention#inputs_apis&gt;

Inputs APIs

Methods to manage inputs associated with your Loggly account.

Input
/inputs/[id]/
HTTP GET

Provides an input or list of inputs for an account.  Use an input id to return only that id's info.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/input_pics?rev=1311374781&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-22T22:46:21+00:00</dc:date>
        <title>input_pics</title>
        <link>http://wiki.loggly.com/input_pics?rev=1311374781&amp;do=diff</link>
        <description>Input Options

Protocols

Syslog UDP



Syslog TCP



Stripped Protocols

Syslog UDP Stripped



Syslog TCP Stripped



Default Remote

Syslog on port: 514



HTTP

Syslog shipped via HTTP



Secure Syslog

Secure Syslog</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/inputbasics?rev=1330551797&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-02-29T21:43:17+00:00</dc:date>
        <title>inputbasics</title>
        <link>http://wiki.loggly.com/inputbasics?rev=1330551797&amp;do=diff</link>
        <description>Loggly Inputs are a logical way for you to segment your log files.  For example, you may want to have an input called “prod-apache”, which could be all of your Apache log files for production servers.  You should use names that clearly identify what kind of data is being handled by the input. Many different servers can send logs to one Loggly Input.  Each server that sends logs is called a Device within Loggly.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/inputsexplained?rev=1311366720&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-22T20:32:00+00:00</dc:date>
        <title>inputsexplained</title>
        <link>http://wiki.loggly.com/inputsexplained?rev=1311366720&amp;do=diff</link>
        <description>Input Services

These pages are extremely helpful for configuring your Loggly account to work with:

	*  Syslog 
	*  rsyslog  

If you're looking for some backgound info to fill in some gaps you found the right page.
Perhaps, due to circumstances outside of your control, you're not sure which what the differences are between the drop down options (well you found the right place)</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/javascriptlogging?rev=1307377262&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-06T16:21:02+00:00</dc:date>
        <title>javascriptlogging</title>
        <link>http://wiki.loggly.com/javascriptlogging?rev=1307377262&amp;do=diff</link>
        <description>Logging to Loggly from JavaScript

You can include a small JavaScript library in the HTML of your website to enable logging to Loggly from any web browser that accesses your site.  The format of the log events can be customized and controlled, and can be used to record simple things like hits to your website, or complex things like clicks, UI interaction, or even debug logs generated by your site's code.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/languagespecific?rev=1319217508&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T17:18:28+00:00</dc:date>
        <title>languagespecific</title>
        <link>http://wiki.loggly.com/languagespecific?rev=1319217508&amp;do=diff</link>
        <description>We want to make it as easy as possible for you to get your log data into Loggly.  Here are some pages devoted to specific development types:

	*  JavaScript
		*  Node.js
		*  PHP 
		*  Python
		*  Ruby
		*  .NET
		*  Java (log4j SyslogAppender)
		*  AppEngine
		*  MySQL</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/live_tail?rev=1330987150&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-05T22:39:10+00:00</dc:date>
        <title>live_tail</title>
        <link>http://wiki.loggly.com/live_tail?rev=1330987150&amp;do=diff</link>
        <description>Coming Soon!!</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/log4j?rev=1320432385&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-11-04T18:46:25+00:00</dc:date>
        <title>log4j</title>
        <link>http://wiki.loggly.com/log4j?rev=1320432385&amp;do=diff</link>
        <description>Logging from your Java Application

Would you rather log JSON over HTTP? Check out this blog post: &lt;http://loggly.com/blog/2011/09/logging-out-of-your-java-code/&gt;

To use syslog4j to log out of your java application, you'll need to set up the standard SyslogAppender to route from your app to your local syslog (port 514, using one of the Local* facilities), then set up syslog to forward from there to your logs.loggly.com port</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/logging-configurations?rev=1287711888&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-22T01:44:48+00:00</dc:date>
        <title>logging-configurations</title>
        <link>http://wiki.loggly.com/logging-configurations?rev=1287711888&amp;do=diff</link>
        <description>loggingconfiguration&lt;strong&gt;You will be redirected to  in approximately 3 seconds.&lt;/strong&gt;&lt;script&gt;url=&quot;/loggingconfiguration&quot;;setTimeout(&quot;location.href=url&quot;,3000);&lt;/script&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/logging-in-your-code?rev=1287711565&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-22T01:39:25+00:00</dc:date>
        <title>logging-in-your-code</title>
        <link>http://wiki.loggly.com/logging-in-your-code?rev=1287711565&amp;do=diff</link>
        <description>loggingfromcode&lt;strong&gt;You will be redirected to  in approximately 3 seconds.&lt;/strong&gt;&lt;script&gt;url=&quot;/loggingfromcode&quot;;setTimeout(&quot;location.href=url&quot;,3000);&lt;/script&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/loggingconfiguration?rev=1311360647&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-22T18:50:47+00:00</dc:date>
        <title>loggingconfiguration</title>
        <link>http://wiki.loggly.com/loggingconfiguration?rev=1311360647&amp;do=diff</link>
        <description>It usually takes a few minutes to configure your default logging systems and any configurations can be made so that logging to local files is left intact.  To help with managing retention and storage needs, you may wish to turn off local logging when you are certain we are receiving all your events.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/loggingfromcode?rev=1307374129&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-06T15:28:49+00:00</dc:date>
        <title>loggingfromcode</title>
        <link>http://wiki.loggly.com/loggingfromcode?rev=1307374129&amp;do=diff</link>
        <description>wiki:start&lt;strong&gt;You will be redirected to  in approximately 3 seconds.&lt;/strong&gt;&lt;script&gt;url=&quot;/wiki:start&quot;;setTimeout(&quot;location.href=url&quot;,3000);&lt;/script&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/loggingjargon?rev=1336426437&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-05-07T21:33:57+00:00</dc:date>
        <title>loggingjargon</title>
        <link>http://wiki.loggly.com/loggingjargon?rev=1336426437&amp;do=diff</link>
        <description>de⋅vice [di-ˈvīs] noun:
A device is a machine, host, or source which sends data to a Loggly input. You can view the devices sending data to an input from the input detail page on your account.  Devices are used for access control purposes, and conducting searches for events sent from them.  Each input has a set of devices assigned that are allowed to send data to that input.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/logglyshell?rev=1321301292&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-11-14T20:08:12+00:00</dc:date>
        <title>logglyshell</title>
        <link>http://wiki.loggly.com/logglyshell?rev=1321301292&amp;do=diff</link>
        <description>shellcommands&lt;strong&gt;You will be redirected to  in approximately 3 seconds.&lt;/strong&gt;&lt;script&gt;url=&quot;/shellcommands&quot;;setTimeout(&quot;location.href=url&quot;,3000);&lt;/script&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/logshipper?rev=1320973968&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-11-11T01:12:48+00:00</dc:date>
        <title>logshipper</title>
        <link>http://wiki.loggly.com/logshipper?rev=1320973968&amp;do=diff</link>
        <description>Log Forwarding with syslog-shipper

The syslog-shipper app is a Ruby gem which provides log file monitoring and TCP forwarding over the syslog protocol. If you run a syslog server which doesn't do file monitoring and you can't log directly out of your app, you can use syslog-shipper to forward your logs to Loggly.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/logstash?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>logstash</title>
        <link>http://wiki.loggly.com/logstash?rev=1319155289&amp;do=diff</link>
        <description>Logstash</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/lucenerev?rev=1308245563&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-16T17:32:43+00:00</dc:date>
        <title>lucenerev</title>
        <link>http://wiki.loggly.com/lucenerev?rev=1308245563&amp;do=diff</link>
        <description>Jon Gifford Presents Loggly's NRS at Lucene Revolution

Jon is Loggly's CTO.  His presentation at Lucene Revolution provides an overview of how we use Solr to scale to massive volumes per day and store large indexes in our proprietary search cluster.  It's hotness.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/mysqllogging?rev=1307746111&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-10T22:48:31+00:00</dc:date>
        <title>mysqllogging</title>
        <link>http://wiki.loggly.com/mysqllogging?rev=1307746111&amp;do=diff</link>
        <description>How you send log messages to Loggly from MySQL will depend on how you are shipping your logs to loggly.  You can always send your logs using the API, but your best bet will be to send your logs using syslog.

Sending MySQL errors to syslog

In your server's my.cnf file (usually located in /etc/), simply add these two lines...</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/nginxlogging?rev=1316714868&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-09-22T18:07:48+00:00</dc:date>
        <title>nginxlogging</title>
        <link>http://wiki.loggly.com/nginxlogging?rev=1316714868&amp;do=diff</link>
        <description>Nginx is a light-weight web server that typically replaces Apache. You can send nginx error logs to loggly by monitoring the nginx error.log file, commonly at /var/log/nginx/error.log

These instructions are simply a specifically tailored nginx version of the rsyslog instructions for adding file monitoring support: Configuring rsyslog for File Monitoring.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/nodelogging.md?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>nodelogging.md</title>
        <link>http://wiki.loggly.com/nodelogging.md?rev=1319155289&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://wiki.loggly.com/nodelogging?rev=1297539033&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-02-12T19:30:33+00:00</dc:date>
        <title>nodelogging</title>
        <link>http://wiki.loggly.com/nodelogging?rev=1297539033&amp;do=diff</link>
        <description>Updated documentation is here.

nodelogging.md&lt;strong&gt;You will be redirected to  in approximately 3 seconds.&lt;/strong&gt;&lt;script&gt;url=&quot;/nodelogging.md&quot;;setTimeout(&quot;location.href=url&quot;,3000);&lt;/script&gt;</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/oauth?rev=1323904734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-14T23:18:54+00:00</dc:date>
        <title>oauth</title>
        <link>http://wiki.loggly.com/oauth?rev=1323904734&amp;do=diff</link>
        <description>Loggly supports oAuth. oAuth is a way for a third-party component to access data of a Loggly user without the Loggly user having to provide his username and password. 

Assume the following setup: We have an application “App” which uses the Loggly APIs to access logs stored in Loggly. One way of allowing this App to access your data would be to provide it with your credentials i.e., your username and password. They would store those credentials and could potentially even use them to log into the…</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/osxlogging?rev=1311360529&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-22T18:48:49+00:00</dc:date>
        <title>osxlogging</title>
        <link>http://wiki.loggly.com/osxlogging?rev=1311360529&amp;do=diff</link>
        <description>Logging from OSX

OSX ships with a modified syslog process named 'syslogd'.  You can see the process and it's PID by running the following command from a terminal shell:
jeangrey$ ps -ax |grep syslog
15 ??         0:00.89 /usr/sbin/syslogd
Note: OSX's syslogd service only support UDP transport and does not provide file monitoring or forwarding.  If you need to monitor a specific log file on an OSX box, you'll need to follow the instructions below and then setup syslog-shipper to monitor a file.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/overviewscreencast?rev=1327368387&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-24T01:26:27+00:00</dc:date>
        <title>overviewscreencast</title>
        <link>http://wiki.loggly.com/overviewscreencast?rev=1327368387&amp;do=diff</link>
        <description>Here's a screencast that runs through some of Loggly's most popular features:</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/pagesweneed?rev=1310428967&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-12T00:02:47+00:00</dc:date>
        <title>pagesweneed</title>
        <link>http://wiki.loggly.com/pagesweneed?rev=1310428967&amp;do=diff</link>
        <description>Help Contribute

If you can't find what you are looking for, and don't want to add it, throw it in here.  This is the list of pages we need completed:

	*  Logging from Apache
	*  Logging from PHP
	*  Logging from MySQL
	*  Authentication
	*  Log4j and Single-Line Stack Traces</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/phplogging?rev=1331064285&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-06T20:04:45+00:00</dc:date>
        <title>phplogging</title>
        <link>http://wiki.loggly.com/phplogging?rev=1331064285&amp;do=diff</link>
        <description>How you send log messages to Loggly from PHP will depend on how you are shipping your logs to loggly.  You can always send your logs using the API, but your best bet will be to send your logs using syslog.  There are also some great open source projects to help you get started.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/pixellogging?rev=1312417796&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-04T00:29:56+00:00</dc:date>
        <title>pixellogging</title>
        <link>http://wiki.loggly.com/pixellogging?rev=1312417796&amp;do=diff</link>
        <description>Our HTTP inputs support hitting a 'pixel' that you can use for logging. This is a very common tool used by advertising and web analytics companies to ship hits and other data events to their servers.

So why not use it for logging?

Usage

	*  Create an HTTP input and enable JSON.
	*  Append '.gif' to your http input url (&lt;http://logs.loggly.com/inputs/your-key.gif&gt;)
	*  Add any query parameters to the url and those are logged in json.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/postgresqllogging?rev=1307748892&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-10T23:34:52+00:00</dc:date>
        <title>postgresqllogging</title>
        <link>http://wiki.loggly.com/postgresqllogging?rev=1307748892&amp;do=diff</link>
        <description>How you send log messages to Loggly from PostgreSQL will depend on how you are shipping your logs to loggly.  You can always send your logs using the API, but your best bet will be to send your logs using syslog.

Sending data to syslog

In your server's postgresql.conf file (usually located in /var/lib/pgsql/data/), simply change this line...</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/powershell?rev=1307142283&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-03T23:04:43+00:00</dc:date>
        <title>powershell</title>
        <link>http://wiki.loggly.com/powershell?rev=1307142283&amp;do=diff</link>
        <description>Logging via Powershell

Windows PowerShell is Microsoft's task automation framework, consisting of a command-line shell and associated scripting language built on top of, and integrated with the .NET Framework.  Logging out of PowerShell can be done with a simple POST to Loggly's input APIs:</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/pricing?rev=1331701793&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-14T05:09:53+00:00</dc:date>
        <title>pricing</title>
        <link>http://wiki.loggly.com/pricing?rev=1331701793&amp;do=diff</link>
        <description>Pricing FAQ

How much daily log volume do I need?

You should pick a daily log volume that is equal to the maximum amount you expect to send in a day.  If your normal log volumes are 1GB/day and you want to be able to handle bursts of 2GB/day, you should pick a 2GB/day volume.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/productbrochure?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>productbrochure</title>
        <link>http://wiki.loggly.com/productbrochure?rev=1319155289&amp;do=diff</link>
        <description>Click here to download PDF</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/python_js?rev=1308689156&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-21T20:45:56+00:00</dc:date>
        <title>python_js</title>
        <link>http://wiki.loggly.com/python_js?rev=1308689156&amp;do=diff</link>
        <description>Creating Visualizations with Loggly and Python/JS

In order to output Loggly’s data into visualization, we need Python and JavaScript to
communicate with 1 another. For this specific tutorial, we will be taking advantage of
Google Chart Tools and Hoover’s API. Please make sure that you have the latest Hoover library installed. The object of this tutorial is to obtain a JSON file from a local server and visualize that data in some form using Google Charts.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/pythonlogging?rev=1312995922&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-10T17:05:22+00:00</dc:date>
        <title>pythonlogging</title>
        <link>http://wiki.loggly.com/pythonlogging?rev=1312995922&amp;do=diff</link>
        <description>Logging to Loggly with Python

Before we get into the nitty gritty it's important to know the differences between the two libraries below.  The first loggly python library (loggly 0.1.2) is strictly involved in getting information from devices and inputs via the Loggly admin API, not specifically logging from python.  Hoover (hoover 0.5.3) handles both devices and inputs as well as logging directly from your python code.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/pythonsdk?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>pythonsdk</title>
        <link>http://wiki.loggly.com/pythonsdk?rev=1319155289&amp;do=diff</link>
        <description>Loggly Python SDK

If you are not just logging information from Python, but you want to administer your Loggly objects from Python, here is a Python SDK that lets you do so:

Documentation is online as well. Version 0.1.2 supports the following calls:</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/releases?rev=1317157528&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-09-27T21:05:28+00:00</dc:date>
        <title>releases</title>
        <link>http://wiki.loggly.com/releases?rev=1317157528&amp;do=diff</link>
        <description>This doc is no longer maintained.

0.4.0 Release, August 10, 2010

This release went so long that we had to bribe the whole dev team with promises of smooth whiskey, diving lessons, and ThinkGeek coupons to get it out.  Things are starting to come together nicely, and you can even see some evidence of the UI design team beginning to influence the interfaces.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/responsecodes?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>responsecodes</title>
        <link>http://wiki.loggly.com/responsecodes?rev=1319155289&amp;do=diff</link>
        <description>Response Codes

These are fairly standard HTTP/RESTful response codes.  From time to time we'll use them in our replies to your queries.
Status Message  Description 200 OK  Indicates that the request was successful. 201 Created  The object was successfully created. This is for a POST call. 204 Deleted  The object was deleted. This pertains to DELETE calls. 400 Bad Request  Check your request parameters. You might be using an unsupported parameter or have a malformed something or another. 401 Una…</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/retrieve_events?rev=1293920578&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-01T22:22:58+00:00</dc:date>
        <title>retrieve_events</title>
        <link>http://wiki.loggly.com/retrieve_events?rev=1293920578&amp;do=diff</link>
        <description>Retrieving Events via the APIs

Loggly APIs are accessed using your account's subdomain.  An example of a subdomain+loggly.com address is pixlcloud.loggly.com. Loggly's APIs require authentication, and OAuth, BASIC Auth, and cookie-based authentication are supported.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/rsysloginstallation?rev=1336881575&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-05-13T03:59:35+00:00</dc:date>
        <title>rsysloginstallation</title>
        <link>http://wiki.loggly.com/rsysloginstallation?rev=1336881575&amp;do=diff</link>
        <description>Rsyslog is an open source program for forwarding log messages in an IP network for UNIX and Unix-like systems. It implements the basic syslog protocol, extends it with content-based filtering, rich filtering capabilities, flexible configuration options and adds important features such as using TCP for transport. - From Wikipedia</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/rubylogging?rev=1307145274&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-03T23:54:34+00:00</dc:date>
        <title>rubylogging</title>
        <link>http://wiki.loggly.com/rubylogging?rev=1307145274&amp;do=diff</link>
        <description>Logging to Loggly with Ruby

Via Syslog

Syslog based logging out of Ruby can be done with the syslog module.  You'll need to configure the box the code is running on to forward logs to us.  If you haven't done so, see the Logging Configuration page for more information on setting up syslog forwarding to forward to Loggly.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/s3archive?rev=1319218109&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T17:28:29+00:00</dc:date>
        <title>s3archive</title>
        <link>http://wiki.loggly.com/s3archive?rev=1319218109&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://wiki.loggly.com/s3bucketaccess?rev=1333012486&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-29T09:14:46+00:00</dc:date>
        <title>s3bucketaccess</title>
        <link>http://wiki.loggly.com/s3bucketaccess?rev=1333012486&amp;do=diff</link>
        <description>Loggly stores your logs in a large scale search engine hosted on the Internet.  The amount of time we store your logs in our search engine index is called the 'index retention time' which you can set from your pricing tab under your account.  Once events in an account reach an age that is older than the max index retention time for your account, the events are removed from the index.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/savedsearch?rev=1326405327&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-12T21:55:27+00:00</dc:date>
        <title>savedsearch</title>
        <link>http://wiki.loggly.com/savedsearch?rev=1326405327&amp;do=diff</link>
        <description>With Loggly Saved Searches, you now have the capability to store queries that you run frequently. Here's how to make the most of our newest feature.  This feature is still in beta, so please let us know how we can make it even more useful!

	*  You no longer have to remember long &amp; complicated queries
	*  Easily keep tabs on events you care about
	*  Quick links to either graph or search on your query</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/search_404?rev=1306970958&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-01T23:29:18+00:00</dc:date>
        <title>search_404</title>
        <link>http://wiki.loggly.com/search_404?rev=1306970958&amp;do=diff</link>
        <description>Search 404's



Using the 'search' shell command:

Here's a screen shot showing some 404 errors/pageviews from the raw logs you've sent over to Loggly! 

Note the two searches are over different time intervals

Example:
search 404
Check out who's running into your 404 page</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/searchbasics?rev=1331067227&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-06T20:53:47+00:00</dc:date>
        <title>searchbasics</title>
        <link>http://wiki.loggly.com/searchbasics?rev=1331067227&amp;do=diff</link>
        <description>Searching Basics

Loggly's search interface looks like a bit like a terminal shell, but it's actually a powerful search interface written in JavaScript and some code downloaded from a space probe NASA built in the 70s. 

You can access the shell by typing in a key term in the shell input box at the top of each page.  Searching in the shell is as easy as typing something like:</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/searchguide?rev=1296557894&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-02-01T10:58:14+00:00</dc:date>
        <title>searchguide</title>
        <link>http://wiki.loggly.com/searchguide?rev=1296557894&amp;do=diff</link>
        <description>Loggly uses a search language for searching and filtering event results.  The search language is accessed by the search command in the shell, and the /search/ endpoint in the APIs. Loggly can also return facet data for a search, which is used by the graph command in the shell, and the /facets/ endpoint in the APIs.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/securetransport?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>securetransport</title>
        <link>http://wiki.loggly.com/securetransport?rev=1319155289&amp;do=diff</link>
        <description>Secure Transport

Forward OSSEC events via HTTP on Syslog

Example

Forwarding plain syslog over TLS

loggerglue 

Forwarding plain syslog over HTTPS

logglyproxy</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/send_events?rev=1333757143&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-07T00:05:43+00:00</dc:date>
        <title>send_events</title>
        <link>http://wiki.loggly.com/send_events?rev=1333757143&amp;do=diff</link>
        <description>Sending Events via the APIs

Events can be sent into Loggly via syslog or HTTP POSTs.  If you need to configure your servers to send Loggly data via a syslog based service, please refer to the Logging Configuration page.

To send in events via the APIs, through HTTP POSTs, you'll use the hostname logs.loggly.com (instead of the [subdomain].loggly.com format used by the other API calls).  The APIs on the proxy cluster support both HTTP and HTTPs, and use a SHA-2 key in the URL for validation.  Th…</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/shellcommands?rev=1335483142&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-26T23:32:22+00:00</dc:date>
        <title>shellcommands</title>
        <link>http://wiki.loggly.com/shellcommands?rev=1335483142&amp;do=diff</link>
        <description>help

Displays this list of shell commands.

search
  search &lt;search terms&gt;
Searches for events with the given terms in the current context.  More details are on the Search Basics wiki page. Example:
  search 404
 More on &quot;search&quot;

graph
  graph &lt;search terms&gt;
Graphs events matching the given terms in the current context. Graph takes the same arguments as the search command.  See the Search Basics wiki for more information. Example:</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/siloamsprings?rev=1308703657&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-22T00:47:37+00:00</dc:date>
        <title>siloamsprings</title>
        <link>http://wiki.loggly.com/siloamsprings?rev=1308703657&amp;do=diff</link>
        <description>Siloam Springs Shares Their Logging Story

Christopher Hobbs, senior system administrator for The City of Siloam Springs, Arkansas, talks to Kord about how he uses Loggly to debug and troubleshoot the dizzing array of systems he maintains for the city and police and fire departments.  You can follow Chris and Siloam Springs on Twitter, and browse his public repos on Github.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/snare?rev=1307659962&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-09T22:52:42+00:00</dc:date>
        <title>snare</title>
        <link>http://wiki.loggly.com/snare?rev=1307659962&amp;do=diff</link>
        <description>Using Snare to get your Logs

Snare is a group of open-source agents, and a commercial server, used to collect audit log data from a variety of operating systems and applications to facilitate centralized log analysis.  The acronym supposedly stands for System iNtrusion Analysis and Reporting Environment.  Whatever.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/start?rev=1333468137&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-04-03T15:48:57+00:00</dc:date>
        <title>start</title>
        <link>http://wiki.loggly.com/start?rev=1333468137&amp;do=diff</link>
        <description>Loggly is a cloud-based log management service.  Our goal is to provide you a quick and easy way to aggregate, retain, and search your log files and application events in near-realtime.

This wiki is community editable, and contributions are welcome.  The wiki serves as Loggly's documentation and API reference, as well as a source of examples for integrating Loggly search into your own applications.  A list of our common logging phrases is available via the Jargon page.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/startsendingdata?rev=1307148385&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-04T00:46:25+00:00</dc:date>
        <title>startsendingdata</title>
        <link>http://wiki.loggly.com/startsendingdata?rev=1307148385&amp;do=diff</link>
        <description>Get Started Using Loggly

A Loggly account without log data is a bit like a Twitter account with no tweets; you really need to send us some data before we can do anything useful.  You can send your logs to Loggly by setting up your syslog system to forward logs to our syslog servers.  We also run HTTP/HTTPS services to allow you to quickly send in events via web POSTs.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/syslog514?rev=1287709534&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-22T01:05:34+00:00</dc:date>
        <title>syslog514</title>
        <link>http://wiki.loggly.com/syslog514?rev=1287709534&amp;do=diff</link>
        <description>Some syslog servers, such as those used in routers or other network devices, may not support sending log data over anything but UDP port 514.  This has the unfortunate side effect of preventing you from changing the destination to a port Loggly uses to listen for your data.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/syslognginstallation?rev=1320688409&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-11-07T17:53:29+00:00</dc:date>
        <title>syslognginstallation</title>
        <link>http://wiki.loggly.com/syslognginstallation?rev=1320688409&amp;do=diff</link>
        <description>syslog-ng is an open source implementation of the Syslog protocol for Unix and Unix-like systems. It extends the original syslogd model with content-based filtering, rich filtering capabilities, flexible configuration options and adds important features to syslog, like using TCP for transport. As of today syslog-ng is developed by Balabit IT Security Ltd.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/thefaq?rev=1294775637&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-11T19:53:57+00:00</dc:date>
        <title>thefaq</title>
        <link>http://wiki.loggly.com/thefaq?rev=1294775637&amp;do=diff</link>
        <description>This document covers basic questions about Loggly's logging service.  If you have a question that doesn't appear here, please visit the forums or make the addition yourself by creating an account on the wiki.

How does Loggly get my logs?

As one of the collection methods, Loggly runs a syslog based logging service. In the most simple terms, if you point your syslog server at logs.loggly.com, we'll catch and eat those logs and put them in your account for you. There are instruction below for con…</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/thelogglyshell?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>thelogglyshell</title>
        <link>http://wiki.loggly.com/thelogglyshell?rev=1319155289&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://wiki.loggly.com/thewiki?rev=1297538627&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-02-12T19:23:47+00:00</dc:date>
        <title>thewiki</title>
        <link>http://wiki.loggly.com/thewiki?rev=1297538627&amp;do=diff</link>
        <description>About Loggly's Wiki

Loggly's wiki is powered by Dokuwiki.  Dokuwiki provides a Wikimedia like wiki syntax, and does all this without the hassle of setting up a database.  Dokuwiki is written in PHP.

Syntax Support

Loggly's wiki supports two different syntaxes:</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/timestamps?rev=1287700726&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-21T22:38:46+00:00</dc:date>
        <title>timestamps</title>
        <link>http://wiki.loggly.com/timestamps?rev=1287700726&amp;do=diff</link>
        <description>There are a few facts that need to be known about how Loggly handles timestamps in the current version of Loggly:

	*  Loggly timestamps all events with a time of when it arrives in our system.
	*  Timestamp strings contained in the event itself are not modified or extracted by Loggly.
	*  The colorized timestamp tags shown in the shell are the event arrival timestamps.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/trackingpixel?rev=1319070950&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-20T00:35:50+00:00</dc:date>
        <title>trackingpixel</title>
        <link>http://wiki.loggly.com/trackingpixel?rev=1319070950&amp;do=diff</link>
        <description>Using the Loggly Tracking Pixel

Loggly provides two different ways to log out of HTML and JavaScript.  You can use the Castor JavaScript logging library, or you can log to Loggly using a simple tracking pixel.  Loggly's pixel works in a simliar way to other site's tracking pixels, except it allows you to send in arbitrary key value pairs.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/troubleshooting?rev=1307374408&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-06T15:33:28+00:00</dc:date>
        <title>troubleshooting</title>
        <link>http://wiki.loggly.com/troubleshooting?rev=1307374408&amp;do=diff</link>
        <description>Troubleshooting

Loggly is easy to use, but the difficulty in getting logs into Loggly can depend heavily on your current logging solution and network setup.  If you are having issues, here are a few tips on tracking down where things are going wrong.</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/ventrilologging?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>ventrilologging</title>
        <link>http://wiki.loggly.com/ventrilologging?rev=1319155289&amp;do=diff</link>
        <description>Yes, that's right, this is another gamer entry. A large number of people use “Ventrilo,” which is a program that enables instant voice communication for large groups (and has lots of permissions functions which are quite handy). “Ventrilo” requires a server, and produces text logs of its users/errors/etc, and there are a number of hosts which could easily benefit from aggregated logs (to find IPs to ban, servers with problems, and more).</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/verslystory?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>verslystory</title>
        <link>http://wiki.loggly.com/verslystory?rev=1319155289&amp;do=diff</link>
        <description>Versly Shares Their Logging Story

Benjamin Renaud, CEO of Versly, talks to Kord about all the logs they generate while making people's life better when working together on content.  You can follow Team Versly and Ben on Twitter.



Additional Formats

	*  iPhone Mobile (8.7 MB)
	*  iPhone Broadband (96 MB)</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/videos?rev=1299305703&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-05T06:15:03+00:00</dc:date>
        <title>videos</title>
        <link>http://wiki.loggly.com/videos?rev=1299305703&amp;do=diff</link>
        <description>Loggly Videos

 * Getting Started with Loggly</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/vrslystory?rev=1306967741&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-01T22:35:41+00:00</dc:date>
        <title>vrslystory</title>
        <link>http://wiki.loggly.com/vrslystory?rev=1306967741&amp;do=diff</link>
        <description>Versly Shares Their Logging Story

Benjamin Renaud, CEO of Versly, talks to Kord about all the logs they generate while making people's life better when working together on content.  You can follow Team Versly and Ben on Twitter.



Additional Formats

	*  iPhone Mobile (8.7 MB)
	*  iPhone Broadband (96 MB)</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/windowslogging?rev=1326144407&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-09T21:26:47+00:00</dc:date>
        <title>windowslogging</title>
        <link>http://wiki.loggly.com/windowslogging?rev=1326144407&amp;do=diff</link>
        <description>Logging from Windows

Windows doesn't log exactly like other operating systems.  Still, we love logs, so we'll be happy to take them if you're happy to do a little bit of legwork to forward 'em on to us.

Log via Powershell

Windows PowerShell is Microsoft's task automation framework, consisting of a command-line shell and associated scripting language built on top of, and integrated with the .NET Framework.  Logging out of PowerShell can be done with a simple POST to Loggly's input APIs:</description>
    </item>
    <item rdf:about="http://wiki.loggly.com/wordpress?rev=1319155289&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-10-21T00:01:29+00:00</dc:date>
        <title>wordpress</title>
        <link>http://wiki.loggly.com/wordpress?rev=1319155289&amp;do=diff</link>
        <description>Are you using Wordpress and you want to log to Loggly?

Here is a plugin that you can use to send wordpress log entries via syslog: &lt;http://www.ossec.net/main/wpsyslog2&gt;</description>
    </item>
</rdf:RDF>

