jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3357) Allow TimeSeries to track external counters
Date Mon, 02 Jul 2012 12:44:22 GMT

    [ https://issues.apache.org/jira/browse/JCR-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405042#comment-13405042
] 

Jukka Zitting commented on JCR-3357:
------------------------------------

The code looks reasonable to me, though it seems like we're already entering the territory
of something that's beyond the scope of Jackrabbit.

Why do such external time series need to be exposed through the RepositoryStatistics mechanism?
Instead of registering them with the repository, couldn't a deployment simply make such time
series directly available to clients through JMX or some other management/monitoring interface?
                
> Allow TimeSeries to track external counters
> -------------------------------------------
>
>                 Key: JCR-3357
>                 URL: https://issues.apache.org/jira/browse/JCR-3357
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>         Attachments: JCR-3357.patch
>
>
> We should extend the current TimeSeries to be able to track external counters. 
> This would facilitate the exposure of potentially already existing information by simply
wrapping it into counters that will then be tracked by a normal TimeSeries and exposed as
a repository statistic.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message