January 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-263) Adding atom feed links into the UI

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-263: ------------------------------- Summary: Adding atom feed links into the UI Key: SRAMP-263 URL: https://issues.jboss.org/browse/SRAMP-263 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kurt Stam Assignee: Eric Wittmann Fix For: 0.3.1 - jBPM - bugfix 1 Linking to the specific atomfeed for an artifact, and maybe also feed buttons for queries. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-347) Refactor services part of UI backend, to support multiple providers

by Gary Brown (JIRA)

Gary Brown created RTGOV-347: -------------------------------- Summary: Refactor services part of UI backend, to support multiple providers Key: RTGOV-347 URL: https://issues.jboss.org/browse/RTGOV-347 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Currently the services information is obtained only from switchyard. Need to provide an abstraction layer that will enable other service container providers to be supported. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-342) ElasticSearch Event Processor implementation

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-342?page=com.atlassian.jira.plugin.... ] ivan mckinley reassigned RTGOV-342: ----------------------------------- Assignee: ivan mckinley (was: Gary Brown) > ElasticSearch Event Processor implementation > -------------------------------------------- > > Key: RTGOV-342 > URL: https://issues.jboss.org/browse/RTGOV-342 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.M1 > > > The EventProcessor configuration should be provided with: > a) Index name > b) Type name > c) MVEL expression for obtaining id from the event > NOTE: Also need to be able to indicate that a random id should be used - possibly if mvel expression is not defined? > If REST call does not succeed, then throw exception to prompt a retry of the event. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-343) EPN to store activity events, response times and situations in ElasticSearch

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-343?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-343: ------------------------------------- Considerations - concept for indexing of information in elasticsearch. -parent child relationship (situation a child of ActvityUnit ect), - building new index based on service type? - Sharding of information. - related situations and activities should route on the same shard. this results in less overhead on the elasticsearch backend - > EPN to store activity events, response times and situations in ElasticSearch > ---------------------------------------------------------------------------- > > Key: RTGOV-343 > URL: https://issues.jboss.org/browse/RTGOV-343 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Standard EPN deployment for storing activity events and situations in ElasticSearch. > The ActivityUnit (possibly minus the events, although would provide efficient retrieval of the whole unit) should be stored as one type, the ActivityType derived objects as another, response times and the situations as their own type. > Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs? -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-343) EPN to store activity events, response times and situations in ElasticSearch

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-343?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-343: ---------------------------------- With storage of the ResponseTime information, as the object is also used for aggregation of multiple response time results, the property names are avg, min and max. However when storing the individual values in ElasticSearch, it may be better to just record the value in the 'avg' property in a 'value' field. > EPN to store activity events, response times and situations in ElasticSearch > ---------------------------------------------------------------------------- > > Key: RTGOV-343 > URL: https://issues.jboss.org/browse/RTGOV-343 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Standard EPN deployment for storing activity events and situations in ElasticSearch. > The ActivityUnit (possibly minus the events, although would provide efficient retrieval of the whole unit) should be stored as one type, the ActivityType derived objects as another, response times and the situations as their own type. > Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs? -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-346) Explore whether ElasticSearch server can be integrated into EAP

by Gary Brown (JIRA)

Gary Brown created RTGOV-346: -------------------------------- Summary: Explore whether ElasticSearch server can be integrated into EAP Key: RTGOV-346 URL: https://issues.jboss.org/browse/RTGOV-346 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Determine whether ElasticSearch could be integrated as a service within EAP/Wildfly. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-346) Explore whether ElasticSearch server can be integrated into EAP

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-346?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-346: ----------------------------- Fix Version/s: 2.0.0.M1 > Explore whether ElasticSearch server can be integrated into EAP > --------------------------------------------------------------- > > Key: RTGOV-346 > URL: https://issues.jboss.org/browse/RTGOV-346 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Determine whether ElasticSearch could be integrated as a service within EAP/Wildfly. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-343) EPN to store activity events, response times and situations in ElasticSearch

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-343?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-343: ----------------------------- Description: Standard EPN deployment for storing activity events and situations in ElasticSearch. The ActivityUnit (possibly minus the events, although would provide efficient retrieval of the whole unit) should be stored as one type, the ActivityType derived objects as another, response times and the situations as their own type. Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs? was: Standard EPN deployment for storing activity events and situations in ElasticSearch. The ActivityUnit (minus the events) should be stored as one type, the ActivityType derived objects as another, and the situations as their own type. Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs? > EPN to store activity events, response times and situations in ElasticSearch > ---------------------------------------------------------------------------- > > Key: RTGOV-343 > URL: https://issues.jboss.org/browse/RTGOV-343 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Standard EPN deployment for storing activity events and situations in ElasticSearch. > The ActivityUnit (possibly minus the events, although would provide efficient retrieval of the whole unit) should be stored as one type, the ActivityType derived objects as another, response times and the situations as their own type. > Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs? -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-343) EPN to store activity events, response times and situations in ElasticSearch

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-343?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-343: ----------------------------- Summary: EPN to store activity events, response times and situations in ElasticSearch (was: EPN to store activity events and situations in ElasticSearch) > EPN to store activity events, response times and situations in ElasticSearch > ---------------------------------------------------------------------------- > > Key: RTGOV-343 > URL: https://issues.jboss.org/browse/RTGOV-343 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Standard EPN deployment for storing activity events and situations in ElasticSearch. > The ActivityUnit (minus the events) should be stored as one type, the ActivityType derived objects as another, and the situations as their own type. > Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs? -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-344) Course grained access to ElasticSearch

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-344?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-344: ---------------------------------- This proxy service should only initially provide search capabilities - not the ability to store or update information. > Course grained access to ElasticSearch > -------------------------------------- > > Key: RTGOV-344 > URL: https://issues.jboss.org/browse/RTGOV-344 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > ElasticSearch does not provide any authentication/authorization mechanism, so a proxy service should be implemented to provide this functionality. The location of the ElasticSearch cluster can be obtained from the rtgov properties. -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues January 2014