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

Refactor User Logs for Timeline Feature and Standardize Log Collection #2193

Open
6 of 10 tasks
vinit717 opened this issue Oct 3, 2024 · 0 comments
Open
6 of 10 tasks
Assignees

Comments

@vinit717
Copy link
Member

vinit717 commented Oct 3, 2024

Issue Description

To implement a user timeline feature or any logs query functionality, we need to refactor the current user activity logs. The existing log storage is not consistent with the data model and lacks essential fields like metadata, timestamps, and proper key-value structure. The current logging implementation at certain functions is inadequate and needs to be refactored to align with the desired user timeline functionality.

Expected Behavior

  • Logs should follow a consistent data model with appropriate key-value pairs.
  • Each log entry should contain essential fields such as meta, created_at, and a precise timestamp etc.
  • Refactored logs should allow for a seamless generation of user timelines, capturing all relevant user activities.

Current Behavior

  • Logs are not stored in a structured manner and lack uniformity across different parts of the application.
  • Critical fields like meta, created_at, and timestamp are either missing or inconsistent.
  • This makes it challenging to build a reliable user timeline and track activity efficiently.

Screenshots

image
image

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Check existing log storage in functions where user activity is logged.
  2. Note the absence or inconsistency in key fields like meta and created_at, and body.

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

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.
@vinit717 vinit717 self-assigned this Oct 3, 2024
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

No branches or pull requests

1 participant