<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monitoring on Rudi Bruchez</title><link>https://www.pachadata.com/en/tags/monitoring/</link><description>Recent content in Monitoring on Rudi Bruchez</description><generator>Hugo</generator><language>en</language><atom:link href="https://www.pachadata.com/en/tags/monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>Basic counters</title><link>https://www.pachadata.com/en/docs/howtos/administration/monitoring/basic-counters/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.pachadata.com/en/docs/howtos/administration/monitoring/basic-counters/</guid><description>&lt;p&gt;Here is a list of the Windows and SQL Server performance counters to watch, to make sure SQL Server is running properly.&lt;/p&gt;&#10;&lt;h2 id="processor---processor-time"&gt;Processor / % Processor Time&lt;/h2&gt;&#10;&lt;p&gt;Total processor time as a percentage, and per core where useful, to watch how the threads are distributed.&lt;/p&gt;&#10;&lt;h2 id="physical-disk--avg-disk-secread"&gt;Physical Disk / Avg. Disk sec/Read&lt;/h2&gt;&#10;&lt;p&gt;Watch this on the disks holding the SQL Server data files.&lt;/p&gt;&#10;&lt;p&gt;It is the average time in seconds of a data read from disk — a latency measurement. Depending on the type of disk, local or remote, the value should ideally stay below .025, that is 25 milliseconds of latency.&lt;/p&gt;</description></item><item><title>Monitoring with PRTG</title><link>https://www.pachadata.com/en/docs/howtos/administration/monitoring/prtg/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.pachadata.com/en/docs/howtos/administration/monitoring/prtg/</guid><description>&lt;p&gt;PRTG Network Monitor is a commercial monitoring product from Paessler. This guide explains how to configure it to monitor SQL Server.&lt;/p&gt;&#10;&lt;p&gt;There does not appear to be a package or counter group tailored to SQL Server natively in PRTG. You have to add them by hand.&lt;/p&gt;&#10;&lt;p&gt;To do that, add a &lt;a href="https://www.paessler.com/manuals/prtg/perfcounter_custom_sensor"&gt;&amp;ldquo;Windows PerfCounter Custom&amp;rdquo;&lt;/a&gt; sensor, and register the Windows performance counters related to SQL Server.&lt;/p&gt;&#10;&lt;p&gt;The simplest approach is to look the counters up directly on the SQL Server machine to identify the ones you care about, then enter them by hand in PRTG.&lt;/p&gt;</description></item></channel></rss>