Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(dynamic_routing): enhance metrics to include separate enteries for all consecutive attempts happening for a payment #6756

Open
Tracked by #5751
prajjwalkumar17 opened this issue Dec 5, 2024 · 0 comments
Assignees
Labels
A-routing Area: Routing enhancement New feature or request

Comments

@prajjwalkumar17
Copy link
Contributor

prajjwalkumar17 commented Dec 5, 2024

We already have the DB schema in-place, the change that needs to be done is as follows(which will help us for the accounts where smart-retries are enabled):

Population of every attempt's data to the dynamic_routing_stats table (right now we are only considering the last attempt's data). This can possibly be done by considering the first and last payment in the chain of attempts being made, or else we can consider every attempts happening, the point is which dynamo connector to choose.

Payment Connectors Dynamic Routing Connectors Payment Status
Stripe (Adyen, BOA, Stripe) Failure
Adyen (Adyen, BOA, Stripe) Failure
BOA (Adyen, BOA, Stripe) Success

So which connector to choose from the dynamic routing list of connectors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-routing Area: Routing enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant