-
Notifications
You must be signed in to change notification settings - Fork 2
DRAFT: add first draft of load simulator #172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 7 commits
a888ee4
12fb40a
6866079
0c274c9
2010bdc
e960f09
eac7bc5
0113ca5
9b1e57c
6950812
183a234
3429e47
339b044
03b1aec
dc6dee9
055bc08
acb5356
6c37f0b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| # Unless explicitly stated otherwise all files in this repository are licensed under the Apache License Version 2.0. | ||
| # This product includes software developed at Datadog (https://www.datadoghq.com/). | ||
| # Copyright 2025-Present Datadog, Inc. | ||
|
|
||
| # Load testing service configuration | ||
| # Usage: docker compose -f docker-compose.yml -f docker-compose.load-test.yml --profile load-test run --rm load-simulator | ||
|
|
||
| services: | ||
| # Disable rate limiting for load testing | ||
| web-backend: | ||
| environment: | ||
| - SKIP_RATE_LIMIT=true | ||
|
|
||
| user-management: | ||
| environment: | ||
| - RateLimiting__Enabled=false | ||
|
|
||
| load-simulator: | ||
| image: grafana/k6:latest | ||
| volumes: | ||
| - ./load-tests:/scripts | ||
| environment: | ||
| - TARGET_URL=http://traefik:80 | ||
| - EXTERNAL_URL=http://localhost:8080 | ||
| - WORKLOAD=${WORKLOAD:-smoke} | ||
| - SCENARIO=${SCENARIO:-mixed} | ||
| - TEST_EMAIL=${TEST_EMAIL:-user@stickerlandia.com} | ||
| - TEST_PASSWORD=${TEST_PASSWORD:-Stickerlandia2025!} | ||
| command: run /scripts/load-test.js | ||
| depends_on: | ||
| traefik: | ||
| condition: service_healthy | ||
| user-management: | ||
| condition: service_healthy | ||
| sticker-catalogue: | ||
| condition: service_healthy | ||
| sticker-award: | ||
| condition: service_healthy | ||
| web-backend: | ||
| condition: service_started | ||
| datadog-agent: | ||
| condition: service_started | ||
|
||
| profiles: | ||
| - load-test | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -480,6 +480,7 @@ services: | |
| container_name: datadog-agent | ||
| profiles: | ||
| - monitoring | ||
| - load-test | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does it make sense to turn agent on if load-testing is on but monitoring isnt?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @scottgerring Hmm, good question. I guess for what we are using load testing for is to generate data for the agent. Not load testing in the traditional sense. So yeah, I think we should turn load testing on even if monitoring isn't. Which is what this will do right? Or have I misunderstood docker profiles?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is an agent - so this'll turn on the datadog-agent, if we ask for load-testing |
||
| environment: | ||
| # Core Datadog configuration | ||
| - DD_API_KEY=${DD_API_KEY} | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.