Error Analytics : Player usernames are not filtered out in some cases, resulting in duplicate error entries

Bug Reports Creator Hub (create.roblox.com) Bugs
#1

Currently, as of 9/30/24, the error analytics Roblox provides in the creator dashboard does not always correctly filter out player usernames. For example, If an error message contains a reference to something inside a player’s avatar, their username is not filtered from that error message.

E.g. Humanoid is not a valid member of Model "Noble_Draconian"

This results in many duplicate unique error entries showing up in analytics, making it harder to look through queries.

Expected behavior

It is expected that player usernames would be filtered out from error messages, preventing duplicate errors from cluttering error analytics queries

Page URL: https://create.roblox.com/dashboard/creations/experiences/2799591695/analytics/errors?rangeType=Last1Day&tab=Gems&filter_LogSeverity=Error&filter_LogSource=Server

1 Like
#2

Hi:
The reason we do not regex that is because most of the time, the model name is the actual model used in game so regex it out will cause creators not knowing what exactly is wrong for the model.
Your case is very special and because it is already inside the model name, we cannot tell if it is a true model name or just a random player name. So merging all the errors like this together might be harmful for you to debug other issues. but we are trying to see if there is a more intelligent way for us to detect player name and remove it. We will get back to you later.

3 Likes
#3

Maybe we could have some sort of API where we can define a string formatting function? It would work similar to DataModel:BindToClose()

E.g.

local AnalyticsService = game:GetService("AnalyticsService")
local Players = game:GetService("Players")

AnalyticsService:FormatErrors(function(ErrorMessage)
	for _,Player in pairs(Players:GetPlayers()) do
		if string.find(ErrorMessage,Player.Name) ~= nil then
			return string.gsub(ErrorMessage,Player.Name,"<PlayerName>")
		end
	end
	
	return ErrorMessage
end)

The callback would be invoked whenever an error is about to be logged to analytics. A benefit of having an API like this is that developers can filter out their own cases where they have a unique model name, but don’t necessarily want it to show up as unique errors in analytics.

1 Like
#4

Thanks for the suggestion, we will consider this feature request balanced against the other projects we have planned on our roadmap

1 Like