Add structured log event emitted when a creator key TTL extension is triggered#567
Open
jaynomyaro wants to merge 2 commits into
Open
Add structured log event emitted when a creator key TTL extension is triggered#567jaynomyaro wants to merge 2 commits into
jaynomyaro wants to merge 2 commits into
Conversation
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
1 participant
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.
Summary
Adds a structured log event whenever a creator key TTL (Time-To-Live) extension is triggered. This improves observability by making TTL extension operations traceable for monitoring, debugging, and auditing purposes.
Changes
Added a structured log event that is emitted whenever a creator key TTL is successfully extended.
Included relevant metadata in the log event, such as:
Creator identifier/key.
Storage key affected.
Previous TTL value (where available).
Updated TTL value.
Ledger sequence or timestamp (where applicable).
Ensured the event is emitted only after a successful TTL extension.
Standardized the log format to align with existing structured logging conventions.
Why
TTL extensions are important lifecycle events for contract storage but were previously not visible through structured logs. Emitting a dedicated event improves operational visibility, simplifies debugging, and enables downstream monitoring and audit tooling without affecting contract behavior.
Testing
Added unit tests to verify the structured log event is emitted when a creator key TTL extension occurs.
Verified the emitted event contains the expected metadata.
Confirmed no log event is emitted when the TTL extension is skipped or fails.
Verified existing contract functionality remains unchanged.
Closed #553