Skip to content

Commit f47a2da

Browse files
authored
Update HighPaymentsRequestsLatency.rst
1 parent 36a2e37 commit f47a2da

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/how-it-works/HighPaymentsRequestsLatency.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ Troubleshooting steps
77
----------------------
88

99
1. Check the pods the alert is fired on for errors
10-
2. Check that the `postgres` pod on the cluster is up and running properly. It's used to store and get payment requests.
11-
If the `postgres` db is unhealthy, this is probably the cause for it. For this, contact the DB INFRA team
12-
3. Check account-config workload. It's also used on the payment requests flow. For errors in this workload, contact the `config management` application team
10+
2. Check that the *postgres* pod on the cluster is up and running properly. It's used to store and get payment requests.
11+
If the *postgres* db is unhealthy, this is probably the cause for it. For this, contact the DB INFRA team
12+
3. Check *account-config* workload. It's also used on the payment requests flow. For errors in this workload, contact the `config management` application team
1313

1414
If any of the above has error, this is most likely the issue

0 commit comments

Comments
 (0)