A constant struggle with the error analytics is that a proportionally large amount of the results are just roblox engine specific errors of which we have zero control over. These warns/errors serve no value to Devs as they cannot fix them, and it’s not like we can just forward them all to staff anyways.
As a Dev, it would be incredibly useful if we could hide these errors/warns all together so we can focus on the actual ones relating to our game instead of having to constantly scroll past react warns that are larger than our entire monitor resolution.
It’s a constant struggle trying to find useful information in the error analytics when we have to spend so much additional time sorting out which ones are of any value to us.
Here’s an example of just the kind of pointless information we have to constantly skim through
I see this requested a lot here, I agree. Roblox should have a filter for “Roblox” errors, those which have nothing to do with the experience and “Everything else” which should be any errors or warnings you have setup for yourself to keep track of.
I want showcase a video of how bad the situation can get sometimes. Effectively blocking out all useful information entirely with walls of coregui/react errors. Like this should be absolutely unacceptable.
Bumping this, this is still an issue. As well as filtering engine warns/errors, it’d be nice to be able to prevent certain types of errors from popping up (i.e. the many edge cases that can occur with larger games - objects sometimes being nil but it not really mattering anyway, but it logs anyway). Right now, you have to be super on top of every possible error in order to make proper use of the error analytics, since there’s a limit of 500 unique errors, and different names of objects/things in the messages counts towards this limit.
Being able to filter the engine errors out, or just any type of error in particular, would be amazing
