'Events' tab in a group should show more detail?

[gtaylor]

I know this isn't fully inline with the main project page, but it'd be super helpful to see which server errors came from on the /group/<#>/events/ view. This view is immensely helpful in finding patterns in bugs. Sometimes you get those really annoying ones that only happen on one app server. Spammed IRC, here it is:

[16:02] <gtaylor> So, philosophical discussion.
[16:02] <gtaylor> The 'Events' tab under a group shows the last handful occurrences of an error. This is great.
[16:02] <gtaylor> You then have a 'URLs' and 'Servers' tab, which are also great.
[16:03] <gtaylor> The problem is, the 'Servers' tab is an aggregate count of occurrences. It's not easy to see if the last X occcurrences happened on a particular server or URL, since those tabs are aggregate counts of occurrences.
[16:03] <gtaylor> I wonder if the 'Events' tab should have the server (and possibly URL?) somewhere on each event entry so you can more easily look for patterns?
[16:04] <gtaylor> alternatively, in addition to the aggregates on URLs and Servers tabs, show the last X events with the URL and Server instead of the logger

[dcramer]

So thoughts on what changes:

• Params for messages can change
• Interfaces can change, though we can't know for sure.
• We generally treat URL and server name as first class citizens (even though url is part of a data interface), so both of those are reasonable candidates
• Possibly two different views depending on if they're viewing "Stream" (main page) or the events tab. Both probably need improved though.

[gtaylor]

Those all sound reasonable. I think the thing that I am looking for, regardless of how it's done, are better methods to find patterns. Is it happening to one app server? Is it only certain URLs? Is it certain URLs on certain app servers?

Perhaps that helps to hear, I don't know :)

[heynemann]

@dcramer Any plans on implementing this in any future releases?