Distinct Error and Empty states for Error Tracking page

The following discussion from gitlab-ce!23770 should be addressed:

  • @ameliabauerly started a discussion: (+4 comments)

    @psimyn, I don't think we've officially established a policy for messaging empty states from within tables yet, so I would probably recommend a blank table with an error message on the top of the page explaining why the table is blank, something like:

    Empty

    @svoegeli, how does this seem to you? Also, any thoughts on what the error text should be? It seems like we might want to give the users a little more information about why it 'failed to load' but not 100% sure what would be more appropriate here. I know the 'view on Sentry' button is directly below the message so users can pretty easily click on that button to view the errors directly in Sentry from there...

    As a side note: I know that our pattern library alert component doesn't match the one currently in use on GitLab, so the alert in this mock-up won't match the component you would probably pull from. I believe the one currently in use elsewhere is solid red. It is fine to match the one currently in use.

Edited by 🤖 GitLab Bot 🤖