Impact

• Upgrading cAdvisor requires updating the Docker plugin options to include a containerd endpoint when available. This is necessary to maintain metrics coverage (notably for overlayfs-backed containers).
• Your PR already includes the required code and doc updates; below is a concise summary to help reviewers understand why they were needed and what changed.

What changed and why it matters

• In newer cAdvisor (and the Grafana fork you pin via replace), the Docker plugin accepts an additional option to supply the containerd endpoint. This allows cAdvisor to read container information correctly in environments where overlayfs is used by containerd.
• The project switched the replace to a Grafana cAdvisor fork tag “grafana-v0.54.1-noglobals,” indicating internal changes around globals removal; no extra code changes are required here in your tree beyond the plugin options update.

Required code changes

• Pass the containerd endpoint to the Docker plugin options:

--- a/internal/static/integrations/cadvisor/cadvisor.go
+++ b/internal/static/integrations/cadvisor/cadvisor.go
@@ -94,11 +94,12 @@ func New(logger log.Logger, c *Config) (integrations.Integration, error) {
 		}),
 		"crio": crio.NewPlugin(),
 		"docker": docker.NewPluginWithOptions(&docker.Options{
-			DockerEndpoint: c.Docker,
-			DockerTLS:      c.DockerTLS,
-			DockerCert:     c.DockerTLSCert,
-			DockerKey:      c.DockerTLSKey,
-			DockerCA:       c.DockerTLSCA,
+			DockerEndpoint:     c.Docker,
+			DockerTLS:          c.DockerTLS,
+			DockerCert:         c.DockerTLSCert,
+			DockerKey:          c.DockerTLSKey,
+			DockerCA:           c.DockerTLSCA,
+			ContainerDEndpoint: c.Containerd,
 		}),
 		"systemd": systemd.NewPlugin(),
 	}

Docs change associated with the upgrade

• A note was added advising that for overlayfs storage, the containerd host must be configured:
  • “If a container is using the overlayfs storage driver, ensure the containerd_host attribute is set correctly to be able to retrieve its metrics.”

References

• Your repository changes clearly demonstrate the API usage requirement for the new plugin option and the documentation guidance for overlayfs.

Impact

• No code changes in your tree are required. The integration configuration and usage remain the same.

Observations from your tree

• No changes were needed to your exporter wiring or configuration structures.
• Testdata and example Alloy snippets retain the same fields (e.g., mongodb_uri, direct_connect, discovering_mode) and behavior.
• This suggests that the library surface you’re using remains compatible across this bump.

Notes

• v0.x versions can include breaking changes, but there are no surfaced API changes in your usage between these versions in this repo.

Impact

• Patch-level update; no API changes required.

Observations from your tree

• No code updates were introduced to accommodate this version bump.
• This aligns with typical patch releases containing bug fixes and minor improvements only.