Project

General

Profile

Actions
Copy link

Feature #4466

closed

Report duplicate IDs

Added by Pavel Kácha almost 6 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Development - Tools
Target version:
Backlog
Start date:
12/04/2018
Due date:
% Done:

0%

Estimated time:
To be discussed:
No

Description

Events with duplicate IDs cannot be saved into db. It's deliberate, as ID is also used as primary key. However, duplicate IDs should be inspected and originators notified - either their IDs do not have sufficient entropy, or their connectors generate duplicate messages for whatever reason.

Bonus: originator can be notified automatically if duplicate ID comes from the same connector.

We should either watch logs or propagate error into runlog and report from there.

Related issues

Related to Mentat - Feature #3367: Implement sending of critical errors via emailClosed03/21/2017

Actions
Actions
Copy link
 #1

Updated by Pavel Kácha almost 5 years ago

Maybe related to #3367?

Actions
Copy link
 #2

Updated by Pavel Kácha over 3 years ago

  • Related to Feature #3367: Implement sending of critical errors via email added
Actions
Copy link
 #3

Updated by Pavel Kácha over 3 years ago

  • Assignee deleted (Jan Mach)
Actions
Copy link
 #4

Updated by Rajmund Hruška over 1 year ago

  • Status changed from New to Rejected

This issue is solved in Warden, in #5066. Furthermore, we have Nagios, which checks the events ending up in errors directory due to ID not being unique.

Actions
Copy link

Also available in: Atom PDF