I attempted to copy the zoom template for similar products that use the same status page API, which half works.

This is my code, file name mitel.status.template:

{
  "prtg": {	
  
    "description" : {
      "device": "status.mitel.io",
      "query": "/api/v2/components.json",
      "comment": "Documentation is at https://status.mitel.io/api/v2"
    },
    "result": [
      {
        "Value":{ "["+ #1 +"]" + " Status": $.components..({ @.name : lookup(@.status, "operational") }).*},
		"ValueLookup": "mitel.status"
      }
		  ]
  }
}

This does label the channels, however it does not get the channel value. Instead it just returns "0 (configured lookup mitel.status is empty or not available)". I assumed this would work exactly the same as the Zoom template, but it looks like there might be some additional coding within PRTG that allows Zoom to work?

Article Comments

Hello,

Thank you for your message.

The result provided by the API contains components with the same name such as Billing, Authentication, Carrier, for each service called "CloudLink Services ()". PRTG can only create an unique channel for each of them.

Services


I'm afraid that the REST Custom sensor can't be used in that case (if you want to monitor the components of each CloudLink Services() ). However, you have the possibility to use a custom script with the EXE/Script Advanced sensor. Here is the documentation regarding custom sensors: https://www.paessler.com/manuals/prtg/custom_sensors#advanced_sensors.

Regards.


Jan, 2021 - Permalink