-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat(dynamic_routing): analytics improvement using separate postgres table #6723
Open
prajjwalkumar17
wants to merge
27
commits into
main
Choose a base branch
from
analytics_sr
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed Files
|
hyperswitch-bot
bot
added
the
M-database-changes
Metadata: This PR involves database schema changes
label
Dec 2, 2024
prajjwalkumar17
added
A-routing
Area: Routing
C-feature
Category: Feature request or enhancement
labels
Dec 3, 2024
prajjwalkumar17
changed the title
feature(dynamic_routing): analytics improvement using separate postgres table
feature(euclid): analytics improvement using separate postgres table
Dec 3, 2024
prajjwalkumar17
changed the title
feature(euclid): analytics improvement using separate postgres table
feat(dynamic_routing): analytics improvement using separate postgres table
Dec 3, 2024
Chethan-rao
requested changes
Dec 3, 2024
migrations/2024-12-02-095127_add_new_table_dynamic_routing_stats/up.sql
Outdated
Show resolved
Hide resolved
migrations/2024-12-02-095127_add_new_table_dynamic_routing_stats/up.sql
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-routing
Area: Routing
C-feature
Category: Feature request or enhancement
M-database-changes
Metadata: This PR involves database schema changes
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
Previously we were pushing the Dynamic routing metrics to Prometheus, but due to high cardinality of some values(payment_id) we were not able to add that in our attributes, hence we are pushing this after creating a new table in our Database (dynamic_routing_stats).
Additional Changes
Motivation and Context
Required to get the payment_id for our metrics purpose.
How did you test it?
Can be tested in the following ways:
dynamic_routing_stats
table for the specific value associated with thepayment_id
.Checklist
cargo +nightly fmt --all
cargo clippy