New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


How can I monitor Cisco Webex with PRTG?

Votes:

0

Your Vote:

Up

Down

I use Cisco Webex for video conferencing, meetings, etc. How can I monitor this with PRTG?

cisco prtg rest-custom video webex

Created on Apr 20, 2020 12:46:03 PM by  Brandy Greger [Paessler Support]



15 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

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 meaningful name 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.

Cisco Webex Status sensor settings
Click to enlarge.

  • Click Create to save your settings and to create the sensor.

Cisco Webex Status sensor overview
Click to enlarge.

You can now monitor the availability of your Cisco Webex services.

More

Created on Apr 20, 2020 12:58:00 PM by  Brandy Greger [Paessler Support]

Last change on Aug 26, 2020 9:35:52 AM by  Jochen Greger [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Good morning! I ran into the issue that our Channel limit 50 exceeded after a few months of having this sensor. I have been trying to see where I can adjust this however I can't seem to pinpoint it. Would you be able to point me in the right direction to resolve this issue perhaps?

Thank you :)

Created on Jul 15, 2020 4:03:03 PM by  fbourassa (0)



Votes:

0

Your Vote:

Up

Down

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  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Would be interested in the updated template, too. Please let us know if it's available.

Created on Jul 31, 2020 1:32:40 PM by  u19 (0)



Votes:

1

Your Vote:

Up

Down

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  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

New template soon? We'd love to add this to our monitoring dashboard.

Created on Aug 25, 2020 2:21:41 PM by  Network Services (149) 3 1



Votes:

0

Your Vote:

Up

Down

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  Jochen Greger [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks, but how do we get this new sensor or Powershell-Script?

Created on Aug 28, 2020 10:44:08 AM by  u19 (0)



Votes:

0

Your Vote:

Up

Down

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  Florian Lesage [Paessler Support]

Last change on Aug 28, 2020 11:54:04 AM by  Florian Lesage [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Sorry, didn't realize the updated instructions and the availabilty of the files... It's working. Appreciate your work, helpful sensor. Thanks!

Created on Aug 28, 2020 1:53:43 PM by  u19 (0)



Votes:

0

Your Vote:

Up

Down

Ich erhalte folgende Fehlermeldung:

XML: Das zurückgelieferte XML entspricht nicht dem erwarteten Schema. (Code: PE233) -- JSON: Das zurückgelieferte JSON entspricht nicht der erwarteten Struktur (Invalid JSON.). (Code: PE231)

Created on Aug 31, 2020 7:45:47 AM by  guenter (190) 1 1



Votes:

0

Your Vote:

Up

Down

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]. Als Betreff nutzen Sie bitte PAE2018977, damit die Mail zugeordnet werden kann.

Created on Aug 31, 2020 10:48:23 AM by  Jochen Greger [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I'm getting the same error as Guenter. I downloaded the zip files from the link today.

XML: The returned XML does not match the expected schema. (code: PE233) -- JSON: The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231)

this is the sensor error log

& : File D:\Program Files (x86)\custom sensors\EXEXML\cisco_webex.ps1 cannot be loaded. The file D:\Program Files (x86)\custom sensors\EXEXML\cisco_webex.ps1 is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170. At line:1 char:138 + ... l.Utility};&'D:\Program Files (x86)\custom sensors\EXEXML\cisco_webex ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : SecurityError: (:) [], PSSecurityException + FullyQualifiedErrorId : UnauthorizedAccess

Is there an easy fix for this?

Created on Sep 22, 2020 9:35:18 AM by  David O'Connor (0) 1



Votes:

0

Your Vote:

Up

Down

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:

Image description

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  Florian Lesage [Paessler Support]



Please log in or register to enter your reply.


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.