healthcheckv2extension with memory_limiter return NOT OK when memory is low

[EmpireErwinKooi]

When I run the custom built opentelemetry-collector-contrib with the experimental healthcheckv2extension enabled, and with memory_limiter active, I would love to see the health check endpoint http response to flip from OK to NOT OK when memory is running low, so that k8s can recycle the container based on the liveness probe.

To illustrate, I have the collector running on docker compose with a low memory limit, and then I'm sending a postman request to the health endpoint:

otel-collector-1     | 2025-09-03T14:53:56.834Z warn    [email protected]/memorylimiter.go:193     Memory usage is above hard limit. Forcing a GC. {"resource": {"service.instance.id": "99d3b996-b99e-4d18-9886-941ebdfa7d2d", "service.name": "otelcol-contrib", "service.version": "0.132.0"}, "otelcol.component.kind": "processor", "cur_mem_mib": 17}
otel-collector-1     | 2025-09-03T14:53:56.846Z info    [email protected]/memorylimiter.go:168     Memory usage after GC.  {"resource": {"service.instance.id": "99d3b996-b99e-4d18-9886-941ebdfa7d2d", "service.name": "otelcol-contrib", "service.version": "0.132.0"}, "otelcol.component.kind": "processor", "cur_mem_mib": 17}