Official New Performance Reporting Dashboard

It looks nice ... but

It seems very clunky to use.
Clicking either of the sort-able columns (Count or Last Seen) causes a reload which takes you back to the top of the screen but doesn't actually change the sorting of the report table. To then apply the sort after the data refresh you have to click Apply which then causes another refresh and spring back to the top. The spring back to the top gets a little annoying when we're so used to content changing in situ plus the chart takes up so much of the screen you always have to scroll back down to see the actual reports.

We also used to be able to clear down the reports in there but now it seems we can only tag a problem ID as closed. I could do with clearing all logs at the moment so I can start some fresh recording as they're currently logged against a whole host of app version numbers while i've been playing with things and purposefully causing reports to be logged. The ability to delete reports, potentially as well as the hide\closed is essential I think.

If you tag a problem as closed then under the default settings it would be hidden from view. The issue there is that if another report comes in for that same problem (yep, we've all considered a problem closed at some point and woah, it rears it's head again) the closed tag remains and the further reports are hidden unless you specifically turn off the Exclude closed problems checkbox.

The filtering isn't that intuitive. If you select a specific problem and then try to filter on a field within that, the filter will present you with values that haven't necessarily been associated with that problem. e.g. Application Versions that aren't associated with that problem ID. Going back to the earlier bit it also means that without the ability to clear down old logs you'll always have those values in the filter options. Any filter added will also carry through from the main reports page to the individual report page. That's not too bad I guess but if you apply a filter within the individual reports page it also works up the hierarchy and remains applied if you back out to the full report listing page again.

Is there any way to switch back to the old version until this one becomes a bit more functionally sound ?

 

Need to agree with srmatthe! The new dashboard looks all fancy and new but is making things a lot harder than with the old one.

 

Great stuff

Change is always a pain but with a few functionality tweaks it's looking good and useful.

 

The new update is great and much more attractive on the eye, the ability to tag and mark as closed is great too.

I'd echo some of the comments above about reloading data when you change columns and not being able to delete issues. I like to leave this up during beta and then wipe the lot on launch day to start fresh.

If its the case that you mark an issue as closed, does it get tied to a version number, so if it happens on a newer version it untags it?

Another improvement I'd love to see is on the Symbols page. Just a list of version numbers you've uploaded symbols for to start with would be handy. Sometimes I don't see full stacks and realise I've not uploaded symbols, but the symbols page is a bit of a black hole at the moment.

^_^

 

Feels much more usable with the sorting and list options working directly now along with the page staying in place.

One more suggestion on the sorting. When the page loads the table is sorted by Count descending which makes sense. If you then click to sort by the Last Seen column its first response is to sort by ascending and this is then the case going back to the Count column.

Can it default to descending sort the first time a new column is selected rather than ascending ?
I'd imagine that most people's likely sort preference would be descending so either highest count or most recent report is listed at the top when changing column sort. To get to that currently it's two clicks and two refreshes.

 

I did not see a way to search for a keyword in the new version. Is that still possible? Thanks!

 

Great! Thanks

 

Am I just missing it, or is there a close button somewhere for marking an issue as closed? I see a way to add a "Closed" tag, but it's buried in the "EDIT TAGS" button, requiring extra clicks to close issues. Currently it takes 4 clicks to mark an issue as closed while looking at the details of it.

 

It would be very nice to have a way to bulk close issues from the list. There are typically a lot of one-off native crashes on iOS with no useful information. Currently I have to go into each one and close it, a total of 6 clicks per issue to close it.

 

Looking good, but a couple of requests:
- In the problems list add columns for Platform and Application Version
- Allow exclusion filters (I need a way to see multiple platforms in one list, e.g., I want to look at iOS and Android, but not WindowsEditor and MacEditor)

 

Is there any way at all to actually get symbols loaded? All the documentation seems outdated and I've wasted days trying to load symbol files. I can't even find a reference to which files need to be uploaded. I'm experiencing crashes only on OSX builds, not on the windows or linux builds of my game and the traceback is filled with "symbols missing for uuid: xxxxxxx". All I have to work with is the crash message of: "Native Crash - Mono JIT frame (Unknown File)"

... which isn't very helpful

I've tried uploading the .mdb files but it says "Warning: no image found" and I have no further information.

 

Thanks, I have done so.

It would still be nice to find out how to upload symbols though is there any information on how to do this anywhere?

 

Is it possible to download the data? It would be great to do so in order to apply custom filters.

 

Hi, so far, that's cool new stuff, here's some notes though :
Removing / sizing down the occurences field would be much appreciated, I don't use it much. and it takes a lot of space on the screen

And I have no idea how closed problems are supposed to be handled properly: I mean, i can fix something, then tag it as closed, ok. But what If the bug comes back two versions later ? If it's the same that is tagged as closed, I'm screwed, I won't see it unless I start to scroll into bugs tagged as close.
Isn't there a way to tag a bug as closed but like..only for a specific application value ?

Also, same thing as I would love to see also in alpha bug reports, when you are in a performance bug report, the ability to directly go to the next or previous one without going back to previous page.

 

Ok, thanks!
Oh, and still in bug reports, possibly already planned considering the alpha state, but It would be much easier to actually delete the report directly without going into it (which can be a tiring process, since that if we go into a bug report and go back on main page, the filters are lost and must be setted again).

 

@johng_unity While not directly related to the new page, we really need a way to get a proper stack trace with line numbers in builds.
As far as I can tell this is currently only doable if creating a developer build, which we clearly don't want to release.
There should be an option to include full debug symbols with release builds. A stack trace without line numbers isn't really all that useful.

 

Filtering on Application Version is now broken. No drop down with valid entries appear, and manually inputting a version is ignored.

 

Hi @Geminior! Our dashboard briefly experienced a bug where our dropdown fields weren't filtering properly. We released a fix yesterday for that so you should be good to go. Would you mind double checking if you're still experiencing the issue?

 

It is working as expected now, thanks.

 

Ok, and here I thought it would be as simple as including full debug symbols instead of partial.
If that really isn't possible, might I suggest an option to build in debug mode, without a 'Development Build' watermark.

 

Any way for me to get these reports into Playfab?

Cheers

 

Do you happen to have an ETA of when we can expect line numbers in stacktraces for IL2CPP?

Thanks,
Tom.

 

Last successful builds in Unity 2017.4.4f1 have next exception:

Exception occurred attempting to connect to Unity Performance Reporting service.  Native symbols will not be uploaded for this build. Exception details:

System.Net.WebException: The remote server returned an error: (403) Forbidden.

I have access to Unity and Perfomance section. But upload process is "Fobidden". What could be the problem?

 

is slack/webhook integration in the roadmap ?

 

Hi,
About the number of "Users Affected". I suppose it's a count of distinct users across the period of time you are looking at and not a sum of distinct users from each day?

 

Would be great to be able to filter on multiple app version

 

It would be awesome to see some kind of crash-rate graph per released application version.
Also a percentage of how many users experiences a specific crash would be nice.

 

Hi team, is it possible to filter by build number, not just version number?

 

Hi, I'm getting the same exception as MihaPro_CarX. Please advise.


Exception occurred attempting to connect to Unity Performance Reporting service. Native symbols will not be uploaded for this build. Exception details:
System.UriFormatException: Absolute URI is too short

 

Hi,
I wonder if you have notifications to email/phone when Unity has detected Exception/Crash rate grow?

Or do you have some kind of API that I can use for getting the info you have on performance reports dashboard so i can create a notification on my side?

 

That would be great. You could also get notified if there’s a ‘significant’ new issue related to a new build version.

 

I don't see this written anywhere, does Performance Reporting provide me with line numbers when a crash occurs on a user's phone when using an Android app that I released in production to the Play Store?

Like this (from Crashlytics which only shows errors so detailed in NON production builds, a.k.a development builds):


Can Performance Reporting provide a detailed call stack like this for production apks?

 

Hello!
I think it is crucial to be able to send global custom data with the thrown error/exception.
Typically like crashlytics offers, you should be able to add some global game state...
I for example have over 100 levels, and I very much would like to know in which scene and at what player position the error occurred. I would then know which object has a missing reference... Now the only alternative is to manually add an exception myself for each script and case where the null might occur...