Use FIELD_ANOMALY_TYPE instead of FIELD_CONTEXT
We did it for general anomaly however not the whitelisted one. This CL fixes it. Change-Id: I6603ffbaf1d097b360c86406ae0675bfe8a20410 Fixes: 109804858 Test: RunSettingsRoboTests
This commit is contained in:
@@ -157,7 +157,7 @@ public class AnomalyDetectionJobService extends JobService {
|
||||
metricsFeatureProvider.action(context,
|
||||
MetricsProto.MetricsEvent.ACTION_ANOMALY_IGNORED,
|
||||
packageName,
|
||||
Pair.create(MetricsProto.MetricsEvent.FIELD_CONTEXT,
|
||||
Pair.create(MetricsProto.MetricsEvent.FIELD_ANOMALY_TYPE,
|
||||
anomalyInfo.anomalyType),
|
||||
Pair.create(MetricsProto.MetricsEvent.FIELD_APP_VERSION_CODE,
|
||||
versionCode));
|
||||
|
Reference in New Issue
Block a user