Be able to take smart actions on connectors errors

[amr-cossi]

Problem to Solve

The connector monitoring section shows errors found during the run of one connector. The goal of this feature is to be able to act on each of these errors prevent them from appearing again.

Current Workaround

Understand the error, fix the data already in the platform manually, ignore errors that can't be fixed.

Proposed Solution

For each error displayed, let the user choose an action :

• Acknowledge and ignore : for some connectors importing invalid IOCs (hostnames with an _ for eg), possibility to say that this error has been handled. Every future run of this connector should not raise the same error on the same data.
• Re-import bundle : if a fix has been done in the platform, tries to re-import the same bundle that was in error.
• Merge and re-import : if there is a conflict between existing data and the new bundle, allows a merge of entities in conflict.

The number of errors still to be handled has to be differentiated from the number of errors already handled.

Additional Information

There may be a need to standardize the various errors that a connector can raise to be handle to suggest a right actions for the right errors.

[SamuelHassine]

When a connector raises an error:

As an example:

• Too many entities resolved: propose a button to visualize impacted entities with aliases, and fix the problem easily in this screen.