Ad Widget

Collapse

IIS Application Pool Request/Sec and Transactions/Sec

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Indalecio_Trujillo
    Junior Member
    • May 2024
    • 1

    #1

    IIS Application Pool Request/Sec and Transactions/Sec

    I have created these items to obtain these performance counters values.
    IIS: AppPool {#APPPOOL} Transactions/Sec perf_counter_en["\ASP.NET Applications({#APPPOOL})\Transactions/Sec"]
    IIS: AppPool {#APPPOOL} Request/Sec perf_counter_en["\ASP.NET Applications({#APPPOOL})\Requests/Sec"]

    but im getting this message on zabbix

    "Cannot obtain performance information from collector."

    I have added these items in application pools discovery.


    Any idea why I'm getting this error message?

  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4807

    #2
    Might be, that those perf counters are not enabled on host...

    Comment


    • Indalecio_Trujillo
      Indalecio_Trujillo commented
      Editing a comment
      Yes, the perf counter exist on server i can see using performance monitor
  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4807

    #3
    Then I have no idea.. Too few experience with perf metrics...

    Comment

    • PeterZielony
      Senior Member
      • Nov 2022
      • 146

      #4
      iis management scripts and tools installed?

      Hiring in the UK? Drop a message

      Comment

      • amjelnes
        Junior Member
        • May 2014
        • 4

        #5
        Not sure it's related but I just had an issue with two servers of 4 identical servers where for some reason perf counters failed on the two.
        When opening perf monitor on the affected servers I would get an error pop up.
        Fix was:
        cmd elevated:

        Code:
         cd c:\windows\system32
          lodctr /R
            cd c:\windows\sysWOW64
          lodctr /R
        If any errors when you run those commands run them once more.

        After restarting agent service, data started flowing again and errors went away

        Comment

        Working...