[ANALYTICS-485] Review caching time and its error handling of Analytic modules Created: 06/Jun/23  Updated: 06/Jun/23

Status: Open
Project: Analytics
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Lam Nguyen Bao Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates ANALYTICS-462 Evaluate metadata command monthly exe... Closed
is duplicated by ANALYTICS-462 Evaluate metadata command monthly exe... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: AuthorX Maintenance
Team: AuthorX

 Description   

Analytic modules have configuration for getting new metadata once a month by cron job (GA4, Adobe...).

The problems are:

  • We define the time by feeling (big assumption should be avoided). 
  • Metadata is purely text and it size is very small -> verify on GA4 metadata ~100kb. 

The caller catches error and log is written. In associate with cron job we may unaware of having error, it could take long time before we know something unusual. 

Possible solutions:

  • Metadata can be configured once a day.
  • Ensure there's notification once we had exception (wrap to custom exception and expect the error is shown on notifications app). 

Discussion
https://magnolia-cms.slack.com/archives/C04RAB1K3J5/p1685012491906329


Generated at Sun Feb 11 23:19:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.