Filing in the old component because I'm not sure where it maps to in the new components. We've got an old push-load one-off :RaFromBRC and :relud set up that I believe populates a redshift database somewhere. It appears to run about 5 times a day. If this job is still running correctly and the redshift database is being used from re:dash, we should probably get it migrated to logging 2.0 / parquet. If the data is not being used or the job is failing, we should decommission it. Last I was aware this was supposed to run daily, but perhaps we bumped the frequency to keep up with load.
Once we are outputting to parquet in logging 2.0, and bbangert has moved his needed dashboards to rely on
Depends on: 1364209
on the parquet outputs*
:benbangert does the quicksight stuff you have now sufficiently replace the prod push redshift cluster, and logging 1.0 job to load it?
We have sufficient info to replace this now, it can be dropped. Thanks!
Component: Metrics: Pipeline → Operations
Product: Cloud Services → Data Platform and Tools
QA Contact: jthomas
Status: NEW → RESOLVED
Last Resolved: 7 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.