When is the next update to the dashboard UI coming?
stevescott
Posted on
May 24 2014
Dash UI hasn't changed in months...was hoping we'd have some sort of better visualization by now, like grid view or something...any ideas?
John-Daniel Trask
Raygun
Posted on
May 29 2014
Hi Steve,
I pinged you via email about this. Sorry about the delay. Moving this forward, could you describe exactly what you're looking for? Grid view doesn't give quite enough context - are you talking about a grid of the instances, or the groups, etc?
More detail is appreciated :-)
John-Daniel Trask
stevescott
Posted on
May 30 2014
Example: https://elmah.io/
Look at about 30 seconds in...I have a grid of errors as they occur not grouped into annoying exception messages which you then have to drill into...then once you're in there you have to slowly page through the detailed data.
I want a configurable grid which shows me new errors in realtime (or near) and lets me choose the columns I'd like to look at.
For ME...I want to see | Date\Time | Message | Type (CS\JS...error provider, whatever) | Url | User | OS | Browser
...that gives me at a glance the only stuff I really ever look at. It also helps our support track things down because when someone (jane.doe@email.com) calls in, he can open the error list and just see jane within the last hour. Instead of having to do a "search" and end up with more grouped results. Lets say she has a JS error which is causing a CS error in the backend on post or something. The grid would show us something like that where the grouping doesn't even SHOW me the provider type...I just have to infer that its a backend or clientside error.
Like the top graph is "neat" in overview mode, like I can filter based on it, but I rarely do...I would rather deal with things as they happen near the top of the list instead of spending hours drilling into "similar" issues...it's also REALLY annoying when an exception has a message that's kinda the same but not so the grouping just outright fails.
Know where I'm coming from?...it's an efficiency thing. We're reactionary here, when someone tell us there's a problem we use these tools to try to figure out the cause. We don't go in every day to clean out and deal with errors because it's just flooded with too many false\garbage errors (usually clientside stuff we can't fix or have no control over).
stevescott
Posted on
Jun 03 2014
Could I pester you for a reply on this please :)
Callum
Posted on
Jun 03 2014
Sorry about the delay on this, we're just back from a public holiday weekend.
Your request for a datagrid with configurable columns has been noted and it does appear this would be a valuable addition for some use cases, in particular presenting only the particular data you are interested in. With regards to support looking for recent occurrences though, this is already present as the error group list can be sorted by most recent occurrence. There most likely would be issues with scaling for users with large error volumes - for instance there is little point in displaying every instance of the same error when thousands occurred in the previous hour, drowning out other occurrences of bugs with smaller volumes, yet which could be just as critical.
With regards to not presenting the provider from which an error came from - Raygun is designed so one piece of the system is represented by one API key, so a front-end JS site can deliver its errors to one App in Raygun, while the backend sends its errors to another (and many of our users send mobile clients to yet another). Thus any errors which appear in that app in Raygun are by definition from that piece of the architecture, so clientside errors are kept separate and won't flood the notifications from the rest of the infrastructure. Having both the frontend and backend use the same API key would produce the confusing, noisy error group list which you may be seeing.
Poor auto grouping performance is a separate issue - we can look into specifics if you send us an instance of one (or two) errors that should/should not be grouped - you can do this via the Feedback button in Raygun.
Regardless, we have noted the request for a configurable datagrid and will look at the feasibility of it. We invite you to create a Suggestion in that forum so that it can receive votes - we are guided by user demand here so we will keep an eye on it. This most likely will not be added in the short-term however as there are several pressing features which the team is currently working on, but we will keep you posted with any developments.
Regards,
Callum Gavin
Mindscape Limited