|
|
| Subject: | getZenProperties, getZenProperty... Where did it go? |
| Author: | [Not Specified] |
| Posted: | 2015-06-22 10:11 |
This works on 4x:
curl -k -u user:pw -X POST -H 'Content-Type: application/json' -d '{"action":"DeviceRouter","method":"getZenProperty","data":[{"zProperty":"cLatitude","uid":"/zport/dmd/Devices/Ping/devices/10.4.0.129"}], "tid":1}' https://zenoss/zport/dmd/device_router
But on 5x I get:
DirectException: 'getZenProperty' is not the name of a method on DeviceRouter
And even this if I change methods:
DirectException: 'getZenProperties' is not the name of a method on DeviceRouter
So, where did it go This is essential for me so any help will be truly appreciated.
| Subject: | Looks like there is a new |
| Author: | [Not Specified] |
| Posted: | 2015-06-22 13:24 |
Looks like there is a new router called PropertiesRouter.
| Subject: | My friend, you are a |
| Author: | [Not Specified] |
| Posted: | 2015-06-22 16:51 |
My friend, you are a lifesaver
curl -k -u user:pw -X POST -H 'Content-Type: application/json' -d '{"action":"PropertiesRouter","method":"getZenProperty","data":[{"zProperty":"cLatitude","uid":"/zport/dmd/Devices/Ping/devices/10.4.0.129"}], "tid":1}' https://zenoss/zport/dmd/properties_router
{"uuid": "4477e42c-e44c-4af3-9ff9-e068affe28b3", "action": "PropertiesRouter", "result": {"data": {"path": "/Ping/devices/10.4.0.129", "type": "float", "options": [], "value": -22.5449637981382, "valueAsString": -22.5449637981382}, "success": true}, "tid": 1, "type": "rpc", "method": "getZenProperty"}
Mind if I ask you where did you get this information I looked everywhere...
| Subject: | Looked through the source. |
| Author: | [Not Specified] |
| Posted: | 2015-06-23 06:54 |
Looked through the source. /opt/zenoss/Products/Zuul/routers .. then grep getZenProperty *.py :-)
| Subject: | Haha... I guess Google is |
| Author: | [Not Specified] |
| Posted: | 2015-06-23 08:55 |
Haha... I guess Google is overrated :) Thanks.
| < |
Previous MetricShipper missing some health checks |
Next Zenoss Core 5 High Availability Cluster |
> |