create new table to track weekly unlabeled routes for payments #2686
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
…itle of original table
charlie-costanzo
changed the title
charlie-costanzo
requested review from
atvaccaro,
lauriemerrell and
SorenSpicknall
as code owners
charlie-costanzo
changed the title
atvaccaro
approved these changes
Jun 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
create new weekly unlabeled routes tracking table
v2_payments_reliability_weekly_unlabeled_routes, rename original title fromv2_payments_reliability_unlabeled_routestov2_payments_reliability_monthly_unlabeled_routesOnce this is merged, we can create the alert in the SBMTD dashboard as requested in #2619
Type of change
How has this been tested?
tested locally with dbt
Post-merge follow-ups
Set up alerts in Metabase