|
|
|
|
|
by 2468ben
4905 days ago
|
|
Please Both. You need to be able to see real-time and long-term. All Dashboards should show goals you set or something that's unusual compared to your past data. THAT is the reason why everyone's confused by most dashboards - they're visualization for the sake of looking good first. When they're done right they let you see the state of things, whereas feeds are like alarms - too many or too few can make you stop giving a damn. Be like a scientist - ask every question you can think of. Then try to answer it with data and if that answer changes over time, keep it on a dashboard. Then set alerts and snapshots to the feed, so only what's really important will bother you. What we need to work on is how deep you can ask questions of an external service. Giving me my choice of 12 pre-baked table columns or API endpoints isn't going to answer my real goals. 12 pre-designed draggable widgets aren't either. I want to ask big questions first instead of combining little answers. |
|