I use Cisco Webex for video conferencing, meetings, etc. How can I monitor this with PRTG?
Created on Apr 20, 2020 12:46:03 PM by
How can I monitor Cisco Webex with PRTG?
Votes:
0
20 Replies
Accepted Answer
Votes:
0
This article applies as of PRTG 20
Monitoring Cisco Webex with PRTG
With PRTG, you can monitor Cisco Webex out of the box with the EXE/Script Advanced sensor. You can use this sensor to monitor the status of Webex meetings and Webex calling, for example. Among others, the sensor can show the following:
- Webex Meetings status
- Webex Messenger status
- Webex Control Hub status
- Webex Teams status
- UCM Cloud status
For an overview of all Webex services and their status, see the Webex service status page.
Download, extract, and copy the files
You can download the .zip file here. Extract the files and then copy the files as follows:
- Copy the PowerShell script file cisco_webex.ps1 into the Custom Sensors\EXEXML subfolder of the PRTG program directory on the probe system that you will execute the file on.
- Copy the lookup file cisco.webex.status.ovl into the lookups\custom subfolder of the PRTG program directory on the PRTG core server system.
Optional: The .zip file also includes a device icon for your Cisco Webex device. For more information on custom device icons, see How can I add my own device icons for use in the PRTG web interface?
Note: If necessary, (re)load the files by clicking the Go! button in the PRTG web interface under Setup | System Administration | Administrative Tools, section Load Lookups and File Lists.
Create an EXE/Script Advanced sensor
- Create a device on the probe system that you will execute the file on. For IPv4 Address/DNS Name, enter service-status.webex.com.
- Optional: For Device Icon, select the Cisco icon.
- Add an EXE/Script Advanced sensor to the device.
- In the sensor settings, set the following:
- For Sensor Name, enter a name to identify the sensor, such as Cisco Webex Status.
- For EXE/Script, select cisco_webex.ps1 from the dropdown list.
- For Parameters, enter -ValueLookup cisco.webex.status.
- For Scanning Interval, select 10 minutes from the dropdown list.
Note: To avoid overloading the API, we recommend that you do not use a shorter scanning interval.
- Click Create to save your settings and to create the sensor.
You can now monitor the availability of your Cisco Webex services.
More
Created on Apr 20, 2020 12:58:00 PM by
Last change on Jan 9, 2023 7:43:07 AM by
Votes:
0
Hello,
that can't be done with configuring PRTG, because the sensor queries the target and converts the results into channels. PRTG is optimized to monitor traffic and device statuses, the sensor architecture currently does not support large result tables.
The approach would be to do the query via script, for example with Powershell, and splitting the results into smaller parts which are then parsed. This is not trivial to implement.
Created on Jul 15, 2020 7:45:35 PM by
Votes:
0
Hello fbourassa,
we currently work on a new template which hopefully helps to keep the channel count below 50. There is no release date yet, I estimate it takes a couple of days.
Created on Jul 21, 2020 1:39:32 PM by
Votes:
1
Hello,
it is still in progress, but I wanted to let you know that we think we can offer a new template which works better. The article will be updated when it is available.
Created on Aug 3, 2020 12:45:59 PM by
Votes:
0
Hello,
As Cisco added additional services and changed the JSON query, it was necessary to create a PowerShell script instead. The new sensor will only show the main services and not the subservices to avoid performance issues.
Created on Aug 26, 2020 1:49:29 PM by
Votes:
0
Hello,
You can download the archive via the link provided in the first response above, under "Download, extract, and copy the files".
Best regards
Created on Aug 28, 2020 11:53:37 AM by
Last change on Aug 28, 2020 11:54:04 AM by
Votes:
0
Hallo guenter,
haben sie vorher schon den Rest Custom Sensor um Cisco Webex zu monitoren, verwendet?
Falls ja, löschen sie bitte die Lookup Datei cisco.webex.status.ovl aus dem Custom Lookup Ordner (lookups\custom) und kopieren diese Datei aus dem entpackten Cisco_Webex wieder in den Custom Lookup Ordner. Diese Datei hat sich obwohl der Name gleich geblieben ist geändert und ist daher nicht mit dem PowerShell Script kompatibel.
Falls der Fehler weiterhin besteht, aktivieren Sie in den Sensor Einstellungen die Option Write Sensor Result to Disk. Bitte warten Sie anschließend mindestens ein Scanning Interval des Sensors ab. Sie erhalten dann im Ordner C:\ProgramData\Paessler\PRTG Network Monitor\Logs\sensors\ entsprechende Debugging-Dateien in der Form Result of Sensor [ID].txt ([ID] ist hierbei die ID des Sensors). Diese Dateien enthalten dann die Rückgabe des Skripts, bzw. entsprechende Fehlermeldungen die bei der Ausführung des Skripts oder der Verarbeitung des Ergebnis aufgetreten sind. Diese Dateien schicken Sie bitte per Mail an [email protected].
Created on Aug 31, 2020 10:48:23 AM by
Last change on May 11, 2022 11:25:26 AM by
Votes:
0
Hello,
Thank you very much for your message.
This error comes from Windows which blocks the file for security reason. You can unblock it by checking the corresponding box in the Properties menu of the file like on the following screenshot:
In case it doesn't fix the issue, please check the Execution Policy by executing the command Get-ExecutionPolicy in a PowerShell console.
Created on Sep 22, 2020 11:50:46 AM by
Votes:
0
After configuring the device and sensor as descriped I'm receiving an proxy authentication error.
"The remote server returned an error: (407) Proxy Authentication Required. at line : At C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\cisco_webex.ps1:16 char:17 + $response = Invoke-RestMethod $script:url | select -expand compon"
Other internet probes are working fine, I also tried configuring a proxy with valid user credentials under Setup > System Administration > Core & Probes
What can I do to solve this?
Votes:
0
Hello,
Thank you for your message.
As the monitoring of Cisco WebEx is done via a script, I'm afraid that configuring the proxy inside PRTG can't fix the issue.
You have to configure the proxy directly in the script at line 16 for the PS cmdlet Invoke-RestMethod. To do so, please have a look to the documentation of the cmdlet here: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/invoke-restmethod?view=powershell-7.1
Regards.
Created on Feb 24, 2021 6:36:47 AM by
Votes:
0
Hello,
If you copied over the custom lookup files from the zip file ("cisco.webex.status.ovl") to "C:\Program Files (x86)\PRTG Network Monitor\lookups\custom" and it's still showing this error.
Go to "Setup" > "System Administration" > "Administrative Tools" and click "Go!" in the box for "Load Lookups and File Lists" to reload the lookup files.
In my test after another scan period everything was as expected, if it still isn't: either try to recreate the sensor or check in the channel settings if the correct lookup is selected and adjust accordingly.
Kind regards,
Johannes Beyerlein, Technical Support Team
Created on Feb 6, 2023 3:28:37 PM by
Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Add comment