-
Notifications
You must be signed in to change notification settings - Fork 22
Add freshly fetched configs from config poller #1441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds logging of freshly fetched configuration data from the config poller. The change enhances the debug logging output to include the actual configuration snapshots that were retrieved during the batch refresh operation.
- Added
chainConfigSnapshotandsourceChainConfigsto debug log output
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| c.lggr.Debugw("Batch refreshed configs via chainAccessor", | ||
| "chain", chainSel, | ||
| "latency", time.Since(start), | ||
| "chainConfigSnapshot", chainConfigSnapshot, |
Copilot
AI
Dec 3, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Logging potentially sensitive configuration data at debug level could expose internal system details in production logs. Consider whether this data contains sensitive information (API keys, private endpoints, etc.) that should not be logged, or restrict this logging to trace level instead of debug level.
| "chainConfigSnapshot", chainConfigSnapshot, | |
| "chainConfigSnapshot", chainConfigSnapshot, | |
| ) | |
| c.lggr.Tracew("Batch refreshed sourceChainConfigs via chainAccessor", | |
| "chain", chainSel, |
|
Uh oh!
There was an error while loading. Please reload this page.