Availability report information is currently limited to: * resource id * availability type * start time There is no way for the plugin container to send a report with error messages, which would come from the plugin container itself, or from plugin code. Example of plugin error: * "Apache availability is DOWN because HTTP connection timed out" * "Postgres availability is DOWN because the JDBC connection could not be established but the process is available" Example of plugin container: * CPU availability is DOWN because the availability scan time out on this resource Impacts: * Plugin API * Plugin Container * Server Services * Data Model * GUI Note: This RFE comes from BZ862893