http://blogs.technet.com/jonathanalmquist/archive/2009/03/19/is-alert-grooming-working.aspxEvaluate whether alert grooming is working.&#160; No result is good. $Threshold = (Get-Date).ToUniversalTime().AddDays(-(get-defaultsetting)[42].Value).Date;Get-Alert | Where {$_.TimeResolved -and $_.TimeResolved.Date -lt $Threshold} | Measure-Objecten-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/jonathanalmquist/archive/2009/03/19/is-alert-grooming-working.aspx#3221293Thu, 02 Apr 2009 01:50:42 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3221293Nathan<p>I ran this query against my Opsmgr database and got 38. &nbsp;Any tips on troubleshooting this?</p>http://blogs.technet.com/jonathanalmquist/archive/2009/03/19/is-alert-grooming-working.aspx#3221314Thu, 02 Apr 2009 02:45:27 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3221314jtalmquist<P>First, I want to say that I just realized&nbsp;I was getting local time.&nbsp; I&nbsp;just changed the command to get GMT, which will be&nbsp;more accurate depending on your time zone and when you actually run the query.&nbsp; Try running the&nbsp;updated query, and&nbsp;see if that returns the same result.</P> <P>If same result...&nbsp;</P> <P>Alert Grooming in the database is a fairly simple process. &nbsp;It simply selects alerts that have a resolution state = 255 and TimeResolved &lt;&gt; NULL. &nbsp;Then calculates, if TimeResolved + Resolved Alert retention days = Today...groom alert. &nbsp;So, if there is a problem I would first check the InternalJobHistory.</P> <P>SELECT * FROM InternalJobHistory Order By InternalJobHistoryId DESC</P> <P>If you see any jobs with a status code &lt;&gt; 1, then the job isn't starting or finishing as expected. &nbsp;You could run the job manually, to see if it succeeds. &nbsp;Or, check again tomorrow and see if it ran successfully. &nbsp;If either results in a status code &lt;&gt; 1, then you'll need to do some further digging.</P>http://blogs.technet.com/jonathanalmquist/archive/2009/03/19/is-alert-grooming-working.aspx#3221777Fri, 03 Apr 2009 02:50:52 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3221777nathan<p>Thanks for the update. &nbsp;The new query returns no data. &nbsp;Not even a 0. &nbsp;I assume this is good!</p> <p>I also checked that Internaljob status and all have a code of 1.</p> <p>So it appears that all is healthly. &nbsp;Thanks again.</p>http://blogs.technet.com/jonathanalmquist/archive/2009/03/19/is-alert-grooming-working.aspx#3221789Fri, 03 Apr 2009 03:54:48 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3221789jtalmquist<P>That's right, Nathan. &nbsp;No result from the query is a good thing. &nbsp;That means no alerts were "stuck" after grooming finished. &nbsp;I suppose I could write some output if the command returns no data, but I'm only giving core examples here.</P> <P>The reason why this needs to calculate based on GMT is because that's how the Date-Time stamp is stored in the database. &nbsp;So, if you are located in GMT-6:00, for example, the query would return today's alert count if you run the command afte 7:00PM local time. &nbsp;This would result in a false positive in the command results.</P> <P>Now I've got to go back and fix all my other commands that use an alert field containing a Date-Time stamp in a calulation. &nbsp;Arghhh...</P>