system_account
and subscribing/requesting using a system account user.>
, do not receive system events and vice versa. Using accounts requires either:$SYS.ACCOUNT.<id>.CONNECT
(client connects)$SYS.ACCOUNT.<id>.DISCONNECT
(client disconnects)$SYS.ACCOUNT.<id>.SERVER.CONNS
(connections for an account changed)$SYS.SERVER.<id>.CLIENT.AUTH.ERR
(authentication error)$SYS.ACCOUNT.<id>.LEAFNODE.CONNECT
(leaf node connects)$SYS.ACCOUNT.<id>.LEAFNODE.DISCONNECT
(leaf node disconnects)$SYS.SERVER.<id>.STATSZ
(stats summary)$SYS.REQ.SERVER.<id>.STATSZ
(request server stat summary)$SYS.REQ.SERVER.PING
(discover servers - will return multiple messages)$SYS.REQ.SERVER.<id>.<endpoint-name>
(request server monitoring endpoint corresponding to endpoint name.)$SYS.REQ.SERVER.PING.<endpoint-name>
(from all server, request server monitoring endpoint corresponding to endpoint name - will return multiple messages)VARZ
CONNZ
ROUTEZ
GATEWAYZ
LEAFZ
SUBSZ
JSZ
ACCOUNTZ
"$SYS.REQ.ACCOUNT.<account-id>.<endpoint-name>
(from all server, request account specific monitoring endpoint corresponding to account id and endpoint name - will return multiple messages)CONNZ
LEAFZ
SUBSZ
JSZ
INFO
nats-account-server
publish system account messages when a claim is updated, the nats-server listens for them, and updates its account information accordingly:$SYS.ACCOUNT.<id>.CLAIMS.UPDATE
nats sub -s nats://admin:[email protected]:4222 ">"
and observe what happens when you do something like nats pub -s "nats://a:[email protected]:4222" foo bar
. Examples on how to use system services can be found here.