feat(core): Add non-breaking flow execution statistics collection#4
Merged
madawei2699 merged 2 commits intomainfrom Mar 25, 2025
Merged
feat(core): Add non-breaking flow execution statistics collection#4madawei2699 merged 2 commits intomainfrom
madawei2699 merged 2 commits intomainfrom
Conversation
Pull Request Test Coverage Report for Build 3ff6c10190ba671e234d76aebc6471aabc2523d8-PR-4Details
💛 - Coveralls |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a new flow execution statistics feature without breaking existing APIs. It is the first phase of implementing execution limits and monitoring capabilities.
Key Changes
ExecutionStatsmodule for tracking flow execution metricsFlowmodule with zero API changesFlow.get_last_execution_stats/0Future Enhancements
This lays the foundation for future phases:
The changes are implemented in a backward-compatible manner, ensuring existing code continues to work without modification while enabling new monitoring capabilities.