March 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-157) Message triggered activity event logging

by Gary Brown (JIRA)

Gary Brown created RTGOV-157: -------------------------------- Summary: Message triggered activity event logging Key: RTGOV-157 URL: https://issues.jboss.org/browse/RTGOV-157 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.1 If activity event logging is disabled by default, provide the ability for a particular business transaction initiating message (interaction) to enable the activity logging for that single transaction. This may be used in situations where activity logging is disabled in production for performance reasons, but on occasions the administrator wishes to get a profile of the performance of the system based on an individual business transaction's execution. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-156) XSLT transformer for transforming information content

by Gary Brown (JIRA)

Gary Brown created RTGOV-156: -------------------------------- Summary: XSLT transformer for transforming information content Key: RTGOV-156 URL: https://issues.jboss.org/browse/RTGOV-156 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M5 Provide an xslt implementation of the org.overlord.rtgov.activity.processor.InformationTransformer interface. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-155) Situation should identify physical location

by Gary Brown (JIRA)

Gary Brown created RTGOV-155: -------------------------------- Summary: Situation should identify physical location Key: RTGOV-155 URL: https://issues.jboss.org/browse/RTGOV-155 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M5 One of the standard properties recorded with a situation should be the physical location where the problem occurred. So (for example) if the situation relates to a service, then the location information should identify the server upon which the service instance was executing, and the specific service implementation. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-154) Situation list filter

by Gary Brown (JIRA)

Gary Brown created RTGOV-154: -------------------------------- Summary: Situation list filter Key: RTGOV-154 URL: https://issues.jboss.org/browse/RTGOV-154 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M5 Situation events are created when an event processor detects a problem based on activity information generated by executing business transactions. The situations are associated with a target component that indicates where the problem has arisen. In some situations, a particular component may be known to an administrator, and therefore they wish to temporarily ignore any problems being reported about it. Although this filtering could be provided in the presentation layer, it may be better that it is centrally managed, to enable other applications that access the Situations list through the REST API to also be subject to the same filtering. The issue is where to apply this filter, and where will it get the list of blacklisted entries from. In terms of the filter, should the overall list remain unchanged, and just have a derived list that applies the filter? If the complete list is maintained, then the benefit is that when the component is removed from the blacklist, its associated Situations would then immediately re-appear within the displayed list. The other point to consider is whether Situations associated blacklisted components should be persisted, or atleast marked to indicate that they were flagged as a known problem? As this mechanism is primarily intended to de-clutter the UI, to avoid known problems overshadowing other Situations that may occur, it is likely that persisting Situation events would be unaffected by this mechanism. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-153) Define ootb EPN for persisting Situation events

by Gary Brown (JIRA)

Gary Brown created RTGOV-153: -------------------------------- Summary: Define ootb EPN for persisting Situation events Key: RTGOV-153 URL: https://issues.jboss.org/browse/RTGOV-153 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M5 Use the JPA event processor to persist Situation events in a database. This should be defined in a separate EPN, to enable other user supplied EPNs that create Situation objects to also publish them to a well-defined subject to be picked up by the common Situation persisting EPN. This means that the current SLA monitor example would need to be updated to distribute the Situation derived events to this well-defined subject. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-151) Persist event processor derived results

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-151?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-151: ---------------------------------- Have a JPA based event processor that can persist incoming events to a database identified in properties supplied to the event processor. > Persist event processor derived results > --------------------------------------- > > Key: RTGOV-151 > URL: https://issues.jboss.org/browse/RTGOV-151 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > > Support the ability to persist results derived from event processor networks. > The initial usecase is situations, where service level agreement based analysis may detect violations. Historic analysis of the violations may be required for reporting purposes. > However there may be other cases where facts derived from this event analysis may be required in historic contexts. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-27) Security: require the user to log in to the UI (JAAS?)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-27?page=com.atlassian.jira.plugin... ] Eric Wittmann closed SRAMPUI-27. -------------------------------- > Security: require the user to log in to the UI (JAAS?) > ------------------------------------------------------ > > Key: SRAMPUI-27 > URL: https://issues.jboss.org/browse/SRAMPUI-27 > Project: S-RAMP UI > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > The s-ramp UI should be protected by JAAS. The user should be prompted to authorize with a username/password. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-27) Security: require the user to log in to the UI (JAAS?)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-27?page=com.atlassian.jira.plugin... ] Eric Wittmann commented on SRAMPUI-27: -------------------------------------- The JBoss version of the s-ramp-ui now assumes it is deployed within Overlord's SSO configuration. So the UI now uses a SAML assertion as the proxy authentication mechanism (when the UI servlets call the s-ramp atom api rest services). > Security: require the user to log in to the UI (JAAS?) > ------------------------------------------------------ > > Key: SRAMPUI-27 > URL: https://issues.jboss.org/browse/SRAMPUI-27 > Project: S-RAMP UI > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > The s-ramp UI should be protected by JAAS. The user should be prompted to authorize with a username/password. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-27) Security: require the user to log in to the UI (JAAS?)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-27?page=com.atlassian.jira.plugin... ] Eric Wittmann updated SRAMPUI-27: --------------------------------- Git Pull Request: https://github.com/Governance/s-ramp-ui/pull/50 > Security: require the user to log in to the UI (JAAS?) > ------------------------------------------------------ > > Key: SRAMPUI-27 > URL: https://issues.jboss.org/browse/SRAMPUI-27 > Project: S-RAMP UI > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > The s-ramp UI should be protected by JAAS. The user should be prompted to authorize with a username/password. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-27) Security: require the user to log in to the UI (JAAS?)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-27?page=com.atlassian.jira.plugin... ] Eric Wittmann resolved SRAMPUI-27. ---------------------------------- Resolution: Done > Security: require the user to log in to the UI (JAAS?) > ------------------------------------------------------ > > Key: SRAMPUI-27 > URL: https://issues.jboss.org/browse/SRAMPUI-27 > Project: S-RAMP UI > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > The s-ramp UI should be protected by JAAS. The user should be prompted to authorize with a username/password. -- 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2013