Skip to content

Commit 0b1c4d2

Browse files
committed
Fix json example in url grouping docs
The url value in the json should be the same as name when the url grouping is applied.
1 parent e7a929d commit 0b1c4d2

File tree

10 files changed

+50
-30
lines changed

10 files changed

+50
-30
lines changed

docs/sources/next/using-k6/http-requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -165,6 +165,8 @@ That code would produce JSON output like this:
165165
{{< code >}}
166166

167167
```json
168+
// For http://example.com/1, note that the url is not present in the JSON.
169+
168170
{
169171
"type":"Point",
170172
"metric":"http_req_duration",
@@ -175,12 +177,12 @@ That code would produce JSON output like this:
175177
"method":"GET",
176178
"name":"PostsItemURL",
177179
"status":"200",
178-
"url":"http://example.com/1"
180+
"url":"PostsItemURL"
179181
}
180182
}
181183
}
182184

183-
// and
185+
// and for http://example.com/2
184186

185187
{
186188
"type":"Point",
@@ -192,7 +194,7 @@ That code would produce JSON output like this:
192194
"method":"GET",
193195
"name":"PostsItemURL",
194196
"status":"200",
195-
"url":"http://example.com/2"
197+
"url":"PostsItemURL"
196198
}
197199
}
198200
}

docs/sources/v0.47.x/using-k6/http-requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,8 @@ That code would produce JSON output like this:
158158
{{< code >}}
159159

160160
```json
161+
// For http://example.com/1, note that the url is not present in the JSON.
162+
161163
{
162164
"type":"Point",
163165
"metric":"http_req_duration",
@@ -168,12 +170,12 @@ That code would produce JSON output like this:
168170
"method":"GET",
169171
"name":"PostsItemURL",
170172
"status":"200",
171-
"url":"http://example.com/1"
173+
"url":"PostsItemURL"
172174
}
173175
}
174176
}
175177

176-
// and
178+
// and for http://example.com/2
177179

178180
{
179181
"type":"Point",
@@ -185,7 +187,7 @@ That code would produce JSON output like this:
185187
"method":"GET",
186188
"name":"PostsItemURL",
187189
"status":"200",
188-
"url":"http://example.com/2"
190+
"url":"PostsItemURL"
189191
}
190192
}
191193
}

docs/sources/v0.48.x/using-k6/http-requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,8 @@ That code would produce JSON output like this:
158158
{{< code >}}
159159

160160
```json
161+
// For http://example.com/1, note that the url is not present in the JSON.
162+
161163
{
162164
"type":"Point",
163165
"metric":"http_req_duration",
@@ -168,12 +170,12 @@ That code would produce JSON output like this:
168170
"method":"GET",
169171
"name":"PostsItemURL",
170172
"status":"200",
171-
"url":"http://example.com/1"
173+
"url":"PostsItemURL"
172174
}
173175
}
174176
}
175177

176-
// and
178+
// and for http://example.com/2
177179

178180
{
179181
"type":"Point",
@@ -185,7 +187,7 @@ That code would produce JSON output like this:
185187
"method":"GET",
186188
"name":"PostsItemURL",
187189
"status":"200",
188-
"url":"http://example.com/2"
190+
"url":"PostsItemURL"
189191
}
190192
}
191193
}

docs/sources/v0.49.x/using-k6/http-requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,8 @@ That code would produce JSON output like this:
158158
{{< code >}}
159159

160160
```json
161+
// For http://example.com/1, note that the url is not present in the JSON.
162+
161163
{
162164
"type":"Point",
163165
"metric":"http_req_duration",
@@ -168,12 +170,12 @@ That code would produce JSON output like this:
168170
"method":"GET",
169171
"name":"PostsItemURL",
170172
"status":"200",
171-
"url":"http://example.com/1"
173+
"url":"PostsItemURL"
172174
}
173175
}
174176
}
175177

176-
// and
178+
// and for http://example.com/2
177179

178180
{
179181
"type":"Point",
@@ -185,7 +187,7 @@ That code would produce JSON output like this:
185187
"method":"GET",
186188
"name":"PostsItemURL",
187189
"status":"200",
188-
"url":"http://example.com/2"
190+
"url":"PostsItemURL"
189191
}
190192
}
191193
}

docs/sources/v0.50.x/using-k6/http-requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,8 @@ That code would produce JSON output like this:
158158
{{< code >}}
159159

160160
```json
161+
// For http://example.com/1, note that the url is not present in the JSON.
162+
161163
{
162164
"type":"Point",
163165
"metric":"http_req_duration",
@@ -168,12 +170,12 @@ That code would produce JSON output like this:
168170
"method":"GET",
169171
"name":"PostsItemURL",
170172
"status":"200",
171-
"url":"http://example.com/1"
173+
"url":"PostsItemURL"
172174
}
173175
}
174176
}
175177

176-
// and
178+
// and for http://example.com/2
177179

178180
{
179181
"type":"Point",
@@ -185,7 +187,7 @@ That code would produce JSON output like this:
185187
"method":"GET",
186188
"name":"PostsItemURL",
187189
"status":"200",
188-
"url":"http://example.com/2"
190+
"url":"PostsItemURL"
189191
}
190192
}
191193
}

docs/sources/v0.51.x/using-k6/http-requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,8 @@ That code would produce JSON output like this:
158158
{{< code >}}
159159

160160
```json
161+
// For http://example.com/1, note that the url is not present in the JSON.
162+
161163
{
162164
"type":"Point",
163165
"metric":"http_req_duration",
@@ -168,12 +170,12 @@ That code would produce JSON output like this:
168170
"method":"GET",
169171
"name":"PostsItemURL",
170172
"status":"200",
171-
"url":"http://example.com/1"
173+
"url":"PostsItemURL"
172174
}
173175
}
174176
}
175177

176-
// and
178+
// and for http://example.com/2
177179

178180
{
179181
"type":"Point",
@@ -185,7 +187,7 @@ That code would produce JSON output like this:
185187
"method":"GET",
186188
"name":"PostsItemURL",
187189
"status":"200",
188-
"url":"http://example.com/2"
190+
"url":"PostsItemURL"
189191
}
190192
}
191193
}

docs/sources/v0.52.x/using-k6/http-requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -165,6 +165,8 @@ That code would produce JSON output like this:
165165
{{< code >}}
166166

167167
```json
168+
// For http://example.com/1, note that the url is not present in the JSON.
169+
168170
{
169171
"type":"Point",
170172
"metric":"http_req_duration",
@@ -175,12 +177,12 @@ That code would produce JSON output like this:
175177
"method":"GET",
176178
"name":"PostsItemURL",
177179
"status":"200",
178-
"url":"http://example.com/1"
180+
"url":"PostsItemURL"
179181
}
180182
}
181183
}
182184

183-
// and
185+
// and for http://example.com/2
184186

185187
{
186188
"type":"Point",
@@ -192,7 +194,7 @@ That code would produce JSON output like this:
192194
"method":"GET",
193195
"name":"PostsItemURL",
194196
"status":"200",
195-
"url":"http://example.com/2"
197+
"url":"PostsItemURL"
196198
}
197199
}
198200
}

docs/sources/v0.53.x/using-k6/http-requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -165,6 +165,8 @@ That code would produce JSON output like this:
165165
{{< code >}}
166166

167167
```json
168+
// For http://example.com/1, note that the url is not present in the JSON.
169+
168170
{
169171
"type":"Point",
170172
"metric":"http_req_duration",
@@ -175,12 +177,12 @@ That code would produce JSON output like this:
175177
"method":"GET",
176178
"name":"PostsItemURL",
177179
"status":"200",
178-
"url":"http://example.com/1"
180+
"url":"PostsItemURL"
179181
}
180182
}
181183
}
182184

183-
// and
185+
// and for http://example.com/2
184186

185187
{
186188
"type":"Point",
@@ -192,7 +194,7 @@ That code would produce JSON output like this:
192194
"method":"GET",
193195
"name":"PostsItemURL",
194196
"status":"200",
195-
"url":"http://example.com/2"
197+
"url":"PostsItemURL"
196198
}
197199
}
198200
}

docs/sources/v0.54.x/using-k6/http-requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -165,6 +165,8 @@ That code would produce JSON output like this:
165165
{{< code >}}
166166

167167
```json
168+
// For http://example.com/1, note that the url is not present in the JSON.
169+
168170
{
169171
"type":"Point",
170172
"metric":"http_req_duration",
@@ -175,12 +177,12 @@ That code would produce JSON output like this:
175177
"method":"GET",
176178
"name":"PostsItemURL",
177179
"status":"200",
178-
"url":"http://example.com/1"
180+
"url":"PostsItemURL"
179181
}
180182
}
181183
}
182184

183-
// and
185+
// and for http://example.com/2
184186

185187
{
186188
"type":"Point",
@@ -192,7 +194,7 @@ That code would produce JSON output like this:
192194
"method":"GET",
193195
"name":"PostsItemURL",
194196
"status":"200",
195-
"url":"http://example.com/2"
197+
"url":"PostsItemURL"
196198
}
197199
}
198200
}

src/data/markdown/translated-guides/en/02 Using k6/01 HTTP requests.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,8 @@ That code would produce JSON output like this:
156156
<CodeGroup labels={[ ]} lineNumbers={[true]}>
157157

158158
```json
159+
// For http://example.com/1, note that the url is not present in the JSON.
160+
159161
{
160162
"type":"Point",
161163
"metric":"http_req_duration",
@@ -166,12 +168,12 @@ That code would produce JSON output like this:
166168
"method":"GET",
167169
"name":"PostsItemURL",
168170
"status":"200",
169-
"url":"http://example.com/1"
171+
"url":"PostsItemURL"
170172
}
171173
}
172174
}
173175

174-
// and
176+
// and for http://example.com/2
175177

176178
{
177179
"type":"Point",
@@ -183,7 +185,7 @@ That code would produce JSON output like this:
183185
"method":"GET",
184186
"name":"PostsItemURL",
185187
"status":"200",
186-
"url":"http://example.com/2"
188+
"url":"PostsItemURL"
187189
}
188190
}
189191
}

0 commit comments

Comments
 (0)