[
https://issues.apache.org/jira/browse/TINKERPOP3-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022612#comment-15022612
]
Bob Briody commented on TINKERPOP3-665:
---------------------------------------
It's possible that this capability isn't as important as we originally thought.
Perhaps [~mbroecheler] could comment on the importance of this capability since
he has some experience implementing the metrics framework now.
> Consider supporting aggregated nested metrics in Metrics Framework
> ------------------------------------------------------------------
>
> Key: TINKERPOP3-665
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-665
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.2-incubating
> Reporter: Bob Briody
> Assignee: Bob Briody
> Priority: Minor
>
> The Metrics Framework supports nested metrics, which is good for most
> underlying operations. However, there are cases where many similar operations
> can be grouped together, such as a vendor implementation that makes many
> similar calls to a DB or Index. The Metrics Framework should provide the
> ability to aggregate these operations into a single entity without losing
> information about each individual operation such as it's duration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
