The `postgres-archive` service (`main` stage), `cpu` component has a saturation exceeding SLO and is close to its capacity limit
Summary
The postgres-archive
service (main
stage), cpu
component has a saturation exceeding SLO and is close to its capacity limit
More information will be added as we investigate the issue.
Timeline
All times UTC.
...
2020-05-02
- ...
-
04:43
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
04:43
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
04:44
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
04:44
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit.
2020-05-03
-
13:21
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
13:21
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
13:22
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
15:08
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
15:08
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
15:09
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
15:09
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
16:04
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
16:04
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
16:05
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
16:05
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
16:05
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
17:23
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
17:24
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
17:24
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. -
17:24
- General alert triggered: Thepostgres-archive
service (main
stage),cpu
component has a saturation exceeding SLO and is close to its capacity limit. - And on it goes...
This saturation appears to have been on-going since around 2020-05-01 0430 UTC
.
I'm going to put in a silence until Monday, and then re-evaluate.
Edited by Nels Nelson