A way to log occurances to an Amazon Simple DB (requires Gigaom Simple DB).

Zach Tirrell

methnen

Gigaom Simple DB

Establish a connection to Amazon Simple DB. Uses the awesome php-sdb2 SDB library.

<p>A way to log occurances to an Amazon Simple DB (requires <a href="http://github.com/GigaOM/go-simple-db/" rel="nofollow ugc">Gigaom Simple DB</a>).</p>
<p>We originally created this to allow us to log errors in our code when we weren’t able to access the PHP error logs on the server and weren’t able to reproduce them locally.  However, since then we’ve found it useful in a few other cases as well.</p>
<p>Here’s our short list (you may be able to think of more):</p>
<ol>
<li>When you need to log errors but don’t have admin access to the error logs on the server.</li>
<li>When you need a cosolidated log between two different servers that are running related code.
<ul>
<li>In our case we had two servers talking to each other and needed a view into how that conversation was going in a consolidated fashion.</li>
</ul>
</li>
<li>When you have a rare error that you need to log but don’t want to dig through months of error log files.</li>
</ol>
<h3>Usage</h3>
<ol>
<li>Set config info by filtering the go_config hook and returning an array of Amazon Simple DB credentials when the second filter attribute is go-slog.
<ul>
<li><code>array(<br />
'aws_access_key' => 'YOUR_KEY',<br />
'aws_secret_key' => 'YOUR_SECRET',<br />
'aws_sdb_domain' => 'YOUR_SDB_DOMAIN',<br />
);</code></li>
<li>The SDB Domain value is analagous to an SQL Table. It’s the space where your log items will be written to.  If the SDB Domain doesn’t exist yet <a href="http://github.com/GigaOM/go-simple-db/" rel="nofollow ugc">Gigaom Simple DB</a> will create it for you.</li>
<li>See: <a href="http://docs.aws.amazon.com/AmazonSimpleDB/latest/GettingStartedGuide/Welcome.html" rel="nofollow ugc">Amazon Simple DB Getting Started Guide</a> for more information on getting your Key and Secret values.</li>
</ul>
</li>
<li>Log items: <code>apply_filters( 'go_slog', $code, $message, $data );</code>
<ul>
<li>$code – Some error code string (e.g. warning, error, error-type-1, etc…)</li>
<li>$message – Some error message (e.g. Attempt to contact the endpoint failed.)</li>
<li>$data – An array of data that will be helpful in debugging (e.g. <code>array( 'post_id' => 131, 'post_title' => 'Test Post' )</code>)
<ul>
<li>Note: Amazon Simple DB values have a <a href="http://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/SDBLimits.html" rel="nofollow ugc">1024 byte size limit</a>.</li>
<li>Note: we currently have no method for doing an exponentional backoff as <a href="http://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/APIUsage.html#APIErrorRetries" rel="nofollow ugc">suggested by Amazon</a> so too many attempts to write to the slog in a short amount of time can trigger ServiceUnavailable responses from Amazon SDB. In our experience this hasn’t been much of a problem but it’s on our to do list of things to improve.</li>
</ul>
</li>
</ul>
</li>
<li>View Slog: /wp-admin/tools.php?page=go-slog-show
<ul>
<li>Slogs can be paged through with up to 1000 items at a time (SDB has a 1000 item query limit)</li>
<li>Slog items can also be exported to CSV.</li>
<li>If you need to clear out your Slog you can do that from the admin panel as well.</li>
</ul>
</li>
</ol>
<h3>Contributing</h3>
<p>This plugin is developed and <a href="https://github.com/GigaOM/go-slog/" rel="nofollow ugc">available on GitHub</a>. Contributions and questions are welcome!</p>


Alternatives to Gigaom Slog

Top alternatives