Subversion Repositories SmartDukaan

Last modification

• Rev 37684 2026-09-17 17:53:22
• Author: amit

• Log message:

  Schedule the knowlarity insights pull here instead of in the fofo tomcat
  
  Eight times a day, unchanged times (11:40, 13:40, 15:40, 17:40, 18:40, 19:15,
  20:00, 20:40) so the shape of the day's data does not move. Calls
  KnowlarityInsightsSyncService (dao r37683).
  
  This lands next to KnowlarityCallMonitorScheduler on purpose: that one owns the
  WebSocket status feed into cs.rbm_break_log, this one owns the periodic KPI pull
  into cs.agent_daily_insight. They are the two halves of the same integration and
  were previously split across two processes for no reason other than history.
  
  What it replaces: the same schedule inside the fofo tomcat, where every run
  started an ~850MB headless chrome on a box that holds a -Xmx8g tomcat and a
  -Xmx2g cron jar on 16GB and has been kernel-OOM-killed twice. A run is now four
  HTTPS calls, ~2-3 seconds.
  
  ⚠ Only fires under --spring.profiles.active=scheduled; a one-shot CLI run does
  not start the schedulers.
  
  staging.properties gains the knowlarity block. It had NO knowlarity keys at all,
  which means the WebSocket call monitor has never run there either -- this fixes
  both. Same credentials as prod; there is no separate SR tenant for staging.
  
  Cadence is worth revisiting separately: the 8 slots were chosen when a run cost
  75 seconds and 850MB. At 2 seconds, hourly or every 15 minutes during the
  10:00-21:00 window (matching the call monitor) would be nearly free.