element_domain), not from the servers that answered, so a server that is down appears with config-server-reachable: no and null counts instead of vanishing or reading as empty. A server has 3 seconds to answer.config-server-out-of-sync-count counts the server's keys whose config-in-sync is no, including keys other servers lack; keys that are not-expected or unknown are left out, so a non-zero count is always worth a look. The serving server reports config-server-reachable: no when it cannot read its own table. An inventory entry that is not a valid hostname is listed as unreachable and never contacted. GET /appinfo lists the raw inventory instead.GET is answered.Authorization: Bearer ********************curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/nmsconfig/servers' \
--header 'Authorization: Bearer <token>'[
{
"config-server": "core1.example.com",
"config-server-local": "yes",
"config-server-reachable": "yes",
"config-server-config-count": 412,
"config-server-out-of-sync-count": 1
},
{
"config-server": "core2.example.com",
"config-server-local": "no",
"config-server-reachable": "yes",
"config-server-config-count": 412,
"config-server-out-of-sync-count": 1
},
{
"config-server": "core3.example.com",
"config-server-local": "no",
"config-server-reachable": "no",
"config-server-config-count": null,
"config-server-out-of-sync-count": null
}
]