The content you are looking for has been archived. View related content below.
[root@ESA]# /opt/rsa/esa/client/bin/esa-client --profiles carlos carlos:offline||jmx:localhost:com.rsa.netwitness.esa:/>carlos-connect RemoteJmsDirectEndpoint { jms://localhost:50030?carlos.useSSL=true } ; running = true carlos:localhost||jmx:localhost:com.rsa.netwitness.esa:/>cd nextgen /Workflow/Source/nextgenAggregationSource carlos:localhost||jmx:localhost:com.rsa.netwitness.esa:/Workflow/Source/nextgenAggregationSource>get.
"name" : "10.xx.xx.xx:56005", "note" : "", "sessionId" : 24462390949, "sessionsBehind" : 58501036, "state" : "IDLE_QUEUED", "status" : "Streaming", "time" : 1459508373000 }, { "filterCount" : 0, "name" : "10.xx.xx.xx:56005", "note" : "", "sessionId" : 34177054228, "sessionsBehind" : 149462451, "state" : "IDLE_QUEUED", "status" : "Streaming", "time" : 1459507000000
For 11.3 and above:
The platform for the ESA Device has changed with the release of the Correlation Server as opposed to the traditional rsa-esa and rsa-nw-esa-server. The esa-client will no longer work in 11.3 and above.
You have two ways to find this information. The easy way is to go to Health and wellness and look for the sessions behind value in the UI like below. Note you will have one for each deployment and each device being aggregated from.
The alternative:
Similar stats are now available in the UI under the explore view for the correlation service. Take the below screenshot as an example:
The highlighted value on the right is a Unix Epoch time (time since the Epoch). Truncate the last 3 zeros and put it into an Epoch timestamp converter and you'll have the time it has for the last session in the concentrator. This will give you an idea of how far you