[ https://issues.apache.org/jira/browse/IGNITE-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15479740#comment-15479740 ]
Andrew Mashenkov commented on IGNITE-1296: ------------------------------------------ This ticket seems to be resolved in version 1.6. See [IgniteKernal.java|https://github.com/apache/ignite/blob/ignite-1.6/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java] > Add to local node metrics new value - up time > --------------------------------------------- > > Key: IGNITE-1296 > URL: https://issues.apache.org/jira/browse/IGNITE-1296 > Project: Ignite > Issue Type: Task > Components: UI > Affects Versions: ignite-1.4 > Reporter: Pavel Konstantinov > Priority: Trivial > > Currently looking at the node console output I don't understand how many time > node already working. So I suggesting to add this info to the (for example) > the Node section as 'up time=4d 23h 45m 32sec'. > {code} > Metrics for local node (to disable set 'metricsLogFrequency' to 0) > ^-- Node [id=79d693a9, name=tester-DC1] > ^-- H/N/C [hosts=2, nodes=2, CPUs=32] > ^-- CPU [cur=4.7%, avg=4.84%, GC=0%] > ^-- Heap [used=23324MB, free=35.94%, comm=29244MB] > ^-- Public thread pool [active=0, idle=32, qSize=0] > ^-- System thread pool [active=0, idle=32, qSize=0] > ^-- Outbound messages queue [size=0] > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)