Skip to content

Conversation

@raymondkfcheung
Copy link
Contributor

@raymondkfcheung raymondkfcheung commented Jun 3, 2025

This PR replaces log with tracing instrumentation on XCM-related modules to significantly improve debugging capabilities for XCM execution flows.

Continues #8724 and partially addresses #6119 by providing structured logging throughout XCM components, making it easier to diagnose execution failures, fee calculation errors, and routing issues.

Key Features

  • Consistent targets: All components use predictable xcm::* log targets
  • Structured fields: Uses ?variable syntax for automatic Debug formatting
  • Zero runtime impact: No behavioural changes, only observability improvements

@raymondkfcheung raymondkfcheung requested a review from a team as a code owner June 3, 2025 13:13
@raymondkfcheung raymondkfcheung marked this pull request as draft June 3, 2025 13:13
@raymondkfcheung raymondkfcheung self-assigned this Jun 3, 2025
@raymondkfcheung raymondkfcheung added the T6-XCM This PR/Issue is related to XCM. label Jun 3, 2025
@raymondkfcheung raymondkfcheung changed the title Ray check semver tests Add comprehensive tracing to XCM-related modules Jun 3, 2025
@raymondkfcheung raymondkfcheung changed the title Add comprehensive tracing to XCM-related modules Add comprehensive tracing to XCM components Jun 3, 2025
@raymondkfcheung raymondkfcheung moved this to In Progress in Bridges + XCM Jun 3, 2025
@raymondkfcheung raymondkfcheung changed the title Add comprehensive tracing to XCM components Add comprehensive tracing to XCM-related modules Jun 3, 2025
@raymondkfcheung
Copy link
Contributor Author

/cmd prdoc --audience runtime_dev --bump patch

@raymondkfcheung raymondkfcheung marked this pull request as ready for review June 4, 2025 15:20
@paritytech-review-bot paritytech-review-bot bot requested a review from a team June 4, 2025 15:21
@raymondkfcheung raymondkfcheung moved this from In Progress to In-Review in Bridges + XCM Jun 6, 2025
@raymondkfcheung raymondkfcheung force-pushed the ray-check-semver-tests branch from 980d46b to 021d32a Compare June 9, 2025 15:41
@paritytech-review-bot paritytech-review-bot bot requested a review from a team June 24, 2025 15:56
@raymondkfcheung raymondkfcheung requested a review from karolk91 June 25, 2025 08:53
@raymondkfcheung raymondkfcheung changed the title Add comprehensive tracing to XCM-related modules Replace log with tracing to XCM-related modules Jun 25, 2025
@raymondkfcheung raymondkfcheung disabled auto-merge July 4, 2025 08:34
@raymondkfcheung raymondkfcheung requested a review from karolk91 July 4, 2025 15:57
@raymondkfcheung raymondkfcheung enabled auto-merge July 8, 2025 12:30
@raymondkfcheung raymondkfcheung requested a review from rosarp July 8, 2025 12:34
Copy link
Member

@rosarp rosarp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@raymondkfcheung Could you once check suggested changes.

@raymondkfcheung raymondkfcheung requested a review from rosarp July 10, 2025 10:33
@raymondkfcheung raymondkfcheung added this pull request to the merge queue Jul 10, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 10, 2025
@raymondkfcheung raymondkfcheung added this pull request to the merge queue Jul 10, 2025
Merged via the queue into paritytech:master with commit 466149d Jul 10, 2025
264 of 265 checks passed
@raymondkfcheung raymondkfcheung deleted the ray-check-semver-tests branch July 10, 2025 13:35
@github-project-automation github-project-automation bot moved this from In-Review to Done in Bridges + XCM Jul 10, 2025
github-merge-queue bot pushed a commit that referenced this pull request Aug 4, 2025
This PR replaces `log` with `tracing` instrumentation on `xcm-emulator`
by providing structured logging.

Continues #8732
alvicsam pushed a commit that referenced this pull request Oct 17, 2025
This PR replaces `log` with `tracing` instrumentation on XCM-related
modules to significantly improve debugging capabilities for XCM
execution flows.

Continues #8724 and partially addresses #6119 by providing structured
logging throughout XCM components, making it easier to diagnose
execution failures, fee calculation errors, and routing issues.

## Key Features

- **Consistent targets**: All components use predictable `xcm::*` log
targets
- **Structured fields**: Uses `?variable` syntax for automatic Debug
formatting
- **Zero runtime impact**: No behavioural changes, only observability
improvements
alvicsam pushed a commit that referenced this pull request Oct 17, 2025
This PR replaces `log` with `tracing` instrumentation on `xcm-emulator`
by providing structured logging.

Continues #8732
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T6-XCM This PR/Issue is related to XCM.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants