April 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-372) ActivityStore implementation of the Metrics Provider API

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-372?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-372. ------------------------------ Fix Version/s: (was: 2.0.0.Final) Resolution: Rejected Following discussion with Michael Clay, it has been decided to just use the Kibana dashboard for metrics, with the service list/detail pages being just to show service information (but no metrics). > ActivityStore implementation of the Metrics Provider API > -------------------------------------------------------- > > Key: RTGOV-372 > URL: https://issues.jboss.org/browse/RTGOV-372 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > > Obtain service metrics from the ActivityStore. > Additional (optional) config information should be used to narrow down the timeframe used to derive the metric 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-370) Metrics provider API

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-370?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-370. ------------------------------ Fix Version/s: (was: 2.0.0.Final) Resolution: Rejected Following discussion with Michael Clay, it has been decided to just use the Kibana dashboard for metrics, with the service list/detail pages being just to show service information (but no metrics). > Metrics provider API > -------------------- > > Key: RTGOV-370 > URL: https://issues.jboss.org/browse/RTGOV-370 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > > Define an API to be used to obtain metrics for services displayed in the RTGov UI. As with the ServicesProvider API, it will be necessary to have a test to determine whether the metrics provider can provide information about the service, in situations where multiple service platforms are being supported. > API should enable the Service and ServiceSummary beans to be supplied, and the metrics provider implementation will fill in the relevant information, based on internal config for now. -- 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 resolved RTGOV-371. ------------------------------ Fix Version/s: (was: 2.0.0.Final) Resolution: Rejected Following discussion with Michael Clay, it has been decided to just use the Kibana dashboard for metrics, with the service list/detail pages being just to show service information (but no metrics). > 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-351) SwitchYard services provider should support remote JMX URL with authentication

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-351?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-351. ------------------------------ Resolution: Done > SwitchYard services provider should support remote JMX URL with authentication > ------------------------------------------------------------------------------ > > Key: RTGOV-351 > URL: https://issues.jboss.org/browse/RTGOV-351 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > SwitchYard services provider supports JMX, but currently uses the local platform MBeanServer. > Need to extend to use a remote JMX MBeanServer via a specified URL, that may also require configuration of a username and 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-351) SwitchYard services provider should support remote JMX URL with authentication

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-351?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-351: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov-ui/pull/32 > SwitchYard services provider should support remote JMX URL with authentication > ------------------------------------------------------------------------------ > > Key: RTGOV-351 > URL: https://issues.jboss.org/browse/RTGOV-351 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > SwitchYard services provider supports JMX, but currently uses the local platform MBeanServer. > Need to extend to use a remote JMX MBeanServer via a specified URL, that may also require configuration of a username and 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-395: -------------------------------- Description: There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: {code} s-ramp:upload /path/to/file.ext "Invalid Type" s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." {code} The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. was: There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: s-ramp:upload /path/to/file.ext "Invalid Type" s-ramp:create "Invalid Type" The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. > S-RAMP allows artifacts to be created with invalid characters in the Artifact Type > ---------------------------------------------------------------------------------- > > Key: SRAMP-395 > URL: https://issues.jboss.org/browse/SRAMP-395 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0 - API Management > > > There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: > {code} > s-ramp:upload /path/to/file.ext "Invalid Type" > s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." > {code} > The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. > We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). > For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- 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] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-395: ----------------------------------- Summary: S-RAMP allows artifacts to be created with invalid characters in the Artifact Type Key: SRAMP-395 URL: https://issues.jboss.org/browse/SRAMP-395 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 0.4.0 - Tomcat Support Reporter: Eric Wittmann Assignee: David virgil naranjo Fix For: 0.5.0 - API Management There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: s-ramp:upload /path/to/file.ext "Invalid Type" s-ramp:create "Invalid Type" The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- 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-318) Add index to Context value and type field

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-318?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-318: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > Add index to Context value and type field > ----------------------------------------- > > Key: RTGOV-318 > URL: https://issues.jboss.org/browse/RTGOV-318 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > An index is required on the Context type and value fields, as otherwise building a call trace becomes very slow due to scanning complete db table. -- 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-344) Course grained access to ElasticSearch

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-344?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-344. ------------------------------ Resolution: Done > Course grained access to ElasticSearch > -------------------------------------- > > Key: RTGOV-344 > URL: https://issues.jboss.org/browse/RTGOV-344 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > 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, 3 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 updated RTGOV-344: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/50, https://github.com/Governance/rtgov-ui/pull/30 > Course grained access to ElasticSearch > -------------------------------------- > > Key: RTGOV-344 > URL: https://issues.jboss.org/browse/RTGOV-344 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > 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, 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