JJ531047 - Replication Grid

Replication Monitoring

Concept version: 2.0

As of 2023-01-01 00:00:00

design note1: this allows CS Team to tailor the page based on their process, no need to ask dev if process changed

Threshold (status count for Monitor, Warning, Critical)
JobJar # (Report)
Teams Channel Email	program_teamchannel@givex.com

CAL1 : 1 VXL4 to 4 CWS

design note 0: graph appears when clicking a cell grid

design note2: clicking on a cell provides a drill-down per data center vs db role

	Cal1				Toronto			Miami			London
STATUS CRITICALITY
	O	M	W	C	M	W	C	M	W	C	M	W	C
trans	3	3	10	30	10	3	5	23	11	6	4	13	3
report	3	10	3	10	3	5	11	6	4	8	3	3	3
robot	3	3	10	3	10	15	4	23	11	6	4	13	3
root	3	10	3	10	8	3	23	11	6	4	13	3	3
shadow	3	10	3	10	3	5	23	11	6	4	13	3	3
spare	3	10	3	10	3	25	16	11	6	4	13	3	3

design note3: shaded cell--->escalation threshold has been reached.
When a cell is clicked, we show "REPLICATION DELAYS" table below

		Cal1			Toronto			Miami			London
STATUS DURATION
DURATION		M	W	C	M	W	C	M	W	C	M	W	C
over 45 mins	trans	1, 3, 200, 300	2, 4, 24	5,11,26	10	3	5	23	11	6	4	13	3
	report	3	10	3	10	3	5	11	6	4	8	3
	robot	3	10	3	10	3	4	23	11	6	4	13	3
	root	3	10	3	10	30	3	23	11	6	4	13	3
	shadow	3	10	3	10	3	5	23	11	6	4	13	3
	spare	3	10	3	10	3	25	16	11	6	4	13	3
15 - 45 mins	trans	1, 3, 200, 300	2, 4, 24	8,95,30	10	3	5	23	11	6	4	13	3
	report	3	10	3	10	3	5	11	6	4	8	3
	robot	3	10	3	10	3	4	23	11	6	4	13	3
	root	3	10	3	10	30	3	23	11	6	4	13	3
	shadow	3	10	3	10	3	5	23	11	6	4	13	3
	spare	3	10	3	10	3	25	16	11	6	4	13	3
1 - 15 mins	trans	1, 3, 200, 300	2, 4, 24	203,33,160	10	3	5	23	11	6	4	13	3
	report	3	10	3	10	3	5	11	6	4	8	3
	robot	3	10	3	10	3	4	23	11	6	4	13	3
	root	3	10	3	10	30	3	23	11	6	4	13	3
	shadow	3	10	3	10	3	5	23	11	6	4	13	3
	spare	3	10	3	10	3	25	16	11	6	4	13	3
under 60 seconds	trans	1, 3, 200, 300	2, 4, 24	5,11,26	10	3	5	23	11	6	4	13	3
	report	3	10	3	10	3	5	11	6	4	8	3
	robot	3	10	3	10	3	4	23	11	6	4	13	3
	root	3	10	3	10	30	3	23	11	6	4	13	3
	shadow	3	10	3	10	3	5	23	11	6	4	13	3
	spare	3	10	3	10	3	25	16	11	6	4	13	3

design note3B: do we use DB numbers or DB ref?

Data Center: Cal1 | DB Role = Trans

From		To		Status / Delay		Duration
1	Vxl	4	CWS	CRITICAL	00:02:36	00:50:00
1	Vxl	3	Admin	CRITICAL	00:03:39	00:50:00
60	JSON	1	vxl	CRITICAL	00:03:50	00:50:00
201	(Admin, IVR, Seq2)	1	vxl	CRITICAL	00:0:45	00:32:00
201	(Admin, IVR, Seq2)	1	vxl	CRITICAL	00:0:45	00:05:00
201	(Admin, IVR, Seq2)	1	vxl	CRITICAL	00:0:45	00:01:00
201	{Show all 49 DB's}	1	vxl	CRITICAL	00:0:45	00:23:00

design note: "Duration" is elapsed time since DB is in that status

design note 4: content can be populated based on selections from "REPLICATION DELAYS"

On-Call: Johnny Techy

Title
Content	1 Vxl 4 CWS CRITICAL 00:02:36, 60 JSON 1 vxlCRITICAL 00:03:50
	Update JobJar
	Send Message to Teams Channel

design note5: we can still present more details -- primary audience: tech team

Filter:

trans

report

robot

root

shadow

special

		Cal1
	From/To		1 T1-1:(ssd) 13.8	2 T1-2:(ssd) 13.8	3 T1-3:(ssd) 13.8	4 T1-4:(ssd) 13.8	5 T1-5:(ssd) 13.8	6 T1-6:(ssd) 13.8	7 T1-7:(ssd) 13.8	8 T1-8:(ssd) 13.8	9 T1-9:(ssd) 13.8	10 T1-10:(ssd) 13.8	11 T1-11:(ssd) 13.8	12 T1-12:(ssd) 13.8	13 T1-13:(ssd) 13.8
trans	1	Vxl
	2	DCDial, DCVpn, LCBO, Mcrs, Sway, XML
	3	Admin
	4	CWS
	5	DC, GAPI, MapU, Trans, UATP
	6	DCBck, DCMulti, JSON, SUN
	7	JSON, XML
	8	DCBck2, JSON, Srvc, WPOS
	9	JSON
	10	Metro,Seq
	11	DC
	12	DC, SUN
	13	JSON
	14	DCDial, DCMulti, JSON, Seq
	15	DCBck2, JSON
	16	CWS
	17	JSON, WPOS