chore: Adds additonal properties in duo workflow event definitions
What does this MR do and why?
Adds additional properties in duo workflow event definitions
References
Please include cross links to any resources that are relevant to this MR This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
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.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
|
|
How to set up and validate locally
-
Send workflow start event with
ai_workflowsscoped token via REST api.POST /api/v4/usage_data/track_event Host: GDK_HOST Content-Type: application/json { "event": "start_duo_workflow_execution", "additional_properties": { "workflow_id": 99 } } -
It should return 200 OK response.
-
To check metrics like total workflow executions and total workflow executions per distinct user
require_relative 'spec/support/helpers/service_ping_helpers.rb' ServicePingHelpers.get_current_usage_metric_value("counts.count_total_start_duo_workflow_execution_monthly") # total number of workflow start events ServicePingHelpers.get_current_usage_metric_value("redis_hll_counters.count_distinct_user_id_from_start_duo_workflow_execution_monthly") # total number of workflows per distinct user