Forum Discussion
Hello Satoshi,
Thank you very much for you're detailled answer.
I tested your solution and it looks great when I work on monitors hosted on the Common partition, but when I try on monitors hosted on user defined partitions it fails :
curl -sku admin:password https://10.200.2.92/mgmt/tm/ltm/monitor/https/~PART1~https_1_0_443/stats?ver=12.1.3 | python -m json.tool
{
"apiError": 1,
"code": 404,
"errorStack": [],
"message": "Object not found - /PART1/https_1_0_443"
}
Am I doing it the right way ? Is there any workaround ?
PS : The object /PART1/https_1_0_443 actually exists
Yes, I am experiencing the same issue.
A GET request to
https://f5.intern/mgmt/tm/ltm/monitor/gateway-icmp/~Common~gateway_icmp/stats
triggers the expected response (containing the "apiRawValues" field).
However, a GET request to
https://f5.intern/mgmt/tm/ltm/monitor/http/~PART1~http_mon_1/stats
triggers 404 Object not found.
On the other hand a monitor in a custom partition, wrapped in an iApp works as expected. A GET request to
https://f5.intern/mgmt/tm/ltm/monitor/http/~PART1~MYAPP.app~MYAPP_http_mon_2/stats
triggers the expected response (containing the "apiRawValues" field).
This is a really strange behavior, whereas I would be very interested in a workaround other than using an iApp.