Skip to content
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

Log percentage of users without selected_sites alongside the total count #3582

Merged
merged 1 commit into from
Oct 6, 2024

Conversation

Baalmart
Copy link
Contributor

@Baalmart Baalmart commented Oct 6, 2024

Description

To log the percentage of users without selected_sites alongside the total count

Changes Made

  • Total Users Processed: Introduced a new variable totalUsersProcessed to keep track of the total number of users processed.
  • Percentage Calculation: After processing all users, the script calculates the percentage of users without selected_sites
  • Formatted Logging: The log statement now includes both the total count and the percentage formatted to two decimal places.

Testing

  • Tested locally
  • Tested against staging environment
  • Relevant tests passed: [List test names]

Affected Services

  • Which services were modified:
    • Auth Service

API Documentation Updated?

  • Yes, API documentation was updated
  • No, API documentation does not need updating

Additional Notes

With these modifications, the script will now log not only the count of users without selected_sites but also what percentage that count represents of all processed analytics users.

Summary by CodeRabbit

  • New Features

    • Enhanced logging of user preferences, now including a percentage of users without selected sites.
  • Bug Fixes

    • Streamlined the data aggregation process for improved performance.
  • Documentation

    • Updated logging messages to provide clearer context on user preferences processed.

Copy link
Contributor

coderabbitai bot commented Oct 6, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request focus on the logUserPreferences function within the preferences-log-job.js file. The modifications involve removing the allUsersWithoutSelectedSites array and introducing a new variable, totalUsersProcessed, to keep track of the number of users processed. The logic for filtering users remains unchanged, but the results are now counted with totalCountWithoutSelectedSites. Additionally, the logging output has been enhanced to display the percentage of users without selected sites, providing better context without altering the core functionality.

Changes

File Path Change Summary
src/auth-service/bin/jobs/preferences-log-job.js Removed allUsersWithoutSelectedSites array; added totalUsersProcessed and totalCountWithoutSelectedSites; updated logging to include percentage of users without selected sites.

Possibly related PRs

  • Reduced Log Frequency #3575: This PR modifies the logUserPreferences function in the same file as the main PR, introducing a new variable for tracking users without selected sites and optimizing logging behavior, which is directly related to the changes made in the main PR.

Suggested reviewers

  • Codebmk
  • OchiengPaul442

🎉 In the code where preferences flow,
A count of users now we know!
With logs that shine and data bright,
The changes bring a clearer sight.
No more arrays to hold the past,
Just totals counted, built to last! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

codecov bot commented Oct 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.68%. Comparing base (665c2d7) to head (7c508d5).
Report is 9 commits behind head on staging.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           staging    #3582      +/-   ##
===========================================
+ Coverage    29.66%   29.68%   +0.01%     
===========================================
  Files          185      185              
  Lines        25016    25016              
  Branches      3315     3315              
===========================================
+ Hits          7421     7426       +5     
+ Misses       17471    17466       -5     
  Partials       124      124              

see 1 file with indirect coverage changes

Copy link
Contributor

github-actions bot commented Oct 6, 2024

Auth-service changes in this PR available for preview here

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (3)
src/auth-service/bin/jobs/preferences-log-job.js (3)

44-47: Nicely refactored user filtering logic.

The use of the filter method here is a great improvement. It makes the code more readable and functional. Well done!

A small optimization suggestion: Consider using Array.prototype.some() for a slight performance boost, as it can short-circuit the iteration:

const usersWithoutSelectedSites = users.filter((user) => {
  const preference = preferencesMap.get(user._id.toString());
  return !preference || !preference.selected_sites.some(site => !isEmpty(site));
});

This change would stop checking selected_sites as soon as it finds a non-empty site.


57-61: Well-implemented percentage calculation.

The percentage calculation logic is sound and includes a safeguard against division by zero. Rounding to two decimal places provides a good balance between precision and readability.

To enhance readability further, consider extracting the calculation into a separate function:

const calculatePercentage = (part, whole) => 
  whole > 0 ? ((part / whole) * 100).toFixed(2) : '0.00';

// Usage
const percentageWithoutSelectedSites = calculatePercentage(
  totalCountWithoutSelectedSites,
  totalUsersProcessed
);

This abstraction would make the main function body cleaner and the calculation reusable if needed elsewhere.


64-64: Informative and comprehensive logging statement.

The updated log message successfully incorporates both the total count and the percentage of users without selected sites. This enhancement significantly improves our ability to monitor and analyze user engagement.

To further improve clarity, consider slightly restructuring the message:

logger.info(
  `💔💔 Users without selected_sites: ${totalCountWithoutSelectedSites} (${percentageWithoutSelectedSites}%) out of ${totalUsersProcessed} total Analytics users.`
);

This format provides a clear breakdown of the statistics and explicitly mentions the total number of users processed.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 44b54da and 7c508d5.

📒 Files selected for processing (1)
  • src/auth-service/bin/jobs/preferences-log-job.js (2 hunks)
🔇 Additional comments (2)
src/auth-service/bin/jobs/preferences-log-job.js (2)

17-17: Excellent addition of the totalUsersProcessed variable.

This new variable is a thoughtful inclusion that aligns perfectly with the PR's objective. It will enable the calculation of the percentage of users without selected sites, enhancing our analytics capabilities.


51-51: Proper increment of totalUsersProcessed.

This line correctly increments the total count of processed users after each batch. It's well-placed within the loop to ensure an accurate count. This addition is crucial for calculating the percentage later on.

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

Successfully merging this pull request may close these issues.

1 participant