Improve observability; add sqlite retries to deal with sqlite_busy errors #352
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the pragma
sqlite_busy
to add automatic retries on sqlite busy errorClean up the prometheus metrics to support dashboards for monitoring impact. The key metrics we want are
Cleanup up prometheus metrics so we can better monitor why learning isn't happening; this was used to track down sqlite busy errors
Support monitoring with Datadog