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:
jackqdyulei
2018-06-13 13:14:46 -07:00
parent a9b742dd53
commit 5f6837ff46
2 changed files with 2 additions and 2 deletions

View File

@@ -157,7 +157,7 @@ public class AnomalyDetectionJobService extends JobService {
metricsFeatureProvider.action(context, metricsFeatureProvider.action(context,
MetricsProto.MetricsEvent.ACTION_ANOMALY_IGNORED, MetricsProto.MetricsEvent.ACTION_ANOMALY_IGNORED,
packageName, packageName,
Pair.create(MetricsProto.MetricsEvent.FIELD_CONTEXT, Pair.create(MetricsProto.MetricsEvent.FIELD_ANOMALY_TYPE,
anomalyInfo.anomalyType), anomalyInfo.anomalyType),
Pair.create(MetricsProto.MetricsEvent.FIELD_APP_VERSION_CODE, Pair.create(MetricsProto.MetricsEvent.FIELD_APP_VERSION_CODE,
versionCode)); versionCode));

View File

@@ -178,7 +178,7 @@ public class AnomalyDetectionJobServiceTest {
verify(mFeatureFactory.metricsFeatureProvider).action(mContext, verify(mFeatureFactory.metricsFeatureProvider).action(mContext,
MetricsProto.MetricsEvent.ACTION_ANOMALY_IGNORED, MetricsProto.MetricsEvent.ACTION_ANOMALY_IGNORED,
SYSTEM_PACKAGE, SYSTEM_PACKAGE,
Pair.create(MetricsProto.MetricsEvent.FIELD_CONTEXT, ANOMALY_TYPE), Pair.create(MetricsProto.MetricsEvent.FIELD_ANOMALY_TYPE, ANOMALY_TYPE),
Pair.create(MetricsProto.MetricsEvent.FIELD_APP_VERSION_CODE, VERSION_CODE)); Pair.create(MetricsProto.MetricsEvent.FIELD_APP_VERSION_CODE, VERSION_CODE));
} }