How to Monitor Your Ruby on Rails App with Pingzo

Ruby on Rails remains a foundational framework for launching scalable SaaS products and complex database-driven web applications due to its comprehensive convention-over-configuration paradigm. However, running a Rails application in production requires continuous monitoring.

If database connection pools deplete or slow Active Record calls saturate your Puma application server threads, your web server will stop accepting new user requests. This tutorial shows you how to configure active monitoring and WhatsApp alerts using Pingzo to protect your Ruby on Rails application.

1. Why Ruby on Rails Apps Need Monitoring

Ruby on Rails applications run on multi-threaded application servers (like Puma). This architecture introduces specific failure modes:

• Puma Thread Starvation: Puma allocates a fixed number of threads per worker process. If several requests hang due to database query latency or slow external API calls, Puma threads quickly saturate. The server returns 502 or 504 errors for all new incoming connections.
• Active Record Pool Starvation: Rails limits the database connection pool. If your code opens threads that do not return connections properly, the database pool starves, causing Active Record errors.
• Sidekiq Worker Crashes: Scheduled tasks and emails run on Sidekiq. If Redis connections disconnect or workers run out of memory, background processing stops silently.

2. What to Monitor in Ruby on Rails

For Rails applications, you should monitor:

• HTML Response & Latency: Monitor response times. A slow response indicates database contention or Puma thread starvation.
• Uptime Check (Health Route): Create a dedicated health check endpoint that pings the database.
• SSL Availability: Protect secure sessions. Set up automatic checks for your certificates using the SSL Inspector.

Here is a recommended health check endpoint configuration in Rails (app/controllers/health_controller.rb):

class HealthController < ApplicationController
  def show
    # Verify Active Record connection is active
    ActiveRecord::Base.connection.active?
    render json: { status: 'healthy', database: 'connected' }, status: :ok
  rescue => e
    render json: { status: 'unhealthy', error: e.message }, status: :service_unavailable
  end
end

Remember to register the path in your config/routes.rb:

get '/health', to: 'health#show'

3. How to Set Up Pingzo in 60 Seconds

Configuring a check for your Rails application on Pingzo is simple:

1. Retrieve Endpoint URL: Copy your Rails app health check address (for example, https://myrailsapp.com/health).
2. Add Monitor: Open your Pingzo dashboard, click Create Monitor, paste the endpoint URL, and select a 1-minute interval.
3. Specify Validation Rules: Set the check to require a 200 OK status and verify that the JSON body contains the text string "status":"healthy".

4. Setting Up WhatsApp Alerts for Rails Outages

Standard email alerts are easily missed or delayed. Pingzo routes critical alerts via the official WhatsApp Business API to deliver instant notifications directly to your phone:

1. Go to Alert Channels in the Pingzo settings and select WhatsApp.
2. Provide your mobile number and enter the validation code.
3. Add the WhatsApp channel to your Rails monitor.

If a database query lock starves your Puma thread pool or your Sidekiq workers crash, you will receive a WhatsApp message within seconds.

Conclusion & Next Steps

Active monitoring keeps your Ruby on Rails application fast and reliable. If you want to check your current page health right now, run an audit using our Website Uptime Checker.