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

Implement Log Aggregation & Searching #88

Open
dgarnitz opened this issue Oct 31, 2023 · 2 comments
Open

Implement Log Aggregation & Searching #88

dgarnitz opened this issue Oct 31, 2023 · 2 comments

Comments

@dgarnitz
Copy link
Owner

VectorFlow has many logs spread of over different containers. We need these logs to be aggregated into a searchable form.

One option could be to use Kibana with Elastic Search. If the logs have metrics in them, we may want to put those into prometheus

@dgarnitz
Copy link
Owner Author

dgarnitz commented Apr 4, 2024

Scope this out. We need this upgrade to solve this issue.

What to Build

  • Add an additional database table that stores error messages. Do this by adding a new model object. Make sure that the job_id and batch_id are tracked
  • For now this can store the entire stacktrace, as long as its not too long,
  • Alter the code in the api, worker and extractor so that whenever an error is logged, it is also saved to the database. add a method to a utils file, save_error() that does this and use the util method in each file
  • Add an endpoint that returns all the errors for a given batch_id. return a JSON object with a field errors that is an array of stack traces
  • Add an endpoint that returns all the errors for a given job_id. return a JSON object with a field errors that is a dictionary featuring batch_id as the key and an array of stack traces as the value

@dgarnitz
Copy link
Owner Author

dgarnitz commented Apr 8, 2024

No need for kibana or prometheus, just store in the DB

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant