The Daunting Task of Getting Notified in Time

Just about all companies—no matter size or industry they are in— depend highly on having a trustworthy, working monitoring solution. When IT equipment fails, you need to be sure that you can get things back online quickly and without any loss. It’s a tough lesson when you discover that restoring important company services is impossible. The failing system may have been trying to notify you, but somehow, that vital information wasn’t somewhere that you noticed its broken state in time.

Windows PowerShell and Panorama9 Custom Issues

PowerShell scripts are a great solution when you need to look for errors that require your attention. They can free you from the repetitive tasks of opening, inspecting, and filtering things such as logs on multiple servers.

Get notifications in your monitoring platformIn combination with Panorama9’s Custom Issues, you can automate tasks and be notified when things go awry. Then, you’ll retrieve only needed information and instantly know through Panorama9’s streamlined notification system that an issue requires your attention. You don’t need to worry about mail settings, help desk ticket creation, or spamming yourself about an issue again and again. Panorama9 will handle it for you. You just need to decide which problems should result in a notification and who should get notifications.

Start the P9 Custom Issue executable from PowerShell

The Panorama9 Custom Issue executable “p9-issue.exe” is installed with the P9 agent for Windows. You find the executable in the folder:

C:\%programfiles(x86)%\Panorama9

You start “p9-issue.exe” from PowerShell using the Start-Process command. When your script detects an issue, you can report it to Panorama9 using:

Start-Process -FilePath "C:\%programfiles(x86)%\Panorama9\p9-issue.exe" -ArgumentList " --type="custom-availability" --id="UNIQE_ID" --text="Ouch, broken state" --desc="A bad thing has happened" --ttl="24"" -Wait -Passthru -ErrorAction SilentlyContinue

You need to adjust the “-ArgumentList” option to include information about the detected issue. Your script doesn’t need to know if it has already reported the issue. You can report the same issue repeatedly, but Panorama9 will only notify you once.

When the issue has been fixed, you can use the P9 executable to report the resolved state. If not, the issue will automatically be considered as resolved once TTL expires.

For more information about using Panorama9 Custom Issues and command line arguments, click here.

Fresh Tips Directly in Your Inbox

Submit your email address below and get our updates on the most important things MSPs should know.

Leave a Reply

Your email address will not be published. Required fields are marked *