ka3de

Research: support verbose tracing

1

Research the possibilities of using the tracing implementation done in #1100, which was mainly targeted towards providing a representation of browser actions to end users, as a means to also...

Currently, after #1100, traces are generated in order to represent the actions performed by k6 browser and the state changes in the page as a result of these. One of...

Currently `slowMo` option can only be defined at the `browser` level, which applies for the whole browser "object" utilization. k6 browser should support defining `slowMo` at the `browserContext` level, where...

* Log publisher errors (#661) * Remove max check labels verification (#659)

Now that k6 browser supports `connect` method, in order to connect to a remotely running browser, instead of launching one, it would be useful to provide _cmdline_ snippets that can...

`Response.AllHeaders()` does not include security-related headers

1

### Brief summary Currently the k6 HTTP `Response` implementation contains the headers returned in the `Network.responseReceived` CDP [event](https://chromedevtools.github.io/devtools-protocol/tot/Network/#event-responseReceived). These headers are the ones that should be returned for example when...

**[DO NOT MERGE]** Adds the protobuf definitions for the supported alerts per check type.

Reduce boilerplate for browser tests

5

Currently, as of [`v0.46.0`](https://github.com/grafana/k6/releases/tag/v0.46.0), browser tests require the `browser.type` option to be set. This can only be defined in a scenario definition such as: ```js export const options = {...

Allow configuring k6 runner blocked hostnames

2

The internal k6 runner implementation in the agent hardcodes the `--block-hostnames` k6 option to `*.cluster.local` ([here](https://github.com/grafana/synthetic-monitoring-agent/blob/c701b67315c0c24139eb74d9206380739acde549/internal/k6runner/k6runner.go#L580)). This should be configurable following a similar approach to the one implemented for `--blacklist-ip`....