According to UI plugin lifecycle [1], if an uncaught exception escapes (originates) from plugin code due to the infrastructure being the initiator of the call (i.e. invoking specific plugin event handler function), this will be considered as internal error within the plugin code -- the infrastructure will remove such plugin from service (move plugin to FAILED state).

[1] http://www.ovirt.org/Features/UIPlugins#Plugin_lifecycle

This RFE aims to support error detection within the plugin code, i.e. introduce new event handler function that will be called by the infrastructure right before the plugin is removed from service due to uncaught exception.

For example:

api.register({
    UiInit: function() {
        // code might throw exception
    },
    PluginError: function(ex) {
        // process exception before being removed from service
        // this can be useful during plugin development
    }
});

We can also consider revisiting current approach of removing plugins out of service due to uncaught exception, i.e. swallow exception and let plugin stay in service.