Removes --features from the cmd, adds an explicit --disable-k6 to disable the runner + k6 checks.
Updates the error message for k6 capability missing on probe.
Users upgrading from older probes (will) have k6 scripts disabled by default in the API if they weren't already running k6 checks. There are 2 cases for them:
Had k6 FF in args: no impact, this setup makes it default-enabled.
Did not have k6 FF: this was the default. If they use the Docker image or have k6 on their PATH, then their upgraded agent would be able to set up a k6Runner. Any previously-assigned MultiHTTP or scripted checks may start running. They will need to enable in the UI to assign k6 checks.
For new probes, this change aligns the agent's default with the default assumption of the UI/Terraform (k6-enabled), so it should reduce issues with setup.
Also updated the error message when k6 is missing - feedback appreciated.
Resolves https://github.com/grafana/synthetic-monitoring-agent/issues/721 Decision (Slack)
Summary:
--featuresfrom the cmd, adds an explicit--disable-k6to disable the runner + k6 checks.Users upgrading from older probes (will) have k6 scripts disabled by default in the API if they weren't already running k6 checks. There are 2 cases for them:
k6FF in args: no impact, this setup makes it default-enabled.k6FF: this was the default. If they use the Docker image or have k6 on their PATH, then their upgraded agent would be able to set up ak6Runner. Any previously-assigned MultiHTTP or scripted checks may start running. They will need to enable in the UI to assign k6 checks.For new probes, this change aligns the agent's default with the default assumption of the UI/Terraform (k6-enabled), so it should reduce issues with setup.
Also updated the error message when k6 is missing - feedback appreciated.