Skip to main content

monitoring event storms in mom 2005 ...

as an avid mom administrator, i'm sure you check your total # of events per day, right?  this is really, the only real way to know if events are firing off in a manner that's out of control or heading that way.  some events aren't set to alert when they're picked up so there's a high likelihood that this could be happening in your environment, without your knowledge.

if you're old-school, you can walk in every morning, get your cup of coffee, fire up a t-sql query program and execute something like this:

SELECT COUNT(*) AS 'Event Count'
FROM SDKEventView
WHERE TimeGenerated > GetDate()-1


a successful execution will bring back the total number of events from the day prior.  i suppose if that's all you need, you can stop reading right here and go back to the way you were.  but if you're a lazy, little squirrel then keep reading.

still reading, aren't you? :)  since this method can be a monotonous pain in the ass, try something a little more automated.  you have mom for crying out loud.  make it work.  instead of walking in every morning and doing this ourselves, wouldn't it be so much more productive to have mom do it for us?  with that in mind, all we need is a script.  mom will handle the rest. 

for that, here's a script that will perform the exact same thing above with an added feature.  it will take the event count and throw it into the performance data stream and write it to the database as a performance counter.  we can do all kinds of things with it in that format.  to start off... here's the script:

Dim objConn
Dim objRS

Set objConn=CreateObject("ADODB.Connection")
Set objRS = CreateObject("ADODB.Recordset")


sDataBase = ScriptContext.Parameters.Get("DataBaseName")
sMgmtGroup = ScriptContext.Parameters.Get("ManagementGroup")

objConn.ConnectionString = _
     "Driver={SQL Server};" &_
     "Server=" & sDataBase & ";" &_
     "Database=Onepoint;" &_
     "Trusted_Connection=yes;"

'Open the database connection
objConn.Open

'Define the SQL query
strSQLQuery =       "SELECT COUNT(*) AS 'Event Count' " & _
                       "FROM SDKEventView " & _
                       "WHERE TimeGenerated > GetDate()-1"

'Open the recordset
objRS.Open strSQLQuery, objConn ', adOpenForwardOnly, adLockReadOnly, adCmdText

objRS.MoveFirst
iTotalEvents = objRS.Fields(0)

'Close up the objects
objRS.Close
objConn.Close
Set objRS = Nothing
Set objConn = Nothing

CreatePerfData "MOM",sMgmtGroup,"Total Events",iTotalEvents

Sub CreatePerfData(strObjectName,strInstanceName,strCounterName,numValue)
    Set objPerfData = ScriptContext.CreatePerfData
   objPerfData.ObjectName = strObjectName
    objPerfData.InstanceName = strInstanceName
    objPerfData.CounterName = strCounterName
    objPerfData.Value = numValue
    ScriptContext.Submit objPerfData
End Sub


it's not going to work if you just copy and paste it into mom.  you'll have to create a script in the "scripts" container (no, really?) and add some parameters.  if you look at the script, you'll see the parameters you need.  they're prefaced by paramters.get.

  • DatabaseName
  • ManagementGroup

once you've got the script in there, create a rule group, attach it to your mom management server computer group and create a timed provider to execute the script.  i set mine to synchronize every 24 hours at 00:01 just to make sure that it executes around the same time every day.  for the responses, add the script you created above with the parameters filled out to match your environment.

once the script executions begin, you'll be able to graph the performance counter of your total events.  it should come in like this:

  • performance object name: MOM
  • performance instance: [ManagementGroup]
  • performance counter: Total Events

when you graph it out, you'll be able to see the results of your labor:

image

Comments

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m