Available Counters Can Be Reviewed Outside of Kaseya by Exploring Perfmon

Troubleshooting Monitor Sets that are Not Responding

Monitor sets are an of import office of Kaseya's ability to maintain the wellness of your servers and workstations. Monitor set can perform three split up tasks,   monitor Windows PerfMon counters (Counter Thresholds), monitor services (Services Check) or monitor a Process (Process Status).

Kaseya monitor sets are fairly like shooting fish in a barrel to setup, and normally work but fine, only in cases where they are non working, hopefully this article will help you troubleshoot them.

Virtual Administrator default monitor sets

Monitor Sets take one or more counters associated with them.  Each counter will have a corresponding value when viewed through the Monitor> Agent Monitoring> Monitor Log.  When we ready up your business relationship Virtual Administrator added ii monitor sets to your server templates (a_server_template).

a_VA – Base Server Performance (monitors Avail memory, CPU Utilization, and Paging)

a_VA – CM2-Critical 2 % Low Complimentary Disk Infinite for all Drives

These ii monitor sets are automatically applied to machines that have the amanuensis installed using the Server Deployment Packet.   You lot tin review the status of a monitor ready by going to Monitor tab -> Agent Monitoring -> Monitor Log.   Then click on the machine ID that you want to review.

How a monitor fix gets applied

When a Monitor Gear up is applied at least two files are created in the agent working directory (usually C:\kworking).  There will be the XML file with a file proper name similar "KMON$1234.xml" in the kMonitorSets  folder (i.e. C:\kworking\kMonitorSets\ KMON$1234) and i or more CSV file with a file proper noun like "KLOG$1234.csv" (i.e. C:\kworking\KLogs\KLOG$1234).

To figure out which XML file belongs to which monitor set, go to the Assign Monitoring office, and hold the cursor over the "pencil/graph" icon to the left of the Monitor Set and look at the bottom of the page.  In the example below Monitor Fix "ZC-SV2-Auto Health" creates KMON$1063.xml.

Determining the KLOG$ files requires a fiddling earthworks.    Open up the KMON$ XML file in Notepad, and you volition meet which KLOG$ files are existence used past that monitor set up.   In this example KMON$1063 created  KLOG$1076.csv, KLOG$1078.csv and KLOG$1080.csv

Troubleshooting Monitor Sets

Step 1.  – Bank check Agent Version

Equally with many problems in Kaseya the start step is to make sure you have the most current version of the Kaseya agent installed.  Go to Upgrade Version> Update Agent.  Bank check the "Force update"  box and click "Update Agent".  Older agents versions will be in crimson messages.

Pace two. – Remove and re-apply Monitor set

Too try removing so reapplying the Monitor Set up.  It's possible some of the files are missing or corrupted. Reapplying the monitor set should recreate the files.  The monitor sets tin can have 20 minutes to start returning data.

Stride 3. – Bank check permissions and credentials

If the monitor sets are still not working  cheque to make sure the XML and CSV files are created in the agent working directory.  If they are not, the about mutual cause is the credentials on the agent do not have read/write permission to the agent temp folder AND the sub folders.  By default the amanuensis uses the system business relationship credentials.  To add other credential go to the Agent> Configure Agents" Prepare Credentials folio and add.  Make sure to run the Exam to verify that they work.  You should get "Passed".

Step 4 – Check PerfMon

If the files are created simply the Monitor Fix is non responding, await at the Performance Monitor (Start> Run> type "Perfmon" press Enter).   Wait for counter with the corresponding Monitor Gear up number with KCTR$xxxx.  These are the logs that perfmon is saving the information to.  If it is green it is running.  If it is red try to offset information technology by right clicking on it and clicking "Start".

Windows XP and Server 2003

Windows 7 and Server 2008

Pace 6-  Check Event Logs

If the Perfmon counter doesn't kickoff, open your effect viewer and come across if in that location are any errors created.  Research and resolve those errors.  Kaseya can't report on it, if it doesn't work in Windows directly.

Pace vii –  Check Operation Logs and Alerts Service

If the proper files are existence created by the monitor ready and the Monitor Set is still non responding the issues is well-nigh likely the Perfomance Logs and Alerts service.  Research any errors y'all find and become the service running. Then reapply the monitor sets.

Misc –

If the Base Server Performance monitor is working but the 2% gratis space is not effort running the diskperf –yv command to enable the counter.

andrewswortatuslege.blogspot.com

Source: https://virtualadministrator.com/troubleshooting-kaseya-k2-monitor-sets/

Share this post