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

How to reset current_timestamp for TS_URL="${CHARGEBACK_READINESS_PROBE_URL}${CURRENT_TS_PROBE}" #9

Open
DorenMeng opened this issue Jan 21, 2024 · 1 comment
Assignees
Labels
stale Stale Issues that might have been valid

Comments

@DorenMeng
Copy link

If the app didn't grab full data in the past days, how can it reset current_timestamp to re-grab data for a period?
For example, like screenshot below, the data began missing since 14 Dec.
image

Thanks!

@waliaabhishek
Copy link
Owner

Generally if there was no data grabbed, the feeder will automatically scan whatever data is missing after some time/scrapes and refeed it to the system. This allows for missing data to be captured again. The self healing code is located here --

def locate_next_fetch_date(

Looking at the graphs it seems like there might be some issue/bug with (maybe) newer billing types. Can you check the ccloud_chargeback_handler pod logs for any Errors and/or issues and report back?

@waliaabhishek waliaabhishek added the stale Stale Issues that might have been valid label Mar 22, 2024
@waliaabhishek waliaabhishek self-assigned this Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale Issues that might have been valid
Projects
None yet
Development

No branches or pull requests

2 participants