[
https://issues.apache.org/jira/browse/OAK-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061756#comment-15061756
]
Teodor Rosu commented on OAK-3791:
----------------------------------
Also, for now, I assumed a simple metric naming scheme
canonical.class.name.{local_metric_name}
Not sure if an oak metric naming convention exists, but one would be useful (
graphite/elasticsearch friendly ).
> Time measurements for DocumentStore methods
> -------------------------------------------
>
> Key: OAK-3791
> URL: https://issues.apache.org/jira/browse/OAK-3791
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, documentmk
> Reporter: Teodor Rosu
> Priority: Minor
> Attachments: OAK-3791-RDB-0.patch
>
>
> For monitoring ( in big latency environments ), it would be useful to measure
> and report time for the DocumentStore methods.
> These could be exposed as (and/or):
> - as Timers generated obtained from StatisticsProvider ( statistics registry )
> - as TimeSeries
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
