Skip to content

remove logs that cause logs quota exhaustion

Yurii Kondakov requested to merge remove_logs_that_cause_logs_quota_exhaustion into master

HOTFIX. We saw log quota exhaustion in prod. The biggest culprit was notification service traces. We have identified 3 log entries that appear to be causing the bulk of the issues and these should be removed

  1. Log message startswith "Notification process started for message with id" - from notification service
  2. Log message startswith "Start worker task : {messageId" - from core-lib-azure
  3. Log message startswith "End worker task duration(ms)" from core-lib-azure

Merge request reports