You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
revert(load-generator): replace k6 with Locust (#3873)
* revert(load-generator): replace k6 with Locust
Reverts #3564. Restores the pre-k6 Locust-based load generator
(locustfile.py, requirements, Envoy /loadgen/ route, compose service
config) while keeping everything unrelated added since that commit.
This reverts commit 18b36c7.
Assisted-by: Claude Sonnet 5
* fix(load-generator): address Copilot review findings on Locust revert
- otel-collector: restore allowed_headers (content-type, traceparent,
baggage) on the OTLP HTTP receiver's CORS config, otherwise the
browser's baggage-bearing preflight requests are rejected and
frontend-web telemetry disappears.
- locustfile.py: register the RoofBinoculars response listener before
navigating instead of after, so a fast image response isn't missed.
- demo.flagd.json: restore loadGeneratorTraffic and loadGeneratorVUs,
which the flagd-ui scheduler tests still assert exist.
- services.py: correct the frontend-web exclusion comment; browser
traffic is enabled in every scope, it's just low-weighted relative
to HTTP traffic, not disabled.
- README.md: point to the stable Locust docs instead of the 2.16
archive, since the restored lockfile pins 2.44.4.
Assisted-by: Claude Sonnet 5
* Apply suggestion from @julianocosta89
* fix(flagd-ui): exclude non-off-resting flags from generic revert tests
loadGeneratorTraffic rests at "on" and loadGeneratorVUs rests at its own
default variant, not "off". With the fixed seed used by these tests, the
scheduler deterministically picked one of them, so the generic "reverts
to off" assertions never passed. Restrict those tests to off-resting
flags, matching the pattern already used elsewhere in this file.
Assisted-by: Claude Sonnet 5
* fix(load-generator): remove dead k6-era load-generator flags
loadGeneratorTraffic and loadGeneratorVUs were introduced by the k6
migration (#3564) and consumed only by its entrypoint.sh wrapper; the
restored Locust code never observed them. Remove both flags along
with the flagd-ui scheduler test cases and README section that
existed only to accommodate their non-off resting state, restoring
the pre-k6 flag set.
Assisted-by: Claude Sonnet 5
* fix(load-generator): use registered telemetry attributes
Replace unregistered span attributes (product.id, quantity, category,
item.count, flood.count) with their existing demo.* registry
equivalents, adding a new demo.request.flood.count attribute for the
one case with no existing match, and declare all of them for
service.load_generator per the telemetry-schema conventions.
Assisted-by: Claude Sonnet 5
* fix(load-generator): correct changelog and telemetry schema docs
- Restore the #3564 changelog bullets under 3.0.0, which was already
released with them, and add a new Unreleased entry for this revert
instead of rewriting released history.
- Fix the service.load_generator attribute group: its brief claimed
"baggage attributes" but most of its members are plain span
attributes, and it was missing user.id, which locustfile.py also
emits as a span attribute.
Assisted-by: Claude Sonnet 5
* default flagd.json
---------
Co-authored-by: Juliano Costa <julianocosta89@outlook.com>
Co-authored-by: Juliano Costa <juliano.costa@datadoghq.com>
Copy file name to clipboardExpand all lines: src/flagd/demo.flagd.json
+4-15Lines changed: 4 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -93,24 +93,13 @@
93
93
"on": 100
94
94
}
95
95
},
96
-
"loadGeneratorTraffic": {
97
-
"defaultVariant": "on",
98
-
"description": "Enable synthetic traffic from the load generator. Turn off to pause all load-generator scenarios.",
96
+
"loadGeneratorFloodHomepage": {
97
+
"defaultVariant": "off",
98
+
"description": "Flood the frontend with a large amount of requests.",
99
99
"state": "ENABLED",
100
100
"variants": {
101
101
"off": 0,
102
-
"on": 1
103
-
}
104
-
},
105
-
"loadGeneratorVUs": {
106
-
"defaultVariant": "5",
107
-
"description": "Number of concurrent virtual users the load generator's HTTP scenario runs. Changes take effect on the wrapper's next poll, restarting k6.",
0 commit comments