You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/how-it-works/HighPaymentsRequestsLatency.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,8 @@ Troubleshooting steps
7
7
----------------------
8
8
9
9
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.
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
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
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
13
13
14
14
If any of the above has error, this is most likely the issue
0 commit comments