DDM...how you like them Agents?
Secret Agent Man August 4 2008 12:20:08 PM
If a picture is worth a 1,000 words, then seeing something live in person must be priceless.
But what if what you want to see can't really be seen? Domino does so many things well and so much behind the scenes it is no surprise admins and developers want to find out more information as time goes by.
Domino Domain Monitor. known as DDM, was a huge step up in uncovering the hidden layers of Domino functions. But still it only goes so far and is ONLY available for Release7 and 8 for probing although it can read and understand documents found in the NAB. And it superseded these stalwarts of Domino networks or at least aggregates them, and more:
- Statistics (statrep.nsf)
- Reports (reports.nsf)
- Activity logging (activity.nsf)
- Database catalog (catalog.nsf)
- The standard log (log.nsf)
- Log analysis (loga4.nsf)
You can configure it to let you know when an Agent has a Fatal, Failure, Warning or Normal occurrence. Great! It's a start especially for new admins that had no idea an Agent could cripple their server or network. Then when you follow the path of details, usually more is found in one's statrep.nsf database,(can also configure email notifications or some other method) and you can see if the Agent was delayed and if it ran or not. You can also see who the owner of the Agent is.
Now that is all very helpful. But what if you need more help? What if you end up like Martin(thanks for looking at us and probably wanting to use us, if it were free) and needed a solution for a Release prior to 7? Or maybe you want a product more advanced than a notification? One which would not only recognize a problem, but either resolve it or produce a possible solution for it?
We built EAM, Essential Agent Master to do this from Release5 and up. What if you needed to see all your Agents and who signed them so you can stop keeping ancient admins alive in your NAB? Maybe you just have a scheduling problem between ini settings, configuration documents, Domino, Quickr, Sametime or BES housekeeping? Like a chart or a timeline to help? Check EAM out.
Why? Because as an Admin or a Developer the most common problem, especially in testing, is runaway agents or code. From a messaging perspective, the worst thing in the world is an automatic Agent scripted to send off emails or reply automatically, but coded in such a way that it never stops. How would you find it or troubleshoot it? Years of experience help, but now you can have it one database.
"Guess how many agents on the servers"
In a site of 40+ servers and over 10,000 users and you need to find one? Do you know how many agents you may have running on that network? We do! (A screenshot is available for proof when we post it from one company).
In fact we feel so confident NO ONE can guess the number we arranged with management to not only send you our famous "Domino Rocks" T-shirt but some other nice items as well for your office or staff.
So go on, take a guess, pending a winner sometime soon, we will let this run for at least a week or 2 or 4 and update you as we go along.
- Comments [0]