In the open-model scenarios, k6 provisions VUs to send them at the specified rate.
If the SUT performance completely tanks, k6 at some point will not be able to provision more VUs and will record that an iteration has been ommited. So, many omitted iterations could indicate a test failure. (Paraphrasing @sniku's explanation here; any errors introduced are my own).
"Too many skipped iterations" could be a valuable performance insight. What's more, just having an alert about it could help inform users about the coordinated omission problem.
In the open-model scenarios, k6 provisions VUs to send them at the specified rate.
If the SUT performance completely tanks, k6 at some point will not be able to provision more VUs and will record that an iteration has been ommited. So, many omitted iterations could indicate a test failure. (Paraphrasing @sniku's explanation here; any errors introduced are my own).
"Too many skipped iterations" could be a valuable performance insight. What's more, just having an alert about it could help inform users about the coordinated omission problem.