View Issue Details

Related ChangesetsJump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004333SymmetricDSImprovementpublic2020-03-31 11:002021-05-28 20:40
Reporterpyotrk Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.11.7 
Target Version3.12.10Fixed in Version3.12.10 
Summary0004333: Monitor events purger condition
DescriptionCurrently, the purger is removing events from monitor_event table that are older than purge.retention.minutes parameter (see PurgerService.purgeMonitorEvents()). I think that it isn't correct because it removes also events that weren't resolved and an admin (user) wasn't notified about them (I mean that flags is_notified and is_resolved is 0).

I suggest adding a condition to an SQL query "deleteMonitorEventSql" to remove events where is_resolved != 0
Steps To ReproduceNo need
Additional Information-
Tagspurge

Activities

pyotrk

2020-09-28 08:31

reporter   ~0001790

Please let me know if the description isn't clear. This is definitely a bug in the purger behavior.

elong

2020-09-30 17:03

developer   ~0001791

Confirmed as defect.

Related Changesets

SymmetricDS: 3.12 b94ceda3

2021-05-17 16:53:11

admin

Details Diff 		0004333: Monitor events purge by time when resolved Affected Issues
0004333
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/PurgeServiceSqlMap.java Diff File

Issue History

Date Modified Username Field Change
2020-03-31 11:00 pyotrk New Issue
2020-09-28 08:31 pyotrk Note Added: 0001790
2020-09-30 17:03 elong Status new => confirmed
2020-09-30 17:03 elong Note Added: 0001791
2021-05-17 16:53 elong Assigned To => elong
2021-05-17 16:53 elong Status confirmed => resolved
2021-05-17 16:53 elong Resolution open => fixed
2021-05-17 16:53 elong Fixed in Version => 3.12.10
2021-05-17 16:53 elong Target Version => 3.12.10
2021-05-17 16:54 elong Tag Attached: purge
2021-05-17 17:00 admin Changeset attached => SymmetricDS 3.12 b94ceda3
2021-05-28 20:40 admin Status resolved => closed