monitoring(soteria): tune PVC backup age thresholds for nightly cadence
This commit is contained in:
parent
55fa72d446
commit
fb43b02b2a
@ -2338,17 +2338,19 @@ def build_overview():
|
||||
"mode": "absolute",
|
||||
"steps": [
|
||||
{"color": "green", "value": None},
|
||||
{"color": "yellow", "value": 6},
|
||||
{"color": "orange", "value": 12},
|
||||
{"color": "red", "value": 24},
|
||||
{"color": "yellow", "value": 20},
|
||||
{"color": "orange", "value": 40},
|
||||
{"color": "red", "value": 50},
|
||||
],
|
||||
},
|
||||
)
|
||||
)
|
||||
panels[-1]["links"] = link_to("atlas-storage")
|
||||
panels[-1]["description"] = (
|
||||
"Backup age in hours computed from last-success timestamps for restic-managed PVCs. "
|
||||
"PVCs that have backup history but currently no successful backup (missing/no_completed/error) are pinned to 999h for visibility."
|
||||
"Backup age in hours computed from last-success timestamps for restic-managed PVCs "
|
||||
"(nightly target: <=20h green, <40h yellow, <50h orange, >=50h red). "
|
||||
"PVCs that have backup history but currently no successful backup (missing/no_completed/error) "
|
||||
"are pinned to 999h for visibility."
|
||||
)
|
||||
|
||||
panels.append(
|
||||
|
||||
@ -2539,15 +2539,15 @@
|
||||
},
|
||||
{
|
||||
"color": "yellow",
|
||||
"value": 6
|
||||
"value": 20
|
||||
},
|
||||
{
|
||||
"color": "orange",
|
||||
"value": 12
|
||||
"value": 40
|
||||
},
|
||||
{
|
||||
"color": "red",
|
||||
"value": 24
|
||||
"value": 50
|
||||
}
|
||||
]
|
||||
}
|
||||
@ -2583,7 +2583,7 @@
|
||||
"targetBlank": true
|
||||
}
|
||||
],
|
||||
"description": "Backup age in hours computed from last-success timestamps for restic-managed PVCs. PVCs that have backup history but currently no successful backup (missing/no_completed/error) are pinned to 999h for visibility."
|
||||
"description": "Backup age in hours computed from last-success timestamps for restic-managed PVCs (nightly target: <=20h green, <40h yellow, <50h orange, >=50h red). PVCs that have backup history but currently no successful backup (missing/no_completed/error) are pinned to 999h for visibility."
|
||||
},
|
||||
{
|
||||
"id": 30,
|
||||
|
||||
@ -2548,15 +2548,15 @@ data:
|
||||
},
|
||||
{
|
||||
"color": "yellow",
|
||||
"value": 6
|
||||
"value": 20
|
||||
},
|
||||
{
|
||||
"color": "orange",
|
||||
"value": 12
|
||||
"value": 40
|
||||
},
|
||||
{
|
||||
"color": "red",
|
||||
"value": 24
|
||||
"value": 50
|
||||
}
|
||||
]
|
||||
}
|
||||
@ -2592,7 +2592,7 @@ data:
|
||||
"targetBlank": true
|
||||
}
|
||||
],
|
||||
"description": "Backup age in hours computed from last-success timestamps for restic-managed PVCs. PVCs that have backup history but currently no successful backup (missing/no_completed/error) are pinned to 999h for visibility."
|
||||
"description": "Backup age in hours computed from last-success timestamps for restic-managed PVCs (nightly target: <=20h green, <40h yellow, <50h orange, >=50h red). PVCs that have backup history but currently no successful backup (missing/no_completed/error) are pinned to 999h for visibility."
|
||||
},
|
||||
{
|
||||
"id": 30,
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user