locked
Rename Windows Server 2003 performance counters RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, 

    I'm monitoring MSMQ 2003 using System Center Operations Manager 2007R2. I have been requested to monitor the number of messages in the MSMQ error queues.  II first though I could use the exisiting 'Number of messages' monitor included in the MSMQ2003 MP.  Buth this is not the case as it is not recommended (by Kevin Holman) to use this monitor if the healthy state is 0 messages in the queue.

    So I set about creating custom monitors which worked fine for our MSMQ 2008R2 servers.

    The problem I have is that the MSMQ names are very long and Windows 2003 has a charater limit.  So the my queue names are:

    servername\private$\company.finance.ledger.bus.endpoints.financialtransactioncreated.error

    servername\private$\company.finance.ledger.bus.endpoints.financialtransactioncreated.input

    servername\private$\company.finance.ledger.bus.endpoints.financialtransactioncreated.input.audit

    actually appear in the performance counter as:

    servername\private$\company.finance.ledger.bus.endpoints.financ

    servername\private$\company.finance.ledger.bus.endpoints.financ#1

    servername\private$\company.finance.ledger.bus.endpoints.financ#2

    This means I can't pick out a particular queue name to specifiy in the Monitor performance properties.  The monitor itself is a windows performance counter monitor with a simple threshold.  Is there a way to rename the perfomance monitor counters so that they under the windows 2003 character limit?  I can't change the queue names so I'm stuck as to how to monitor the queues.

    Tuesday, February 1, 2011 2:27 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Try a wild card in the name counter name (does not work with object name)
    Microsoft Corporation
    Monday, March 28, 2011 4:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered". Either the previous steps should be helpful for many similar scenarios and will be marked as answer, or this post will be marked as answer in order to close the thread. Feel free to re-open the thread if you have additional information about this specific case or to open a new thread for a new case. In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks,

    Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 + 2013 and Microsoft Community Contributor 2011 + 2012 Recipient

    Tuesday, March 19, 2013 3:38 PM