Summary

Implements a pluggable telemetry logging system for the Trigger Actions Framework to track Salesforce limits and performance metrics during trigger action execution. This feature addresses issue#176 by providing developers with debugging and performance monitoring capabilities.

Key Features

• ITriggerActionTelemetryLogger interface for pluggable telemetry implementations
• Default LimitLogger implementation tracking SOQL queries, DML statements, CPU time, and heap usage
• TelemetryContext class providing execution metadata (action class, operation, sObject type, record count)
• Enable_Telemetry__c checkbox field to enable/disable telemetry per trigger action
• Telemetry_Logger_Class__c text field to specify custom logger implementations
• Namespace-aware permission checking for improved package compatibility

Implementation Details

• Telemetry logging occurs at START and FINISH phases of trigger action execution
• Graceful fallback to LimitLogger if custom logger class fails to instantiate
• Debug-level logging for minimal performance impact
• Comprehensive test coverage with all 147 tests passing
• Compatible with existing trigger actions without requiring changes

Testing

• ✅ All existing tests continue to pass (147/147)
• ✅ New test classes added for LimitLogger and telemetry functionality
• ✅ Successfully deployed to scratch org without issues
• ✅ Namespace safety validated with permission checking enhancements

Usage Example

// Enable telemetry in Custom Metadata TypeTrigger_Action__mdtmyAction=newTrigger_Action__mdt(Apex_Class_Name__c='MyTriggerAction',Enable_Telemetry__c=true,Telemetry_Logger_Class__c='LimitLogger'// Optional, defaults to LimitLogger);

Sample debug output:

[START] BEFORE_INSERT on Account.MyTriggerAction (5 records) - Queries: 0/100, DML: 0/150, CPU: 12/10000ms, Heap: 2048/6000000bytes[FINISH] BEFORE_INSERT on Account.MyTriggerAction (5 records) - Queries: 2/100, DML: 0/150, CPU: 45/10000ms, Heap: 3072/6000000bytes

Test plan

• All existing tests pass (147/147 tests)
• New telemetry functionality properly tested
• Scratch org deployment successful
• No breaking changes to existing functionality
• Telemetry can be enabled/disabled per trigger action
• Custom logger classes can be specified and fall back gracefully
• Namespace-aware permission checking works correctly

🤖 Generated withClaude Code