Skip to content

Migrate compliance_unique_visits_data to use Metric Instrumentation class

Michał Wielich requested to merge michold-migrate-compliance-instr into master

What does this MR do and why?

Related to #339318 (closed)

Move events from usage_data to new instrumentation_class pattern.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

  1. Generate service ping payload data 
    data = ServicePing::BuildPayload.new.execute
  2. Verify that data contains all the required compliance keys (it should be the same keys and values on both MR branch and master branch) 
     data['compliance_unique_visits']
 => {"compliance_unique_visits_for_any_target"=>7,
  "a_compliance_audit_events_api"=>1,
  "g_compliance_dashboard"=>3,
  "g_compliance_audit_events"=>3,
  "i_compliance_audit_events"=>4,
  "i_compliance_credential_inventory"=>5,
  "compliance_unique_visits_for_any_target_monthly"=>7}

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Michał Wielich

Merge request reports