Hello,
I'm trying to create a custom sensor package for some API/WEB servers that we run. The metrics I need to collect are as follows:
CPU Util (builtin)
Memory Util (builtin)
Avg response time to IIS (builtin)
ASP.net Requests per second
ASP.net requests queued
The last two are giving me fits. I know that I have to use the PERF_COUNTERS on the servers, but I can't find a sensor to match.
Is there a guide, or set-by-step instructions, on how to configure the PERF-COUNTERS, then create a custom sensor to monitor the ASP.NET targets above?
Thanks, In Advance,
TMK
Article Comments
Hello,
thank you for your KB-post.
Did you check the following guide to locate available performance counters on Windows Systems using perfmon.exe?
These Performance Counters can then be used within the PerfCounter Custom sensor.
On a side-note, since you're monitoring a web-server on which you run your own code, consider the following for very flexible monitoring/sensors:
- Create a webpage that is only accessible internally (or by PRTG) which queries and parses all relevant counters and generate an XML-like document that complies with PRTG's API for custom Sensors. There's an example in JSON and XML available here.
- Within PRTG, deploy an HTTP Data Advanced sensor pointing to the URL of your "monitoring page", i.e. http://myserver.local/prtgmonitoring
- The sensor will display on channel for each metric in the xml-document, it allows limits and alerts like any other sensor.
You can also have multiple XML-sites/documents on your webserver to publish different statistics (IIS, Application, SQL, etc). This is performance-wise a lot better/faster than using the PerfCounter Custom sensor as PRTG doesn't have to perform the whole WMI/Windows authentication and connection, only HTTP requests.
Best Regards,
Luciano Lingnau [Paessler Support]
Sep, 2016 - Permalink
Awesome! Thanks for pointing me in the right direction!
Sep, 2016 - Permalink
Hello,
thank you for your KB-post.
Did you check the following guide to locate available performance counters on Windows Systems using perfmon.exe?
These Performance Counters can then be used within the PerfCounter Custom sensor.
On a side-note, since you're monitoring a web-server on which you run your own code, consider the following for very flexible monitoring/sensors:
You can also have multiple XML-sites/documents on your webserver to publish different statistics (IIS, Application, SQL, etc). This is performance-wise a lot better/faster than using the PerfCounter Custom sensor as PRTG doesn't have to perform the whole WMI/Windows authentication and connection, only HTTP requests.
Best Regards,
Luciano Lingnau [Paessler Support]
Sep, 2016 - Permalink