Expose Last Successful Poll Timestamp - #660
Conversation
closes Core-Foundry#621 - Added lastSuccessfulPollAt tracking to EventSubscriber - Extended HealthReport to include lastSuccessfulPollAt - Fixed syntax/indentation errors in index.ts - Ensures failed polls do not update the timestamp Closes Core-Foundry#621
|
@najeebullahii Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
closes Core-Foundry#621 - Added lastSuccessfulPollAt tracking to EventSubscriber - Extended HealthReport to include lastSuccessfulPollAt - Fixed pre-existing syntax error (unclosed try block) in index.ts - Ensures failed polls do not update the timestamp Closes Core-Foundry#621
|
@maintainers I've implemented the feature to expose the last successful poll timestamp as specified in issue #621. Implementation Summary:
Note on CI Failures: The implementation strictly follows the acceptance criteria and is additive-only (no breaking changes to existing functionality). Ready for review! |
|
@maintainers I've implemented the feature to expose process uptime in the health information as specified in issue #622. Implementation Summary:
Note on CI Failures: The implementation strictly follows the acceptance criteria and is additive-only (no breaking changes to existing functionality). Ready for review! |
closes #621
Overview
Related Issue
Closes #
Changes
Verification
How to Test
Checklist
maincargo fmt --allrun (if Rust changes)npm run lintpasses (if TypeScript changes)