feat(analytics): add source, service_call and execution_mode to connector events

[gopikrishna000]

Closes #12717

What

Tags every connector event with three low-cardinality dimensions so downstream analytics can attribute each call:

column	values
source	hyperswitch
service_call	external (direct connector HTTP) / internal (UCS gRPC)
execution_mode	primary / shadow

How

• New EventSource and ServiceCall enums in common_enums (reusing the existing ExecutionMode), plus three fields on ConnectorEvent.
• Direct connector calls → hyperswitch / external / primary.
• UCS gRPC calls → hyperswitch / internal with the execution mode of the leg.
• The UCS gRPC event is now emitted for the shadow leg as well (previously only the primary leg), so shadow executions are captured as hyperswitch / internal / shadow.
• Adds the matching LowCardinality(String) columns to the connector_events ClickHouse queue, tables and materialized views.

Behaviour matrix

mode	event(s) emitted (source / service_call / execution_mode)
Direct	hyperswitch / external / primary
UCS primary	hyperswitch / internal / primary
Shadow — primary leg	hyperswitch / external / primary
Shadow — UCS leg	hyperswitch / internal / shadow

Testing

cargo check -p router -p hyperswitch_interfaces -p common_enums passes.

Companion

UCS side: juspay/hyperswitch-prism#1501

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
crates/router/src/core/unified_connector_service.rs	86% smaller
crates/analytics/docs/clickhouse/scripts/connector_events.sql	Unsupported file format
crates/common_enums/src/enums.rs	0% smaller
crates/hyperswitch_interfaces/src/api_client.rs	0% smaller
crates/hyperswitch_interfaces/src/events/connector_api_logs.rs	0% smaller

[XyneSpaces]

Automated Review Summary

PR: feat(analytics): add source, service_call and execution_mode to connector events
Reviewer: PR Reviewer Agent

---

Verification Passed

✅ Schema consistency — New columns added to all connector_events tables (queue, main, audit, payout_audit) and all materialized views

✅ Enum naming — EventSource and ServiceCall use full words, no abbreviations

✅ Default values — Proper #[default] attributes on enum variants match the PR's behavior matrix

✅ Shadow leg visibility — Removing the ExecutionMode::Primary guard and adding the execution_mode field captures shadow executions as documented

✅ Error context preservation — No error chains dropped; all connector errors flow through unchanged

---

Findings

🔍 1. Consider adding a CHANGELOG entry

The behavioral change (shadow leg now emits events) is significant for analytics consumers. Document this in the CHANGELOG or migration notes.

---

Verdict: ✅ Approve — Clean, well-documented analytics enhancement. No blocking issues.