The Operations dashboard is a unified view of several aspects of Control Hub. In the background, your browser is pulling from a couple different Control Hub applications, primary notification and jobrunner. The REST API would have to be utilized and filtered to retrieve this information. For example, the following endpoints were utilized during the loading of the dashboard (from my view):
https://[hostname]/notification/rest/v1/alerts?offset=0&len=250
https://[hostname]/notification/rest/v1/alerts?offset=0&len=250&alertStatus=ACKNOWLEDGED
https://[hostname]/jobrunner/rest/v1/jobs/byStatus?offset=0&len=1&jobStatus=ACTIVE&withWrapper=true
https://[hostname]/jobrunner/rest/v1/jobs?offset=0&len=1&withWrapper=true&jobStatusColor=RED
https://[hostname]/jobrunner/rest/v1/sdcs?offset=0&len=250&executorType=COLLECTOR
https://[hostname]/jobrunner/rest/v1/sdcs?offset=0&len=250&executorType=TRANSFORMER
https://[hostname]/jobrunner/rest/v1/sdcs?offset=0&len=250&executorType=EDGE
https://[hostname]/jobrunner/rest/v1/jobs?offset=0&len=5&order=DESC&withWrapper=true&jobStatusColor=RED
To use this information, the information would have to be pulled and the JSON filtered from these endpoints. The client pulling the information would also have to account for paging in the event the alerts/engines/etc are greater than the length specified in the URL. A UI would then need to be created using a tool of your choice.
The recommendation would be to use the Operations dashboard as more of a guide in order to have an idea of what type of information you would like to populate your personal dashboard with.
(Users can find API calls via the UI -> Question mark icon (in the right upper corner) -> RESTful API. )
