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

FEAT(ws): Improve monitoring report format #339

Open
vfedotovs opened this issue Nov 6, 2024 · 0 comments
Open

FEAT(ws): Improve monitoring report format #339

vfedotovs opened this issue Nov 6, 2024 · 0 comments

Comments

@vfedotovs
Copy link
Owner

To enhance the readability of your report, consider organizing it into a structured table format and using clearer column headings. Here’s an improved version for easier readability:

Example Report Format

Date TSA Count [A] LA TBL Count [B] AinB Count [C] KLAT (A not in B) [D] New Ads (A not in B) Removed from LA (B not in A) RA TBL Count
2024-11-02 58 58 58 0 0 0 1749
2024-11-03 58 58 57 1 1 1 1750
2024-11-04 60 58 57 3 3 1 1751
2024-11-05 58 60 57 1 1 3 1754
2024-11-06 58 58 56 2 2 2 1756

Explanation of Columns

  • TSA Count [A]: Total count of entries in TSA.
  • LA TBL Count [B]: Count of entries in LA TBL.
  • AinB Count [C]: Count of entries present in both TSA and LA TBL.
  • KLAT (A not in B) [D]: Entries in TSA but not in LA TBL.
  • New Ads (A not in B): Number of new ads found in TSA that are not in LA TBL.
  • Removed from LA (B not in A): Number of entries removed from LA TBL but still in TSA.
  • RA TBL Count: Count of entries in RA TBL.

This approach highlights the key metrics and makes it easier to compare data day-by-day without repetitive labels.

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