Skip to content

Logging improvements for the collator revamp#12282

Open
tdimitrov wants to merge 3 commits into
masterfrom
tsv-revamp-logging
Open

Logging improvements for the collator revamp#12282
tdimitrov wants to merge 3 commits into
masterfrom
tsv-revamp-logging

Conversation

@tdimitrov

Copy link
Copy Markdown
Contributor

Some logging updates:

  • Decrease log levels in wait_for_first_leaf to DEBUG, to avoid startup spam
  • Use warn_if_frequent for fetch errors
  • Log assignment changes on view change
  • pick_best_advertisement: trace logs for each outcome
  • update_view: log scheduling parent <-> assigned core mapping
  • update_view: log sp removal
  • handle_seconded_collation: logs for each error case
  • PeerManager: log reputation updates

Partially addresses #10402

…ntal:

- Decrease log levels in `wait_for_first_leaf` to DEBUG, to avoid startup spam
- Use `warn_if_frequent` for fetch errors
- Log assignment changes on view change
- pick_best_advertisement: trace logs for each outcome
- update_view: log scheduling parent <-> assigned core mapping
- update_view: log sp removal
- handle_seconded_collation: logs for each error case
- PeerManager: log reputation updates
@tdimitrov tdimitrov added T8-polkadot This PR/Issue is related to/affects the Polkadot network. A4-backport-unstable2604 Pull request must be backported to the unstable2604 release branch A4-backport-stable2606 Pull request must be backported to the stable2606 release branch labels Jun 5, 2026
@tdimitrov tdimitrov requested a review from alindima June 5, 2026 12:12
@tdimitrov

Copy link
Copy Markdown
Contributor Author

/cmd prdoc --audience node_dev --bump patch

@sandreim sandreim left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM, but not sure about the INFO level additions.


let scheduled_paras = collation_manager.assignments();

gum::info!(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why is this important to be logged at info level ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Ok, let's downgrade this to debug too.
My initial idea was to have information about assignments on INFO level, but it will be too noisy.

);

if old_assignments != new_assignments {
gum::info!(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why not debug ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

You are right, this is not a good idea.
groupRotation is 10 on polkadot, so we'll have this log ~each minute, which is not worth it. I'll downgrade it to debug.

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

Labels

A4-backport-stable2606 Pull request must be backported to the stable2606 release branch A4-backport-unstable2604 Pull request must be backported to the unstable2604 release branch T8-polkadot This PR/Issue is related to/affects the Polkadot network.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants