diff --git a/docs/cwa/monitors/automate-server-unwanted-event-logs-monitoring.md b/docs/cwa/monitors/automate-server-unwanted-event-logs-monitoring.md index f2e7929f8b..202877fb90 100644 --- a/docs/cwa/monitors/automate-server-unwanted-event-logs-monitoring.md +++ b/docs/cwa/monitors/automate-server-unwanted-event-logs-monitoring.md @@ -7,7 +7,7 @@ keywords: ['ticket', 'monitoring', 'automate', 'event', 'error', 'critical'] description: "This document outlines the setup for a remote monitor that generates an urgent ticket in ProVal's Autotask portal when critical events from specified sources occur more than 10 times within 60 minutes on the Automate server. It is specifically designed for On-Prem partners and includes detailed configuration settings and dependencies." tags: ['autotask'] draft: false -unlisted: false +unlisted: True --- ## Summary diff --git a/docs/cwa/monitors/broken-integration.md b/docs/cwa/monitors/broken-integration.md deleted file mode 100644 index eda227af8e..0000000000 --- a/docs/cwa/monitors/broken-integration.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -id: 'a3e17618-1629-4eca-ae93-e70dd47e3496' -slug: /a3e17618-1629-4eca-ae93-e70dd47e3496 -title: 'Broken Integration' -title_meta: 'Broken Integration' -keywords: ['connectwise', 'integration', 'ticket', 'monitor', 'autotask'] -description: 'This document outlines the process to create an urgent ticket in ProVal’s AutoTask Portal for a broken integration between ConnectWise Automate and ScreenConnect. It includes dependencies and target settings for effective monitoring.' -tags: ['connectwise', 'ticketing'] -draft: false -unlisted: false ---- - -## Summary - -This monitor is intended to create an urgent ticket in ProVal's AutoTask Portal for a broken integration between ConnectWise Automate and ScreenConnect. - -## Dependencies - -[Email RAWSQL Monitor Set Failures* [Autofix]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) - -The "△ Custom - Email RAWSQL Monitor set results to ProVal" alert template should be applied. - -## Target - -Global - This should be run without explicitly defined targets. \ No newline at end of file diff --git a/docs/cwa/monitors/cw-manage-plugin-errors.md b/docs/cwa/monitors/cw-manage-plugin-errors.md index d6fd26c09d..32731362b5 100644 --- a/docs/cwa/monitors/cw-manage-plugin-errors.md +++ b/docs/cwa/monitors/cw-manage-plugin-errors.md @@ -7,7 +7,7 @@ keywords: ['monitor', 'notification', 'connectwise', 'alerts', 'plugin', 'error' description: 'This document outlines the setup and dependencies for an internal monitor that notifies the specified email address of critical errors or issues related to the ConnectWise Manage Plugin. It includes information on the necessary dependencies and the target configuration for global monitoring.' tags: ['connectwise', 'email'] draft: false -unlisted: false +unlisted: True --- ## Summary diff --git a/docs/cwa/monitors/cwm-automate-automate-unsynced-ticket-content.md b/docs/cwa/monitors/cwm-automate-automate-unsynced-ticket-content.md index e9f7449b2c..a4331866c7 100644 --- a/docs/cwa/monitors/cwm-automate-automate-unsynced-ticket-content.md +++ b/docs/cwa/monitors/cwm-automate-automate-unsynced-ticket-content.md @@ -7,7 +7,7 @@ keywords: ['monitor', 'tickets', 'alerts', 'synchronization', 'cwmanage'] description: 'This document outlines the setup and dependencies for the Unsynced Ticket Comments Monitor, which alerts partners about any ticket comments that have not been synchronized with CW Manage. It includes details on required plugins and configuration steps to ensure alerts are sent correctly.' tags: ['cwmanage', 'email'] draft: false -unlisted: false +unlisted: true --- ## Summary diff --git a/docs/cwa/monitors/cwm-automate-monitor-failed-email-monitoring.md b/docs/cwa/monitors/failed-email-monitoring.md similarity index 80% rename from docs/cwa/monitors/cwm-automate-monitor-failed-email-monitoring.md rename to docs/cwa/monitors/failed-email-monitoring.md index 2bdb52a146..2e3d281b92 100644 --- a/docs/cwa/monitors/cwm-automate-monitor-failed-email-monitoring.md +++ b/docs/cwa/monitors/failed-email-monitoring.md @@ -1,8 +1,8 @@ --- id: 'f1a15d3d-85d7-4d72-9c08-ad4ca6a7dfbb' slug: /f1a15d3d-85d7-4d72-9c08-ad4ca6a7dfbb -title: 'CWM - Automate - Monitor -Failed Email Monitoring' -title_meta: 'CWM - Automate - Monitor -Failed Email Monitoring' +title: 'Failed Email Monitoring' +title_meta: 'Failed Email Monitoring' keywords: ['email', 'ticket', 'monitor', 'failure', 'notification'] description: 'This document outlines a monitor that reports any failed email occurrences that are not related to specific exclusions. It generates a ticket detailing the failed emails every hour, providing crucial information for troubleshooting and resolution.' tags: ['report', 'security', 'setup'] @@ -16,7 +16,7 @@ This monitor reports any failed email that is not related to 'Google Authenticat Each hour, a ticket with the details of all the failed emails from the previous hour will be generated. -**Ticket Subject:** Automate Failed Email Detected +**Ticket Subject:** `Automate Failed Email Detected` **Sample Ticket Body:** @@ -36,7 +36,7 @@ Below is the information of all the emails that failed in the last hour: **Subject:** Stuff **Body:** Things **Error Message:** Bad Stuff - **Failure Date:** 2022-07-01 10:03:20 + **Failure Date:** 2022-07-01 10:03:20 ## Important Notes @@ -46,9 +46,8 @@ For hosted partners, it will be the minimum computer ID of Client ID 1. If Clien ## Dependencies -[Ticket Creation - Without Computer Information And Failures Only [Autofix]](/docs/730449e6-1c73-46ca-a93d-d7b9526e1ef9) - -"△ Custom - Ticket Creation - Without Computer Details" alert template should be applied to the monitor set. +- [Ticket Creation - Without Computer Information And Failures Only [Autofix]](/docs/730449e6-1c73-46ca-a93d-d7b9526e1ef9) +- `△ Custom - Ticket Creation - Without Computer Details` alert template should be applied to the monitor set. ## Target diff --git a/docs/cwa/monitors/heartbeat-anomaly-audit.md b/docs/cwa/monitors/heartbeat-anomaly-audit.md index 10048a7a19..65a2994b70 100644 --- a/docs/cwa/monitors/heartbeat-anomaly-audit.md +++ b/docs/cwa/monitors/heartbeat-anomaly-audit.md @@ -3,8 +3,8 @@ id: 'fc109cdb-9f88-448b-8c57-b866b2e3c7c2' slug: /fc109cdb-9f88-448b-8c57-b866b2e3c7c2 title: 'Heartbeat Anomaly Audit' title_meta: 'Heartbeat Anomaly Audit' -keywords: ['heartbeat', 'monitor', 'ticketing', 'anomaly', 'autotask'] -description: "This document outlines the implementation of a monitor that creates a ticket in ProVal's AutoTask Portal when fewer heartbeats than expected are detected from machines checking in within the environment. It includes dependencies, target settings, and ticketing details for alerts." +keywords: ['heartbeat', 'monitor', 'ticketing', 'anomaly'] +description: "This document outlines the implementation of a monitor that creates a ticket in ProVal's Halo PSA when fewer heartbeats than expected are detected from machines checking in within the environment. It includes dependencies, target settings, and ticketing details for alerts." tags: ['networking', 'security', 'ticketing'] draft: false unlisted: false @@ -12,12 +12,12 @@ unlisted: false ## Summary -This monitor is intended to create a ticket in our (ProVal's) AutoTask Portal if there are fewer heartbeats than expected from the machines checking in within the environment. +This monitor is intended to create a ticket in our (ProVal's) Halo PSA if there are fewer heartbeats than expected from the machines checking in within the environment. ## Dependencies -[Email RAWSQL Monitor Set Failures* [Autofix]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) -"△ Custom - Email RAWSQL Monitor set results to ProVal" Alert template should be applied. +- [Script - Email Creation - Computer* [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) +- `△ Custom - Email RAWSQL Monitor set results to ProVal` Alert template should be applied. ## Target @@ -25,7 +25,7 @@ Global - Should be run without explicitly defined targets. ## Ticketing -**Subject**: CWA - Heartbeat Anomaly Detected +**Subject**: `CWA - Heartbeat Anomaly Detected` **Body**: It has been detected that more than half of the agents do not appear to be properly updating their heartbeat, which can cause some false positives with offline alerting: diff --git a/docs/cwa/monitors/screenconnect-broken-integration.md b/docs/cwa/monitors/screenconnect-broken-integration.md new file mode 100644 index 0000000000..7bf0900689 --- /dev/null +++ b/docs/cwa/monitors/screenconnect-broken-integration.md @@ -0,0 +1,24 @@ +--- +id: 'a3e17618-1629-4eca-ae93-e70dd47e3496' +slug: /a3e17618-1629-4eca-ae93-e70dd47e3496 +title: 'ScreenConnect - Broken Integration' +title_meta: 'ScreenConnect - Broken Integration' +keywords: ['connectwise', 'integration', 'ticket', 'monitor'] +description: 'This document outlines the process to create an urgent ticket in ProVal’s Halo PSA for a broken integration between ConnectWise Automate and ScreenConnect. It includes dependencies and target settings for effective monitoring.' +tags: ['connectwise', 'ticketing'] +draft: false +unlisted: false +--- + +## Summary + +This monitor is intended to create an urgent ticket in ProVal's Halo PSA for a broken integration between ConnectWise Automate and ScreenConnect. + +## Dependencies + +- [Script - Email Creation - Computer* [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) +- The `△ Custom - Email RAWSQL Monitor set results to ProVal` alert template should be applied. + +## Target + +Global - This should be run without explicitly defined targets. \ No newline at end of file diff --git a/docs/cwa/monitors/scripting-engine-hung.md b/docs/cwa/monitors/scripting-engine-hung.md index efba209473..3aacb0a846 100644 --- a/docs/cwa/monitors/scripting-engine-hung.md +++ b/docs/cwa/monitors/scripting-engine-hung.md @@ -20,8 +20,8 @@ The email is sent to the address specified in the system property `"ProVal_Alert ## Dependencies -[Scripting Engine Hung - Troubleshooting](/docs/64cf5b44-11bf-42dc-87bc-f1f93582ed8d) -**Alert Template:** `△ Custom - Email RAWSQL Monitor set results to ProVal` +- **Alert Template:** `△ Custom - Email RAWSQL Monitor set results to ProVal` +- [Script - Email Creation - Computer* [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) ## Target @@ -31,14 +31,14 @@ The email is sent to the address specified in the system property `"ProVal_Alert ### Subject ``` -CWA - Scripting Engine Hung +Urgent! - CWA - Scripting Engine Hung ``` ### Body #### Failure ``` %RESULT% Troubleshooting Article: -https://content.provaltech.com/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9#troubleshoot +https://content.provaltech.com/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9#troubleshooting ``` #### Success ``` @@ -55,26 +55,26 @@ Top Script IDs shown below: ## Troubleshooting -![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image1.webp) +![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image1.webp) When you see a ticket like the above for any partner please follow the below troubleshooting steps. -1. Navigate to the System >> VNC / Ticket Priority >> MAX Running Scripts. Look for the "MAX Running Scripts" and ensure its value is at least 1/3 of the value of its agent count. This applies only to the environment where you have seen frequent Scripting Engine Hung issues. This is not a stated statement; rather, it is being assumed to prevent situations in the partner environment if they continuously encounter Scripting engine crash issues. Navigate to the System >> Configuration >> Dashboard >> Config >> Configuration >> Properties. Look for the property "LT_MAXRunningScripts" and ensure its value is reflected +1. Navigate to the `System` >> VNC / `Ticket Priority` >> `MAX Running Scripts`. Look for the "MAX Running Scripts" and ensure its value is at least 1/3 of the value of its agent count. This applies only to the environment where you have seen frequent Scripting Engine Hung issues. This is not a stated statement; rather, it is being assumed to prevent situations in the partner environment if they continuously encounter Scripting engine crash issues. Navigate to the `System` >> `Configuration` >> `Dashboard` >> `Config` >> `Configuration` >> `Properties`. Look for the property "*LT_MAXRunningScripts*" and ensure its value is reflected -![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image2.webp) +![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image2.webp) -2. Navigate to the Automation >> Monitor >> Internal Monitor +2. Navigate to the `Automation` >> `Monitor` >> `Internal Monitor` 3. Right-click and select the "New Monitor" -![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image3.webp) +![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image3.webp) 4. Start Fresh >> Next -![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image4.webp) +![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image4.webp) 5. Run the query as mentioned below. Export the list to share with the consultant. Check for the top scripts whose running count is too much figure out why it has been running like that and fix it if found irrelevant. Bring the concern to the consultant with the note point and screenshots. -![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image5.webp) +![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image5.webp) ```sql SELECT @@ -103,9 +103,9 @@ ORDER BY 6. Run another query. Follow steps 2-4, then run the below query. Please validate the stuck scripts and get that report exported to Excel to forward to the consultant with your feedback and review analysis reporting. -![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image6.webp) +![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image6.webp) -![image](/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image7.webp) +![image](../../../static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image7.webp) ```sql SELECT @@ -127,4 +127,4 @@ WHERE AND CASE WHEN c.lastcontact > NOW() - INTERVAL 15 MINUTE THEN l.ScriptFlags = 0 ELSE l.scriptflags = 1 END ``` -7. **Only if the scripting engine appears to be hung with a lot of scripts reporting in the queue**, Restart the DB Agent service. Navigate to Help >> Server Status >> Restart Database Agent. This will remove all queued scripts and will fix the script engine hung temporarily if the script queuing issue is not fixed from the above query results. \ No newline at end of file +7. **Only if the scripting engine appears to be hung with a lot of scripts reporting in the queue**, Restart the DB Agent service. Navigate to `Help` >> `Server Status` >> `Restart Database Agent`. This will remove all queued scripts and will fix the script engine hung temporarily if the script queuing issue is not fixed from the above query results. \ No newline at end of file diff --git a/docs/cwa/monitors/svc-cwafileservice.md b/docs/cwa/monitors/svc-cwafileservice.md index 9b16ce63fc..78006eaac9 100644 --- a/docs/cwa/monitors/svc-cwafileservice.md +++ b/docs/cwa/monitors/svc-cwafileservice.md @@ -4,7 +4,7 @@ slug: /5ae52dd7-e476-49dd-823f-582cbf6de17e title: 'SVC-CWAFileService' title_meta: 'SVC-CWAFileService' keywords: ['monitor', 'service', 'automate', 'ticket', 'status'] -description: 'This document outlines the CWAFileService monitor for the Automate server, detailing its purpose to check the service status and create urgent tickets in Autotask if the service is down, specifically for on-prem partners.' +description: 'This document outlines the CWAFileService monitor for the Automate server, detailing its purpose to check the service status and create urgent tickets in Halo if the service is down, specifically for on-prem partners.' tags: ['ticketing'] draft: false unlisted: false @@ -12,7 +12,7 @@ unlisted: false ## Summary -CWAFileService is one of the important services for the Automate server. This monitor checks the service status and is intended to create an urgent ticket in our (ProVal's) Autotask portal if it is down. It should be created against the "Labtech Server" group for on-prem partners only. +CWAFileService is one of the important services for the Automate server. This monitor checks the service status and is intended to create an urgent ticket in our (ProVal's) Halo PSA if it is down. It should be created against the "Labtech Server" group for on-prem partners only. ## Details diff --git a/docs/cwa/monitors/svc-cwaiismgr.md b/docs/cwa/monitors/svc-cwaiismgr.md index 35dc514e76..61997d781f 100644 --- a/docs/cwa/monitors/svc-cwaiismgr.md +++ b/docs/cwa/monitors/svc-cwaiismgr.md @@ -4,7 +4,7 @@ slug: /f73d6546-470e-448b-b3db-d7b57d3d8df4 title: 'SVC-CWAIISMgr' title_meta: 'SVC-CWAIISMgr' keywords: ['monitor', 'service', 'automate', 'ticket', 'labtech', 'server'] -description: 'This document outlines the CWAIISMgr service monitor for the Automate server, detailing its purpose, configuration, and alert settings to ensure timely ticket creation in the Autotask portal when the service is down.' +description: 'This document outlines the CWAIISMgr service monitor for the Automate server, detailing its purpose, configuration, and alert settings to ensure timely ticket creation in the Halo PSA when the service is down.' tags: ['windows'] draft: false unlisted: false @@ -12,7 +12,7 @@ unlisted: false ## Summary -CWAIISMgr is one of the important services for the Automate server. This monitor checks the service status and is intended to create an urgent ticket in our (ProVal's) Autotask portal if it is down. It should be created against the "Labtech Server" group for the on-prem partners only. +CWAIISMgr is one of the important services for the Automate server. This monitor checks the service status and is intended to create an urgent ticket in our (ProVal's) Halo PSA if it is down. It should be created against the "Labtech Server" group for the on-prem partners only. ## Details diff --git a/docs/cwa/monitors/svc-cwamessagequeue.md b/docs/cwa/monitors/svc-cwamessagequeue.md index 4d45c0eafa..93c7121b84 100644 --- a/docs/cwa/monitors/svc-cwamessagequeue.md +++ b/docs/cwa/monitors/svc-cwamessagequeue.md @@ -4,7 +4,7 @@ slug: /a1fb4b3c-b08f-4090-9df7-66e7d80ca93d title: 'SVC-CWAMessageQueue' title_meta: 'SVC-CWAMessageQueue' keywords: ['cwa', 'monitoring', 'service', 'alert', 'ticket'] -description: 'This document outlines the monitoring setup for the CWAMessageQueue service in ConnectWise Automate. It details the alert configuration, suggested parameters, and target server roles to ensure timely notifications and ticket creation in Autotask when the service becomes unavailable.' +description: 'This document outlines the monitoring setup for the CWAMessageQueue service in ConnectWise Automate. It details the alert configuration, suggested parameters, and target server roles to ensure timely notifications and ticket creation in Halo when the service becomes unavailable.' tags: [] draft: false unlisted: false @@ -12,7 +12,7 @@ unlisted: false ## Summary -CWAMessageQueue is one of the important services for the Automate server. This monitor is intended to alert on the status of that service and create an urgent ticket in our (ProVal's) Autotask portal in the event that the service becomes unavailable. It should be created against the "Labtech Server" group for the on-prem partners only. +CWAMessageQueue is one of the important services for the Automate server. This monitor is intended to alert on the status of that service and create an urgent ticket in our (ProVal's) Halo PSA in the event that the service becomes unavailable. It should be created against the "Labtech Server" group for the on-prem partners only. ## Details diff --git a/docs/cwa/monitors/svc-ltredirsvc.md b/docs/cwa/monitors/svc-ltredirsvc.md index 641bbf0745..fd8e5ef87c 100644 --- a/docs/cwa/monitors/svc-ltredirsvc.md +++ b/docs/cwa/monitors/svc-ltredirsvc.md @@ -4,7 +4,7 @@ slug: /33120745-9fa1-4864-aff6-b97d083e3fd5 title: 'SVC-LTRedirSVC' title_meta: 'SVC-LTRedirSVC' keywords: ['automate', 'monitoring', 'service', 'alert', 'ticket'] -description: 'This document outlines the monitoring setup for the LTRedirSVC service on the Automate server, including alert configurations and service check details to ensure timely notifications and ticket creation in Autotask.' +description: 'This document outlines the monitoring setup for the LTRedirSVC service on the Automate server, including alert configurations and service check details to ensure timely notifications and ticket creation in Halo.' tags: [] draft: false unlisted: false @@ -12,7 +12,7 @@ unlisted: false ## Summary -LTRedirSVC is one of the important services for the Automate server. This monitor is intended to alert on the status of that service and create an urgent ticket in our (ProVal's) Autotask portal if the status becomes failed. +LTRedirSVC is one of the important services for the Automate server. This monitor is intended to alert on the status of that service and create an urgent ticket in our (ProVal's) Halo PSA if the status becomes failed. It should be created against the "Labtech Server" group for on-prem partners only. diff --git a/docs/cwa/monitors/ticket-sync-unsuccessful.md b/docs/cwa/monitors/ticket-sync-unsuccessful.md index 4e8a3cc423..daef22f33b 100644 --- a/docs/cwa/monitors/ticket-sync-unsuccessful.md +++ b/docs/cwa/monitors/ticket-sync-unsuccessful.md @@ -7,7 +7,7 @@ keywords: ['ticket', 'sync', 'monitor', 'psa', 'automate'] description: 'This document outlines a monitor for identifying tickets within ConnectWise Automate that have failed to sync successfully to the PSA. It includes dependencies and target details for effective implementation.' tags: ['connectwise'] draft: false -unlisted: false +unlisted: true --- ## Summary diff --git a/docs/cwa/scripts/automate-server-event-log-monitoring-autofix.md b/docs/cwa/scripts/automate-server-event-log-monitoring-autofix.md index ce84243e7d..4e572f5b09 100644 --- a/docs/cwa/scripts/automate-server-event-log-monitoring-autofix.md +++ b/docs/cwa/scripts/automate-server-event-log-monitoring-autofix.md @@ -7,7 +7,7 @@ keywords: ['event', 'logs', 'monitoring', 'alert', 'script'] description: 'This document describes a script designed to monitor unwanted event logs in the Automate Server environment. It provides details on how the script functions, its dependencies, and the process it follows to alert users when unwanted logs are detected.' tags: ['email'] draft: false -unlisted: false +unlisted: true --- ## Summary diff --git a/docs/cwa/scripts/automate-server-monitoring-service-restart-autofix.md b/docs/cwa/scripts/automate-server-monitoring-service-restart-autofix.md index 011d107818..e2df3015b9 100644 --- a/docs/cwa/scripts/automate-server-monitoring-service-restart-autofix.md +++ b/docs/cwa/scripts/automate-server-monitoring-service-restart-autofix.md @@ -1,8 +1,8 @@ --- id: '870dc2c7-95ea-494e-aefd-05609925545b' slug: /870dc2c7-95ea-494e-aefd-05609925545b -title: 'Automate Server Monitoring - Service - Restart Autofix' -title_meta: 'Automate Server Monitoring - Service - Restart Autofix' +title: 'Automate Server Monitoring - Service - Restart [Autofix]' +title_meta: 'Automate Server Monitoring - Service - Restart [Autofix]' keywords: ['automate', 'monitoring', 'email', 'notification', 'service'] description: 'This document details a script designed for use with remote monitors in the Automate server and CW Manage Plugin Monitoring. The script is structured to send a SUCCESS email only if a FAILURE email has already been dispatched for the monitored service, ensuring efficient communication and alert management.' tags: ['email'] @@ -60,13 +60,13 @@ This script will not work manually; it can be used via the `△ Custom - Autofix | Name | Example | Required | Description | |-------------------------------|---------|----------|---------------------------------------------------------------------------------------------------| -| `\\_Failure_Email` | 1 | True | Keeps track of whether the failure email has been sent for the `\\` or not. | +| `_Failure_Email` | 1 | True | Keeps track of whether the failure email has been sent for the `` or not. | ## Process - Check the status of the Monitor Set. - Try restarting the service(s). -- Send an email to [Alerts@provaltech.com](mailto:Alerts@provaltech.com), creating an urgent ticket in ProVal's AutoTask. +- Send an email to [Alerts@provaltech.com](mailto:Alerts@provaltech.com), creating an urgent ticket in ProVal's Halo. Please reference the agnostic content documentation for the Service Restart Process. diff --git a/docs/cwa/scripts/backup-scriptsmonitorscustomizations.md b/docs/cwa/scripts/backup-scriptsmonitorscustomizations.md index 36ee796f0f..9fff0858e7 100644 --- a/docs/cwa/scripts/backup-scriptsmonitorscustomizations.md +++ b/docs/cwa/scripts/backup-scriptsmonitorscustomizations.md @@ -1,8 +1,8 @@ --- id: '19787a52-3223-44e1-8670-ecf74f1b415c' slug: /19787a52-3223-44e1-8670-ecf74f1b415c -title: 'Backup ScriptsMonitorsCustomizations' -title_meta: 'Backup ScriptsMonitorsCustomizations' +title: 'Backup Scripts/Monitors/Customizations' +title_meta: 'Backup Scripts/Monitors/Customizations' keywords: ['backup', 'customizations', 'export', 'scripts', 'monitoring', 'dataviews', 'role', 'virus'] description: 'This document details a script designed to export various ConnectWise Automate customizations for backup and versioning. It supports multiple customization types and includes features for email alerts and system property configuration, ensuring a reliable backup process.' tags: ['backup'] @@ -24,7 +24,7 @@ This script allows you to export various CW Automate customizations for backup a - ExtraData Fields - Virus Scanners -This is a client script. The `AutomateBackup_Computerid` property should store the computer ID of the machine where the backup data will be saved. If the computer ID is offline or does not exist in Automate, it will send an email to [alerts@provaltech.com](mailto:alerts@provaltech.com) with the details of the problem. This will trigger a high-priority ticket in ProVal’s Autotask system to resolve the issue. +This is a client script. The `AutomateBackup_Computerid` property should store the computer ID of the machine where the backup data will be saved. If the computer ID is offline or does not exist in Automate, it will send an email to [alerts@provaltech.com](mailto:alerts@provaltech.com) with the details of the problem. This will trigger a high-priority ticket in ProVal’s Halo system to resolve the issue. The script will also use another system property called `AutomateBackup_Base_Directory` to determine the destination path for the backup data. If this property is not configured or left blank, the script will default to `C:/CWA Solutions Backup`. If the variable is not correctly defined in the property, it will default to `C:/CWAutomate`. @@ -55,7 +55,7 @@ Source: [https://forums.mspgeek.org/files/file/17-script-backup/?_fromLogin=1](h ## Dependencies -[CWA - Script - Dataview - Save as CSV [Custom Location]](/docs/ef644f47-8268-43fd-9e8a-ab32f64ec617) +[Dataview - Save as CSV [Custom Location]](/docs/ef644f47-8268-43fd-9e8a-ab32f64ec617) ## User Parameters diff --git a/docs/cwa/scripts/connectwise-manage-plugin-syncmapping-audit.md b/docs/cwa/scripts/connectwise-manage-plugin-syncmapping-audit.md index 0e4a068232..0e83f84e1b 100644 --- a/docs/cwa/scripts/connectwise-manage-plugin-syncmapping-audit.md +++ b/docs/cwa/scripts/connectwise-manage-plugin-syncmapping-audit.md @@ -7,7 +7,7 @@ keywords: ['email', 'alerts', 'cwmanage', 'unsynced', 'components'] description: 'This document outlines a script designed to send email alerts when unsynced or unmapped components are detected in the CW Manage plugin. The script runs weekly and checks for various unsynced configurations, generating a ticket in Autotask if issues are found.' tags: ['report', 'security'] draft: false -unlisted: false +unlisted: true --- ## Summary diff --git a/docs/cwa/scripts/database-size-increased-by-5-percent-global.md b/docs/cwa/scripts/database-size-increased-by-5-percent-global.md index b12111a204..487888f71d 100644 --- a/docs/cwa/scripts/database-size-increased-by-5-percent-global.md +++ b/docs/cwa/scripts/database-size-increased-by-5-percent-global.md @@ -7,7 +7,7 @@ keywords: ['labtech', 'database', 'alert', 'ticket', 'autotask'] description: 'This document outlines a script designed to monitor the Labtech Database size and create a ticket in AutoTask if the database size increases by a specified threshold within the last 24 hours. The script can be scheduled to run hourly and includes details on variables, global parameters, and the process flow for execution.' tags: ['database'] draft: false -unlisted: false +unlisted: true --- ## Summary diff --git a/docs/cwa/scripts/email-creation-computer-failure-only.md b/docs/cwa/scripts/email-creation-computer-failure-only.md index ebe1a14062..ff0a173644 100644 --- a/docs/cwa/scripts/email-creation-computer-failure-only.md +++ b/docs/cwa/scripts/email-creation-computer-failure-only.md @@ -1,8 +1,8 @@ --- id: '901470a2-73d2-4d29-b0d3-c5f15cf19c41' slug: /901470a2-73d2-4d29-b0d3-c5f15cf19c41 -title: 'Email Creation - Computer Failure Only' -title_meta: 'Email Creation - Computer Failure Only' +title: 'Email Creation - Computer [Failure Only]' +title_meta: 'Email Creation - Computer [Failure Only]' keywords: ['email', 'rawsql', 'monitor', 'failure', 'notification'] description: 'This document describes a script designed to send email notifications for failed outcomes of a RAWSQL monitor. It details the email addresses used for notifications, system properties required, and the process flow for handling failures. The script is linked to a specific alert template and includes configuration for success email notifications.' tags: ['email'] @@ -12,7 +12,7 @@ unlisted: false ## Summary -This script functions similarly to the [CWM - Automate - Script - Ticket Creation - Computer](/docs/63beba3c-f4a6-41a5-98e2-d4e4ce885035) script; however, instead of creating a ticket, it is designed to send the FAILED outcomes of a RAWSQL monitor to the email address provided in the system property. +This script functions similarly to the [Ticket Creation - Computer](/docs/63beba3c-f4a6-41a5-98e2-d4e4ce885035) script; however, instead of creating a ticket, it is designed to send the FAILED outcomes of a RAWSQL monitor to the email address provided in the system property. This script sends emails to two different addresses: @@ -25,7 +25,7 @@ This script sends emails to two different addresses: ## Sample Run -It's an Autofix script and is currently attached to the "△ Custom - Email RAWSQL Monitor set results to ProVal" alert template. +It's an Autofix script and is currently attached to the `△ Custom - Email RAWSQL Monitor set results to ProVal` alert template. ![Sample Run](../../../static/img/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41/image_1.webp) diff --git a/docs/cwa/scripts/nightly-database-backup-monitoring.md b/docs/cwa/scripts/nightly-database-backup-monitoring.md index a4ce0899a9..b2d11a3e9c 100644 --- a/docs/cwa/scripts/nightly-database-backup-monitoring.md +++ b/docs/cwa/scripts/nightly-database-backup-monitoring.md @@ -4,7 +4,7 @@ slug: /002e4435-9142-4373-a857-6bf91c16d7af title: 'Nightly Database Backup Monitoring' title_meta: 'Nightly Database Backup Monitoring' keywords: ['ticket', 'backup', 'failure', 'connectwise', 'automate', 'email', 'notification'] -description: 'This document describes a script that creates a ticket in the ProValtech Autotask Portal when the ConnectWise Automate nightly backup fails. It details the process, variables, and system properties involved in the script, ensuring timely notifications for backup issues.' +description: 'This document describes a script that creates a ticket in the ProValtech Halo PSA when the ConnectWise Automate nightly backup fails. It details the process, variables, and system properties involved in the script, ensuring timely notifications for backup issues.' tags: ['backup', 'connectwise', 'database', 'email'] draft: false unlisted: false @@ -12,7 +12,7 @@ unlisted: false ## Summary -This script will create a ticket in our (ProValtech's) Autotask Portal if the ConnectWise Automate nightly backup fails. +This script will create a ticket in our (ProValtech's) Halo PSA if the ConnectWise Automate nightly backup fails. ## Sample Run diff --git a/docs/cwa/scripts/ticket-creation-without-computer-information-and-failures-only-autofix.md b/docs/cwa/scripts/ticket-creation-without-computer-information-and-failures-only-autofix.md index f85351c9f5..d5d391d399 100644 --- a/docs/cwa/scripts/ticket-creation-without-computer-information-and-failures-only-autofix.md +++ b/docs/cwa/scripts/ticket-creation-without-computer-information-and-failures-only-autofix.md @@ -1,8 +1,8 @@ --- id: '730449e6-1c73-46ca-a93d-d7b9526e1ef9' slug: /730449e6-1c73-46ca-a93d-d7b9526e1ef9 -title: 'Ticket Creation - Without Computer Information And Failures Only Autofix' -title_meta: 'Ticket Creation - Without Computer Information And Failures Only Autofix' +title: 'Ticket Creation - Without Computer Information And Failures Only [Autofix]' +title_meta: 'Ticket Creation - Without Computer Information And Failures Only [Autofix]' keywords: ['ticket', 'creation', 'monitor', 'alert', 'sql'] description: 'This document describes a script that creates tickets without including computer details, functioning similarly to the CWM Automate script for ticket creation. It outlines the variables used, the process for ticket creation, and the expected output, focusing on RAWSQL monitor sets and internal monitors.' tags: ['sql'] @@ -12,11 +12,11 @@ unlisted: false ## Summary -This script operates similarly to the [CWM - Automate - Script - Ticket Creation - Computer](/docs/63beba3c-f4a6-41a5-98e2-d4e4ce885035) script; however, instead of creating a ticket with the computer's details, it will create a ticket without including them. Additionally, no actions are defined in the script for the SUCCESS status of the monitors. +This script operates similarly to the [Ticket Creation - Computer](/docs/63beba3c-f4a6-41a5-98e2-d4e4ce885035) script; however, instead of creating a ticket with the computer's details, it will create a ticket without including them. Additionally, no actions are defined in the script for the SUCCESS status of the monitors. ## Sample Run -This is an Autofix Script, and it is currently being used with the “~Custom Ticket Creation without Computer Details” alert template. +This is an Autofix Script, and it is currently being used with the `~Custom Ticket Creation without Computer Details` alert template. ![Sample Run](../../../static/img/docs/730449e6-1c73-46ca-a93d-d7b9526e1ef9/image_1.webp) diff --git a/docs/cwa/scripts/ticket-sync-failed.md b/docs/cwa/scripts/ticket-sync-failed.md index 4ebec33ec8..5404264821 100644 --- a/docs/cwa/scripts/ticket-sync-failed.md +++ b/docs/cwa/scripts/ticket-sync-failed.md @@ -7,7 +7,7 @@ keywords: ['ticket', 'sync', 'email', 'monitor', 'automate'] description: 'This document details an Autofix script designed to be triggered by the monitor for unsuccessful ticket synchronization to the PSA. It gathers ticket information and forwards it to a specified email address to ensure no tickets are missed, saving time and improving efficiency.' tags: ['email', 'psa'] draft: false -unlisted: false +unlisted: true --- ## Summary diff --git a/docs/cwa/scripts/volume-free-space-monitor-creation-automate-server-only.md b/docs/cwa/scripts/volume-free-space-monitor-creation-automate-server-only.md index d2913ec76e..4a865a5423 100644 --- a/docs/cwa/scripts/volume-free-space-monitor-creation-automate-server-only.md +++ b/docs/cwa/scripts/volume-free-space-monitor-creation-automate-server-only.md @@ -7,7 +7,7 @@ keywords: ['monitor', 'volume', 'free', 'space', 'ticket', 'drives', 'autotask'] description: 'This document details a script designed to monitor the free space on drives of the Automate server and generate tickets in the Autotask portal for any failures. It builds upon the existing Volume Free Space Monitor Creation script with modifications to enhance functionality and reporting.' tags: ['autotask'] draft: false -unlisted: false +unlisted: true --- ## Summary diff --git a/docs/solutions/automate-server-and-cw-manage-plugin-monitoring.md b/docs/solutions/automate-server-and-cw-manage-plugin-monitoring.md index 427a2d1dda..490506e3f7 100644 --- a/docs/solutions/automate-server-and-cw-manage-plugin-monitoring.md +++ b/docs/solutions/automate-server-and-cw-manage-plugin-monitoring.md @@ -20,29 +20,31 @@ The goal of this solution's development is to improve the efficiency and proacti | Content | Priority | Type | Supported Environment | Function | | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [Script - Unsynced Tickets](/docs/eb434aae-87c4-4315-bf73-202a41ff3a96) | High | Client Script | Both | Email the details of the unsynced tickets to the email address(es) set in the system property `Unsynced_Ticket_Email_Address`. | -| [Script - Backup Scripts/Monitors/Customizations](/docs/19787a52-3223-44e1-8670-ecf74f1b415c) | High | Client Script | Both | To perform a scheduled backup of the following customizations:
- Scripts
- Scriptlets
- Internal Monitors
- Group Monitors
- Remote Monitors
- Dataviews
- Role Definitions
- ExtraData Fields
- VirusScanners
Creates an Autotask ticket if the computerid to save the backup is not properly configured.
Email Subject: Automate Customizations Backup FAILED | -| [Script - Nightly Database Backup Monitoring*](/docs/002e4435-9142-4373-a857-6bf91c16d7af) | Medium | Script | Both | This script will create a ticket in our (ProValtech's) Autotask Portal if Labtech's Nightly backup Fails.
Subject: Nightly Database Backup Failed
*Change to two days in a row of failed backups since we now have our backup script | -| [ProVal - Production - Failed Email Monitoring](/docs/f1a15d3d-85d7-4d72-9c08-ad4ca6a7dfbb) | Medium | Internal Monitor | Both | This Monitor reports any failed email that is not related to 'Google authenticator', 'Testing Email Flow', or 'Authentication Token' that has occurred within the last hour.
It will generate only one ticket per hour with the information of all the emails that failed within that interval.
Alert Template: ~Custom Ticket Creation without computer Details
Subject: Automate Failed Email detected
*Convert this to a client script? | -| [Over 90% Licenses Used [G]](/docs/b3d41d1c-e687-4e39-811a-83d6fb99c14d) OR [Less Than 10 Licenses Remaining [G]](/docs/86cf6cf1-58cc-404d-ab7a-a80658e7b91f) | Medium | Internal Monitor | Both | Check current Automate license availability. Suggested monitor failure is 90% usage. It will notify the partners of the failures.
Alert Template: Default Create Automate Ticket
**The Ticket Category of the monitor set should be adjusted as per the requirements.
Subject: Automate Server Over Licenses
Check current Automate license availability. It will notify the partners if only 10 licenses are left. | -| [Monitor - ScreenConnect - Broken Integration](/docs/a3e17618-1629-4eca-ae93-e70dd47e3496) | Urgent | Internal Monitor | Both | The monitor set is designed to create an urgent ticket to our (ProVal's) AutoTask Portal for a broken integration between ConnectWise Automate and Control.
Alert Template: △ Custom - Email RAWSQL Monitor set results to ProVal
Subject: Urgent - Integration Between Control and Automate is broken | -| [Internal Monitor - Heartbeat Anomaly Audit](/docs/fc109cdb-9f88-448b-8c57-b866b2e3c7c2) | Medium | Internal Monitor | Both | This monitor is intended to create a ticket to our (ProVal's) AutoTask Portal if there are fewer heartbeats than expected from the machines checking in within the environment.
Alert Template: △ Custom - Email RAWSQL Monitor set results to ProVal
Subject: CWA - Heartbeat Anomaly detected | -| [Script - Email Creation - Computer [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) | | Autofix Script | Both | This script functions similarly to the [CWM - Automate - Script - Ticket Creation - Computer](/docs/63beba3c-f4a6-41a5-98e2-d4e4ce885035) script however, instead of creating a ticket, it is designed to send the FAILED outcomes of a RAWSQL monitor to the Email address provided in the system property.
This script sends email to two different addresses:
1. If the script is called by the alert template "△ Custom - Email RAWSQL Monitor set results to ProVal" then it will send an email to the email address set at system property "ProVal_Alerts_Email_Address" which is mostly set to "alerts@provaltech.com".
Note: If the property is missing, the script will automatically set it to "alerts@provaltech.com", but if it is set to a different email address then it will not modified.
2. If the script is called by any other template then it will fetch the email address from the system property "_sysTicketDefaultEmail". | -| △ Ticket Creation - without computer Details | | Alert Template | Both | This alert template should be assigned to the [ProVal - Development - Failed Email Monitoring](/docs/f1a15d3d-85d7-4d72-9c08-ad4ca6a7dfbb) monitor set. It will execute the [Ticket Creation - Without Computer Information And Failures Only [Autofix]*](/docs/730449e6-1c73-46ca-a93d-d7b9526e1ef9) script to create a ticket with the information returned by the monitor set. | -| △ Custom - Email RAWSQL Monitor set results to ProVal | | Alert Template | Both | This alert template should be assigned to the [Monitor - ProVal - Production - ScreenConnect - Broken Integration](/docs/a3e17618-1629-4eca-ae93-e70dd47e3496) monitor sets. It will execute the [Email RAWSQL Monitor Set Failures* [Autofix]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) script to send an email to Alerts@provaltech.com. | -| [Internal Monitor - ProVal - Production - Scripting Engine Hung](/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9) | Medium | Internal Monitor | Both | This monitor creates a critical ticket to the board to inform that the script engine is stuck and none of the scripts is running in the environment.
It also sends an email to the alerts@provaltech.com to review it proactively.
The monitor detects the X number of scripts stuck in the pendingscripts table for longer than Y minutes of the scheduled time. | +| [Unsynced Tickets](/docs/eb434aae-87c4-4315-bf73-202a41ff3a96) | High | Client Script | Both | Email the details of the unsynced tickets to the email address(es) set in the system property `Unsynced_Ticket_Email_Address`. | +| [Backup Scripts/Monitors/Customizations](/docs/19787a52-3223-44e1-8670-ecf74f1b415c) | High | Client Script | Both | To perform a scheduled backup of the following customizations:
- Scripts
- Scriptlets
- Internal Monitors
- Group Monitors
- Remote Monitors
- Dataviews
- Role Definitions
- ExtraData Fields
- VirusScanners
Creates a Halo ticket if the computerid to save the backup is not properly configured.
Email Subject: Automate Customizations Backup FAILED | +| [Nightly Database Backup Monitoring*](/docs/002e4435-9142-4373-a857-6bf91c16d7af) | Medium | Client Script | Both | This script will create a ticket in our (ProValtech's) Halo PSA if Labtech's Nightly backup Fails.
Subject: Nightly Database Backup Failed
*Change to two days in a row of failed backups since we now have our backup script | +| [Failed Email Monitoring](/docs/f1a15d3d-85d7-4d72-9c08-ad4ca6a7dfbb) | Medium | Internal Monitor | Both | This Monitor reports any failed email that is not related to 'Google authenticator', 'Testing Email Flow', or 'Authentication Token' that has occurred within the last hour.
It will generate only one ticket per hour with the information of all the emails that failed within that interval.
`Alert Template: ~Custom Ticket Creation without computer Details`
Subject: Automate Failed Email detected
*Convert this to a client script? | +| [Over 90% Licenses Used [G]](/docs/b3d41d1c-e687-4e39-811a-83d6fb99c14d) OR [Less Than 10 Licenses Remaining [G]](/docs/86cf6cf1-58cc-404d-ab7a-a80658e7b91f) | Medium | Internal Monitor | Both | Check current Automate license availability. Suggested monitor failure is 90% usage. It will notify the partners of the failures.
`Alert Template: Default Create Automate Ticket`
**The Ticket Category of the monitor set should be adjusted as per the requirements.
Subject: Automate Server Over Licenses
Check current Automate license availability. It will notify the partners if only 10 licenses are left. | +| [ScreenConnect - Broken Integration](/docs/a3e17618-1629-4eca-ae93-e70dd47e3496) | Urgent | Internal Monitor | Both | The monitor set is designed to create an urgent ticket to our (ProVal's) Halo PSA for a broken integration between ConnectWise Automate and Control.
`Alert Template: △ Custom - Email RAWSQL Monitor set results to ProVal`
Subject: Urgent - Integration Between Control and Automate is broken | +| [Heartbeat Anomaly Audit](/docs/fc109cdb-9f88-448b-8c57-b866b2e3c7c2) | Medium | Internal Monitor | Both | This monitor is intended to create a ticket to our (ProVal's) Halo PSA if there are fewer heartbeats than expected from the machines checking in within the environment.
`Alert Template: △ Custom - Email RAWSQL Monitor set results to ProVal`
Subject: CWA - Heartbeat Anomaly detected | +| [Scripting Engine Hung](/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9) | Medium | Internal Monitor | Both | This monitor creates a critical ticket to the board to inform that the script engine is stuck and none of the scripts is running in the environment.
It also sends an email to the alerts@provaltech.com to review it proactively.
The monitor detects the X number of scripts stuck in the pendingscripts table for longer than Y minutes of the scheduled time.
`Alert Template: △ Custom - Email RAWSQL Monitor set results to ProVal` | +| [Email Creation - Computer [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) | | Autofix Script | Both | This script functions similarly to the [Ticket Creation - Computer](/docs/63beba3c-f4a6-41a5-98e2-d4e4ce885035) script however, instead of creating a ticket, it is designed to send the FAILED outcomes of a RAWSQL monitor to the Email address provided in the system property.
This script sends email to two different addresses:
1. If the script is called by the alert template *△ Custom - Email RAWSQL Monitor set results to ProVal* then it will send an email to the email address set at system property "ProVal_Alerts_Email_Address" which is mostly set to "alerts@provaltech.com".
Note: If the property is missing, the script will automatically set it to "alerts@provaltech.com", but if it is set to a different email address then it will not modified.
2. If the script is called by any other template then it will fetch the email address from the system property "_sysTicketDefaultEmail". | +| △ Ticket Creation - without computer Details | | Alert Template | Both | This alert template should execute the [Ticket Creation - Without Computer Information And Failures Only [Autofix]*](/docs/730449e6-1c73-46ca-a93d-d7b9526e1ef9) script to create a ticket with the information returned by any monitor set. | +| △ Custom - Email RAWSQL Monitor set results to ProVal | | Alert Template | Both | This alert template should execute the [Email Creation - Computer* [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) script to send an email to Alerts@provaltech.com. | + ### On-Prem Only: | Content | Priority | Type | Supported Environment | Function | | ---------------------------------------------------------------------------------------------------- | -------- | -------------- | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [ProVal - Production - SVC-CWAFileService](/docs/5ae52dd7-e476-49dd-823f-582cbf6de17e) | Urgent | Remote Monitor | On-Prem | Since CWAFileService is one of the important services for the Automate server. So, this monitor set is designed to create an urgent ticket in our (ProVal's) Autotask portal after attempting to restart it.
Alert Template: △ Custom - Autofix - Restart Service - Automate Server Monitoring
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | -| [ProVal - Production - SVC-LTRedirSVC](/docs/33120745-9fa1-4864-aff6-b97d083e3fd5) | Urgent | Remote Monitor | On-Prem | Since LTRedirSVC is one of the important services for the Automate server. So, this monitor set is designed to create an urgent ticket in our (ProVal's) Autotask portal after attempting to restart it.
Alert Template: △ Custom - Autofix - Restart Service - Automate Server Monitoring
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | -| [ProVal - Production - SVC-CWAMessageQueue](/docs/a1fb4b3c-b08f-4090-9df7-66e7d80ca93d) | Urgent | Remote Monitor | On-Prem | Since CWAMessageQueue is one of the important services for the Automate server. So, this monitor set is designed to create an urgent ticket in our (ProVal's) Autotask portal after attempting to restart it.
Alert Template: △ Custom - Autofix - Restart Service - Automate Server Monitoring
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | -| [CWA - Remote Monitors - CWAFileService - Invalid Token](/docs/3ccd3348-558b-41c3-8a81-c65fae2cf04e) | Medium | Remote Monitor | On-Prem | This remote monitor restarts the service 'CWAFileService' on the Automate server if it detects the file 'C:\Windows\Temp\FileService.log' where the file contains the message 'HttpRequest is missing or has invalid Authorization Token' in the last 15 minutes.
The actual message template is:
FileService v24.0 - 3/10/2024 3:08:12 PM - HttpRequest is missing or has invalid Authorization Token::: | -| [Monitor - ProVal - Production - SVC-CWAIISMgr](/docs/f73d6546-470e-448b-b3db-d7b57d3d8df4) | Urgent | Remote Monitor | On-Prem | Since CWAIISMgr is one of the important services for the Automate server. So, this monitor set is designed to create an urgent ticket in our (ProVal's) Autotask portal after attempting to restart it.
Alert Template: △ Custom - Autofix - Restart Service - Automate Server Monitoring
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | -| [Purge IIS Log Files Older than X days[Param]](/docs/a7a7e04e-384d-4018-87c5-6abf2d2b2fb2) | | Script | On-Prem | It will remove the IIS logs older than `Days`(Global Variable) days if the size of the "c:\\inetpub\\logs\\logfiles\\w3svc" folder is greater than `Size`(Global Variable) MB. Preferred is to schedule against the "Labtech Server" Group to run once per week.
By default, it will remove the logs older than 30 days if the size of the directory is greater than 1024 MB.
*Log Entries need fixing
*Change threshold to 16GB? Homefield is always failing because it drops it to 15GB used instead of 19GB. | -| △ Custom - Autofix - Restart Service - Automate Server Monitoring | | Alert Template | On-Prem | This alert template should be assigned to the [ProVal - Development - SVC-CWAFileService](/docs/5ae52dd7-e476-49dd-823f-582cbf6de17e), [ProVal - Development - SVC-LTRedirSVC](/docs/33120745-9fa1-4864-aff6-b97d083e3fd5), [ProVal - Development - SVC-CWAMessageQueue](/docs/a1fb4b3c-b08f-4090-9df7-66e7d80ca93d), and monitor sets. It will attempt to restart the service and will send an Email for Autofix failure to Alerts@ProValtech.com which in turn will generate a ticket in our (ProVal's) Autotask portal.
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | +| [SVC-CWAFileService](/docs/5ae52dd7-e476-49dd-823f-582cbf6de17e) | Urgent | Remote Monitor | On-Prem | Since CWAFileService is one of the important services for the Automate server. So, this monitor set is designed to create an urgent ticket in our (ProVal's) Halo PSA after attempting to restart it.
*`Alert Template: △ Custom - Autofix - Restart Service - Automate Server Monitoring`*
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | +| [SVC-LTRedirSVC](/docs/33120745-9fa1-4864-aff6-b97d083e3fd5) | Urgent | Remote Monitor | On-Prem | Since LTRedirSVC is one of the important services for the Automate server. So, this monitor set is designed to create an urgent ticket in our (ProVal's) Halo PSA after attempting to restart it.
*`Alert Template: △ Custom - Autofix - Restart Service - Automate Server Monitoring`*
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | +| [SVC-CWAMessageQueue](/docs/a1fb4b3c-b08f-4090-9df7-66e7d80ca93d) | Urgent | Remote Monitor | On-Prem | Since CWAMessageQueue is one of the important services for the Automate server. So, this monitor set is designed to create an urgent ticket in our (ProVal's) Halo PSA after attempting to restart it.
*`Alert Template: △ Custom - Autofix - Restart Service - Automate Server Monitoring`*
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | +| [CWAFileService - Invalid Token](/docs/3ccd3348-558b-41c3-8a81-c65fae2cf04e) | Medium | Remote Monitor | On-Prem | This remote monitor restarts the service 'CWAFileService' on the Automate server if it detects the file 'C:\Windows\Temp\FileService.log' where the file contains the message 'HttpRequest is missing or has invalid Authorization Token' in the last 15 minutes.
The actual message template is:
FileService v24.0 - 3/10/2024 3:08:12 PM - HttpRequest is missing or has invalid Authorization Token::: | +| [SVC-CWAIISMgr](/docs/f73d6546-470e-448b-b3db-d7b57d3d8df4) | Urgent | Remote Monitor | On-Prem | Since CWAIISMgr is one of the important services for the Automate server. So, this monitor set is designed to create an urgent ticket in our (ProVal's) Halo PSA after attempting to restart it.
*`Alert Template: △ Custom - Autofix - Restart Service - Automate Server Monitoring`*
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | +| [Purge IIS Log Files Older than X days[Param]](/docs/a7a7e04e-384d-4018-87c5-6abf2d2b2fb2) | | Script | On-Prem | It will remove the IIS logs older than `Days`(Global Variable) days if the size of the "c:\\inetpub\\logs\\logfiles\\w3svc" folder is greater than `Size`(Global Variable) MB. Preferred is to schedule against the "Labtech Server" Group to run once per week.
By default, it will remove the logs older than 30 days if the size of the directory is greater than 1024 MB.
*Log Entries need fixing
*Change threshold to 16GB? Homefield is always failing because it drops it to 15GB used instead of 19GB. | +| [Automate Server Monitoring - Service - Restart [Autofix]](/docs/870dc2c7-95ea-494e-aefd-05609925545b) | | Script |On-Prem | This autofix script restarts the above services and sends an email to ProVal with "Urgent" pre-fix in the subject if the services fails to restart. | +| △ Custom - Autofix - Restart Service - Automate Server Monitoring | | Alert Template | On-Prem | This alert template should be assigned to the [SVC-CWAFileService](/docs/5ae52dd7-e476-49dd-823f-582cbf6de17e), [SVC-LTRedirSVC](/docs/33120745-9fa1-4864-aff6-b97d083e3fd5), [SVC-CWAMessageQueue](/docs/a1fb4b3c-b08f-4090-9df7-66e7d80ca93d), and [SVC-CWAIISMgr](/docs/f73d6546-470e-448b-b3db-d7b57d3d8df4) monitor sets. It will execute the [Automate Server Monitoring - Service - Restart [Autofix]](/docs/870dc2c7-95ea-494e-aefd-05609925545b) script and attempt to restart the service and will send an Email for Autofix failure to `Alerts@ProValtech.com` which in turn will generate a ticket in our (ProVal's) Halo PSA.
Email Subject Success: URGENT - SVC - @FieldName@ - SUCCESS - Automate Server - %ComputerName% (%Computerid%)
Email Subject Failure: URGENT - SVC - @FieldName@ - FAILED - Automate Server - %ComputerName% (%Computerid%) | ## Implementation @@ -53,18 +55,18 @@ The goal of this solution's development is to improve the efficiency and proacti - △ Custom - Autofix - Restart Service - Automate Server Monitoring 2. Modify the following System Properties - If any of these values are not provided by the consultant, reach out to clarify: - - Unsynced_Ticket_Email_Address - This is where the partner would like alerts for any ticket sync issues to go to. - - AutomateBackup_Computerid - This is going to be the AgentID of where the partner would like their content backup to be stored. - - _sysTicketDefaultEmail - This is a default email address that is set for sending data in the case where the user wants the email to be sent from the script. - - ProVal_Alerts_Email_Address - This email address is used when the script calls from the alert template "△ Custom - Email RAWSQL Monitor set results to ProVal".
Note: It is mandatory to use the [alerts@provaltech.com](mailto:alerts@provaltech.com) with this system property as it is intentionally created for the alerts which is required to be passed on to the ProVal support team from the partner environment for proactive fixes. + - `Unsynced_Ticket_Email_Address` - This is where the partner would like alerts for any ticket sync issues to go to. + - `AutomateBackup_Computerid` - This is going to be the AgentID of where the partner would like their content backup to be stored. + - `_sysTicketDefaultEmail` - This is a default email address that is set for sending data in the case where the user wants the email to be sent from the script. + - `ProVal_Alerts_Email_Address` - This email address is used when the script calls from the alert template "*△ Custom - Email RAWSQL Monitor set results to ProVal*".
Note: It is mandatory to use the [alerts@provaltech.com](mailto:alerts@provaltech.com) with this system property as it is intentionally created for the alerts which is required to be passed on to the ProVal support team from the partner environment for proactive fixes. Optional System Properties: - - AutomateBackup_Base_Directory - If the consultant specified any custom value for this, please update it. Otherwise, it will go to the default directory of 'C:\\CWA Solutions Backup'. + - `AutomateBackup_Base_Directory` - If the consultant specified any custom value for this, please update it. Otherwise, it will go to the default directory of 'C:\\CWA Solutions Backup'. 3. Import and set the **approved content** to the partner's environment using the ProSync Plugin. If it is NOT specified to specifically not import certain content, assume it is all approved. The content required for import has been listed below: - [Script - Unsynced Tickets](/docs/eb434aae-87c4-4315-bf73-202a41ff3a96) - [Script - Email RAWSQL Monitor Set Failures* [Autofix]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) - - [CWM - Automate - Script - Email Creation - Computer [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) + - [Script - Email Creation - Computer [Failure Only]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) - [Client Script - Automate - Backup Scripts/Monitors/Customizations](/docs/19787a52-3223-44e1-8670-ecf74f1b415c) - [Client Script - Nightly Database Backup Monitoring*[Global]](/docs/002e4435-9142-4373-a857-6bf91c16d7af) - [Internal Monitor - ProVal - Production - Failed Email Monitoring](/docs/f1a15d3d-85d7-4d72-9c08-ad4ca6a7dfbb) @@ -74,34 +76,34 @@ The goal of this solution's development is to improve the efficiency and proacti - [Internal Monitor - ProVal - Production - Scripting Engine Hung](/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9) 4. Setup the content that was just imported: - - Navigate to the System Dashboard screen --> Management --> Scheduled Client Scripts + - Navigate to the `System Dashboard` screen > `Management` > `Scheduled Client Scripts` - Schedule [Script - Unsynced Tickets](/docs/eb434aae-87c4-4315-bf73-202a41ff3a96) to run every 2 hours - Schedule [Client Script - Automate - Backup Scripts/Monitors/Customizations](/docs/19787a52-3223-44e1-8670-ecf74f1b415c) to run weekly, Every Monday at 5:40 AM - Schedule [Client Script - Nightly Database Backup Monitoring*[Global]](/docs/002e4435-9142-4373-a857-6bf91c16d7af) to run daily at 2:30 PM - - Navigate to Automate --> Monitors + - Navigate to `Automate` > `Monitors` - Setup [Internal Monitor - ProVal - Production - Failed Email Monitoring](/docs/f1a15d3d-85d7-4d72-9c08-ad4ca6a7dfbb) - **For hosted partners only**, you must modify this client ID variable in the monitor to whatever the partner's client ID is: - - Assign the alert template '△ Custom - Ticket Creation - Without Computer Details' to the monitor + - Assign the alert template `△ Custom - Ticket Creation - Without Computer Details` to the monitor - Right-click the monitor and select Run Now and Reset Monitor - Setup [Internal Monitor - ProVal - Production - Automate - Less Than 10 Licenses Remaining [G]](/docs/86cf6cf1-58cc-404d-ab7a-a80658e7b91f) OR [Internal Monitor - ProVal - Production - Automate - Over 90% Licenses Used [G]](/docs/b3d41d1c-e687-4e39-811a-83d6fb99c14d) - Depending on what the Consultant has requested - - Apply the 'Default - Create Automate Ticket' alert template to the monitor + - Apply the `Default - Create Automate Ticket` alert template to the monitor - Right-click the monitor and select Run Now and Reset Monitor - Setup [Internal Monitor - ProVal - Production - ScreenConnect - Broken Integration](/docs/a3e17618-1629-4eca-ae93-e70dd47e3496) - - Apply the '△ Custom - Email RAWSQL Monitor set results to ProVal' alert template to the monitor + - Apply the `△ Custom - Email RAWSQL Monitor set results to ProVal` alert template to the monitor - Right-click the monitor and select Run Now and Reset Monitor - Setup [Internal Monitor - Heartbeat Anomaly Audit](/docs/fc109cdb-9f88-448b-8c57-b866b2e3c7c2) - - Apply the '△ Custom - Email RAWSQL Monitor set results to ProVal' alert template to the monitor + - Apply the `△ Custom - Email RAWSQL Monitor set results to ProVal` alert template to the monitor - Right-click the monitor and select Run Now and Reset Monitor - Setup [Internal Monitor - ProVal - Production - Scripting Engine Hung](/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9) - - Apply the '△ Custom - Email RAWSQL Monitor set results to ProVal' alert template to the monitor + - Apply the `△ Custom - Email RAWSQL Monitor set results to ProVal` alert template to the monitor - Right-click the monitor and select Run Now and Reset Monitor ### On-Prem Only: 1. Import and set the following content using the ProSync Plugin: - Script: [Purge IIS Log Files Older than X days[Param]](/docs/a7a7e04e-384d-4018-87c5-6abf2d2b2fb2) - - Script: [CWM - Automate - Script - Automate Server Monitoring - Service - Restart [Autofix]](/docs/870dc2c7-95ea-494e-aefd-05609925545b) - - Alert Template: △ Custom - Autofix - Restart Service - Automate Server Monitoring + - Script: [Automate Server Monitoring - Service - Restart [Autofix]](/docs/870dc2c7-95ea-494e-aefd-05609925545b) + - Alert Template: `△ Custom - Autofix - Restart Service - Automate Server Monitoring` 2. Setup the content that was just imported: - Navigate to the LabTech Server Group (Service Plans --> Server Roles --> MSP Specific Servers --> LabTech Server) @@ -393,22 +395,21 @@ The goal of this solution's development is to improve the efficiency and proacti 7. Import the Remote Monitor using the documentation below: - [Import - Remote Monitor - CWAFileService - Invalid Token](/docs/3ccd3348-558b-41c3-8a81-c65fae2cf04e) - - Make sure to set the Alert Template on the monitor to 'Default - Create Automate Ticket' + - Make sure to set the Alert Template on the monitor to '`Default - Create Automate Ticket`' - Use the defaults in the SQL unless otherwise stated. ## Deprecated Content - November 2023 -| Content | Priority | Type | Supported Environment | Function | +|Content | Priority | Type | Supported Environment | Function | | ------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Deprecated:** △ Autofix - Ticket Sync Failed | | Alert Template | Both | This alert template should be assigned to the [ProVal - Production - Automate - Ticket Sync Unsuccessful](/docs/1fa27f5d-ca9d-4bff-8776-569a15f772d3) monitor set. It will execute the [Ticket Sync Failed [Autofix, Globals]](/docs/f490325a-023c-430d-876d-e4d311ff3e89) script. | -| | -| **Deprecated:** [ProVal - Development - Automate - Unsynced Ticket Content](/docs/6a855fe6-df02-4668-81c3-8cd392595c31) | High | Internal Monitor | Both | The main objective of the monitor set is to alert the partners of any unsynced ticket comments for a ticket that has already been synchronized to CW Manage.
Alert Template: ~Custom Email RAWSQL Monitor set results to the Partner.
Subject: Ticket Comment Failed to Sync to Manage for %ExternalID% | -| **Deprecated:** △ Email RAWSQL Monitor set results to the Partner | | Alert Template | Both | This alert template should be assigned to the [ProVal - Development - Automate - Unsynced Ticket Content](/docs/6a855fe6-df02-4668-81c3-8cd392595c31) monitor set. It will execute the [Email RAWSQL Monitor Set Failures* [Autofix]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) script to send an email to the selected template contact/user. | -| **Deprecated:** [ProVal - Development - CW Manage Plugin Errors](/docs/cc311e32-be16-4133-ae95-fca238aea891) | Medium | Internal Monitor | Both | The internal monitor is designed to notify [alerts@provaltech.com](mailto:alerts@provaltech.com) of any critical errors and issues with the ConnectWise Manage Plugin.
Alert Template: ***** use Default - Do Nothing for now until we have an opportunity to look further into these action items from this monitor.
Subject: CW Manage Plugin Errors Detected for %Result%
e.g., CW Manage Plugin Errors Detected for Contacts on 2022-08-09 | -| **Deprecated:** ~Custom Email RAWSQL Monitor set results to ProVal | | Alert Template | Both | This alert template should be assigned to the [ProVal - Development - CW Manage Plugin Errors](/docs/cc311e32-be16-4133-ae95-fca238aea891) and [ProVal - Development - Control - Broken Integration](/docs/a3e17618-1629-4eca-ae93-e70dd47e3496) monitor sets. It will execute the [Email RAWSQL Monitor Set Failures* [Autofix]](/docs/901470a2-73d2-4d29-b0d3-c5f15cf19c41) script to send an email to [Alerts@provaltech.com](mailto:Alerts@provaltech.com). | -| **Deprecated:** [ProVal - Development - Automate Server - Unwanted Event Logs Monitoring](/docs/88dfd269-1df7-4c57-a898-9445dec162b5) | Medium | Remote Monitor | On-Prem | The purpose of this remote monitor is to generate an Urgent ticket in our (ProVal's) Autotask portal if an error or critical event from either of "DBAgent", "ASPWCC2", or "MySQL" event sources is generated more than 10 times within the past 60 minutes on Automate server.
Alert Template: ***** use Default - Do Nothing for now until we have an opportunity to look further into these action items from this monitor.
Subject: Urgent - Automate Server - Unwanted Event Logs Detected | -| **Deprecated:** [Automate Server - Event Log Monitoring [Autofix]](/docs/f36b7367-99c7-478b-abc9-6802182431e4) | | Autofix Script | On-Prem | The purpose of the script is to send the information of the event logs detected by the "[ProVal - Development - Automate Server - Unwanted Event Logs Monitoring](/docs/88dfd269-1df7-4c57-a898-9445dec162b5)" monitor set.
The result sometimes crosses the character limit of 100 characters and hence, the script was needed for the alerting purpose. Also, this is not designed to send any notifications for the Success status of the monitor set. | -| **Deprecated:** △ Automate Server - Event Log Monitoring [Autofix] | | Alert Template | On-Prem | This alert template should be assigned to the [ProVal - Development - Automate Server - Unwanted Event Logs Monitoring](/docs/88dfd269-1df7-4c57-a898-9445dec162b5) monitor set. It will execute the [Automate Server - Event Log Monitoring [Autofix]](/docs/f36b7367-99c7-478b-abc9-6802182431e4) script to send the event log's information to [alerts@provaltech.com](mailto:alerts@provaltech.com) as an urgent ticket. | -| **Deprecated:** [Database size increased by 5%*[Global]](/docs/1e7111ed-fd09-4b58-bc4b-becb2dc3c8e0) | Medium | Script | Both | The ultimate goal of this script is to create a ticket in our (ProVal's) AutoTask portal if the overall size of the Labtech Database increases by 5% (threshold is flexible) within the last 24 hours (it depends on the frequency of the schedule).
Subject: Database size increased by @SizeToCompare@ Percent within the last @Hours@ Hour
e.g., Database size increased by 5 Percent within the last 24 Hour | -| **Deprecated:** [Volume Free Space - Monitor Creation - Automate Server Only](/docs/8b42e4f9-eb46-4058-b4f9-e0f1ea8840cd) | Medium | Script | On-Prem | This is an exact copy of the [CWM - Automate - Script - Volume Free Space - Monitor Creation](/docs/dee853b7-69a6-4f0d-ad2f-7238a10851f4) script with a few changes. The purpose here is to use the dynamic monitor generated by the [CWM - Automate - Script - Volume Free Space - Monitor Creation](/docs/dee853b7-69a6-4f0d-ad2f-7238a10851f4) script to monitor the Automate server's drives and to generate a ticket in our (ProVal's) Autotask portal for the failures. We would like to proactively monitor the drive and perform the basic actions (like removing some unnecessary files logs or folders ) to free up some space for our partners.
Subject: Volume Space - %FieldName%: (%ComputerName%-%Computerid%)
e.g, Volume Space - C: (CW-Computer-200) | -| **Deprecated:** [ConnectWise Manage Plugin Sync/Mapping Audit](/docs/474cb433-c577-450c-b214-e7fc6a1c73f3) | Medium | Script | Both | This script will send an email to [alerts@provaltech.com](mailto:alerts@provaltech.com) if it finds any necessary component as unsynced or unmapped in the CW Manage plugin. The Email will contain all the necessary details to act upon.
Alert Template: ***** use Default - Do Nothing for now until we have an opportunity to look further into these action items from this monitor.
Subject: Unmapped/Unsynced entity detected in CW Manage Plugin | \ No newline at end of file +| **Deprecated:** `△ Autofix - Ticket Sync Failed` | | Alert Template | Both | This alert template should be assigned to the `Ticket Sync Unsuccessful` monitor set. It will execute the `Ticket Sync Failed [Autofix, Globals]` script. | +| **Deprecated:** `Automate - Unsynced Ticket Content` | High | Internal Monitor | Both | The main objective of the monitor set is to alert the partners of any unsynced ticket comments for a ticket that has already been synchronized to CW Manage.
Alert Template: ~Custom Email RAWSQL Monitor set results to the Partner.
Subject: Ticket Comment Failed to Sync to Manage for %ExternalID% | +| **Deprecated:** `△ Email RAWSQL Monitor set results to the Partner` | | Alert Template | Both | This alert template should be assigned to the `Unsynced Ticket Content` monitor set. It will execute the `Email RAWSQL Monitor Set Failures* [Autofix]` script to send an email to the selected template contact/user. | +| **Deprecated:** `CW Manage Plugin Errors` | Medium | Internal Monitor | Both | The internal monitor is designed to notify [alerts@provaltech.com](mailto:alerts@provaltech.com) of any critical errors and issues with the ConnectWise Manage Plugin.
Alert Template: ***** use Default - Do Nothing for now until we have an opportunity to look further into these action items from this monitor.
Subject: CW Manage Plugin Errors Detected for %Result%
e.g., CW Manage Plugin Errors Detected for Contacts on 2022-08-09 | +| **Deprecated:** `~Custom Email RAWSQL Monitor set results to ProVal` | | Alert Template | Both | This alert template should be assigned to the `ProVal - Development - CW Manage Plugin Errors` and `ProVal - Development - Control - Broken Integration` monitor sets. It will execute the `Email RAWSQL Monitor Set Failures* [Autofix]` script to send an email to [Alerts@provaltech.com](mailto:Alerts@provaltech.com). | +| **Deprecated:** `Automate Server - Unwanted Event Logs Monitoring` | Medium | Remote Monitor | On-Prem | The purpose of this remote monitor is to generate an Urgent ticket in our (ProVal's) Halo PSA if an error or critical event from either of "DBAgent", "ASPWCC2", or "MySQL" event sources is generated more than 10 times within the past 60 minutes on Automate server.
Alert Template: ***** use Default - Do Nothing for now until we have an opportunity to look further into these action items from this monitor.
Subject: Urgent - Automate Server - Unwanted Event Logs Detected | +| **Deprecated:** `Automate Server - Event Log Monitoring [Autofix]` | | Autofix Script | On-Prem | The purpose of the script is to send the information of the event logs detected by the `Automate Server - Unwanted Event Logs Monitoring` monitor set.
The result sometimes crosses the character limit of 100 characters and hence, the script was needed for the alerting purpose. Also, this is not designed to send any notifications for the Success status of the monitor set. | +| **Deprecated:** `△ Automate Server - Event Log Monitoring [Autofix]` | | Alert Template | On-Prem | This alert template should be assigned to the `ProVal - Development - Automate Server - Unwanted Event Logs Monitoring` monitor set. It will execute the `Automate Server - Event Log Monitoring [Autofix]` script to send the event log's information to [alerts@provaltech.com](mailto:alerts@provaltech.com) as an urgent ticket. | +| **Deprecated:** `Database size increased by 5%*[Global]` | Medium | Script | Both | The ultimate goal of this script is to create a ticket in our (ProVal's) Halo PSA if the overall size of the Labtech Database increases by 5% (threshold is flexible) within the last 24 hours (it depends on the frequency of the schedule).
Subject: Database size increased by @SizeToCompare@ Percent within the last @Hours@ Hour
e.g., Database size increased by 5 Percent within the last 24 Hour | +| **Deprecated:** `Volume Free Space - Monitor Creation - Automate Server Only` | Medium | Script | On-Prem | This is an exact copy of the `Volume Free Space - Monitor Creation` script with a few changes. The purpose here is to use the dynamic monitor generated by the `CWM - Automate - Script - Volume Free Space - Monitor Creation script to monitor the Automate server's drives and to generate a ticket in our (ProVal's) Halo PSA for the failures. We would like to proactively monitor the drive and perform the basic actions (like removing some unnecessary files logs or folders ) to free up some space for our partners.
Subject: Volume Space - %FieldName%: (%ComputerName%-%Computerid%)
e.g, Volume Space - C: (CW-Computer-200) | +| **Deprecated:** `ConnectWise Manage Plugin Sync/Mapping Audit` | Medium | Script | Both | This script will send an email to [alerts@provaltech.com](mailto:alerts@provaltech.com) if it finds any necessary component as unsynced or unmapped in the CW Manage plugin. The Email will contain all the necessary details to act upon.
Alert Template: ***** use Default - Do Nothing for now until we have an opportunity to look further into these action items from this monitor.
Subject: Unmapped/Unsynced entity detected in CW Manage Plugin | \ No newline at end of file diff --git a/static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image1.webp b/static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image1.webp index 9ede986910..a85f1f44a8 100644 Binary files a/static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image1.webp and b/static/img/docs/9292f135-cca4-4eba-97ff-cd4276ab62e9/image1.webp differ