July 2, 2015

Mini Post: 20 More Pulseway Alerts with PowerShell

Posted on July 2, 2015  •  2 minutes  • 407 words

The Pitch

In my last post I showed how you could extend the possible alerts generated by Pulseway with PowerShell and Windows' Event Log.

The example used, checking to see if a disk was present within the operating system, was just the tip of the iceberg (and rather mundane.)

In this mini post I’ll list 20 more ideas for PowerShell fuelled Pulseway alerts.

Disclaimer from last post: Be careful about over saturating yourself with notifications. Set the appropriate notification level based on your needs and those of the business. If you’re getting flooded with alerts you could become desensitized to the really important ones.


  1. A new account has been added to the local administrators group!
  2. A new local account has been created!
  3. You have redundant internet links - and use BGP to keep services up - you’re running on your slower backup link!
  4. One of your contractors has just logged onto a server! (But you don’t want notifications about staff logging into a server.)
  5. Someone just installed the GUI onto your beautiful Server Core box!
  6. Your external IP Address changed! (great for you home PC…)
  7. New post on an RSS feed!
  8. Your favorite website has been down for five minutes!
  9. Your wireless mouse’s battery is running low/flat!
  10. An update is available for your favorite text editor!
  11. A game on your Steam wishlist is on sale!
  12. Active Directory FSMO role holder has changed!
  13. You forgot to change your password and now your account is locked out! (Better to alert that password is expiring that day, but this is funnier.)
  14. A physical network interface in a Windows NIC Teaming interface has failed!
  15. Someone turned Windows Firewall off on a server!
  16. A new wireless SSID is being broadcast! (assuming monitored PC has a wireless interface.)
  17. … And it’s an open/insecure wireless network!
  18. Your Pester test cases failed! (Assuming you have so many that they take a while, our you just have some that take a while to complete.)
  19. You save a PowerShell script an hour ago but didn’t push it to your repo!
  20. You haven’t blogged in over a month, maybe you should get on that…

Closing Notes

As you can see you can literally alert on anything as long as PowerShell can get it’s hooks into it.

If you want to see any of these ideas fleshed out into a real script (and don’t know how to go about it yourself), let me know in the comments.

comments powered by Disqus
Follow me