Jump to content

Search the Community

Showing results for tags 'internal monitor'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • MSPGeek
    • The Geek Cast
    • Code of Conduct
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development


  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me


Agent Count













Found 12 results

  1. Hello, We copied and modified an internal monitor for free space alerting and we're looking to add another condition to look for 'online' computers only. This is what we currently have in the 'Additional Condition' field: Drives.Size > 20480 and Drives.FileSystem not in ('ERR','CDFS','UNKFS','DVDFS','FAT','FAT32','NetFS') and Drives.free < 4096 and Drives.internal=1 and Drives.Missing !=1 and Drives.Model not like '%USB%' Would we need to add another AND condition at the end of the above like this?: and Computers.Uptime >= 0 AND DATE_ADD(Computers.LastContact, INTERVA
  2. Hello, I've used Automate for several years, and have dabbled with scripts and monitors, but need a little help. I'd like to create an internal monitor to measure a server's up-time and then create a ticket to flag it to be rebooted manually if it exceeds the threshold.
  3. Hi there, I know this subject has been talked about in the past but I was not able to lookup anything interesting for my needs. Actually, I would need to create an internal monitor that would warn me whenever we are close to reaching our max allowed agents. I know for sure there is no way to query how many agents we are allowed to deploy according to our plan, but it doesn't really matter since this info would be set manually in the script/internal monitor. What I need is to query the LTServer database and somehow return the total number of deployed agents. This info can easily
  4. Once a role has been detected for an agent, it will remain in the list of roles for that system even if the detection rule no longer applies. There are no timestamps, so it is impossible to know if the non-detection state is short term or permanent. This Internal Monitor will identify every inactive role on an agent, which adds a separate active alert for that role on the agent with a timestamp for when the role was first found missing. The RAWSQL monitor is three queries in one. The first one checks for any role that was reported missing more than 7 days ago, and deletes the role from the age
  5. Thanks to WNichols for the idea. An Internal Monitor to detect hardwired connections that are not operating at Gigabit speeds. Because who still uses Fast Ethernet? To help reduce noise, only agents that are at their assigned location network (Agent public Router IP matches Location Router IP). Virtual Adapters, WiFi adapters, etc. are ignored. I restricted the monitor to only consider the primary NIC (the NIC with the IP Address matching the agents LocalAddress). I like these types of monitors myself not so much for creating tickets/work, but to organize this information in a way that I
  6. This monitor identifies the current agent version for OSX, Linux and Windows Agents. Each hour the monitor checks for agents that are not at the current version, and issues the Agent Update command to a small batch of online agents. It will only issue the command once per day for any particular agent, and only if there are no pending/executing update commands already in the queue. This has been moved to the File Download section. You can download it here: https://www.mspgeek.com/files/file/45-cwa-agent-version-update-monitor/
  7. Hello, we're looking for a way to take different actions based on how many results show up in the monitor that calls this script. To be more specific, we want to execute a SQL stored proc if there are fewer than 10 results, and if there are more than 10, we want to send an alert email. The way I understand it, though, when you call a script based on the results of an internal monitor, the script simply receives one row at a time and executes based on the data in that row, rather than receiving all of the rows at once and running on each one in a loop. Am I understanding this correctly,
  8. Hello All, Is it possible to pass %FIELDNAME% from a monitor to a script? Example would be - low disk internal monitor. It uses %FIELDNAME% to represent the drive letter that is throwing the alert. If I allow the monitor itself to create the ticket, this variable works. If I have the monitor run a script, the %FIELDNAME% variable does not function within the script. Any ideas? Thank you! Arthur
  9. Hi All, Spent a lot of time working this one out but believe I have it, in case anyone else wants it. The below Internal Monitor has to be RAWSQL and it will return a list of all computers that have had over 500 'Failed Logins' (defined by the event ID's of the pre-built Internal Monitor) in a 1 day period Create Temporary Table IF NOT EXISTS Tcomp (INDEX (Computerid)) SELECT computerid FROM computers WHERE ComputerID NOT IN (Select ComputerID from AgentIgnore Where AgentID=4114); Select DISTINCT computers.computerid as TestValue,eventlogs.Message as IdentityField,computers.com
  10. This monitor will identify (16gb minimum) drives that have grown or shrunk. This can be used to generate a ticket if backup software will need settings adjusted after the drive size was changed. By default this monitor should raise an alert for any disks identified. Import in Control Center -> Tools -> Import -> SQL File. A monitor named "Detect Drive Size Change" will be created. MONITOR - Detect Drive Size Change.zip
  11. I thought this one of mine was worth sharing, especially helpful if you need a method of mass generating alerts/tickets/warnings for clients running Office 2007 or earlier. https://gavsto.com/internal-monitor-rawsql-machines-running-office-2007-v12-or-earlier/ Instructions and download above!
  12. This query can be used as an Additional Condition for an Internal Monitor, or merged with other queries. It attempts to identify computers that are "at their home" by looking at their public IP. It determines what the public IP should be for each location by selecting the probe for each location, and domain controllers in each location. If the computer's public IP matches with the probe's public IP, the computer is considered to be at it's assigned location. If this does not match, it will check the public IP for DC's at that location. If the computer's public IP matches with a Dom
  • Create New...