Subversion Repositories SmartDukaan

Last modification

• Rev 37491 – 37 d 16 h
• Author: amit

• Log message:

  errors: ship ERROR events to GlitchTip via the log4j2 Sentry appender
  
  io.sentry:sentry-log4j2:7.22.6 in all three deployables. Pinned to 7.x because
  8.x drops Java 8; verified class major version 52.
  
  minimumEventLevel=ERROR is load-bearing. It only became safe after r37490 moved
  business validations to WARN -- 32% of the ERROR stream was HTTP 400s where the
  user is simply told what to fix, and sending those would have made "insufficient
  balance" the top issue and buried real bugs. Breadcrumbs come from INFO so an
  issue arrives with the log lines that preceded it.
  
  Attached to the application loggers only; framework noise is not our bug.
  
  web's log4j2.xml is committed here. cron's and fofo's are held back: both carry
  uncommitted local development paths (a user.home expansion, and an absolute
  /Users path) that would break production logging and the Alloy log tailing.
  Their Sentry blocks are staged locally and should land with whoever owns those
  path edits.