Availability Monitoring for your Computer Monitor the websites within your community (office or broader public community) to know that the services you rely upon are available when you need them. You can make a request which is just the website to know that the website is up. You can query a function which reaches back into a website application and database in order to ensure that the deeper application is available and working. Monitor for files that should be in a location or that should not be there. In this way you can know, good or bad, the presence of action needs for files. Monitor for machines by Ping, RDP, SMB, HTML, WINRM or other port availability to know that portions of access and interface are operating as expected. Monitor Services and Processes on your localhost computer in order to see that processes you need or want are in place and working. You can look to ensure that the numbers of these processes has also not ballooned to point which affect your performance or are suspicious and be warned when this is the case. You can also look for impersonation processes and sevices that you don't want.
AVLMonitor is a multi-level monitoring tool to detect active availability. This can be of good websites, machines, files, services or processes or bad ones. Run manually, from shortcuts or through a scheduled task this process uses CSV based monitoring lists to target objects of interest within your community, environment and machine. If no arguements are provided to this process then the user is prompted to indicate the type of responses requested and the monitoring list to use.
As a starting CPI/CSI tool this is a great start and has the flexibility to expand as you learn. You can look for a website like weather.gc.ca or the weather application by calling https://weather.gc.ca/city/pages/on-118_metric_e.html. You can look for a gateway 10.0.0.1 PING to ensure it is still up and responding, you can see if a file like badfile.png is in the roaming area or you an look for too many instances of powershell running (Note to run the task it will be at least 1 instance of powershell*). If you have an Active directory failure you can make you debugging easier in the future if you include these components (machines, ports, services) into your review so you can spot this quickly, if they go down again. You can even bundle these very detailed debugging profiles into separate monitor lists and leave just a couple of key peices in the generally run review.
Optionally arguement1 indicates either a HEARTBEAT review in which all tests and states will be passed along to a notification list, or a PERIODCHECK which will do all tests but only provide notification if a Negative result is determined (negative state of a positive expectation or a positive state of a negative expectation i.e., website not responding like it should or a bad service detected).
Optionally arguement2 indicates if a non-default MonitorList.csv file is to be used for the review. Any monitoring list can have any number of targets of any of the types supported. Specific lists might be useful for detailed failure evaluation that is more detailed and extensive than for regular monitoring. It alos allows for different timing considerations of evaluation between lists.
Optionally areguement 3 is to provide a time delay in a run. Without the parameter the time delay is 0 seconds and so is "Now". This parameter is typically an integer from 1 to N and represents hours within which this process will run once. If a process would typically run once a week then this could be a value up to 168. A random number of seconds will be determined within the range of 5 to (N*60*60)-600 seconds.
Set-up as either ShortCut or within a Scheduled Task the following clips can be used: %systemroot%\System32\WindowsPowerShell\v1.0\powershell.exe -executionpolicy Bypass -Windowstyle Hidden -file "c:\users\owner\documents\winpwrshlPractice\opsTestURLS\AVLmanyForms.ps1" HEARTBEAT. Scheduled once a day this provides a regular pulse that this machine is running and ir profile is working well. PERIODCHECK can be set from 4 to 47 times per day providing a high degree of Community checking and providing notification when something is amiss. %systemroot%\System32\WindowsPowerShell\v1.0\powershell.exe -executionpolicy Bypass -WindowStyle Hidden -file "c:\users\owner\documents\winpwrshlPractice\opsTestURLS\AVLmanyForms.ps1" PERIODCHECK MonitorList.csv. In the example is the specification of the Monitoring list file which can be substituted as your situation dictates. You may have a Master, and Heartbeat subset, a PeriodCheck subset, and exchange debugging subset, an Active Directory services subset or whatever your environment experience includes.