AnyCable logo lightAnyCable logo darkAnyCable

  • Overview
    • Getting Started
    • Architecture
    • WebSocket Servers
    • Benchmarks
    • Pro version pro
    • Troubleshooting 🔥
    • Commercial Support 🆘
    • Release Notes
  • Ruby
    • Getting Started with Rails
    • CLI
    • Configuration
    • Authentication
    • Channels State
    • gRPC Middlewares
    • Health Checking
    • Logging
    • Exceptions Handling
    • Instrumentation via Yabeda 🔗
    • Action Cable Compatibility
    • Using with Hotwire
    • Using with Stimulus Reflex
    • Non-Rails Usage
    • Broadcast Adapters
  • AnyCable-Go
    • Getting Started
    • Configuration
    • Instrumentation
    • Health Checking
    • Tracing
    • OS Tuning
    • JWT Identification
    • Speedy Hotwire & Cable Ready
    • Apollo GraphQL pro
    • Binary formats pro
    • Embedded NATS
    • Using as a Library
  • JS/TS client 🔗
  • Deployment
    • Heroku
    • Fly.io
    • Render
    • Docker
    • Kubernetes
    • Capistrano
    • Systemd
    • AWS Beanstalk 🔗
    • AWS ECS 🔗
    • Load Balancing
    • Load Testing
  • Misc
    • Action Cable Protocol
    • Protobuf Definitions
    • How to Write AnyCable-Compatible Server
  • Upgrade Notes
    • From v1.2.x to v1.3.0
    • From v1.0.x to v1.1.0
    • From v0.6.x to v1.0.0
  • Community
    • Twitter
    • Discord

AnyCable-Go Health Checking

Health check endpoint is enabled by default and accessible at /health path.

You can configure the path via the --health-path option (or ANYCABLE_HEALTH_PATH env var).

You can use this endpoint as readiness/liveness check (e.g. for load balancers).

PREVIOUS
Instrumentation
NEXT
Tracing