[ https://issues.apache.org/jira/browse/IGNITE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16264357#comment-16264357 ]
Alexey Kuznetsov edited comment on IGNITE-6846 at 11/23/17 1:53 PM: -------------------------------------------------------------------- [~vkulichenko] Should we create separate metric for 'invoke removal' ? Or it shold be counted by 'invoke update' metric? was (Author: alexey kuznetsov): [~vkulichenko] Should we create separate metric for 'invoke removal' ? Or it shold be counted by 'invoke update' metric? PS now it is included in 'cache removal' metric > Add metrics for entry processor invocations > ------------------------------------------- > > Key: IGNITE-6846 > URL: https://issues.apache.org/jira/browse/IGNITE-6846 > Project: Ignite > Issue Type: Improvement > Components: cache > Affects Versions: 2.3 > Reporter: Valentin Kulichenko > Assignee: Alexey Kuznetsov > Priority: Critical > Labels: iep-6 > Fix For: 2.4 > > > {{CacheMetrics}} object has multiple metrics for various cache operations > like {{get}}, {{put}} and {{remove}}, but nothing for > {{invoke}}/{{EntryProcessor}}. It makes sense to add such metrics, for > example: > * Total number of `invoke` operations executed. > * Number of `invoke` operations that included updates. > * Number of read-only `invoke` operations. > * Min/max/avg execution time. > * ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)