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,
|
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));
|
||||||
|
@@ -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));
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user