[
https://issues.apache.org/jira/browse/IGNITE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306596#comment-16306596
]
Denis Magda commented on IGNITE-6925:
-------------------------------------
Now I see. Seems I was doing something wrong in my initial reproducer.
Updated cache metrics readme doc by purging any events related parameters from
there:
https://apacheignite.readme.io/v2.3/docs/cache-metrics
The events readme doc looks good to me. Just updated the javadoc of
IgniteEvents#*Query methods to bring MemoryEventStorageSpi to users attention.
As for the cache events, it’s an oversight that there is no parameter that
enables/disables the events per cache. Let’s add
CacheConfiguration.setEventsEnabled method and have it enabled by default
(current behavior). If the user deploys hundreds of caches or just interested
in the events of specific ones then he can always set this property to ‘false’
in a configuration of the caches of no interest:
https://issues.apache.org/jira/browse/IGNITE-7346
[~alex_pl], could you take over IGNITE-7346 in 2.4 release timeframe?
> Simplify cache metrics activation
> ---------------------------------
>
> Key: IGNITE-6925
> URL: https://issues.apache.org/jira/browse/IGNITE-6925
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Magda
> Assignee: Aleksey Plekhanov
> Labels: iep-6, important
> Fix For: 2.4
>
>
> The user needs to do 3 things to enabled cache metrics:
> - set {{statisticsEnabled}} to {{true}}.
> - set not a dummy {{EventsStorageSpi}}
> - list metrics of the interest.
> This process has to be reduced to 2 steps or, preferably, to 1.
> More details are here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Annoying-extra-steps-for-enabling-metrics-td21865.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
