[
https://issues.apache.org/jira/browse/IGNITE-22962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872814#comment-17872814
]
Ignite TC Bot commented on IGNITE-22962:
----------------------------------------
{panel:title=Branch: [pull/11469/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11469/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Cache 13{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=8022349]]
* {color:#013220}IgniteCacheTestSuite13:
CacheMetricsConflictResolverTest.testCacheConflictResolver - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8022447&buildTypeId=IgniteTests24Java8_RunAll]
> Conflict resolver metrics per cache
> -----------------------------------
>
> Key: IGNITE-22962
> URL: https://issues.apache.org/jira/browse/IGNITE-22962
> Project: Ignite
> Issue Type: New Feature
> Components: extensions
> Reporter: Maksim Davydov
> Assignee: Maksim Davydov
> Priority: Major
> Labels: IEP-59, ise
> Fix For: 2.17
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently there is no metrics for conflict resolved entries. Thus, it's hard
> to analyze the overall picture for the process, especially if custom plugin
> for Conflict Resolver is used.
> This ticket solves the issue by adding metrics counting for conflict resolver
> without depending on its origin. Metrics would be accessable for each cache,
> that is `per cache monitoring`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
