Health check troubleshooting
Get help resolving common health check issues.
Health check failures
When Health Checks fail, verify the target Share is active and accessible, confirm the specified endpoint exists and responds correctly, validate timeout settings allow sufficient response time, and ensure the expected HTTP response code matches your service's actual response.
Timeout issues
Frequent timeouts typically require adjusting configured timeout values for services with longer processing times. Investigate backend service performance for bottlenecks or resource constraints, and consider network latency between NetFoundry's infrastructure and your services when setting timeout values.
Authentication errors
Authentication problems occur when health check endpoints are improperly secured or have overly restrictive access controls. Verify endpoints maintain appropriate security while remaining accessible to NetFoundry's monitoring infrastructure, and ensure health endpoints don't require complex authentication flows that interfere with automated monitoring.
General diagnotic steps
-
Test with simple endpoints: Start troubleshooting with basic endpoints returning simple, predictable responses to isolate whether issues stem from health check configuration or service endpoint complexity.
-
Validate share configuration: Ensure your underlying Share functions correctly by testing it directly before troubleshooting Health Checks, as a properly working Share is fundamental to successful health check operation.
-
Check service logs: Monitor backend service logs during health check execution to understand how your service processes automated requests and identify issues like authentication failures, database connectivity problems, or resource constraints.