[
https://issues.apache.org/jira/browse/IGNITE-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Veselovsky updated IGNITE-5168:
------------------------------------
Description:
Now in Ignite the only way to see IGFS metrics is to get them programmically
from the code. But customers need them to understand what is cached in IGFS, so
to expose the metrics would be useful.
There are options to expose the metrics via
1) MBean
2) console Visor .
3) web console ( https://apacheignite-tools.readme.io/docs/ignite-web-console )
was:
Now in Ignite the only way to see IGFS metrics is to get them programmically
from the code. But customers need them to understand what is cached in IGFS, so
to expose the metrics would be useful.
There are options to expose the metrics via MBean and/or via console Visor
interface.
> Make IGFS metrics available for user
> ------------------------------------
>
> Key: IGNITE-5168
> URL: https://issues.apache.org/jira/browse/IGNITE-5168
> Project: Ignite
> Issue Type: New Feature
> Components: IGFS
> Affects Versions: 2.0
> Reporter: Ivan Veselovsky
> Assignee: Ivan Veselovsky
>
> Now in Ignite the only way to see IGFS metrics is to get them programmically
> from the code. But customers need them to understand what is cached in IGFS,
> so to expose the metrics would be useful.
> There are options to expose the metrics via
> 1) MBean
> 2) console Visor .
> 3) web console ( https://apacheignite-tools.readme.io/docs/ignite-web-console
> )
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
