feat: refactor instrumentation options

[mario-launchdarkly]

Note

Adds an Options.Instrumentation config with per-instrument FeatureFlags and updates client factory to use it, with ExampleApp enabling specific instruments.

• API (Options):
  • Add FeatureFlag.isEnabled helper.
  • Introduce Options.Instrumentation with flags for urlSession, userTaps, memory, memoryWarnings, cpu, launchTimes.
  • Extend Options with new instrumentation property and initializer parameter (default .init()).
• Client Factory:
  • Replace autoInstrumentation.contains(...) checks with options.instrumentation.<instrument>.isEnabled for memoryWarnings, urlSession, launchTimes, memory, and cpu.
• ExampleApp:
  • Configure options.instrumentation to enable urlSession, userTaps, memory, memoryWarnings, launchTimes and disable cpu.

^{Written by Cursor Bugbot for commit dfd4291. This will update automatically on new commits. Configure here.}

[cursor]

Bug: User Taps Instrumentation Ignores Disable

The UserInteractionManager is unconditionally created and started, ignoring the options.instrumentation.userTaps configuration. All other instrumentation types (memory, cpu, urlSession, launchTimes, memoryWarnings) were refactored to check their corresponding instrumentation flags, but userTaps was missed. This causes user tap tracking to run even when disabled via instrumentation.userTaps = .disabled.

Sources/Observability/Client/ObservabilityClientFactory.swift#L112-L116

swift-launchdarkly-observability/Sources/Observability/Client/ObservabilityClientFactory.swift

Lines 112 to 116 in 5d7862c

	let userInteractionManager = UserInteractionManager(options: options) { interaction in
	interaction.startEndSpan(tracer: tracerDecorator)
	}
	userInteractionManager.start()

 

---

[cursor]

Bug: User interaction tracking cannot be disabled.

The UserInteractionManager is always created and started unconditionally, ignoring the options.instrumentation.userTaps setting. While other instrumentation types were refactored to check their respective instrumentation flags, userTaps was missed. This causes user tap tracking to run even when disabled, inconsistent with the refactored instrumentation options pattern.

Sources/Observability/Client/ObservabilityClientFactory.swift#L112-L116

swift-launchdarkly-observability/Sources/Observability/Client/ObservabilityClientFactory.swift

Lines 112 to 116 in dfd4291

	let userInteractionManager = UserInteractionManager(options: options) { interaction in
	interaction.startEndSpan(tracer: tracerDecorator)
	}
	userInteractionManager.start()

 

---