Feature #1384

Configure Tissue actions based on reportEvent() exception.

Added by Randy Reitz almost 10 years ago. Updated over 9 years ago.

Start date:
Due date:
% Done:


Estimated time:
1.00 h
Spent time:


The Tissue V2 API "reportEvent()" can return a variety of python exceptions. This proposal is to provide a method to configure a Tissue V2 action
based on a "reportEvent()" exception. This configuration would be exposed on the GUI "configure Issue" page. The "exception action" would be a
pair of exception name (e.g. UnresolvableSystem, NotAuthorized, etc.) and action (e.g. email issue admin, or email computer security team).

If the "exception action" table was left un-configured, the reportEvent() API would return the exception as it current does. If reportEvent() received an
exception configured in the "exception action" table, then reportEvent() would execute that action and return a "ActionExecuted" exception.


#1 Updated by Randy Reitz over 9 years ago

  • Status changed from New to Closed
  • Assignee set to Lauri Carpenter
  • Estimated time set to 1.00 h

There will be fewer "Unresolved System" exceptions after #1863 is implemented.

#2 Updated by Lauri Carpenter over 9 years ago

  • Status changed from Closed to Rejected

Not "closed", "rejected". We are NOT going to implement an arbitrary exception handler in the reportEvent code. We ARE going to tighten it down so that we do not ignore great big chunks of network when trying to resolve a system, so that "UnresolveableSystem" exception is rarely, if ever, thrown.

If that solution is not effective, then we might implement a [possibly configurable] handler for the "UnresolveableSystem" exception. But NOT for any arbitrary exception that might be thrown.

Also available in: Atom PDF