This can already be a indicator that the user has used an incorrect configuration.
When invoking am start [endpoint] we can already make a request to the provided endpoints and see if they work and contain metrics data. If they do not work we can provide a warning, but we should not stop execution of am, since the user might not have started their application.
Depending on the application to be up and running, is a bad experience. Perhaps the workflow of the user is to just turn on am at the start of their development cycle and then just leave it running.
This can already be a indicator that the user has used an incorrect configuration.
When invoking
am start [endpoint]we can already make a request to the provided endpoints and see if they work and contain metrics data. If they do not work we can provide a warning, but we should not stop execution ofam, since the user might not have started their application.Depending on the application to be up and running, is a bad experience. Perhaps the workflow of the user is to just turn on
amat the start of their development cycle and then just leave it running.