Make errors and warnings available from Controller logs and Agent logs

Current Situation

• When Controller and Agent raise errors in response to user instructions then errors and warnings are reported back to JOC Cockpit by use of events.
• This does not apply to errors and warnings that are caused by autonomous operations. For example, in case that a monitored directory is missing or becomes unavailable le the Agent will raise an error that is visible from the Agent's log file only.

Desired Behavior

• Log files of Controller and Agents should be reported back to JOC Cockpit see JS-2088. This happens at an ongoing basis.
• Log output of Controller and Agents are stored to JOC Cockpit's database.
  • Logs are stored in records per day. The time zone for begin of day is specified from a global Setting.
  • Logs are stored in a compressed format.
  • A log retention period determines for how many days the logs will be retained.
    • A global Setting determines the number of days that Controller logs will be retained.
    • A global Setting determines the number of days that Agent logs will be retained.
• Logs are made available from the GUI.
  • The JOC Cockpit's administrative menu identified by the icon is added a "Logs" menu item that opens the Logs view.
  • The Logs view offers two sub-views for Controller Logs and Agent Logs.
    • Controller Logs are offered for the current Controller. 
    • Agent Logs are offered for any Agents assigned the Controller.
  •  Each sub-view of Controller Logs and Agent Logs offers
    • to display logs per day.(in the log Setting's time zone).
    • for Controllers: to display logs per Standalone Controller, Primary and Secondary Controller instances in a cluster within the given day,
    • for Agents: to display logs per Agent within the given day,
    • filters to limit display of log entries to matching log levels: WARNING, ERROR, INFO, DEBUG, TRACE.
• JOC Cockpit creates alerts that become visible from the flag for system errors and warnings in the GUI:
  • when Controller logs and Agent logs are returned by the Controller then the logs will be parsed for errors and warnings that will be added to the flag  using events for the GUI.
• JOC Cockpit creates notifications for errors and warnings from Controller Logs and Agent Logs.
  • The Notification Schema is added the configuration to notify on
    • errors and/or warnings of a Controller. Users can select to notify for all Controllers or for selected Controllers.
    • errors and/or warnings of Agents. Users can select to notify for individual Agents or for all Agents of a given Controller or for Agents of the selected Controller.
    • Repeated errors and warnings will not cause repeated notifications.
    • Notifications will be forwarded in the usual way including e-mail, command line execution or JMS.