<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel>
<title>Backplane Journal</title><link>https://russellallen.info/</link><description>An independent blog about the machinery behind the software: logging pipelines, message queues, build automation and the home lab hardware that holds it all together.</description><language>en-US</language><atom:link href="https://russellallen.info/" rel="self" type="application/rss+xml" />
<item><title>Logging FHT Updates to a Database with FHEM DbLog Setup</title><link>https://russellallen.info/post/2010/10/17/Logging-to-a-Database.aspx</link><guid>https://russellallen.info/post/2010/10/17/Logging-to-a-Database.aspx</guid><pubDate>Fri, 09 Oct 2026 20:35:23 &#43;0000</pubDate><description>Logging FHT updates to a database in FHEM: db.conf setup, the readings worth storing, and why a logged FHT command is not an executed one.</description></item><item><title>Log4Net RabbitMQ Appender: Wiring .NET Logs to a Broker</title><link>https://russellallen.info/post/2012/07/06/Enterprise-Logging-Part-2-Logging-From-Net-to-RabbitMq-via-Log4Net.aspx</link><guid>https://russellallen.info/post/2012/07/06/Enterprise-Logging-Part-2-Logging-From-Net-to-RabbitMq-via-Log4Net.aspx</guid><pubDate>Fri, 09 Oct 2026 20:35:23 &#43;0000</pubDate><description>Log4Net RabbitMQ Appender setup for .NET apps: the three third-party appenders, the XML config, durable queues and broker outages.</description></item><item><title>Jenkins NAnt Build Pipeline: A Setup for .NET Teams</title><link>https://russellallen.info/post/2011/06/04/Creating-a-Simple-Build-Pipeline-with-JenkinsHudson-and-NAnt.aspx</link><guid>https://russellallen.info/post/2011/06/04/Creating-a-Simple-Build-Pipeline-with-JenkinsHudson-and-NAnt.aspx</guid><pubDate>Fri, 09 Oct 2026 20:35:23 &#43;0000</pubDate><description>A Jenkins NAnt build pipeline still holds up: the NAnt build step, five targets worth wiring up, and what to check when the plugin falls behind.</description></item><item><title>Graylog2 Logging and Alerting with RabbitMQ and NEsper</title><link>https://russellallen.info/post/2012/06/24/Enterprise-Logging-and-Alerting-with-Graylog2-RabbitMq-and-NEsper.aspx</link><guid>https://russellallen.info/post/2012/06/24/Enterprise-Logging-and-Alerting-with-Graylog2-RabbitMq-and-NEsper.aspx</guid><pubDate>Fri, 09 Oct 2026 20:35:23 &#43;0000</pubDate><description>Graylog2 logging and alerting: .NET apps publish GELF to RabbitMQ, Graylog2 indexes the messages, Nesper counts events and raises alerts.</description></item><item><title>FHEM Setup on Windows: Port, Perl, and First Start</title><link>https://russellallen.info/post/FHEM-Setup-on-Windows-Home-Server.aspx</link><guid>https://russellallen.info/post/FHEM-Setup-on-Windows-Home-Server.aspx</guid><pubDate>Fri, 09 Oct 2026 20:35:23 &#43;0000</pubDate><description>FHEM setup on Windows in two downloads: the fhem-6.4 zip plus a Strawberry Perl portable build, one start command, port 8083, and the service option.</description></item><item><title>C# Exception Handling Best Practices for Real Services</title><link>https://russellallen.info/post/2011/03/11/C-net-Exception-Handling-Best-Practice-As-Easy-as-1-2-3.aspx</link><guid>https://russellallen.info/post/2011/03/11/C-net-Exception-Handling-Best-Practice-As-Easy-as-1-2-3.aspx</guid><pubDate>Fri, 09 Oct 2026 20:35:23 &#43;0000</pubDate><description>C# exception handling best practices for .NET services: throw specific types, catch only what you can fix, keep the stack trace, log at the root.</description></item>
</channel></rss>
