Opsview 6.8.x End of Support
With the release of Opsview 6.11.0 on February 2025, versions 6.8.x have reached their End of Support (EOS) status, according to our Support policy. This means that versions 6.8.x will no longer receive code fixes or security updates.
The documentation for version 6.8.9 and earlier versions will remain accessible for the time being, but it will no longer be updated or receive backports. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.
Runtime - Monitoring Clusters
This section is for searching for live objects being monitored by Opsview. This is in the Runtime database, hence the URL path is /rest/runtime/{objecttype}.
URL: /rest/runtime/monitoringcluster.
Requires authentication - requires VIEWALL or VIEWSOME permission.
GET— returns monitoring clusters.POST,PUT,DELETE— not implemented.
Access Control Copied
- VIEWALL allows all monitoring clusters to be returned.
- VIEWSOME only lists monitoring clusters that are associated to objects where permission has been granted based on the access object selection.
Retrieving Monitoring Clusters Copied
Response:
list— an array of the results.
Where list is an associative array of the results, consisting of:
id— ID number of the monitoring cluster. id=1 means it is the primary cluster.name— Name of the monitoring cluster.activated— Either 0 or 1.
Example response:
{
"list": [
{
"activated": "1",
"id": 1,
"name": "Master Monitoring Server",
"passive": "0" // Unused
},
{
"activated": "1",
"id": 2,
"name": "ClusterA",
"passive": "0"
},
{
"activated": "1",
"id": 3,
"name": "Cluster",
}
],
}