[
https://issues.apache.org/jira/browse/IGNITE-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430319#comment-15430319
]
Vasiliy Sisko commented on IGNITE-3005:
---------------------------------------
Implemented showing of node ID8, node IP and alert check values:
Alert [id=5026e9cc(@a1), nid8=E1AB7BA2(@n1), ip=172.17.0.1, spec=[-t=5 -tc=gte0
-nc=gte1], values=[tc=77; nc=2], created on=08/22/16, 15:40:21]
> visorcmd: we need to improve alert command
> ------------------------------------------
>
> Key: IGNITE-3005
> URL: https://issues.apache.org/jira/browse/IGNITE-3005
> Project: Ignite
> Issue Type: Improvement
> Components: visor
> Affects Versions: 1.5.0.final
> Reporter: Pavel Konstantinov
> Assignee: Vasiliy Sisko
> Priority: Trivial
> Fix For: 1.8
>
>
> Presently per-node alert prints in log it's info without node ID and user
> cannot understand on what node that alert was triggered.
> {code}
> 04/14/16, 15:06:01 | Alert [id=a8874c91(@a5), spec=-r -t=10 -hu=gt10, created
> on=04/14/16, 14:59:19]
> {code}
> So we need to print out node ID8 in alert info for per-node alerts.
> {code}
> 04/14/16, 15:06:01 | Alert [id=a8874c91(@a5), nid8=12345678, spec=-r -t=10
> -hu=gt10, created on=04/14/16, 14:59:19]
> {code}
> Also will be useful to print out Node IP the same which we printing in 'node'
> command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
