Documente Academic
Documente Profesional
Documente Cultură
Authors: Date:
1|P ag e
Contents
Introduction............................................................................................................................................5 B.0TheBasics........................................................................................................................................6 B.1HotFixes .....................................................................................................................................6 . B.264bitversus32bitOSandSQLServer...........................................................................................6 B.3SystemRequirements..................................................................................................................6 B.4Browsersandworkstationsmakeadifference.............................................................................7 B.5Please,distributeyourscripts!....................................................................................................7 B.6Myscriptsaredistributedbutwhyaretheyallrunninginthemorning!......................................8 B.7TheStatisticsHiddenLink............................................................................................................9 M.0Memory.........................................................................................................................................10 Howtomonitormemory...................................................................................................................10 M.1Processes...................................................................................................................................10 M.264BitOperatingSystem.............................................................................................................11 M.332Bit/3GBintheboot.ini..........................................................................................................11 M.4MemoryBestPractices...............................................................................................................11 C.0CPU...............................................................................................................................................12 C.1MicrosoftReportingServices.................................................................................................12 C.2KaseyaMessageSys ................................................................................................................12 . C.3w3wp....................................................................................................................................13 C.4KaseyaAddons......................................................................................................................13 C.5Largernumberoffilesonserversandworkstations...............................................................13 C.6LogArchiveduration..............................................................................................................13 C.7IISCompression.....................................................................................................................13 C.8DEP.......................................................................................................................................14 N.0Network........................................................................................................................................15 N.1IISCompression........................................................................................................................15 N.2PlanNetworkUtilization...........................................................................................................16 N.3NetworkUtilizationforServiceDesk.........................................................................................17 IO.0DiskPerformance(IO).................................................................................................................18 IO.1KaseyaIOHotSpots ................................................................................................................18 . WindowsPaging............................................................................................................................18 2|P ag e
\Kaseya.......................................................................................................................................... 18 SQL Server TempDB ....................................................................................................................... 18 SQL Server Database and Logs ....................................................................................................... 18 IO.2 Monitor your IO....................................................................................................................... 19 Avg. Disk Queue Length ................................................................................................................. 19 Avg. Disk Sec/Read and Avg. Disk Sec/Write .................................................................................. 19 V.0 Virtualization with ESX................................................................................................................... 20 How to monitor resources under VMWare ESX .................................................................................. 20 V.1VMWare ESX Memory Configuration ........................................................................................... 21 V.2VMWare ESX CPU Configuration Reservations ............................................................................. 22 V.3VMWare ESX CPU Configuration Limit ......................................................................................... 25 V.4VMWare ESX VMWare tools up to date? ..................................................................................... 25 F.0 Federation of Servers ..................................................................................................................... 26 F.1 Single versus Dual Servers ......................................................................................................... 26 F.2 Reporting Database Servers................................................................................................... 26 A.0 AddOn Performance Tips.............................................................................................................. 27 A.1 Service Desk .............................................................................................................................. 27 Performance and Best Practices Check List ............................................................................................ 28 B The Basics...................................................................................................................................... 28 MPerformance Checklist for Memory ............................................................................................... 28 CPerformance Checklist for CPU ....................................................................................................... 28 NNetworking .................................................................................................................................... 29 IODisk Performance (IO) ................................................................................................................... 29 VPerformance Checklist for Virtualization with ESX .......................................................................... 29 FFederation of Servers...................................................................................................................... 30 AAddOn Performance Tips .............................................................................................................. 30 Appendix A Monitor Sets .................................................................................................................... 31 CPU ................................................................................................................................................... 31 CPU Reporting Services ............................................................................................................... 31 CPU Kaseya Messagesys .............................................................................................................. 31 CPU w3wp IIS Workpool Process ..................................................................................................... 32 CPU SQL Server Process .................................................................................................................. 32 3|P ag e
Disk IO ............................................................................................................................................... 33
4|P ag e
Introduction
If you are running Kaseya Version 5.x or previous versions and are close to maximizing your CPU, Networking and/or IO resources, dont expect Version 6.x (K2) to run similarly on the same infrastructure. We hope this guide will help you with your planning on upgrading or a new install of Kaseya K2. Please remember that the Minimum Requirements on the Kaseya Support Site is based on an average. Every customer is different and your mileage will vary. Kaseya is an enterprise application that requires specific hardware and software requirements in order to run effectively. These requirements include a database and IIS server(s), a network capable of handling agent traffic and a client platform and browser to present the user interface. In addition, it is helpful to understand that every environment that is running Kaseya is different. There are many variables that will impact the performance of your Kaseya installation. The recommended requirements on our web site are a general guideline based on measures taken on multiple customer environments. The purpose of this document is to help you give your Kaseya Environment a Health Check by looking at various areas of performance and providing a checklist of items to review to implement best practices as it pertains to performance. This document will go over the various areas of performance with recommendations of best practices where appropriate. Each of the sections are labeled in a way that they can be easily be referenced from the Performance Check List which is in the last section of this document. The sections covered in this guide are: The Basics Memory CPU Network IO Virtualization Federation of Servers AddOn Performance Tips o Service Desk Performance Check List
5|P ag e
B.0TheBasics
B.1HotFixes
Make sure your up to date on hot fixes since performance related issues are addressed through this mechanism. Go to system, configure and make sure you have Enable automatic check checked. Also verify that you are current on hot fixes by looking at the Last Hotfix field. If not, click the Get Lastest Hotfix button. It is also a good idea to run the Reapply Schema link after hot fixes are applied since this may create any missing indexes on the database helping performance. Some customers choose not to have this feature enabled. In this case, you should review this periodically and if you are experiencing performance issues, its best to apply all hot fixes before contacting support.
B.264bitversus32bitOSandSQLServer.
Dont use 32 bit OSs or SQL Server. Its okay for test environments, but will not scale to support Kaseya.
B.3SystemRequirements
Did you review the minimum system requirements at the Kaseya support site? http://www.kaseya.com/support/systemrequirements.aspx Keep in mind that these requirements can vary based on many variables such as: Number of audits Number of patch scans Number of KES scans User/Sample scripts Reporting Log History Agent History Script distribution
It is therefore important for you to monitor your environment at all times and preferably with a Kaseya Agent. This way, you can monitor, track and alert when resources are constrained like CPU, Disk IO, 6|P ag e
Memory, SQL Server Locks, etc Kaseya provides sample monitor sets as well as a NOC service that can monitor these for you. Please feel free to contact our NOC services for more details on this service. As we work with many clients, we constantly update our monitor sets to insure best practices in terms of monitoring the Kaseya solution.
B.4Browsersandworkstationsmakeadifference
The new features and functionality of the new Kaseya UI does require more resources in terms of Networking bandwidth and CPU on the clients workstation running the UI. The reason is that we are now using Java AJAX and JSON in order to render our pages. We have found that using Firefox over Internet Explorer provides better response times on the Kaseya UI and is highly recommended. Chrome appears to be the fastest; however, this browser is not supported at this time. If you notice that the UI is slow, check to see how much CPU your workstation is utilizing during screen refreshes. If the CPU consistently hits 100%, your workstation may be under powered to render the pages. Also compare the CPU utilization between Firefox and Internet Explorer.
B.5Please,distributeyourscripts!
You probably keep hearing this from us as a Kaseya Customer, but it is very important that you distribute your scripts. On the right, the scripts for the Latest Audit are all scheduled at once. And before that, all of the Patch Scans are scheduled in a small time frame as well. If you dont have enough resources on the server, many things can happen. For example: The patch scans may not be finished before
7|P ag e
Keepaneyeonyourscriptdistribution,itisimportant!
B.6Myscriptsaredistributedbutwhyaretheyallrunninginthemorning!
AnotherissuethatisseenwithscriptschedulingisthatmanycompaniesaregoingGreen.Serversand PCsmaybeturnedoff duringthenight.IfPatch ScansandAuditsare distributedandsetto runatnight,theymay bequeueduntil everyoneinthe companycomesinto startuptheirmachines. So,ifyouare experiencingthis,check outyourstatisticsinthe System>Staticstab. NotehowhighyourCPU isrunningandthenlook atthetopsscriptsthat haveruninthelasthour. Ifitappearsthatthere aremorescriptsthat haverunthanwhatyou setasanhourly distribution,youmaybe runningintothis scenario.Consider increasingyourCPU, NetworkingandIOto addressthis.Kaseya minimumrequirements arebasedonanaverage over24hoursassuming anincrementalauditand patchscanaday.
8|P ag e
B.7TheStatisticsHiddenLink
Onveryusefulfeatureisthehiddenlinktoview serverhistoricalstatistics.Thislinkislocatedon theSystem>Statisticspageontheboxwiththe headingstartingwithStatisticscollectedat. Thisisthehiddenlink.Clickthistobringupthe historicalstatisticspage.Here,youcanreview historicalgraphsthatprovideveryuseful informationonthenumberofscriptsrun,CPU, etc Again,oneofthebiggestresourceissuesis scripts.Iftheydontappeardistributed,but spikingasshown,thenyoumayexperience timesofslownessinyourenvironment.Review theCPUgraphtooandseeifyourenvironmenthashistoricallyhighCPUutilizationorspikesaswell.Ifit does,trytodistributeyourscriptstorunmoreevenly.
9|P ag e
M.0Memory
Howtomonitormemory
MemorycanbemonitoredbyusingtheresourcemonitorinWindows2008.Therearetwokey indicatorsthatareimportantto memoryandthisiswhytheyshow onthispanel.Youshouldnotsee excessiveHardFaults/sec.Ideally, thisnumbershouldbeverylowor evenzero.Ifyouseevaluesinthe doubledigitsormore,youare runninglowonmemoryanddisk swappingisoccurring.Thisisbad. Also,makesureyouarenotabove 85%onyourUsedPhysicalMemory. Ifyouare,youshouldconsider addingmoreRAMtoyoursystem.
M.1Processes
Youmusthaveenoughmemoryto supportfiveofthemostmemorydependantprocessesinasinglephysicalKaseyaServerenvironment. Theseprocessesare: KaseyaMessageSys W3wp(IISWorkpool) Kserver MSSqlServer MSSqlReportingServices InKaseyaV6,theKaseyaMessageSys.exeisanewprocessthatwillallowKaseyatoscalewithfuture versionsandworkscloselywithMicrosoftMessageQueuing.Inadditiontothis,Version6alsoadds MicrosoftReportServices. KaseyaMessageSyscanuse380meg.ofRAMforasmallimplementationofKaseya(0250endpoints)to morethan1.2Gig.OfRAMforlargerinstallations(2500ormoreendpoints). InadditiontoKaseyaMessageSys,thenewKaseyaUIrequiresmoreRAMfromIIS(specifically,theIIS workpoolprocesscalledw3wp).Thisprocesscanuse250Megabytesforasmallimplementationto700 Megabytesormoreforlargerimplementations. KaseyaalsoutilizesMicrosoftReportingServiceswhichwilladdadditionalmemorypressureforyour instances.Smallinstancescanuse160200Megabyteswhilelargersystemscanuseevenmore.Itsnot unusualforthisprocesstogrowto1.3Gigabytesormore.
10 | P a g e
M.264BitOperatingSystem
Currently,itishighlyrecommendedthatevensmallinstallationsofKaseyaVersion6use64bitWindows toaddressRAMoverthe32Bitlimitof4Gig.AsshownaboveinsectionM.1,evenasmallinstallationof KaseyacanbeimpactedbynewKaseyaandWindows2008requirements.InadditiontotheOS,SQL Servershouldbe64Bitaswell.
M.332Bit/3GBintheboot.ini
Kaseyahasseenthatthe/3GBswitchintheboot.iniof32bitWindowscausesexcessivepagingsimply becausemoreRAMisbeingallocatedtoapplicationsandnottotheOperatingsystem.Thisswitchisset intheboot.inifileandshouldbetakenout.Initsplace,youshouldupgradeyourWindowsoperating systemto64bitoraddadditionalmemorytoyourexisting32Bitenvironmentandusingthe/PAE switchinitsplace.PAEisusedbySQLServer(byenablingAWE)andcanusetheadditionalmemory abovethe32Bitlimitof4GB.Thisfeaturedoesnotworkon32BitWindowsStandardEdition. Ifyouarelimitedto32bitsystemsand4GigofRAM,youshouldconsidersplittingtheserverintoan applicationanddatabaseserver.ThiswillatleastallowmoreRAMtoboththedatabaseserverandthe applicationserver.
M.4MemoryBestPractices
Makesuretomonitormemoryusageonthefollowingprocessestodevelopusagehistoryandassess Memoryrequirementsspecifictoyourenvironment: Sqlserver.exe W3wp.exe KaseyaMessageSys.exe ReportingServicesService.exe KServer.exe
11 | P a g e
C.0CPU
CPUutilizationcanvarybasedonmanyvariables;however,withK2youmustplantoallocatemoreCPU thanpreviousKaseyaVersion5implementationsforthesamenumberofendpointsmanaged.Thisis duetotheadditionalfunctionalityofthebackenddatabaseandfrontend.Newprocesses,likeKaseya MessageSysandMicrosoftReportingServiceswillrequireCPUresourcesaswell. C.1MicrosoftReportingServices MicrosoftReportingServicesisnewtoK2andutilizesmoreCPUandMemorytorunreportsthanprior versions.Ifyouschedulemanyreportstorun,trynottoschedulethemduringtimesthattheserveris alsorunningauditsandpatchscans.Dependingonyourreportingloadanddatavolume,youcanusea wholecoreormorejustforreporting.OnewaytotrackreportingCPUutilizationistouseanAgenton yourKaseyaserverandcreateamonitorsetforreportingservicesprocess.Fromhereyoucancreate graphsasshownbelowusingKaseya.Inthisexample,thereislittlereporting,butwhenreportingdoes run,itcantake50%ormoreofacore.Pleasenotethatthisisnot50%oftotalCPUonaserver.For
12 | P a g e
C.3 w3wp This is the IIS work pool process. It should be monitored since it is second to SQL server in terms of CPU resource consumption. This process will consume more resources based on the number of administrators on your system and is also impacted by the Service Desk Addon. C.4 Kaseya Addons Depending on the number of addon products like KES, BUDR, User Profile and Service Desk, your requirements can vary appreciable in terms of memory, CPU, networking and IO. C.4.1 Kaseya Addons KES In terms of CPU, KES and Service Desk will have an impact to your overall CPU utilization. For KES, in general, you should plan on an adding an additional 10% over the recommended CPU. C.4.2 Kaseya Addons Service Desk The Service Desk will have an appreciable load on a server that is also running Kaseya. Currently, the following calculations should be done to estimate the additional CPU needed for single or dual server Kaseya implementation: Application Server: Number of named users that will access the Service Desk * 15Mhz Database Server: Number of named users that will access the Service Desk*35Mhz
Just add the two above if this is a single server install. For example, if you know you will have 50 users accessing the Service Desk Addon, you should have the following additional CPU resources added to the Kaseya Minimum requirements: Application Server: 50*15Mhz = 750Mhz Database Server: 50*35Mhz = 1750Mhz
For a single Kaseya Server, just add them together. In this case, we come up with 2500Mhz. So a good rule of thumb is about 50 named users supported by one 2.4Mhz Core of CPU. C.5 Larger number of files on servers and workstations As servers and workstations become larger in size in terms of files, we must compare and store this detail on the Kaseya server. This in turn requires more space on the database and increases CPU to report and process this data especially during Audits. C.6 Log Archive duration The longer you keep agent and monitor logs, the more resources it takes to run reporting and data mining. Try to keep the logs to a minimum. C.7 IIS Compression Some companies may consider using IIS Compression to reduce bandwidth costs at hosting centers and improving performance on low latency/slower networks. The Kaseya application will benefit from compression on IIS6.0 and IIS7.0, but there is a CPU cost. Because of the various compression levels
13 | P a g e
available, it is best to create a baseline on your CPU utilization and then slowly increase compression levels until a good balance is reached with existing CPU resources and improved page performance. C.8 DEP DEP is a new feature for Windows 2008 and Windows 7. It adds logic to prevent execution of programs in memory regions and by default is turned on for all programs in Windows 2008. This does affect CPU and we recommend setting this to Turn on DEP for essential Windows programs and service only. You can access this setting by left clicking Computer properties and then select advanced options. Then select Settings from the Systems Properties window and then select the Data Execution Prevention tab.
14 | P a g e
N.0 Network
Just like CPU, networking will vary based on the number of scripts run, audit scan detail, Kaseya Addon products, etc It is important to monitor this carefully since Kaseya Version 6 will require more network bandwidth than previous versions of Kaseya. Where this is most evident is in the Kaseya UI. The Kaseya UI now is based on Java AJAX and JSON. These technologies bring a feature rich experience to the end user. It is very much like a windows application versus a HTML based application. These features, however, require more networking bandwidth in order to run well.
To enable compression, install the Static and Dynamic Content Compression role services for IIS. Once these services are installed, you must enable them in IIS by opening the IIS Manager and clicking on the Compression icon.
15 | P a g e
Then check the Enable dynamic and static Content compression on the default website as well as the IIS Home. Please note that IIS 7.0 will stop compression if the server is starving for CPU. IIS 6.0 will not. Be sure to monitor CPU utilization on the server before and after this setting to insure the impact isnt excessive.
WAN connection based on an average of 250 Megabytes/Agent/Month Number of Average Bits/Sec 24hrs Agents 100 77,160 1000 771,605 5000 3,858,025 20000 15,432,099 100000 77,160,494 16 | P a g e WAN Connection < T1 T1 T2 T3 Dual T3
Naturally, you should plan for peaks. For example, even though a T1 can handle 5000 agents in an average install, if youre limited to an 8 hour windows versus 24 hours to run audits and high bandwidth scripts, you may need the capacity to support peaks that are three times the average in the tables above. Why the differences? It is due to many reasons. Number, distribution and frequency of full/incremental audits and audit details on servers/workstations Depending on the detail contained on servers and workstations, the agent will send XML documents across the net to the Kserver. These document sizes can vary. Some can be very small like a 10k bytes while others can be as high as 400k Bytes or more. Number, distribution and frequency of patch scans Similar reason as audits Number, distribution and frequency of KES scans Similar reason as audits Number and size of managed files that may be distributed to/from your servers/workstations Customers may send managed files of various sizes to all of their endpoints. Some even bring files back to the Kserver. This all will require bandwidth to manage effectively. Number of administrators that will be using Kaseya to manage and monitor their respective environments The number of administrators makes a difference overall on Kaseya Servers. If you have many of them running dashboards, using the UI extensively or using Service Desk, you should plan on acquiring more network bandwidth. Distribution of Scripts This is described in another section above, but does affect network bandwidth as well. Trying to run too many scripts at a time can cause network saturation
18 | P a g e
19 | P a g e
From here you will see two counters related to VMWare. VM Memory and VM Processor. Each of these is used for the sections below on best practices for a VMware installation in terms of Memory and CPU.
20 | P a g e
21 | P a g e
22 | P a g e
How can you determine if youre starved of CPU cycles? Use the Effective VM Speed in Mhz counter. This counter will show how many cycles a VM is using in Mhz. In this example, you will see that this VM has four virtual cores.
If you select the Host Processor Speed in Mhz counter, it will show that the host processor runs at 3000Mhz (or 3GHz). Technically, this VM if given unlimited CPU cycles from the ESX host, should have 4x3Ghz or 12Ghz total of Effective VM Speed (or 12,000Mhz). In the example below, you will notice that there are times that the VMs CPU is at 100%, however, this would indicate that all 12,000 Mhz was being used to get to 100%. In reality, the VM was only getting 5077Mhz maximum as shown in the Effective VM Speed counter below. This indicates that the VM is being starved of CPU and reservations should be allocated to this server.
23 | P a g e
One reason that this server is being starved of CPU is it could be limited in how many CPU Mhz it receives. This is explained in the next section.
24 | P a g e
25 | P a g e
26 | P a g e
27 | P a g e
C.2
C.3
C.4.1 C.4.2 28 | P a g e
use the following formula to calculate additional CPU requirements. Just add the two together for single Kaseya Server. Application Server: Number of named users that will access the Service Desk * 15Mhz Database Server: Number of named users that will access the Service Desk*35Mhz
C.5
C.6
C.7
If your managed environments contain many files or programs, consider adding more CPU resources to handle the increased volume. For example, a company managing many servers in relations to workstations will see more CPU utilized during Audits. Consider how long you need to keep logs. If you want to keep them longer than 30days (the default), then you will need to increase resources to report on those logs. Will you be using IIS Compression to help with bandwidth and slow networks? If yes, create a CPU baseline and monitor trends as you increase compression levels on IIS. IIS 7.0 offers a CPU rolloff which will stop compressing pages as CPU utilization increases. IIS 6.0 doesnt offer this feature, so you should insure that you monitor your CPU accordingly. Is DEP set for just essential Windows programs and services?
C.8
N-Networking
Section N.1 Description IIS Compression. If you have CPU resources, try installing and setting up compression to help with bandwidth issues. Remember, this creates more load on the CPU based on the compression youre using. Did you plan for WAN network requirements for your Implementation? Did you plan for additional network requirements for Service Desk? Yes/No
N.2 N.3
you split them into a Database and Application Server, did you still reserve memory in ESX for both? V.2 Did you allocate reserved CPU to your Kaseya implementation? If you split them into a Database and Application Server, did you still reserve CPU in ESX for both? Is your VM being limited in Mhz? Make sure it has enough CPU in Mhz to run Kaseya in both a single and dual VM configuration. Is VMWare tools up to date?
V.3 V.4
F-Federation of Servers
Section F.1 F.2 Description If you plan to have more than 5000 agents, are you using two physical servers? If your reporting needs are heavy, did you plan to have a separate reporting database server? Yes/No
30 | P a g e
CPU
These monitoring sets will help with CPU utilization of the major CPU consumption processes on a Kaseya install. Depending on the number of servers in your Kaseya environment, some of this will not apply. For example, where the database is a separate server, you would not use the SQL Server process utilization monitor set. In addition, the CPU in these monitor sets can exceed 100%. Dont confuse this with total CPU utilization of a system. For example, a four core server with reporting services taking up two cores at 100% will read 200% in these measures. If reporting services was using all cores at 100%, you will see the measure report 400%. These are useful in terms of trending as well as providing some feedback to support like a process that may be taking more resources suddenly. CPU Reporting Services <?xml version="1.0" encoding="ISO88591" ?> <monitor_set_definition version="1.0"> <MonitorSet name="Reporting Services Process Util" description='This set is used to monitor and alert based on reporting services process utilization'> <Counters> <Counter name='Processor Time' description='null' counterObject='Process' counter='% Processor Time' counterInstance='ReportingServicesService' counterSampleInterval='60' collectionOperator='Over' collectionThreshold='0' trendTimeSpan='1209600' trendReArm='3600' thresholdOperator='Over' thresholdAmount='50' thresholdDuration='25' thresholdWarning='10' thresholdReArm='3600'/> </Counters> <Services> </Services> <Processes> </Processes> </MonitorSet> </monitor_set_definition>
CPU Kaseya Messagesys <?xml version="1.0" encoding="ISO88591" ?> <monitor_set_definition version="1.0"> <MonitorSet name="KaseyaMessageSys Util" description='This set is used to monitor and alert based on Kaseya messagesys process utilization '> <Counters>
31 | P a g e
<Counter name='Messagesys Processor Time' description='null' counterObject='Process' counter='% Processor Time' counterInstance='KaseyaMessageSys' counterSampleInterval='60' collectionOperator='Over' collectionThreshold='0' trendTimeSpan='1209600' trendReArm='3600' thresholdOperator='Over' thresholdAmount='98' thresholdDuration='5' thresholdWarning='10' thresholdReArm='600'/> </Counters> <Services> </Services> <Processes> </Processes> </MonitorSet> </monitor_set_definition>
</MonitorSet> </monitor_set_definition>
Disk IO
This monitor set should be used on each volume that houses your OS paging file, Kaseya install directory, database data, log and tempDB. The monitor set below assumes that everything is on the C:\. You can import this monitor set and clone it for additional drives in your installation. You should change the Disk Queue Length measure to reflect 2x the number of physical drives in your disk device. This also assumes your using an agent to monitor the Kaseya server(s). <?xml version="1.0" encoding="ISO88591" ?> <monitor_set_definition version="1.0"> <MonitorSet name="Disk IO Best Practices" description='Use this monitor set to insure optimal performance on your disk devices'> <Counters> <Counter name='LogicalDisk' description='RAID 5 of three disks' counterObject='LogicalDisk' counter='Avg. Disk Queue Length' counterInstance='C:' counterSampleInterval='60' collectionOperator='Over' collectionThreshold='1' trendTimeSpan='1209600' trendReArm='3600' thresholdOperator='Over' thresholdAmount='6' thresholdDuration='10' thresholdWarning='10' thresholdReArm='3600'/> <Counter name='LogicalDisk sec/Read C:' description='null' counterObject='LogicalDisk' counter='Avg. Disk sec/Read' counterInstance='C:' counterSampleInterval='60' collectionOperator='Over' collectionThreshold='0.02' trendTimeSpan='1209600' trendReArm='3600' thresholdOperator='Over' thresholdAmount='0.1' thresholdDuration='20' thresholdWarning='10' thresholdReArm='3600'/> <Counter name='LogicalDisk sec/Write C:' description='null' counterObject='LogicalDisk' counter='Avg. Disk sec/Write' counterInstance='C:' counterSampleInterval='60' collectionOperator='Over' collectionThreshold='0.02' trendTimeSpan='1209600' trendReArm='3600' thresholdOperator='Over' thresholdAmount='0.1' thresholdDuration='20' thresholdWarning='10' thresholdReArm='3600'/> </Counters> <Services> </Services> <Processes> </Processes> </MonitorSet> </monitor_set_definition>
33 | P a g e