docs: Update prometheus.exporter.cadvisor to add information about permissions#5009
Merged
clayton-cornell merged 9 commits intomainfrom Feb 17, 2026
Merged
Conversation
Contributor
|
💻 Deploy preview available (Update prometheus.exporter.cadvisor to add information about permissions): |
976a0e3 to
9e681f0
Compare
Contributor
|
💻 Deploy preview deleted (docs: Update prometheus.exporter.cadvisor to add information about permissions). |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the prometheus.exporter.cadvisor documentation to better explain platform limitations and the permissions/mount requirements needed to successfully collect container metrics across common deployment environments.
Changes:
- Adds a Linux-only limitation note and a new permissions/configuration section with tabs for Linux binary, Kubernetes, and Docker container deployments.
- Adds Docker Compose and Kubernetes DaemonSet examples, including required mounts/security settings.
- Makes small wording/heading adjustments (for example, “Example” → “Examples”, minor phrasing tweaks).
docs/sources/reference/components/prometheus/prometheus.exporter.cadvisor.md
Outdated
Show resolved
Hide resolved
docs/sources/reference/components/prometheus/prometheus.exporter.cadvisor.md
Outdated
Show resolved
Hide resolved
docs/sources/reference/components/prometheus/prometheus.exporter.cadvisor.md
Outdated
Show resolved
Hide resolved
docs/sources/reference/components/prometheus/prometheus.exporter.cadvisor.md
Outdated
Show resolved
Hide resolved
…er.cadvisor.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
thampiotr
approved these changes
Feb 17, 2026
Contributor
thampiotr
left a comment
There was a problem hiding this comment.
It looks correct, I'm not able to spot any obvious issues.
docs/sources/reference/components/prometheus/prometheus.exporter.cadvisor.md
Outdated
Show resolved
Hide resolved
…er.cadvisor.md Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com>
grafana-alloybot bot
pushed a commit
that referenced
this pull request
Feb 17, 2026
…rmissions (#5009) This PR adds information about how to set permissions to run Alloy in local, Docker and K8s. It was compared against the related Issues, and compared against advice give in the Alloy forums. Fixes: * #990 * #3482 --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com> (cherry picked from commit 4f096f5)
grafana-alloybot bot
pushed a commit
that referenced
this pull request
Feb 17, 2026
…rmissions (#5009) This PR adds information about how to set permissions to run Alloy in local, Docker and K8s. It was compared against the related Issues, and compared against advice give in the Alloy forums. Fixes: * #990 * #3482 --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com> (cherry picked from commit 4f096f5)
clayton-cornell
added a commit
that referenced
this pull request
Feb 17, 2026
…rmissions [backport] (#5555) ## Backport of #5009 This PR backports #5009 to release/v1.13. ### Original PR Title docs: Update prometheus.exporter.cadvisor to add information about permissions ### Original PR Author @clayton-cornell ### Description This PR adds information about how to set permissions to run Alloy in local, Docker and K8s. It was compared against the related Issues, and compared against advice give in the Alloy forums. Fixes: * #990 * #3482 --- *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> Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com>
clayton-cornell
added a commit
that referenced
this pull request
Feb 17, 2026
…rmissions [backport] (#5554) ## Backport of #5009 This PR backports #5009 to release/v1.12. ### Original PR Author @clayton-cornell ### Description This PR adds information about how to set permissions to run Alloy in local, Docker and K8s. It was compared against the related Issues, and compared against advice give in the Alloy forums. Fixes: * #990 * #3482 --- *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> Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com>
jharvey10
pushed a commit
that referenced
this pull request
Feb 26, 2026
…rmissions (#5009) This PR adds information about how to set permissions to run Alloy in local, Docker and K8s. It was compared against the related Issues, and compared against advice give in the Alloy forums. Fixes: * #990 * #3482 --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Piotr <17101802+thampiotr@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.
This PR adds information about how to set permissions to run Alloy in local, Docker and K8s. It was compared against the related Issues, and compared against advice give in the Alloy forums.
Fixes: