Using Rails' silence_healthcheck_path

[simonjnesta]

I currently have AppSignal setup, in my production config:

  # Log to AppSignal, but rebroadcast logs to stdout
  appsignal_logger = Appsignal::Logger.new("rails")
  appsignal_logger.broadcast_to(ActiveSupport::TaggedLogging.logger($stdout))
  config.logger = ActiveSupport::TaggedLogging.new(appsignal_logger)

  # Prevent health checks from clogging up the logs.
  config.silence_healthcheck_path = "/up"

I am receiving logs in AppSignal, but the silence_healthcheck_path option doesn't seem to be doing anything. Is there a way to get this working? I'd rather my logs not be clogged up.

[tombruijn]

Hi @simonjnesta, unless Rails ignores this for us, I don't think we do anything with this setting, but it would be good if we did.

You say you're still receiving logs from requests made to the /up healthcheck route? Or do you (also) mean trace data (performance and error issues)?

[simonjnesta]

I think Rails should ignore it for you, but it doesn't seem to be working for me.

I'm still getting logs like:

[rails] Completed 200 OK in 0ms (Views: 0.1ms | ActiveRecord: 0.0ms (0 queries, 0 cached) | GC: 0.0ms)
[rails] Started GET "/up" for 10.0.2.211 at 2025-07-29 11:59:27 +0000
[rails] Processing by Rails::HealthController#show as HTML 

Relevant Rails code:
https://github.com/rails/rails/blob/40a3f2fedc12e70750e2b14ad096c135e7bb1df7/railties/lib/rails/application/default_middleware_stack.rb#L57
https://github.com/rails/rails/blob/40a3f2fedc12e70750e2b14ad096c135e7bb1df7/railties/lib/rails/rack/silence_request.rb#L21

Rails.logger.silence { ... } is being called.

I decided to revert the default config in my dev environment, and instead use an initializer:

appsignal_logger = Appsignal::Logger.new("rails")
appsignal_logger.broadcast_to(Rails.logger)
Rails.logger = appsignal_logger

which resulted in weird behaviour in my logging - the GET "/up" line is gone, but everything else is the same (note: this wasn't connected to AppSignal, just using the rebroadcast feature):

[rails] Completed 200 OK in 0ms (Views: 0.1ms | ActiveRecord: 0.0ms (0 queries, 0 cached) | GC: 0.0ms)
[rails] Processing by Rails::HealthController#show as HTML 

And to clarify, if I switch to the default logger, none of those log lines appear for the /up route.

[shairyar]

What version of Rails are you using @simonjnesta

[shairyar]

I am testing it using Rails 8

Rails version                8.0.2
RubyGems version             3.6.9
appsignal                    4.6.0

I configured my test app using multiple logging backends.

Since I am testing it in a development environment, I added the following to my development.rb file.

  # Prevent health checks from clogging up the logs.
  config.silence_healthcheck_path = "/up"

After that, I restarted my application, visited the /up route, and I do not see the logs from that action being sent to AppSignal.

[simonjnesta]

Ruby 3.4.3
Rails 8.0.2
appsignal 4.5.17

Our config setup is slightly different, so I will reconfigure the linked way to see if it's working when I get the chance.

[shairyar]

Sure, let me know whenever you get the chance.