[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:
-----------------------------
Component/s: User Interface
> 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: Feature Request
> 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, 9 months
[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 updated RTGOV-370:
-----------------------------
Component/s: User Interface
> 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, 9 months
[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 updated RTGOV-370:
-----------------------------
Description:
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.
was:
Define an API to be used to obtain metrics for services displayed in the RTGov UI.
> Metrics provider API
> --------------------
>
> Key: RTGOV-370
> URL: https://issues.jboss.org/browse/RTGOV-370
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> 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, 9 months
[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 edited comment on RTGOV-344 at 3/18/14 11:03 AM:
------------------------------------------------------------
This proxy service should only initially provide search capabilities - not the ability to store or update information, or remove/update mappings.
was (Author: objectiser):
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