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

Standardize User Identification Field in Logs Collection for Consistent Querying #2246

Open
6 of 10 tasks
vinit717 opened this issue Nov 11, 2024 · 0 comments · May be fixed by #2226
Open
6 of 10 tasks

Standardize User Identification Field in Logs Collection for Consistent Querying #2246

vinit717 opened this issue Nov 11, 2024 · 0 comments · May be fixed by #2226

Comments

@vinit717
Copy link
Member

vinit717 commented Nov 11, 2024

Issue Description

Currently, the logs collection includes two different fields, createdBy and userId, for user identification within the meta field. This inconsistency complicates queries for logs associated with specific users, as it requires checking both fields. We need to standardize the field name to userId across all log entries.

Expected Behavior

All entries in the logs collection should use a consistent field, userId, for user identification within the meta field. This will allow for uniform querying of logs by userId without having to handle cases where createdBy is used instead.

Current Behavior

Some documents in the logs collection use meta.createdBy while others use meta.userId. This inconsistency makes it more complex to fetch logs for a user, as queries need to account for both fields.

Screenshots

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Additional Information

Checklist

  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.
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 a pull request may close this issue.

1 participant