[Request] "Archive on Stop" for -XX:StartFlightRecording

[andrewazores]

Describe the feature

See #252 and #71. When Cryostat detects a new target and observes that there are already running recordings on that target which Cryostat did not already know about (this requires knowing that this is really a new target, not an alias to an existing one), it should not only check if these recordings are fixed-duration and set timer events to update its own database at the expected duration, but it should also set up an event handler for an "archive on stop" the same way that can be done for recordings started by Cryostat itself.

There should also be a configuration option on Cryostat to enable or disable this "archive on stop externally-started recordings" feature, but we should probably default to turning it on.

Anything other information?

No response

[andrewazores]

Another thought: we don't have any mechanism for getting notified if a remote recording is stopped. We could probably do that over remote JMX by listening for notifications from the FlightRecorderMXBean but we have no equivalent for the Cryostat Agent. It would be nice to have something like this, so that if there is a remote recording that we discover, we can also perform archive-on-stop if a fixed duration recording is stopped early, or if we observe a continuous remote recording and the user manually stops it (or some other process stops it).