Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Syskit Insights latency screen gives you a detailed overview of all the ping intervals made.
According to Microsoft's guidelines, intra-farm latency should be <1 ms one way 99.9% of the time over a period of ten minutes. Microsoft defines Intra-farm latency as the latency between the front-end web servers and the database servers. However, we take it a step further and ping every server in the farm, not just the database server.
On the left side of the screen, you can observe the success rate of pings sent to each monitored server.
Success Rate column: Gives you the number of successful pings for that server in the last interval. The interval will be displayed as critical if the ping success rate is not over 99.9%.
Intra-farm Latency column: Tells you if the latency for given server is according to the guidelines (99.9% of pings under 1 ms in a 10-minute interval).
On the right side are server interval details. Click on any server and its data will appear.
Pings are sent in 10-minute intervals.
The Sent Pings column gives you the number of sent/received pings.
Pings longer than 1 ms tells you how many pings took longer than 1 ms. By default, the value is set to 1 ms per Microsoft's guidelines.. This can be changed in Settings -> Intra-farm Latency Configuration
Maximum Latency tells you the maximum encountered latency in that interval.
The Syskit Insights home page gives you an overview of your index's contents as well as a general performance overview regarding your farm health.
If you are monitoring multiple SharePoint farms, they will all appear here. The metrics shown will change depending on which farm or server is selected.
Server Status – Information about how many servers are in the critical, warning, healthy or offline state.
Logs – Total number of events collected per day. If you click on the date or on the column representing the events, the graph will change into a Logs by Server view and you will see the total number of events per server collected for the selected day.
The Total Index Size and Number of Events in the index are shown at the top of the graph. Also, you can see the Last Update Time of the index.
The index size can fluctuate because of how index reorganization works. Also, since the data retention job deletes data day by day, sudden drops in this metric are possible.
Alerts – An overview of alerts received for the entire farm. For a detailed view, click the View All Alerts button at the bottom of the tile.
CPU Utilization – The top three servers with the highest processor usage based on the last 15 minutes of data collected.
Disk Space Usage – The top three disks by disk space used across all servers, based on the last collected value.
SharePoint Services Status – Whether SharePoint Timer, Search, or User Profile Services are running on the selected farm.
Intra-farm Latency – Shows the servers (if any) with high latency. At the bottom, the + X Critical Servers button will take you to the latency tab, which has detailed information about latency.
Page Response – Shows whether the pages you are monitoring are offline or critical.
To see the server dashboard, click on any server in the navigation.
Logs – The graph will show the number of events by type per selected server on a given day. You can see the total number of event log, SQL and ULS events.
Alerts – The latest alerts for the selected server.
Server Performance – A list of performance counters currently in a critical or warning state.
Services Status – Whether there is a stopped service on the selected server.
Intra-farm Latency – Latency status for the selected server.
Detailed overview on how the Syskit Insights monitors Page Performance.
First you need to:
Add New Page 1. On the Page Performance tab, click Add New.
Select the farm for which you wish to add pages (if you have more than one).
Enter the pages you wish to monitor, either one by one or by importing them from a file. When importing from a file, put each page on a separate line.
Click Import and the import check will start.
For on-premises pages, we use the service account you provided in the configuration wizard. You need to ensure that this account has the necessary permissions.
If you want to monitor a SharePoint Online site, a popup window will ask you to provide the required credentials. When prompted to remember the login, make sure to click yes. The benefits are:
Credentials will be reused for all connections to the same tenant.
The credentials will be valid for more than 5 days.
For more about monitoring SharePoint Online sites, click here.
The pages added will be shown on the Page Performance dashboard.
The data shown here are average values, calculated for the period selected in the data range filter, which is by default the last 24h.
If you want to receive a notification when a metric exceeds its threshold, then set up an alert. For more information on how to do so, please see this article.
Metrics over their threshold will be red on the dashboard. If they are under their threshold, they will be green.
If you click on a page (each entire row is clickable), you will see detailed information about that page, such as SharePoint header metrics and file requests.
Uptime - Calculated time of page availability during the selected period (based on the data range filter).
X-SPHealthScore - The server can monitor the current load and its ability to process requests. If it is monitoring the load, it will return load information to the client in the X-SPHealthScore header. This header is between 0 and 10, where 0 represents a low load and a high ability to process requests and 10 represent a high load and that the server is throttling requests to maintain adequate throughput.
SPRequestDuration - This is how long, in milliseconds, a request took to process on the server.
SPIISLatency - The time in milliseconds taken in the front-end web server after the request has been received by the front-end web server before the web application begins processing the request.
Page Response Time - The total time in milliseconds required to download the page.
SPRequestGuid - While ULS logs have correlation IDs, SharePoint pages have request GUIDs.
The File Requests feature simulates real-world page usage. There is no caching and the numbers shown are what a real user might expect when accessing the page. Syskit Insights will try to load and emulate the browser opening the page.
The data shown are from the 20-second interval during which Syskit Insights monitors the page.
You can monitor Size, Load Time, and Item Count for certain elements of the page. These elements are: HTML, JavaScript, images, CSS, and Fonts. Syskit Insights uses The Coach to monitor performance of your pages, and from the information collected, we calculate the Page Score. For more information, please see this link.
On the right-hand side, there is a waterfall model of a page, like the one you can find in Google Chrome's DevTools, showing you every element loaded.
File requests are collected every 6 hours.
Starting with version 1.1, Syskit Insights includes a web interface. It enables users to access all the functions of Syskit Insights using any web browser.
Syskit Insights Configuration Wizard has a separate step where users can configure the Syskit Insights web interface. Users can choose to enable it or disable it completely. Additionally, users can define which user accounts can access the Syskit Insights web interface. By default, only the user account running the Configuration Wizard and service user account are added to the group of users with permission to access the Syskit Insights web interface. Users can add unlimited user accounts to this group. The people picker will search Active Directories for the users.
Syskit Insights has only been tested on the latest version of Google Chrome but should also work on the latest versions of Microsoft Edge, Mozilla Firefox, and Safari.
The Syskit Insights web interface is hosted at http://{servername}:{port} or at https://{servername}:{port}. In order to use https, the user must set up the certificate manually. You can follow the steps
The Syskit Insights Health Overview gives you an instant overview on the health of your farms, which is based on the data gathered for a selected farm and time interval. An overview can be generated for two time intervals — “Yesterday” or “Last 7 days.” It shows trend comparisons for the current interval and for the previously completed time interval (in percentages). Each report is divided into the following sections:
The Events section provides an overview of events and collected logs within a selected time interval. It has two categories:
Index size— the total disk space occupied by Syskit Insights and how much it has grown since the start of the interval. Its growth depends upon the farm size. Insights will stop collecting data once a maximum limit has been reached.
Entries—an overview of entries for that interval. Entries are sorted by level (Critical, Unexpected, Warning, Error and Exception) and by type (ULS, SQL and Event Log).
For more details on Events, please see this article.
The Performance section provides a performance overview for your farm for a selected time interval. It is divided into the following three categories:
Incidents — the number of performance incidents that have occurred in a set interval;
By category — the counters that have generated the highest number of alerts in a set interval;
By server — the servers that have generated the highest number of alerts in a set interval.
For more details on performance please see this article.
The Alerts section shows the number of alerts generated in a specified time interval and which types of alerts occurred most frequently during this interval.
For more details on Alerts see this article.
The SharePoint Services section provides an overview of SharePoint services, giving you an insight into how many services were stopped, and also how many alerts were generated for the Central Administration or how many service alerts were generated in a specified interval.
For detailed information on managing your SharePoint services, please see this article.
The Page Performance section provides a performance overview on the time interval of any SharePoint pages you monitor. It shows the number of alerts that were generated for all headers and file requests that you have previously enabled for monitoring.
For more details on page performance, please see this article.
The Latency section shows the latency statistics for average ping time between the servers of your farm for a selected interval. It highlights whether there was high latency on the servers. Microsoft recommends that pings should take less than 1 ms, to avoid bad user experience. Pings are recorded every 10 minutes.
For more details on latency, please see this article.
If you wish, you can schedule a health report. To do so, click on the Schedule button and enable Report Scheduling. After that you can choose which sections you want to include in the report, and opt to receive info on report frequency and send time. To receive the report, your email settings must be configured.
This article gives a basic overview of how to use Syskit Insights's Event Viewer.
This article gives a basic overview of how to use Syskit Insights's Event Viewer.
Select the Event Viewer tab in the left navigation.
Select the farm for which you wish to perform the search.
Selecting a farm is only available if multiple farms are used with the same Syskit Insights database.
Select the time range in which to search for events.
Please limit the range as much as possible for optimal performance.
First search will automatically be done with the "Last 10 Minutes" time interval.
Enter your search query. Click here for more details on writing a search query.
An empty query (all events within the specified time range) is also supported, but use sparingly, or on small time ranges. Just click search or press the enter key.
By default, Syskit Insights uses a layout similar to a search engine to display the results. This layout can be changed to a more compact grid layout by using the dropdown button just below the search button. The results can also be exported to an Excel file.
You can refine your query by:
Type of event (ULS, Event Log, SQL)
Additional refiners such as Server and Level are positioned to the left and will modify the query text.
Clicking on terms in the search results will also modify the query text.
for the compact grid layout expand the search result for this functionality to be available.
When satisfied with the constructed query, press the search button again.
You have created a very useful query and would like to be notified when an event that satisfied this query appears? No problem, just create an alert by clicking the alert button on the search results page. Click here for more details.
The Syskit Insights Alerts page gives you an overview of your alerts.
There are five categories:
Performance Counters tab will automatically populate as soon as the application concludes the status's of the performance counters. That usually happens within 15 minutes of starting the application. The columns we provide here are: Farm, Server, Counter, Instance, Avg. Value, Time. A red square in front of the server name indicates that the counter is in Critical state. Yellow square indicates a warning status. Clicking on any Performance Alert will open a detailed view on the right hand side of the window. There you can find more information about the specific Performance Counter. Such as its description, the defined values for the thresholds, and the graph with the collected values. For more information on how to manage the alerts, see this article.
Events tab will be populated as soon as you define a new Alert. For more information on how to do this, click here.
The columns we provide here are: Farm, Server, Name, Query, Time. The square in the Server column is always grey and is indicative of Events Alert. Clicking on a Events Alert will open the details on the right hand side, which will show you the results of the defined query. Clicking on the View Details will preselect the query and take you to the Event Viewer screen.
SharePoint Status tab will automatically be populated. By default Syskit Insights checks the SharePoint Timer Service status and the Central Administration (CA) site status. If the Timer Service job is stopped or the CA is unavailable, you will be notified every 30 minutes. The columns we provide here are: Farm, Server, Source, Value, Time. See the Manage Alerts article to see how you can check the status of another site.
Please note! To check (ping) a SharePoint site we are using the credentials of the service account you provided during the configuration of the Syskit Insights. Also, it is not possible to use forms authentication.
The Latency tab will automatically populate as soon as the application finishes the first ping interval. That usually happens within 15 minutes of starting the application. The columns provided here are: Farm, Server, Bad Pings (number of), and Time. Click on the desired line to open the latency intervals details on the right side of the screen. This shows the maximum latency in that interval, number of pings sent and received, and number of pings that took longer than 1 ms.
The Page Performance tab will only populate if you have added SharePoint pages to monitor. X-SPHealthScore and Page Response Time headers are monitored by default. For more information about Page Performance, click here.
In order to receive the email notification of your alerts you need to enable them. Go to Settings -> Email settings. Select the: "Send email notifications when alerts occur" and fill out all the required fields.
For more information on Insights features see this article.
Detailed overview on how the Syskit Insights collects and presents farm performance data.
Syskit Insights collects performance data by default. This behaviour can be modified in the settings. Additionally user can change the performance data collection interval. The default value is 60 seconds.
The Syskit Insights Agent relies on performance counters to monitor the server performance. The Syskit Insights calculates the following server status:
Healthy – colored green
Warning – colored yellow
Critical – colored red
Offline or not accessible – colored grey
The server is in critical state if at least one metric collected is in critical state, in warning state if at least one metric is in warning state and none of the other metrics are in critical state, and the server is in healthy state if there are no metrics in warning or critical state.
The individual metrics are calculated based on their average value during the last 15 minutes. By using this approach the Syskit Insights can ignore short spikes in activity.
You can filter servers using these statuses. While on Performance tab click on the Filter icon, located right of the search bar. Clicking on the desired status will filter servers. You can even combine more then one status. Such as Warning and Critical.
When the user is located on Performance tab of Syskit Insights a help link will be show. Following that link user can see all the details about the metrics Syskit Insights Agent collects. The description of each metric, warning and error thresholds are listed (where applicable).
The farms performance overview dashboard shows all farms currently monitored by Syskit Insights Agent. It shows status for each server in those farms. Additionally it displays main performance metrics (CPU usage, RAM usage, network usage and disk usage) for each server in a concise manner. Users can choose between three different views: Compact, Tiles, Grid. All views display the same data just in different format. The dashboards are continuously updated as the new data is collected.
There are four option by which you can group the servers. They are:
Farm - grouping will be done by the farm. With Critical servers first, then Warning, Healthy, and the Offline ones.
Type - the servers will be divided in two groups - SharePoint and SQL Servers.
Status - Critical servers first, then the ones with Warning status, then Healthy and the Offline ones.
None - there will be no special grouping, all servers are together. Status is still shown in the usual manner. Critical -> Warning -> Healthy -> Offline.
Sometimes the server will be shown in warning or critical state when none of the four general metrics are in warning or critical state. This indicates that some of the metrics which are not shown on the main dashboard are in critical or warning state.
By clicking on farm name users can navigate to detailed farm overview dashboard and by clicking on specific server the users can navigate to server overview dashboard.
The detailed farm overview dashboard shows more in-depth data about each server in the farm but is limited to just a single farm. Users can view last fifteen minutes of CPU usage, current RAM usage and status of each disk partition on specific server. This dashboard is also continuously updated as the new data is collected. By clicking on specific server users can navigate to Server Overview Dashboard.
The server overview dashboard shows all metrics that are collected for each server. The metrics are separated in different categories. The server role in the SharePoint farm determines which categories are assigned to each server. The categories are assigned to a server following these rules:
General and Disk categories – these categories are assigned to all servers, and the metrics in those categories are collected for every server in farm. The General category shows CPU, RAM, network and disk usages while the Disk category shows detailed information about disks performance
IIS/ASP.NET category – this category is assigned only to a SharePoint Frontend server. These metrics show the usage of IIS on each Frontend server.
.NET category – this category is assigned to all non-SQL SharePoint servers. The metrics in this category show how the processes on each non-SQL SharePoint server are using .NET framework capabilities.
SQL category – this category is assigned to all SQL servers in SharePoint farms. Each server in Always-On cluster is included as well. These metrics show the SQL server performance.
SQL (Named) category – this category is shown only if you are using a named instance - counters collected are specifically for that instance of SQL server.
Search category - this templates helps you track a number of 'search' relevant counters on servers in SharePoint farm. Diagnose various problems and performance issues with ease.
If the metric is in a warning or critical state the notification next to the metric name will indicate a problem using a red color to indicate a critical state, or a yellow to indicate a warning. The status of each metric is calculated based on the average in the last fifteen minutes. The status of metrics for which the warning or critical thresholds are not defined will not be calculated.
Hovering over any chart will show a maximize button in the top right corner. Click it to expand the chart over the entire screen. You can toggle Show thresholds button to show or hide the threshold lines (both critical and warning). When the threshold lines are active the chart will scale to fit both the threshold lines and the values. When the threshold lines are turned off, the chart will be rescaled to optimally include only the collected chart values. If the selected chart/counter has more than one instance, on the top right of the chart (next to the show thresholds button) there will be a dropdown where you can change the instance you wish to observe.
The users can change the time range to view older data. By default Syskit Insights shows data collected during the last sixty minutes. The metric status is still calculated based on the last 15 minutes.
Detailed overview farms and servers that are being tracked. Also, different options on how to add a new farm or a server into existing farm.
On the main application window click Farms. You will see a number of added farms, servers and a License Server Limit, as well as an overview of all the servers in farms. You can also see which SQL servers are in a cluster and instances that are monitored.
To add a farm you simply need to enter a name of the SharePoint server which is a part of that farm. We will autodiscover all other servers in the farm.
Enter (SharePoint) server name or FQDN and press Test Connection. If the everything is in order green check mark will appear. Click Next to continue. 1. In the next step you will see the detected farm. You can configure server roles, edit ULS Path, modify detected farms' name or remove servers from a farm.
If you wish to add an extra server to the farm click Add Server.
Enter the server name, select a role and click Add server. When done click Save and the server will be added to the farm.
Finally you will see an overview on how many servers you are adding. Click Finish to save your work.
You can search for Organisational Units by name, or you can use a dropdown menu to select the ones you want.
After the scan is complete you will see the detected farm/s. You can configure server roles, edit ULS Path, modify detected farms' name or remove servers from a farm.
If you wish to add an extra server to the farm click Add Server.
Enter the server name, select a role and click Add server. When done click Save and the server will be added to the farm.
Finally you will see an overview on how many servers you are adding. Click Finish to save your work.
You can import farm and servers from SPDocKit database. SPDocKit is SharePoint Admin tool for farm documentation and permission management. See here for more information. We support SPDocKit database from version 7 and onward. And, the service account you are using needs to have read permissions on the SPDocKit database. Please note that the service account we are talking about now, is Syskit Insights service account, and not the account you are using with SPDocKit. 1. Enter the Database Server and Name. Choose Authentication type and click Test Connection. Click Next to continue. 1. On Detected Farms screen you will see the detected farm. You can configure server roles, edit ULS Path, modify detected farms' name or remove servers from a farm.
If you wish to add an extra server to the farm click Add Server.
Enter the server name, select a role and click Add server. When done click Save and the server will be added to the farm.
Finally you will see an overview on how many farms and servers you are adding. Click Finish to save your work.
Also, you can manage already added farms by clicking the Manage button.
You can configure server roles, edit ULS Path, modify detected farms' name or remove servers from a farm.
To add a new server click Add Server.
Enter the server name, select a role and click Add server. When done click Save and the server will be added to the farm.
Note that you can also add 3rd party servers, such as: Office Web Apps Server...
When done, click Save to confirm your changes.
When adding a new server to a farm, you don’t need to add it manually. Simply click the Refresh Farm Configuration button and all new servers will be added. Also, your ULS location, if changed in the meantime, will also be updated. A system job will also automatically perform this refresh every night at 4:00 a.m.
Performance Counters help page offers you a list of all the available counters along with their thresholds.
Syskit Insights monitors your server performance by periodically collecting performance counter values. The counters are split into several templates that are applied to your server based on the role it plays in your farm.
Below are the counters that Syskit tracks with their corresponding (default) critical and warning thresholds.
Default template contains counters that are collected for all servers.
% Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
Warning when the value is above 85%. Critical when the value is above 95%.
Displays the amount of used memory, in GB, on a computer.
Warning when there is less than 0.5 GB available. Critical when there is less than 0.25 GB available.
Number of kilobits received and sent per second on the network adapter.
Warning when the value is above 5000 Kbps. Critical when the value is above 10000 Kbps.
Number of bytes read from and written to the disk per second.
Warning when the value is above 100 bytes/sec. Critical when the value is above 200 bytes/sec.
IIS/ASP.NET template helps you keep an eye on your IIS servers in SharePoint farm. Diagnose various problems and performance issues with ease.
Current Connections is the current number of connections established with the Web service.
Bytes Total/sec is the sum of Bytes Sent/sec and Bytes Received/sec. This is the total rate of bytes transferred by the Web service.
The rate HTTP requests using the GET method are made. Get requests are the most common HTTP request.
The rate HTTP requests using the POST method are made.
The number of times that the application pool has been recycled since Windows Process Activation Service (WAS) started.
The number of requests waiting to be processed.
Warning when the value is above 400. Critical when the value is above 1000.
The number of requests rejected because the request queue was full.
Warning when the value is above 2. Critical when the value is above 5.
Number of times a worker process has restarted on the machine.
Warning when the value is above 1. Critical when the value is above 5.
The number of milliseconds the most recent request was waiting in the queue.
Warning when the value is above 800. Critical when the value is above 1200.
SQL template enables you to efficiently monitor your SQL servers. With specified counters you can quickly find possible bottlenecks and performance issues.
Number of users connected to the system.
Percentage of pages that were found in the buffer pool without having to incur a read from disk.
Warning when the value is below 90. Critical when the value is below 80.
Number of buffers written by buffer manager's lazy writer.
Warning when the value is above 15. Critical when the value is above 20.
Number of seconds a page will stay in the buffer pool without references.
Warning when the value is below 400. Critical when the value is below 250.
Number of SQL batch requests received by server.
Warning when the value is above 1000. Critical when the value is above 1500.
Number of SQL compilations.
Warning when the value is above 100. Critical when the value is above 150.
Number of SQL re-compiles.
Warning when the value is above 1. Critical when the value is above 2.
Number of page splits per second that occur as a result of overflowing index pages.
Warning when the value is above 200. Critical when the value is above 300.
Number of unrestricted full scans. These can either be base table or full index scans.
Number of latch requests that could not be granted immediately and had to wait before being granted.
Total latch wait time (milliseconds) for latch requests that had to wait in the last second.
Number of lock requests that could not be satisfied immediately and required the caller to wait before being granted the lock.
Warning when the value is above 1. Critical when the value is above 2.
Number of transactions started for the database.
Processor Queue Length is the number of threads in the processor queue. Unlike the disk counters, this counter shows ready threads only, not threads that are running. There is a single queue for processor time even on computers with multiple processors. Therefore, if a computer has multiple processors, you need to divide this value by the number of processors servicing the workload. A sustained processor queue of greater than two threads generally indicates processor congestion.
Warning when the value is above 2. Critical when the value is above 5.
Disk template helps you keep an eye on your disks across the SharePoint farm. Diagnose possible bottlenecks and performance issues with ease.
Avg. Disk Queue Length is the average number of both read and write requests that were queued for the selected disk during the sample interval.
Warning when the value is above 2. Critical when the value is above 4.
Disk Transfers/sec is the rate of read and write operations on the disk.
Warning when the value is above 200 transfers/sec. Critical when the value is above 400 transfers/sec.
Free GB displays the unallocated space on the disk drive in GB.
Warning when the value is below 5 GB. Critical when the value is below 3 GB.
Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It is the sum of Memory\Pages Input/sec and Memory\Pages Output/sec. It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.
Warning when the value is above 20. Critical when the value is above 50.
Disk Reads/sec is the rate of read operations on the disk.
Avg. Disk Read Queue Length is the average number of read requests that were queued for the selected disk during the sample interval.
Avg. Disk Write Queue Length is the average number of write requests that were queued for the selected disk during the sample interval.
% Idle Time reports the percentage of time during the sample interval that the disk was idle.
Warning when the value is below 20. Critical when the value is below 10.
% Free Space is the percentage of total usable space on the selected logical disk drive that was free.
Warning when the value is below 30. Critical when the value is below 20.
Cache Faults/sec is the rate at which faults occur when a page sought in the file system cache is not found and must be retrieved from elsewhere in memory (a soft fault) or from disk (a hard fault). The file system cache is an area of physical memory that stores recently used pages of data for applications. Cache activity is a reliable indicator of most application I/O operations. This counter shows the number of faults, without regard for the number of pages faulted in each operation.
Critical when the value is above 1.
The amount of the Page File instance in use in percent. See also Process\Page File Bytes.
Warning when the value is below 50. Critical when the value is below 75.
The peak usage of the Page File instance in percent. See also Process\Page File Bytes Peak.
Total Bytes/sec is the rate the Server is reading and writing data to and from the files for the clients on this CPU. This value is a measure of how busy the Server is.
Page Reads/sec is the rate at which the disk was read to resolve hard page faults. It shows the number of reads operations, without regard to the number of pages retrieved in each operation. Hard page faults occur when a process references a page in virtual memory that is not in working set or elsewhere in physical memory, and must be retrieved from disk. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It includes read operations to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files. Compare the value of Memory\Pages Reads/sec to the value of Memory\Pages Input/sec to determine the average number of pages read during each operation.
.NET template helps you track .NET counters on servers in SharePoint farm. Diagnose various problems and performance issues with ease.
This counter displays the number of times the generation 0 objects (youngest most recently allocated) are garbage collected (Gen 0 GC) since the start of the application. Gen 0 GC occurs when the available memory in generation 0 is not sufficient to satisfy an allocation request. This counter is incremented at the end of a Gen 0 GC. Higher generation GCs include all lower generation GCs. This counter is explicitly incremented when a higher generation (Gen 1 or Gen 2) GC occurs. Global counter value is not accurate and should be ignored. This counter displays the last observed value.
This counter displays the number of times the generation 1 objects are garbage collected since the start of the application. The counter is incremented at the end of a Gen 1 GC. Higher generation GCs include all lower generation GCs. This counter is explicitly incremented when a higher generation (Gen 2) GC occurs. Global counter value is not accurate and should be ignored. This counter displays the last observed value.
This counter displays the number of times the generation 2 objects (older) are garbage collected since the start of the application. The counter is incremented at the end of a Gen 2 GC (also called full GC). Global counter value is not accurate and should be ignored. This counter displays the last observed value.
% Time in GC % Time in GC is the percentage of elapsed time that was spent in performing a garbage collection (GC) since the last GC cycle. This counter is usually an indicator of the work done by the Garbage Collector on behalf of the application to collect and compact memory. This counter is updated only at the end of every GC and the counter value reflects the last observed value its not an average.
Search templates helps you track a number of 'search' relevant counters on servers in SharePoint farm. Diagnose various problems and performance issues with ease.
The total number of times a document access has been retried. Having this number high may indicate a problem with accessing the data.
Number of crawls in progress.
Shows the current number of completed documents in the transactions queue.
The number of documents waiting to be processed. When this number goes to zero the catalogue is idle. This number indicates the total queue size of unprocessed documents in the gatherer.
The number of documents in progress.
The number of documents processed per second.
The number of successfully filtered documents per second.
Most counters have a critical and warning threshold defined. When the counter value remains above the threshold for an extended period of time it will be classified with a critical or warning status. This in turn will affect the status of the server seen on the dashboards and it will cause an Alert to be sent - if you have that turned on. Please note that these threshold can be changed to suit your needs more reliably.
See for some guidelines on performance testing and tuning.