Skip to content

Commit 8ae2907

Browse files
authored
[feat] clarify k6/execution counter descriptions
1 parent deb547d commit 8ae2907

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/data/markdown/docs/02 javascript api/06 k6-execution.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -76,13 +76,13 @@ Control the test execution.
7676

7777
### vu
7878

79-
Meta information and execution details about the current vu and iteration.
79+
Meta information and execution details about the current vu.
8080

8181
| Property | Type | Description |
8282
|----------|------|-------------|
83-
| iterationInInstance | integer | The identifier of the iteration in the current instance. |
84-
| iterationInScenario | integer | The identifier of the iteration in the current scenario. |
85-
| idInInstance | integer | The identifier of the VU across the instance. |
83+
| iterationInInstance | integer | The identifier of the iteration in the current instance for this VU. This is only unique for current VU and this instance (if multiple instances). This keeps being aggregated if a given VU is reused between multiple scenarios. |
84+
| iterationInScenario | integer | The identifier of the iteration in the current scenario for this VU. This is only unique for current VU and scenario it is currently executing. |
85+
| idInInstance | integer | The identifier of the VU across the instance. Not unique across multiple instances. |
8686
| idInTest | integer | The globally unique (across the whole test run) identifier of the VU. |
8787
| tags | object | The map that gives control over [VU's Tags](/using-k6/tags-and-groups/#tags). The Tags will be included in every metric emitted by the VU and the Tags' state is maintained across different iterations of the same Scenario while the VU exists. Check how to use it in the [example](#tags) below. |
8888

0 commit comments

Comments
 (0)