[DOCS-10330] Add Set up Worker in ECS Fargate #29356
Conversation
Preview links (active after the
|
|
|
||
| [Create a task definition][1]. The task definition describes which containers to run, the configuration (such as the environment variables and ports), and the CPU and memory resources allocated for the task. | ||
|
|
||
| Set the `DD_OP_SOURCE_*` environment variable according to the configuration of the pipeline and port mappings. `DD_OP_API_ENABLED` and `DD_OP_API_ADDRESS` are used to allow the load balancer to do health checks on the routing targets. The CPU and memory resources should be increased for the production usage. |
There was a problem hiding this comment.
Can we consider:
DD_OP_API_ENABLED and DD_OP_API_ADDRESS allow the load balancer to perform health checks on the routing targets.
Additionally, What are routing targets? Can we simplify?
"The CPU and memory resources should be increased for the production usage." -> to what?
There was a problem hiding this comment.
Additionally, What are routing targets? Can we simplify?
"The CPU and memory resources should be increased for the production usage." -> to what?
@kennonkwok could you take a look?
There was a problem hiding this comment.
Re "routing targets, we can simplify that by calling them "workers" instead.
@ckelner can you advise on the resources?
There was a problem hiding this comment.
Re "routing targets, we can simplify that by calling them "workers" instead.
@kennonkwok Just want to confirm that "workers" are OP Workers?
Edit: NVM, reread and it's OP Workers.
There was a problem hiding this comment.
@kennonkwok @ckelner was chatting with Pratik and we decided to just put xxxx for CPU and memory in the task definition, so users will know to change that. And we'll remove the line:
The CPU and memory resources should be increased for the production usage.
|
|
||
| [Create a task definition][1]. The task definition describes which containers to run, the configuration (such as the environment variables and ports), and the CPU and memory resources allocated for the task. | ||
|
|
||
| Set the `DD_OP_SOURCE_*` environment variable according to the configuration of the pipeline and port mappings. `DD_OP_API_ENABLED` and `DD_OP_API_ADDRESS` are used to allow the load balancer to do health checks on the routing targets. The CPU and memory resources should be increased for the production usage. |
There was a problem hiding this comment.
| Set the `DD_OP_SOURCE_*` environment variable according to the configuration of the pipeline and port mappings. `DD_OP_API_ENABLED` and `DD_OP_API_ADDRESS` are used to allow the load balancer to do health checks on the routing targets. The CPU and memory resources should be increased for the production usage. | |
| Set the `DD_OP_SOURCE_*` environment variable according to the configuration of the pipeline and port mappings. `DD_OP_API_ENABLED` and `DD_OP_API_ADDRESS` allow the load balancer to do health checks on the routing targets. The CPU and memory resources should be increased for the production usage. |
content/en/observability_pipelines/install_the_worker/set_up_the_worker_in_ecs_fargate.md
Outdated
Show resolved
Hide resolved
…he_worker_in_ecs_fargate.md
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes