Monitor usage ping on 13.5

Previous #229464 (closed)

Fix and check new usage counters which time out

The usage ping on 2020-09-08 for gitlab.com is shared in g_telemetry slack channel.

• check Product analytics reviews pending
• 618: "user_container_scanning_jobs": -1,
• 619: "user_dast_jobs": -1,
• 620: "user_dependency_scanning_jobs": -1,
• 621: "user_license_management_jobs": -1,
• 622: "user_sast_jobs": -1,
• 623: "user_secret_detection_jobs": -1,
• 634: "ci_builds": -1,
• 774: "sast_pipeline": -1,
• 775: "dependency_scanning_pipeline": -1,
• 776: "container_scanning_pipeline": -1,
• 777: "dast_pipeline": -1,
• 778: "secret_detection_pipeline": -1,
• 779: "coverage_fuzzing_pipeline": -1,
• 789: "ci_builds": -1,

• redis_hll_counters
• dast_on_demand_pipelines @philipcunningham

New counters

• user_preferences_user_gitpod_enabled
• projects_creating_incidents @seanarnold
• merged_merge_requests_using_approval_rules @asubramanian1
• g_project_management_issue_added_to_epic g_project_management_issue_removed_from_epic g_project_management_issue_changed_epic Issues to Epics @mdelaossa
• api_fuzzing_scans !43763 (merged) @mikeeddington
• api_fuzzing_scans Optimization issue #263306 (closed) @caneldem
• pg_system_id PostgreSQL system identifier in usage ping @stanhu
• projects_incident_sla_enabled !45092 (diffs) @seanarnold

How to test

1. In versions app console RawUsageData.find(uuid: '')
2. on gprd rails console

Time.now
[Time.now, aapayload = Gitlab::UsageData.to_json(force_refresh: true), Time.now]
puts aapayload

## Post to versions app
aares = Gitlab::HTTP.post( 'https://version.gitlab.com/usage_data', body: aapayload, allow_local_requests: true, headers: { 'Content-type' => 'application/json' })

usage_data_id: 21635202

/bin/herokuish procfile exec rails console

puts UsageData.select(:recorded_at, :app_server_type).where(hostname: 'gitlab.com', uuid: 'ea8bf810-1d6f-4a6a-b4fd-93e8cbd8b57f').order('id desc').limit(5).to_json

puts UsageData.find(21635202).raw_usage_data.payload.to_json

What to do if you get mentioned?

In this issue we keep the track of new metrics added to usage ping and metrics that are timing out.

If you get mentioned please check the failing metric and open an optimization issue.