Dashboard #13
Merged
Dashboard #13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Started the work on the dashboard. For the moment it is just an extremely basic table that lists errors and allows marking them as resolved or unresolved. The errors are paginated using infinite scroll with Phoenix LiveView streams. In the future I would like to use cursor-based pagination as it is more efficient that limit+offset pagination, but that can be done anytime.
I've also added a new field to the error to track the last occurrence timestamp. Without this we need to resort to joins and window functions to get this information, and those are much more expensive in DB terms.
The index is unfinished yet and it needs filters and good styling. We also have to implement a detailed page for each error that shows the full stacktrace and every occurrence.