With iControl, developers can write a variety of applications to monitor or manage a network device. This is pretty straightforward stuff. But, a more advanced implementation I continue to hear customers talking about relates to “wiring” application components to proactively tell BIG-IP how to adjust traffic flow to app servers hosting the app component based upon exceptions and classes of exceptions.

The first people talking about it were primarily in the Java world using Log4J to trap exeptions and based upon type and frequency, it could dispatch a message to BIG-IP to reduce traffic to a server hosting a problematic EJB. In fact, an F5 Solution Developer - SSIhubcity - was the first to do it. Drop 'em an email if you want to learn more... Their great guys and more than willing to talk about how they can help.

But, I'm also curious about the .NET world. So, I took a few minutes to browse http://msdn.microsoft.com and found this article... “Exception Management Application Block for .NET” (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/emab-rm.asp)

From this article, it looks like it would be pretty easy to create a custom publisher and based upon classes and frequency of .NET app component exceptions, send instructions via SOAP to BIG-IP to throttle back traffic when a .NET app starts choking in a bad way.

There's a great diagram in the article... I haven't done this BUT I'm wondering: has anyone out there tried this? If so, I would love to hear about it and how it works. Drop me an email at devcentraleditor@f5.com.