Date: Thu, 28 Mar 2024 13:36:22 +0000 (UTC) Message-ID: <1482570991.5379.1711632982849@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5378_253980546.1711632982845" ------=_Part_5378_253980546.1711632982845 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The current API implementation focuses on GET methods and end-us= er views, as well as actions on up.time Elements.
The following is a summary of presently available resources:
list all Elements and attached service mo= nitors; display an Element's information and attached service monitors; dis= play an Element's information and its current status:
GET
GET
GET
/api/v1/elements
/api/v1/elements
/{id}
/status
/{id}/api/v1/elements
update Element configuration:
PUT
/api/v1
/elements
/{id}
add, delete Element:
POST
DELETE
/api/v1/elements
<=
/p>
/api/v1/elements/{id}
list all service monitors; display a spec= ific server monitor; display status information for a service monitor:
GET
GET
GET
/api/v1/monitors
/api/v1/monitors
/{id}
/status
/{id}/api/v1/monitors
list all Element groups, member Elements,= and monitors; list an Element group's member Elements and monitors; displa= y the status of an Element group's member Elements and monitors:
GET
GET
GET
/api/v1/groups
/{=
id}/api/v1/groups
/status
/{id}/api/v1/groups