Ned Andreev

Missing features compared to httpbin.org

4

The following [httpbin.org](https://httpbin.org/) features (besides `/brotli`) are not present in the library: - `now.httpbin.org The current time, in a variety of formats.` (this probably will be more useful as a...

Data segmentation API framework

10

We now have support for partitioning work (i.e. VUs and iterations) between multiple k6 instances, via the `executionSegment` and `executionSegmentSequence` options, originally described in https://github.com/loadimpact/k6/issues/997 and subsequently evolved in https://github.com/loadimpact/k6/pull/1007....

Put metric samples in time series (immutable tag sets) on creation

7

Currently, k6 builds the set of [tags](https://k6.io/docs/using-k6/tags-and-groups) for every metric measurement it emits in a very ad-hoc manner and as a `map[string]string`. For example, building the tags set for the...

Warn on access to the exported script `options` instead of `test.options` in `k6/execution`

1

From https://github.com/grafana/k6/pull/2571/files#r921222735 There are various issues when scripts try to access the exported script `options` from the script. https://github.com/grafana/k6/pull/2571 fixes one bug/undefined behavior, but there are a few other subtle...

This is a proof of concept for the refactoring we need to do to do a simple version of #140. The tests are not fixed yet, and there are quite...

Support non-indexable high-cardinality metric tags / metadata

5

Currently, the k6 [system metric tags](https://k6.io/docs/using-k6/tags-and-groups/#system-tags) are a mix of high-cardinality ones (`url`, `error`, `vu` and `iter`) and relatively low-cardinality ones (everything else). This has already been a problem multiple...

Move integration tests to a dedicated package

2

https://github.com/grafana/k6/pull/2412 and its preceding PRs refactored some cruft in `cmd/` and allowed us to safely and easily write full integration tests of k6. However, these tests are limited to `cmd/`,...

Add explicit tracking and ignoring of metrics and sub-metrics

23

k6 measures a lot of things, and it can and can generate quite a lot of data points for a variety of different metrics. Not everything we measure is important...

While reviewing https://github.com/grafana/k6/pull/2573, I noticed some strange code in `ScenarioConfigs.GetFullExecutionRequirements()`, specifically this part: https://github.com/grafana/k6/blob/556747fbe585c981507904d634e705c68891e663/lib/executors.go#L318-L321 It seems that `currentTimeOffset` is meaningless and we will always add all intermediate steps to `consolidatedSteps`,...

Refactor the engine metrics handling

2

The [current `Engine`](https://github.com/loadimpact/k6/blob/2036baeaa83d76ce17aae95fef7e78e3ef24c735/core/engine.go#L46) vaguely resembles a Rube Goldberg machine... It has slowly been getting better, for example https://github.com/loadimpact/k6/pull/1869 improved it slightly by mostly decoupling the outputs from the `Engine`, but...