Posts Tagged ‘monitoring’

Monitor WCI Analytics with a DB query

Wednesday, May 9th, 2012

Lately I’ve found myself crafting all kinds of database queries for everything from monitoring to reporting, and I’ll be sharing many of those queries on this blog in the coming weeks. Today’s post answers a simple question: If a WebCenter Analytics service falls in the forest and no one is around to hear it, does it make a sound?

Or, more to the point, occasionally the Analytics Collector service keeps running (so many of your existing monitors don’t see it as “down”), but it stops recording data for one reason or another.

The trick is to create a monitor that basically says “let me know if no user logins have occurred in the past day”, because if nothing has been recorded, either the site you’re tracking sucks or the Analytics Collector is sucking. Using whatever tool you’d like (HP’s SiteScope is a popular one, and we use Function1’s Watcher on some sites), just create a monitor that runs the below query once per day, and notifies you if ZERO results are returned, which would indicate a problem with the collector:

select count(1) 
from asfact_logins 
where occurred > (getdate() - 1)

That way, you won’t have to explain to the boss why your Analytics report looks like this:

WCI Health Monitor: Interesting but Useless

Friday, October 28th, 2011

As I’ve dug into the rarely used diagnostic pages in the WebCenter portal, I’ve taken a second look at the System Health Monitor. As mentioned, you can get there through the URL /portal/server.pt?space=Debug, /portal/server.pt/debug, or just by going to Administration -> Select Utility… -> System Health Monitor.

Here you can see various half-baked real-time diagnostic reports. They’re interesting because you’ve probably had your portal running for years (really, are there any NEW Webcenter Interaction clients these days?) and haven’t seen these reports. But they’re not particularly useful because they aren’t reliable – false “offline” reports are common – and don’t provide a decent interface to tie into a reasonable monitoring solution. A REST-based solution would be nice to be able to query the status of various services, for example.

Maybe I’m being hard too hard on this thing. While the high-level “Related Services” or “Remote Host” reports don’t seem to work all that well, if you click on the “Remote Host” links you get a Web Service report showing the status of the various services running on that Remote Server:

Yeah, I suppose that could be useful. I better go figure out why half my portlets are showing offline. You prob’ly should too…

Cool Tools 20: New Relic

Saturday, June 4th, 2011

Every once in a while, a wicked cool app comes along that you look at and say “holy cow, that’s AMAZING!”.

Such is the case with New Relic, a code-level monitoring tool provided as a service. It supports Java, .NET, PHP, Rails, and others through the use of client-side agents that report to New Relic servers, which provide an unprecedented level of diagnostic reporting for your monitoring needs. Unlike most monitoring services, New Relic actually instruments your code (or even out-of-the-box applications) with diagnostic capabilities that not only tell you if your app is performing slowly, but exactly where in the code it’s taking the most time:

And that’s just scratching the surface – here’s a chart showing that, for our Atlassian Confluence installation, response time stays flat as load increases (indicating that we’ve got good scalability built into our system):