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
Recently we increased the tries (hence time) to wait for the agent to be running because we detected that in some cases it was not enough for the agent to be detected as running and healthy. But we are not checking for logs signaling a wrong key-region tuple.
Proposal
Include the logic in the script to support checking for failure logs. Every time we query for the success log, we check too for a failure log. First tests shown that the string we need to query for is: ERR_INVALID_CUSTOMER_KEY .
We should also explore with @mfncl99 if there are other information in the logs that we can include to improve success and failure checks.
The text was updated successfully, but these errors were encountered:
Context:
Recently we increased the tries (hence time) to wait for the agent to be running because we detected that in some cases it was not enough for the agent to be detected as running and healthy. But we are not checking for logs signaling a wrong key-region tuple.
Proposal
Include the logic in the script to support checking for failure logs. Every time we query for the success log, we check too for a failure log. First tests shown that the string we need to query for is:
ERR_INVALID_CUSTOMER_KEY
.We should also explore with @mfncl99 if there are other information in the logs that we can include to improve success and failure checks.
The text was updated successfully, but these errors were encountered: