What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Sensor REST Custom v2 can't handle one of 3 values

Votes:

0

Hi all,

I am using REST Custom v2 Sensor. This is my json response:

{

  "value": {

    "162.GlobalValue.DigitalOut7": 1700000.0,

    "162.GlobalValue.Comparator5C": 0.0,

    "162.GlobalValue.Input19": 1157698.0

  },

  "time": {

    "162.GlobalValue.DigitalOut7": 1643791373825000000,

    "162.GlobalValue.Comparator5C": 1643791373825000000,

    "162.GlobalValue.Input19": 1643791373825000000

  },

  "valueType": {}

}

The sensor works with all values except $.value["162.GlobalValue.Input19"]".

The sensor says:
Unparseable value in channel 1. The queried field "$.value["162.GlobalValue.Input19"]" is empty.

Rest Sensor V1 has no problems with my json. I know the V2 sensor is beta but I really like its features and want to use it.

Any ideas?

json prtg rest

Created on Feb 2, 2022 8:48:12 AM

Last change on Feb 2, 2022 12:04:02 PM by Felix Wiesneth [Paessler Support]



1 Reply

Votes:

0

Hey,

If you want us to take a closer look at this, I would ask you to open a Support Case. That way we can check this in more detail and ask for additional logs.

Kind regards,
Birk Guttmann, Tech Support Team

Created on Feb 16, 2022 2:55:56 PM by Birk Guttmann [Paessler Support]




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.