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

Make ingestor fault tolerant and production ready #42178

Closed
Tracked by #42044
rjo100 opened this issue Dec 8, 2022 · 2 comments · Fixed by #43924
Closed
Tracked by #42044

Make ingestor fault tolerant and production ready #42178

rjo100 opened this issue Dec 8, 2022 · 2 comments · Fixed by #43924
Assignees

Comments

@rjo100
Copy link
Contributor

rjo100 commented Dec 8, 2022

Right now we haven't done a comprehensive overview of metrics and error handling for the ingestor (and associated pipeline steps like post_process and eventstream). We should:

  1. Ensure metric consistency in our new ingestor pipeline with our current processing pipeline
  2. Make sure that all new code pathways fail gracefully
    a. Error handling where appropriate
    b. Invalid payloads are rejected with helpful error messages and don't cause unhandled internal errors
  3. Set up SLO's for existing event and transaction processing with an eye towards occurrence SLO's
@rjo100
Copy link
Contributor Author

rjo100 commented Dec 22, 2022

Need to add more metrics to understand amount of load. Logging is in a decent place

@rjo100
Copy link
Contributor Author

rjo100 commented Jan 20, 2023

Need to make SLOs for events and transactions as well
https://www.notion.so/sentry/SLO-Update-Q4-FY23-3a100322fcd945528e4d58e89e339379

@getsentry getsentry deleted a comment from github-actions bot Jan 20, 2023
@rjo100 rjo100 self-assigned this Jan 24, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Feb 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant