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

Improve graphs/dashboard empty states #3514

Closed
paolodamico opened this issue Feb 28, 2021 · 4 comments
Closed

Improve graphs/dashboard empty states #3514

paolodamico opened this issue Feb 28, 2021 · 4 comments
Labels
design Issues that need a designer's attention enhancement New feature or request feature/dashboards Feature Tag: Dashboards

Comments

@paolodamico
Copy link
Contributor

paolodamico commented Feb 28, 2021

Is your feature request related to a problem?

Currently we have two different empty states for when graphs (in trends and dashboards) have no data. Both of these states are not great (either from a UI or UX standpoint [not very actionable in how to fix]).

Describe the solution you'd like

I'd like us to come up with some very useful and visually attractive empty states. Similar to what we did when a query time outs or errors.

Describe alternatives you've considered

Keep the current messages.

Additional context

Related to #3513

Thank you for your feature request – we love each and every one!

CC @kpthatsme

@paolodamico paolodamico added enhancement New feature or request design Issues that need a designer's attention labels Feb 28, 2021
@corywatilo
Copy link
Contributor

What would you want to see here? Aside from something more visual, probably some text about:

  • Common troubleshooting steps
  • Instructions on how to track events if total number of events in instance == 0?
  • Other ideas?

@corywatilo
Copy link
Contributor

Pasting this for my own reference of other error states:

image

@paolodamico
Copy link
Contributor Author

  • Additional common troubleshooting options: extend the search (i.e. remove filters or extend the timeframe).
  • If it's action-based, maybe something around checking the action to make sure it's property set up to match the desired events.
  • If it's a property aggregate value there might also be something around properties having incorrect types (e.g. numbers formatted as strings), or events not having the correct property.

@EDsCODE EDsCODE added the feature/dashboards Feature Tag: Dashboards label Mar 15, 2021
@clarkus
Copy link
Contributor

clarkus commented Jul 15, 2021

Closing in favor of #3982

@clarkus clarkus closed this as completed Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Issues that need a designer's attention enhancement New feature or request feature/dashboards Feature Tag: Dashboards
Projects
None yet
Development

No branches or pull requests

4 participants