DDS-UI dashboards - Revision history

JoC: /* Schedules Tasks */

2021-02-09T06:55:50Z

Schedules Tasks

← Older revision		Revision as of 06:55, 9 February 2021
Line 157:		Line 157:
	[[File:SFTP Reader dashboard.png\|border\|800x800px]]		[[File:SFTP Reader dashboard.png\|border\|800x800px]]

	== ~~Schedules~~ Tasks ==		== Scheduled Tasks ==
	The Scheduled Tasks page is a general-purpose dashboard for monitoring any regular/repeating tasks or processes performed to support the DDS processing, but not directly part of the processing pipeline itself.		The Scheduled Tasks page is a general-purpose dashboard for monitoring any regular/repeating tasks or processes performed to support the DDS processing, but not directly part of the processing pipeline itself.

JoC at 12:33, 4 February 2021

2021-02-04T12:33:16Z

← Older revision		Revision as of 12:33, 4 February 2021
Line 1:		Line 1:
	This section explains the internal dashboards used to monitor data flows in to and out of DDS. ~~These~~ dashboards have been built into an application called DDS-UI which, in addition to ~~these~~ dashboards, provides many back-end DDS management utilities, such as those for setting up new publisher feeds.		This section explains the internal dashboards used to monitor data flows in to and out of DDS. The dashboards have been built into an application called DDS-UI which, in addition to the dashboards, provides many back-end DDS management utilities, such as those for setting up new publisher feeds.
	__TOC__		__TOC__

JoC: JoC moved page Monitoring and alerting to DDS-UI dashboards without leaving a redirect

2021-02-04T12:06:41Z

JoC moved page Monitoring and alerting to DDS-UI dashboards without leaving a redirect

← Older revision	Revision as of 12:06, 4 February 2021
(No difference)

JoC at 12:03, 4 February 2021

2021-02-04T12:03:19Z

@@ Line 124: / Line 124: @@
 == Frailty API ==
-The Frailty API page specifically displays running statistics on the DDS Frailty API.
+The Frailty API page specifically displays running statistics on the DDS Frailty API. <br />[[File:Frailty API.png|700x700px]]
 <br />
 == HL7 Receiver ==
 == SFTP Reader ==
 == Schedules Tasks ==
 == Exceptions ==
-<br />
+There are a number of aspects of the DDS pipeline that are not monitored with dashboards in the DDS-UI application.

JoC at 11:38, 4 February 2021

2021-02-04T11:38:53Z

← Older revision		Revision as of 11:38, 4 February 2021
Line 115:		Line 115:
	Clicking on a specific subscriber feed will display a detailed view, showing details about each publisher to that subscriber.<br />[[File:Subscriber dashboard2.png\|border\|700x700px]]		Clicking on a specific subscriber feed will display a detailed view, showing details about each publisher to that subscriber.<br />[[File:Subscriber dashboard2.png\|border\|700x700px]]
	== Queue Readers ==		== Queue Readers ==
			The Queue Readers page shows detail on the RabbitMQ queues and Queue Reader applications that are responsible for the inbound and outbound processing. Although it does not directly monitor the Information Model or UPRN APIs, these APIs are indirectly monitored due to the Queue Readers dependency on them – any issues with the API would be evident on this page.

			[[File:Subscribers.png]]

			Unlike the previous dashboards, this page is not oriented around DDS publishers or subscribers, but around the applications themselves. The page a grid of cells, with each cell representing a queue and Queue Reader application. The dashboard shows a clear warning if any queue is not being served by an application, for example if the application crashed or was not started, and also provides a view of current activity within the queues and Queue Readers.

			[[File:Queue Reader dashboard.png\|border\|700x700px]]

	== Frailty API ==		== Frailty API ==
			The Frailty API page specifically displays running statistics on the DDS Frailty API.
			<br />
	== HL7 Receiver ==		== HL7 Receiver ==

JoC at 16:54, 3 February 2021

2021-02-03T16:54:40Z

← Older revision		Revision as of 16:54, 3 February 2021
Line 106:		Line 106:
	== Subscribers ==		== Subscribers ==
	The Subscribers page provides a summary view of both inbound (raw to FHIR store) and outbound (FHIR to subscriber CSV format) processing. Although it does not directly monitor the Information Model or UPRN APIs, these APIs are indirectly monitored due to the Queue Readers dependency on them – any issues with the API would be evident on this page.		The Subscribers page provides a summary view of both inbound (raw to FHIR store) and outbound (FHIR to subscriber CSV format) processing. Although it does not directly monitor the Information Model or UPRN APIs, these APIs are indirectly monitored due to the Queue Readers dependency on them – any issues with the API would be evident on this page.
	<br />
			[[File:Subscribers.png\|border]]

			Each separate subscriber feed is represented as a row, with various counts to show the progress/state of the published data for that subscriber. Any feed with publishers in error, or with significant delays in processing (either inbound or outbound) are highlighted with clear warning labels.

			[[File:Subscriber dashboard.png\|border\|700x700px]]

			Clicking on a specific subscriber feed will display a detailed view, showing details about each publisher to that subscriber.<br />[[File:Subscriber dashboard2.png\|border\|700x700px]]
	== Queue Readers ==		== Queue Readers ==

JoC: /* Subscribers */

2021-02-03T16:47:27Z

Subscribers

← Older revision		Revision as of 16:47, 3 February 2021
Line 105:		Line 105:

	== Subscribers ==		== Subscribers ==
			The Subscribers page provides a summary view of both inbound (raw to FHIR store) and outbound (FHIR to subscriber CSV format) processing. Although it does not directly monitor the Information Model or UPRN APIs, these APIs are indirectly monitored due to the Queue Readers dependency on them – any issues with the API would be evident on this page.
			<br />
	== Queue Readers ==		== Queue Readers ==

JoC at 15:15, 3 February 2021

2021-02-03T15:15:28Z

← Older revision		Revision as of 15:15, 3 February 2021
Line 106:		Line 106:
	== Subscribers ==		== Subscribers ==

	== Queue ~~readers~~ ==		== Queue Readers ==

	== Frailty API ==		== Frailty API ==
Line 114:		Line 114:
	== SFTP Reader ==		== SFTP Reader ==

	== Schedules ~~tasks~~ ==		== Schedules Tasks ==

	== Exceptions ==		== Exceptions ==
	<br />		<br />

JoC: /* Publisher Errors */

2021-02-03T15:14:53Z

Publisher Errors

← Older revision		Revision as of 15:14, 3 February 2021
Line 99:		Line 99:
	The Publisher Errors page displays details of any DDS publisher feeds where the inbound transform (raw data to FHIR record store) has encountered some kind of fatal error.		The Publisher Errors page displays details of any DDS publisher feeds where the inbound transform (raw data to FHIR record store) has encountered some kind of fatal error.
	[[File:Publishers.png\|frameless\|700x700px]]		[[File:Publishers.png\|frameless\|700x700px]]

	The primary purpose, from the monitoring perspective, is to display those services and provide a quick way to view the specific errors. The page also provides functionality for re-queueing data for inbound processing, once whatever issue has caused the error has been rectified.		The primary purpose, from the monitoring perspective, is to display those services and provide a quick way to view the specific errors. The page also provides functionality for re-queueing data for inbound processing, once whatever issue has caused the error has been rectified.

JoC at 15:14, 3 February 2021

2021-02-03T15:14:25Z

← Older revision		Revision as of 15:14, 3 February 2021
Line 94:		Line 94:
	The primary use for this dashboard, from a monitoring perspective, is to detect services where no data has been received into DDS. The page is also used in the set up and configuration of DDS publishers, and controlling how published data is routed through the parallel processing queues.		The primary use for this dashboard, from a monitoring perspective, is to detect services where no data has been received into DDS. The page is also used in the set up and configuration of DDS publishers, and controlling how published data is routed through the parallel processing queues.

	[[File:Publisher_dashboard.png\|alt=\|border~~\|frameless~~\|800x800px]]		[[File:Publisher_dashboard.png\|alt=\|border\|800x800px]]

	== Publisher Errors ==		== Publisher Errors ==
Line 101:		Line 101:
	The primary purpose, from the monitoring perspective, is to display those services and provide a quick way to view the specific errors. The page also provides functionality for re-queueing data for inbound processing, once whatever issue has caused the error has been rectified.		The primary purpose, from the monitoring perspective, is to display those services and provide a quick way to view the specific errors. The page also provides functionality for re-queueing data for inbound processing, once whatever issue has caused the error has been rectified.

	[[File:Publisher errors dashboard.png\|border\|~~700x700px~~]]		[[File:Publisher errors dashboard.png\|border\|800x800px\|alt=]]

	== Subscribers ==		== Subscribers ==