Skip to content

Conversation

@pjiang-dev
Copy link
Contributor

@pjiang-dev pjiang-dev commented Oct 27, 2025

fixes #25093

We noticed 2x increase in log volume likely due to this change: https://github.com/argoproj/argo-cd/pull/21442/files#diff-9312ec23ecb354e9d5c3c7434a6b0d37f6c5d780153e7f1f28221af48ddde453

I think logCtx.Info("Reconciliation completed") should be DEBUG level because

  1. we can use argocd_app_reconcile metrics to track this stat already
  2. Can still see other state change logging like refreshing, syncing, status updates
  3. Still have an option to show it with DEBUG logs.

Same with logCtx.Info("GetRepoObjs stats") - i don't see too much value in having this as log level INFO as well. This is also contributing to high volume as it appears on every reconcile.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@pjiang-dev pjiang-dev requested a review from a team as a code owner October 27, 2025 19:54
@bunnyshell
Copy link

bunnyshell bot commented Oct 27, 2025

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

@codecov
Copy link

codecov bot commented Oct 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.22%. Comparing base (05ccc01) to head (ed29436).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #25092      +/-   ##
==========================================
+ Coverage   60.89%   62.22%   +1.33%     
==========================================
  Files         351      351              
  Lines       60489    49213   -11276     
==========================================
- Hits        36832    30624    -6208     
+ Misses      20736    15660    -5076     
- Partials     2921     2929       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

"time_ms": reconcileDuration.Milliseconds(),
"patch_ms": patchDuration.Milliseconds(),
"setop_ms": setOpDuration.Milliseconds(),
}).Info("Reconciliation completed")
Copy link
Member

Choose a reason for hiding this comment

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

i personally look at the times that are emitted by this log message. they can be helpful in seeing where the application controller is spending its time during a reconcile.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@rumstead Since i'm changing this log line to DEBUG it will still be available, but users need to turn on debug logs.
Would that be sufficient or do you feel like this is a must have log as INFO?

Copy link
Member

Choose a reason for hiding this comment

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

Setting the logging to debug is a reactive step. I see the log line going back to 2019. Why do we feel it's too verbose now?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

isn't that just adding 3 additional fields? project, namespace, and application name?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, those additional field will make the log line longer, but you're right its likely not significant enough to cause the volume increase.

I think we can go ahead and close this ticket as these logs are worth keeping. Thanks for the review anyway @rumstead

Signed-off-by: Peter Jiang <[email protected]>
@pjiang-dev pjiang-dev requested review from a team as code owners October 28, 2025 17:03
@pjiang-dev pjiang-dev closed this Oct 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ArgoCD has significantly increased log volume

3 participants