Analytics: Reduce Error Report Noise With Custom Rules and First Seen Version Tracking

This topic was automatically opened after 10 minutes.

This may seem insignificant to most but this is a fantastic feature. I have several games that suffer from pretty noisy error reports which made it much more difficult to debug anything using it. Great work.

Can we have a toggle to ignore errors from sources we can’t control? A built-in button filtering out coresciript or Roblox-specific errors or warnings would be great, since that’s 90% of all errors in my logs and I have to manually sift through them to find errors that I can actuall fix.

Does this just convert the Error Message into the Output Message? Does Group not create a place that I can expand and collapse and see the raw errors of? Also will there be individual analytic view permissions to assign?

You can use the “Ignore error” option by clicking on the context menu (three dots) for any row on the error table. Or you can create your own custom rules that apply to a wider range. If you create a rule with expression CoreScripts.* and choose to ignore, any error message that has CoreScripts in i

Yes only impacts the output message you see on the error reports page

This is great, thanks for sharing the regular expressions. I’ve been figuring this out by my own, good to have a post as a cheat sheet. So technically with grouping I could group the errors that have custom stuff like player username?

This is a really good update. Its surprisingly not buns

Yes and we recommend you to group them. Error reports page shows only top 500 errors by count and new errors since only shows top 100 new by version. If you group errors efficiently, you might see some types of errors occur very frequently.

quazotheduck: Click the context menu (three dots) on any row and select “Ignore”. Going forward this error won’t be included in the table or on the chart. Can we un-ignore an error? Can we view the list of ignored errors?

quazotheduck: “New errors since” filter Thanks! The “New errors since” along with “First seen version” will be so helpful. I am already using to retroactively find latest introduced errors in our updates

thank you i probably needed this image 462×209 7.04 KB

Yes ignored errors should be on your Rules tab. You can remove them later too.

I really needed this. My “Failed to load sound” errors were up in the tens of millions and completely drowning out all of the other errors that are actually from the scripts that I wrote. I’ve created a lot of rules for ignored errors but they are still there after I refreshed. Does it take a while

Hi: The rules will start to apply all ongoing errors. Old errors that have been showing will not be removed but if you wait for a few minutes and check last 1 hour data you should be able to see those errors are not showing up anymore. You can confirm by keyword search.

I’m aware that this option exists, but there may be other errors I haven’t ignored or new kinds of errors added in the future I have to manually add to the filter (which is a point of friction). It would be helpful if there was some premade filter that automatically filters out all of these that we

is this internal Roblox error, which should be ignored? image 1474×136 12.2 KB

this is an AMAZING update, no longer having to manually filter through errors or determine which ones even apply to the newest updates, especially with how often internal errors are great job roblox, this might be another great week for developers

Yes, this is a core script that should ignored since you can’t do anything to prevent it.