[JBoss JIRA] (SRAMP-197) Auditing: re-implement *not* using JCR observer pattern
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-197?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-197:
--------------------------------
Priority: Minor (was: Major)
> Auditing: re-implement *not* using JCR observer pattern
> -------------------------------------------------------
>
> Key: SRAMP-197
> URL: https://issues.jboss.org/browse/SRAMP-197
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: 0.2.0 - Security & S-RAMP-1.0
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> Re-write the core auditing to no longer use the JCR observer pattern. The JCR observer pattern introduces a number of challenges, including:
> 1) async processing of auditing information. this is problematic in a number of ways, but most importantly is that data may be lost due to slower processing of the auditing information than the information on the artifact itself. Since the JCR observation events don't contain before and/or after values for changes, we have to go after the data directly. If changes happen quickly (before the observer has a crack at it) then data may be lost.
> 2) multi-phase processing of artifact adds/updates in the jcrpersistence impl
--
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
11 years, 6 months
[JBoss JIRA] (RTGOV-208) Update documentation for customising service overview colour script
by Gary Brown (JIRA)
Gary Brown created RTGOV-208:
--------------------------------
Summary: Update documentation for customising service overview colour script
Key: RTGOV-208
URL: https://issues.jboss.org/browse/RTGOV-208
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Priority: Minor
Fix For: 1.0.0.Final
Mechanism has changed from one where the script determines the colour to one where it determines the severity, with the colour being assigned in the svg generator.
The script is now passed four pieces of info:
component (as before)
summary (summary metrics)
latest (latest metrics)
history (list of metrics collected over a time period)
Also now possible to specify the location of an alternative mvel script using a property (MVELSeverityAnalyzer.scriptLocation) in the overlord-rtgov.properties file.
--
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
11 years, 6 months