April 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-423) Support domain mode in EAP

by Gary Brown (JIRA)

Gary Brown created RTGOV-423: -------------------------------- Summary: Support domain mode in EAP Key: RTGOV-423 URL: https://issues.jboss.org/browse/RTGOV-423 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Support domain mode deployment of RTGov. This will involve deploying the rtgov war as a module, and obtaining the properties the xml 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-352) Integrate Kibana into the RTGov UI

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-352?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-352: ----------------------------- Parent: RTGOV-419 Issue Type: Sub-task (was: Feature Request) > Integrate Kibana into the RTGov UI > ---------------------------------- > > Key: RTGOV-352 > URL: https://issues.jboss.org/browse/RTGOV-352 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Integrate Kibana into the new RTGov UI, to enable user to analyse activity, situation and response time information. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-353) Default kibana dashboard for RTGov UI

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-353?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-353: ----------------------------- Parent: RTGOV-419 Issue Type: Sub-task (was: Feature Request) > Default kibana dashboard for RTGov UI > ------------------------------------- > > Key: RTGOV-353 > URL: https://issues.jboss.org/browse/RTGOV-353 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Need to define a suitable default dashboard for kibana, to provide access to services and the activity/response time information associated with them. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-371) ElasticSearch implementation of the Metrics Provider API

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-371?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-371: ----------------------------- Parent: RTGOV-419 Issue Type: Sub-task (was: Feature Request) > ElasticSearch implementation of the Metrics Provider API > -------------------------------------------------------- > > Key: RTGOV-371 > URL: https://issues.jboss.org/browse/RTGOV-371 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > > Implement an ElasticSearch based MetricsProvider to obtain information about a service. > Additional (optional) configuration information should be used to define a time window for the queries - so (for example) an administrator could indicate that the summary metric information should only be related to the past 24 hours. > Use the ElasticSearch Java library. Optional config property (obtained from RTGovProperties) to obtain the URL of the ElasticSearch server - otherwise assume running locally. > Use the 'responsetime' mapping information from the 'rtgov' index, based on the instructions for setting up a demo environment (https://community.jboss.org/thread/237948). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-422) Make ElasticSearch quickstart an "out of the box" EPN in the content folder

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-422?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-422: ---------------------------------- The forum post point 5 discussed some minor changes that could be made to this EPN: - random mvel id script is not necessary - if no script is provided, then just call 'getRandom()' method on the KeyValueStore impl (which is not currently used), so script (and mvel) is only used if a custom approach for generating ids is required - quickstart predicates not required as these are the types published on the inbound subjects - no 'destinationSubjects' are required, as these event processors are not producing any results to be consumed by other EPNs > Make ElasticSearch quickstart an "out of the box" EPN in the content folder > --------------------------------------------------------------------------- > > Key: RTGOV-422 > URL: https://issues.jboss.org/browse/RTGOV-422 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > > As discussed in the forum post (item 4), it would be good to have an out of the box capability to store information in ElasticSearch, as Kibana is now a part of the new RTGov UI. > Therefore it has been agreed to move the current quickstart into the 'contents' folder, and deploy as part of the standard default installation. > This does not prevent users from modifying this default EPN to customise what information they actually want to store in ElasticSearch - but provides a reasonable starting point. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-422) Make ElasticSearch quickstart an "out of the box" EPN in the content folder

by Gary Brown (JIRA)

Gary Brown created RTGOV-422: -------------------------------- Summary: Make ElasticSearch quickstart an "out of the box" EPN in the content folder Key: RTGOV-422 URL: https://issues.jboss.org/browse/RTGOV-422 Project: RTGov (Run Time Governance) Issue Type: Sub-task Reporter: Gary Brown Assignee: ivan mckinley Fix For: 2.0.0.Final As discussed in the forum post (item 4), it would be good to have an out of the box capability to store information in ElasticSearch, as Kibana is now a part of the new RTGov UI. Therefore it has been agreed to move the current quickstart into the 'contents' folder, and deploy as part of the standard default installation. This does not prevent users from modifying this default EPN to customise what information they actually want to store in ElasticSearch - but provides a reasonable starting point. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-421) Make ElasticSearch EventProcessor more generic

by Gary Brown (JIRA)

Gary Brown created RTGOV-421: -------------------------------- Summary: Make ElasticSearch EventProcessor more generic Key: RTGOV-421 URL: https://issues.jboss.org/browse/RTGOV-421 Project: RTGov (Run Time Governance) Issue Type: Sub-task Reporter: Gary Brown Assignee: ivan mckinley Fix For: 2.0.0.Final As discussed in forum post (point 3), as the ElasticSearch capabilities are now encapsulated in the KeyValueStore implementation, it makes sense to make the EventProcessor more generic to cater for any key/store implementation. As pointed out by Ivan, some custom capabilities may be required by particular KeyValueStore implementations (e.g. MongoDB, Cassandra), but these can be added later as extensions to the generic event processor. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-420) Avoid having host location details in ElasticSearch EPNs

by Gary Brown (JIRA)

Gary Brown created RTGOV-420: -------------------------------- Summary: Avoid having host location details in ElasticSearch EPNs Key: RTGOV-420 URL: https://issues.jboss.org/browse/RTGOV-420 Project: RTGov (Run Time Governance) Issue Type: Sub-task Reporter: Gary Brown Assignee: ivan mckinley Fix For: 2.0.0.Final Discussion from forum post " Hosts should be retrieved from RTGovProperties so that can be independently configured by administrator, rather than having to redeploy EPN if a change is required. If not defined, then use default value. Potentially the installer can be updated to ask if ES is used, and install epns and optional hosts configuration. > I’m not sure of this. it may be desired to have certain Stores to connect directly to a specific set of nodes as we know data is stored there. Other wise ES will lookup where the data resides. Further investigated is need into how elastic searches clustering works before a anything is done here. " As a compromise, was wondering whether the ESKeyValueStore could have an optional 'server group' name, which could then be located in the RTGovProperties to obtain the actual host detail(s). If the defined server group does not exist, or is not defined, then a default host value will be checked. And if that does not exist, then a default localhost location will be used. Aim is to move administrator related information outside the EPN which is more in the realm of the business/app developers. -- 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, 3 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: ----------------------------- Parent: RTGOV-419 Issue Type: Sub-task (was: Feature Request) > 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: Sub-task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-417) Add Bulk API support to ElasticSearchKeyValueStore

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-417?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-417: ----------------------------- Parent: RTGOV-419 Issue Type: Sub-task (was: Feature Request) > Add Bulk API support to ElasticSearchKeyValueStore > -------------------------------------------------- > > Key: RTGOV-417 > URL: https://issues.jboss.org/browse/RTGOV-417 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: ivan mckinley > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Currently the ElasticSearchKeyValueStore stores events in elastic search as it receives them. So 500 ActivityUnits will result in 500 communications with Elasticsearch. This is suboptimal for heavy load situations and could potentially result in unnecessary overhead for RTGov. > Recommendation is to add functionality to utilize RTGov bulk API in ElasticSearchKeyValueStore, http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/doc... > This will be enabled by a flag on the configuration of ElasticSearchKeyValueStore. -- 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, 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 April 2014