docs: Edit ECS tutorial to add new steps for the otelcol.receiver.awsecscontainermetrics component #5347
Merged
clayton-cornell merged 15 commits intomainfrom Feb 19, 2026
Merged
Conversation
Contributor
|
💻 Deploy preview deleted (docs: Edit ECS tutorial to add new steps for the |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the ECS/Fargate OpenTelemetry collection tutorial to add an option using the experimental otelcol.receiver.awsecscontainermetrics component, and cleans up existing instructions and examples.
Changes:
- Adds a new “native receiver” path using
otelcol.receiver.awsecscontainermetricswith example Alloy configuration and required--stability.level=experimentalflag. - Refactors the existing Prometheus ECS exporter path, clarifying it as the “stable” option and updating the Alloy configuration to current patterns (e.g.,
env(...), remote_write). - Normalizes bullets, shell paths (e.g.,
/bin/bash), container image versions, and removes unused link references.
Fix potential shell injection vulnerability Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
dehaansa
reviewed
Feb 17, 2026
|
|
||
| #### Prometheus exporter | ||
|
|
||
| If you prefer a stable approach, use the Prometheus ECS exporter as a sidecar container. |
Contributor
There was a problem hiding this comment.
IMO this segue implies that the receiver isn't a great choice, I would lean more towards something like "Running the ECS exporter in a sidecar container does not require running Alloy with experimental stability"
|
|
||
| For the Prometheus exporter, use `"printenv ALLOY_CONFIG_CONTENT > /tmp/config_file && exec /bin/alloy run --server.http.listen-addr=0.0.0.0:12345 /tmp/config_file"`. | ||
|
|
||
| Make sure you don't omit the double quotes around the command. |
Contributor
There was a problem hiding this comment.
Double negative? "Make sure you include..."
|
|
||
| * Only add the {{< param "PRODUCT_NAME" >}} container, not the Prometheus exporter, and run the task as a daemon so it automatically runs one instance per node in your cluster. | ||
| * Update your {{< param "PRODUCT_NAME" >}} configuration to collect metrics from the instance. | ||
| - If you're using the Prometheus exporter, you don't need to add the ecs-exporter sidecar for EC2 instance metrics. |
Contributor
There was a problem hiding this comment.
Suggested change
| - If you're using the Prometheus exporter, you don't need to add the ecs-exporter sidecar for EC2 instance metrics. | |
| - If you're using the awsecscontainermetrics receiver, you don't need to add the ecs-exporter sidecar for EC2 instance metrics. |
dehaansa
approved these changes
Feb 18, 2026
grafana-alloybot bot
pushed a commit
that referenced
this pull request
Feb 19, 2026
…secscontainermetrics` component (#5347) Edit ECS tutorial to add new steps for the `otelcol.receiver.awsecscontainermetrics` component . Split tutorial into two paths... the original "stable" option and the new experimental `otelcol.receiver.awsecscontainermetrics` option. Clean up content: * fix bullets for consistency * fix the paths eg `/bin/bash` instead of just `bash` * removed some unused link definitions Fixes #4566 ### Note to reviewers I used AI to generate the configs. I do not have ECS to do any testing so I relied on AI to check the configuration examples. The configuration code snippets should be checked for validity and accuracy Preview for review is here: https://deploy-preview-alloy-5347-zb444pucvq-vp.a.run.app/docs/alloy/latest/collect/ecs-opentelemetry-data/ --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> (cherry picked from commit d37d130)
clayton-cornell
added a commit
that referenced
this pull request
Feb 19, 2026
…secscontainermetrics` component [backport] (#5585) ## Backport of #5347 This PR backports #5347 to release/v1.13. ### Original PR Author @clayton-cornell ### Description Edit ECS tutorial to add new steps for the `otelcol.receiver.awsecscontainermetrics` component . Split tutorial into two paths... the original "stable" option and the new experimental `otelcol.receiver.awsecscontainermetrics` option. Clean up content: * fix bullets for consistency * fix the paths eg `/bin/bash` instead of just `bash` * removed some unused link definitions Fixes #4566 ### Note to reviewers I used AI to generate the configs. I do not have ECS to do any testing so I relied on AI to check the configuration examples. The configuration code snippets should be checked for validity and accuracy Preview for review is here: https://deploy-preview-alloy-5347-zb444pucvq-vp.a.run.app/docs/alloy/latest/collect/ecs-opentelemetry-data/ --- *This backport was created automatically.* Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
jharvey10
pushed a commit
that referenced
this pull request
Feb 26, 2026
…secscontainermetrics` component (#5347) Edit ECS tutorial to add new steps for the `otelcol.receiver.awsecscontainermetrics` component . Split tutorial into two paths... the original "stable" option and the new experimental `otelcol.receiver.awsecscontainermetrics` option. Clean up content: * fix bullets for consistency * fix the paths eg `/bin/bash` instead of just `bash` * removed some unused link definitions Fixes #4566 ### Note to reviewers I used AI to generate the configs. I do not have ECS to do any testing so I relied on AI to check the configuration examples. The configuration code snippets should be checked for validity and accuracy Preview for review is here: https://deploy-preview-alloy-5347-zb444pucvq-vp.a.run.app/docs/alloy/latest/collect/ecs-opentelemetry-data/ --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Edit ECS tutorial to add new steps for the
otelcol.receiver.awsecscontainermetricscomponent .Split tutorial into two paths... the original "stable" option and the new experimental
otelcol.receiver.awsecscontainermetricsoption.Clean up content:
/bin/bashinstead of justbashFixes #4566
Note to reviewers
I used AI to generate the configs. I do not have ECS to do any testing so I relied on AI to check the configuration examples. The configuration code snippets should be checked for validity and accuracy
Preview for review is here: https://deploy-preview-alloy-5347-zb444pucvq-vp.a.run.app/docs/alloy/latest/collect/ecs-opentelemetry-data/