Stop logging errors in analytics schema
Closed, DeclinedPublic
Actions

Assigned To

None

Authored By

	Sgs
	Jan 12 2022, 12:25 PM

Description

From comment in T238945: Newcomer tasks: log error details:

In T238945#6872596, @Tgr wrote:

Prioritization aside, there is a proper JS error logging infrastructure now, so eventually errors should probably be logged there and not into our analytics schema.

An example can be found in ext.growthExperiments.Homepage.Mobile.js

api.getExtraDataFromPcs( taskPreviewData ).then( function ( task ) {
    ...
}, function ( jqXHR, textStatus, errorThrown ) {
    // Error loading the task
    if ( shouldLog ) {
        homepageModuleLogger.log( 'suggested-edits', 'mobile-summary', 'se-task-pseudo-impression',
            { type: 'error', errorMessage: textStatus + ' ' + errorThrown } );
    }
} );

What's the goal of tracking se-task-pseudo-impression as analytics data? Could we completely remove this kind of event form the analytics schema?