"That can fix the issue with the "pool recycling" for the agent update."
Could you elaborate on that?
There's two things in the mix:
- The agent
- The profiler
The profiler runs in your app itself, which is what requires the recycle event - to reload the application with a newer profiler.
However, the agent itself could be updated when we don't have profiler improvements in a particular release (only agent improvements).
I'm keen to understand though if we've missed something that would make recycling a web app not necessary while also updating the profiler?
All of this is to add, absolutely hear you and will discuss about how we could bring this forward. We're about to ship our support for Ruby & Node which has taken significant effort, but certainly will be looking after that at some of these user experience improvements. I personally hate the "out of date agent" banner too :)
I hope that helps,
Edit: Fixed a sentence to make it clearer