Exclude PrometheusAlerts in count of issues with alerts in service ping
What does this MR do and why?
Changes: This MR cleans up a portion of dead code related to the removal of devopsmonitor Category:Metrics features.
Scope: Any service ping metrics related to PrometheusAlert
records. We're going to be dropping the table referenced from Instrumentations::IssuesWithPrometheusAlertEvents
, which allows us to simplify the implementation of counts.issues_created_from_alerts
. After this merges, the reported value may initially drop, but that's expected and fine.
Context: The Metrics Dashboard (used for monitoring apps deploying using gitlab) was deprecated in 14.7 and removed from the product in 16.0. There are many more files to remove related to this cleanup, but this should be a self-contained chunk.
- grouprespond related issue: Metrics: Delete models & database tables/columns (#397142 - closed)
- Monitor:Metrics removal epic: Monitor: Metrics Deprecation and Removal (&10107)
- Reference MR with all related removals: Draft: Remove all remaining metrics dashboard-r... (!160325 - closed)
- Metrics removal is blocking cells: Drop old unused tables for prometheus alerts (#461838 - closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
How to set up and validate locally
These features were disabled in %16.0 behind the :remove_monitor_metrics
feature flag, and have been partially deleted since then. So there's nothing really to test here. It's no longer possible to set up these features.
Merge request reports
Activity
changed milestone to %17.3
assigned to @syasonik
added pipelinetier-1 label
added sectionanalytics label
- A deleted user
2 Warnings For the following files, a review from the Data team and Analytics Instrumentation team is recommended
Please check the analytics instrumentation Service Ping guide or the Snowplow guide.For MR review guidelines, see the Internal Analytics review guidelines.
spec/lib/gitlab/usage/metrics/instrumentations/issues_with_alert_management_alerts_metric_spec.rb
config/metrics/counts_all/20210216180441_issues_created_from_alerts.yml
ee/spec/lib/ee/gitlab/usage_data_spec.rb
lib/gitlab/usage/metrics/instrumentations/issues_with_alert_management_alerts_metric.rb
lib/gitlab/usage_data.rb
spec/lib/gitlab/usage_data_spec.rb
lib/gitlab/usage/metrics/instrumentations/issues_created_from_alerts_metric.rb
lib/gitlab/usage/metrics/instrumentations/issues_with_prometheus_alert_events.rb
The master pipeline status page reported failures in If these jobs fail in your merge request with the same errors, then they are not caused by your changes.
Please check for any on-going incidents in the incident issue tracker or in the#master-broken
Slack channel.1 Message CHANGELOG missing: If this merge request needs a changelog entry, add the
Changelog
trailer to the commit message you want to add to the changelog.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Category Reviewer Maintainer analytics instrumentation @pskorupa
(UTC+2, 6 hours ahead of author)
Maintainer review is optional for analytics instrumentation backend @subashis
(UTC-6, 2 hours behind author)
@partiaga
(UTC+2, 6 hours ahead of author)
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger Generated bygitlab_quality-test_tooling
.
Slow tests detected in this merge request. These slow tests might be related to this merge request's changes.Click to expand
Job File Name Duration Expected duration #7411658643 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 28.53 s < 27.12 s #7411635974 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 30.78 s < 27.12 s #7431746428 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 35.4 s < 27.12 s #7431774629 spec/lib/gitlab/usage_data_spec.rb#L454
Gitlab::UsageData.data gathers usage data 27.57 s < 27.12 s #7431774810 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 41.65 s < 27.12 s #7432319372 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 39.27 s < 27.12 s #7432319336 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 34.37 s < 27.12 s #7440308732 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 36.73 s < 27.12 s #7440308475 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 32.63 s < 27.12 s #7454458510 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 32.66 s < 27.12 s #7454458448 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 41.61 s < 27.12 s #7466966817 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 33.04 s < 27.12 s #7474286977 ee/spec/lib/ee/gitlab/usage_data_spec.rb#L214
Gitlab::UsageData usage_activity_by_stage_create includes accurate usage_activity_by_stage data 32.33 s < 27.12 s - A deleted user
added rspec:slow test detected label
- Resolved by Michał Wielich
@pskorupa Could you do analytics instrumentation & backend review for this?
requested review from @pskorupa
- Resolved by Sarah Yasonik
added 852 commits
-
3e84d005...38b7bccd - 850 commits from branch
master
- 385a999c - Exclude PrometheusAlerts in count of issues with alerts in service ping
- 37548f3d - Remove unneeded reference from usage_data.rb
-
3e84d005...38b7bccd - 850 commits from branch
requested review from @pskorupa
removed review request for @pskorupa
added pipeline:mr-approved label
added pipelinetier-3 label and removed pipelinetier-1 label
Before you set this MR to auto-merge
This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.
Before you set this MR to auto-merge, please check the following:
- You are the last maintainer of this merge request
- The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
- This pipeline is recent enough (created in the last 8 hours)
If all the criteria above apply, please set auto-merge for this merge request.
See pipeline tiers and merging a merge request for more details.
requested review from @10io
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for b4ed80caexpand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 127 | 0 | 12 | 0 | 139 | ✅ | | Plan | 70 | 0 | 0 | 0 | 70 | ✅ | | Verify | 43 | 0 | 2 | 0 | 45 | ✅ | | Govern | 71 | 0 | 0 | 0 | 71 | ✅ | | Data Stores | 30 | 0 | 1 | 0 | 31 | ✅ | | Package | 16 | 0 | 15 | 0 | 31 | ✅ | | Monitor | 8 | 0 | 0 | 0 | 8 | ✅ | | Secure | 2 | 0 | 0 | 0 | 2 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Manage | 0 | 0 | 1 | 0 | 1 | ➖ | | Fulfillment | 1 | 0 | 0 | 0 | 1 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 375 | 0 | 31 | 0 | 406 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-package-and-test:
test report for b4ed80caexpand test summary
+---------------------------------------------------------------------+ | suites summary | +----------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +----------------+--------+--------+---------+-------+-------+--------+ | GitLab Metrics | 2 | 0 | 1 | 0 | 3 | ✅ | | Monitor | 12 | 0 | 13 | 0 | 25 | ✅ | | Create | 270 | 0 | 34 | 0 | 304 | ✅ | +----------------+--------+--------+---------+-------+-------+--------+ | Total | 284 | 0 | 48 | 0 | 332 | ✅ | +----------------+--------+--------+---------+-------+-------+--------+
removed review request for @10io
added 505 commits
-
27a6ca5d...9ff78286 - 502 commits from branch
master
- 42e08cf2 - Exclude PrometheusAlerts in count of issues with alerts in service ping
- 023d1958 - Remove unneeded reference from usage_data.rb
- ef414bf0 - Remove reference to removed class
Toggle commit list-
27a6ca5d...9ff78286 - 502 commits from branch
requested review from @michold
- Resolved by Sarah Yasonik
added 1 commit
- b4ed80ca - Modify metric description to communicate updated query
mentioned in commit 27e4cffe
mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#7798 (closed)
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-production label and removed workflowproduction label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added groupanalytics instrumentation label and removed grouprespond label