-
Notifications
You must be signed in to change notification settings - Fork 1
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
Freshness checks are warning/failing #411
Comments
@pingpingxiu-DOT-ca-gov the freshness checks are now failing, are you able to take another look? https://california.getdbt.com/deploy/6/projects/10/runs/5449 |
My latest 3 day’s changes on ES had some bug that impacted data relay, which I fixed.
However, the freshness check continue to fail.
Now, the source data, is the remaining cause. I checked on the Oracle source table,
And found the SELECT * FROM PEMS.DETECTOR_CONFIG_LOG where time_id > TRUNC(SYSDATE) – 2
returns empty data. And it is the case for the DETECTOR, STATION and CONTROLLER.
Ken, is there any upstream changes that cause the stale for the config tables?
From: Ian Rose ***@***.***>
Sent: Friday, October 4, 2024 8:56 AM
To: cagov/caldata-mdsa-caltrans-pems ***@***.***>
Cc: Xiu, ***@***.*** ***@***.***>; Mention ***@***.***>
Subject: Re: [cagov/caldata-mdsa-caltrans-pems] Freshness checks are warning/failing (Issue #411)
EXTERNAL EMAIL. Links/attachments may not be safe.
@pingpingxiu-DOT-ca-gov<https://urldefense.com/v3/__https:/github.com/pingpingxiu-DOT-ca-gov__;!!LWi6xHDyrA!97aMtB7LRI2XcWjdleMwxBss753BNqDz6y5v_cjvH3KFt6uLakW8Z83oTaWiXj25L9rtS9BNvFe1kT1MMQtrM6tMSppU320$> the freshness checks are now failing, are you able to take another look?
https://california.getdbt.com/deploy/6/projects/10/runs/5449<https://urldefense.com/v3/__https:/california.getdbt.com/deploy/6/projects/10/runs/5449__;!!LWi6xHDyrA!97aMtB7LRI2XcWjdleMwxBss753BNqDz6y5v_cjvH3KFt6uLakW8Z83oTaWiXj25L9rtS9BNvFe1kT1MMQtrM6tMsLFpEQU$>
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/cagov/caldata-mdsa-caltrans-pems/issues/411*issuecomment-2394010826__;Iw!!LWi6xHDyrA!97aMtB7LRI2XcWjdleMwxBss753BNqDz6y5v_cjvH3KFt6uLakW8Z83oTaWiXj25L9rtS9BNvFe1kT1MMQtrM6tMMDvXSzk$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BDVOYUMO6NDKKT25FACAVSTZZ23AZAVCNFSM6AAAAABPKE2N6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJUGAYTAOBSGY__;!!LWi6xHDyrA!97aMtB7LRI2XcWjdleMwxBss753BNqDz6y5v_cjvH3KFt6uLakW8Z83oTaWiXj25L9rtS9BNvFe1kT1MMQtrM6tMAdq2P2Y$>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Interesting, so it's with the underlying system? That's a problem, but it's good that the freshness checks are working! |
Agree, an effective quality safeguard!
From: Ian Rose ***@***.***>
Sent: Friday, October 4, 2024 11:29 AM
To: cagov/caldata-mdsa-caltrans-pems ***@***.***>
Cc: Xiu, ***@***.*** ***@***.***>; Mention ***@***.***>
Subject: Re: [cagov/caldata-mdsa-caltrans-pems] Freshness checks are warning/failing (Issue #411)
EXTERNAL EMAIL. Links/attachments may not be safe.
Interesting, so it's with the underlying system? That's a problem, but it's good that the freshness checks are working!
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/cagov/caldata-mdsa-caltrans-pems/issues/411*issuecomment-2394339812__;Iw!!LWi6xHDyrA!4vp7vaLEiGPf6hXby3vPsuKdwIxiHQcFkQ68Kld9mr7yxxIlplYyjaLRow1btXiB-2w8m8uWEEOZS4WZlmc8Tk1zNVaXwSM$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BDVOYUMQCQHTXOO5X5NZWVTZZ3M7TAVCNFSM6AAAAABPKE2N6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJUGMZTSOBRGI__;!!LWi6xHDyrA!4vp7vaLEiGPf6hXby3vPsuKdwIxiHQcFkQ68Kld9mr7yxxIlplYyjaLRow1btXiB-2w8m8uWEEOZS4WZlmc8Tk1zxlorHHU$>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Per @kengodleskidot the issue appears to be that the districts are not sending data updates. He will follow up with them to see if there is a failure on there side or if this is expected behavior. If this is expected, @pingpingxiu-DOT-ca-gov says we can add a new timestamp which would detect if the data relay is the issue vs. the equipment data feed. |
I added #436 PR for making less sensitive on the detector config log freshness. |
We've started to get some warnings (which will shortly be errors) in our source freshness checks: https://california.getdbt.com/deploy/6/projects/10/runs/5414
Unsure if the issue is with the checks or with the relay process right now, @pingpingxiu-DOT-ca-gov can you take a look?
The text was updated successfully, but these errors were encountered: