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

Track Events Emitted #56

Open
franTarkenton opened this issue Jun 23, 2023 · 0 comments
Open

Track Events Emitted #56

franTarkenton opened this issue Jun 23, 2023 · 0 comments
Assignees

Comments

@franTarkenton
Copy link
Member

Currently script will collect messages, then when all the messages are collected an event is emitted for the idem_key (datestring). Getting a 200 status code response from the emitted event, then the database will delete all the records for the idem_key.

After this happens more events will continue to stream into the listener. These events get logged, and subsequent queries to the api will tell us that all the files for the current idem_key are missing.

Need another table to track the idem_keys that have been emitted. If the idem_key is in the emitted table then any incomming should not get cached in the database.

Queries to the missing messages api end point, should first check to see if the idem_key exists in the database table for already emitted events. If this is the case the query should just return an empty set as no data is missing as the event has already been emitted.

Add end point that reports on the already emitted events.

Emitted events table should track the following columns:

  • idem_key
  • Action associated with the event (the webhook url)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Product Backlog
Development

No branches or pull requests

1 participant