Commit 854d3eea authored by Alex Kalderimis's avatar Alex Kalderimis

Use consistent event names

Event names now all follow {verb}-{object} order.
parent ec9eb302
......@@ -10,7 +10,7 @@ module Projects
include RedisTracking
track_redis_hll_event :index,
name: 'i_ecosystem_jira_service_issue_list',
name: 'i_ecosystem_jira_service_list_issues',
feature: :usage_data_track_ecosystem_jira_service
before_action :check_feature_enabled!
......
......@@ -66,7 +66,7 @@ module EE
description: description
}
)
log_usage(:issue_create, current_user)
log_usage(:create_issue, current_user)
issue
end
end
......
......@@ -41,7 +41,7 @@ RSpec.describe Projects::Integrations::Jira::IssuesController do
it 'tracks usage' do
expect(Gitlab::UsageDataCounters::HLLRedisCounter)
.to receive(:track_event)
.with('i_ecosystem_jira_service_issue_list', values: user.id)
.with('i_ecosystem_jira_service_list_issues', values: user.id)
get :index, params: { namespace_id: project.namespace, project_id: project }
end
......
......@@ -163,7 +163,7 @@ RSpec.describe JiraService do
expect(Gitlab::UsageDataCounters::HLLRedisCounter)
.to receive(:track_event)
.with('i_ecosystem_jira_service_issue_create', values: user.id)
.with('i_ecosystem_jira_service_create_issue', values: user.id)
jira_service.create_issue('x', 'y', user)
end
......
......@@ -10,12 +10,12 @@
redis_slot: ecosystem
aggregation: weekly
feature_flag: usage_data_track_ecosystem_jira_service
- name: i_ecosystem_jira_service_issue_list
- name: i_ecosystem_jira_service_list_issues
category: ecosystem
redis_slot: ecosystem
aggregation: weekly
feature_flag: usage_data_track_ecosystem_jira_service
- name: i_ecosystem_jira_service_issue_create
- name: i_ecosystem_jira_service_create_issue
category: ecosystem
redis_slot: ecosystem
aggregation: weekly
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment