Skip to content

fix(timeline): #COCO-5341 add some log to track notification and flood trigger to debug production#969

Merged
vbillard91 merged 3 commits intodevelop-b2schoolfrom
fix-COCO-5341-add-logs-to-track-notification
Mar 5, 2026
Merged

fix(timeline): #COCO-5341 add some log to track notification and flood trigger to debug production#969
vbillard91 merged 3 commits intodevelop-b2schoolfrom
fix-COCO-5341-add-logs-to-track-notification

Conversation

@vbillard91
Copy link
Contributor

@vbillard91 vbillard91 commented Mar 4, 2026

Description

Add logs to know when a user trigger the antiflood + log when creating a notification

Fixes

https://edifice-community.atlassian.net/browse/COCO-5341

Type of change

Please check options that are relevant.

  • Chore (PATCH)
  • Doc (PATCH)
  • Bug fix (PATCH)
  • New feature (MINOR)

Which packages changed?

Please check the name of the package you changed

  • admin
  • app-registry
  • archive
  • auth
  • cas
  • common
  • communication
  • conversation
  • directory
  • feeder
  • infra
  • portal
  • session
  • test
  • tests
  • timeline
  • workspace

Tests

  1. Describe here the tests you performed
  2. Step by step
  3. With expected results

Reminder

  • Security flaws

  • Performance impacts (think bulk !)

  • Unit tests were replayed

  • Unit tests were added and/or changed

  • I have updated the reminder for the version including my modifications

  • All done ! 😃

@vbillard91 vbillard91 requested review from jcbe-ode and pb-jo March 4, 2026 09:39
Copy link
Contributor

@jcbe-ode jcbe-ode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Une question + quelques suggestions

if (sender == null || sender.startsWith("no-reply") || json.getBoolean("disableAntiFlood", false) || antiFlood.add(sender)) {
final boolean disableAntiflood = json.getBoolean("disableAntiflood", false);

log.info(String.format("[Timeline.add] Add new notification from sender %s with antiflood activation = %s from module %s for resources %s ",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ca va générer beaucoup de logs, non ?
Logger les cas où l'antiflood se déclenche pourrait-il suffire ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Une par notification, qui peut être à de multiple user. C'est nécessaire si on veut track correctement la situation sur les problèmes de "trop de notification"

vbillard91 and others added 2 commits March 4, 2026 11:31
Co-authored-by: jcbe-ode <67910608+jcbe-ode@users.noreply.github.com>
Co-authored-by: jcbe-ode <67910608+jcbe-ode@users.noreply.github.com>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 4, 2026

@vbillard91 vbillard91 merged commit 7c4294d into develop-b2school Mar 5, 2026
1 check passed
@vbillard91 vbillard91 deleted the fix-COCO-5341-add-logs-to-track-notification branch March 5, 2026 09:02
vbillard91 added a commit that referenced this pull request Mar 9, 2026
…d trigger to debug production (#969)

# Conflicts:
#	timeline/src/main/java/org/entcore/timeline/controllers/TimelineController.java
jenkinsEdificePublic pushed a commit that referenced this pull request Mar 9, 2026
…d trigger to debug production (#969)

# Conflicts:
#	timeline/src/main/java/org/entcore/timeline/controllers/TimelineController.java
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

Successfully merging this pull request may close these issues.

2 participants