[overlord-issues] [JBoss JIRA] (RTGOV-162) Reporting capability against historic activity information with SLA report as example

[Gary Brown (JIRA)]

    [ https://issues.jboss.org/browse/RTGOV-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785521#comment-12785521 ] 

Gary Brown commented on RTGOV-162:
----------------------------------

Changed approach to use activity information directly, instead of situations, as situations represent an alert at a particular time, rather than over a time period.

Also built a deployable report capability, to enable reports to be easily added and accessible via a REST service.

                
> Reporting capability against historic activity information with SLA report as example
> -------------------------------------------------------------------------------------
>
>                 Key: RTGOV-162
>                 URL: https://issues.jboss.org/browse/RTGOV-162
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>            Priority: Critical
>             Fix For: 1.0.0.Final
>
>
> Need to determine what information should be stored in the Situation to enable a report to be compiled based on service performance and availability.
> The criteria for what constitutes a violation of a particular customer's SLA needs to be defined. For example, the SLAs may only apply within particular day/time periods - which will also need to take into account timezones.
> Need to see whether this per customer information can be stored in SRAMP repo, and also reported via Polymita, as requires further analysis of the underlying information - and possibly needs to be presented in a tabular form.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira