Capture agent with no configuration is always shown as "idle"
Steps to reproduce
Steps to reproduce:
1. Use REST endpoint to register a new capture agent as idle
2. Send no additional communication from agent.
3. View "Capture Agents" tab on admin UI
Actual Results:
Capture Agent shows up as "idle" indefinitely
Expected Results:
Capture agent should eventually appear as offline
Workaround (if any):
Send a configuration
Activity
It might have been more accurate to name this "will never be shown as offline", since a state change is still possible via REST.
This is because the UI determines whether a CA is offline based in part on its configured polling interval. This is not something that the CA is required to report, but it is in the reference CA which is why the reference CA is pretty much the only type of CA that will ever appear offline if you just unplug it from the network. This is something that may come up at the unconference so hopefully I will have a better answer after that.
Greg, has the "offline" logic been discussed since this bug was opened?
Unfortunately I was not able to attend the conference in Manchester, but I will bring it up at the meeting tomorrow.
This appears to have been fixed elsewhere. Fix is present in 1.6.x, and 2.0.x.
