See how every kind of Rails log line lands on Laravel Cloud.

Writes at a given severity. Anything below the configured level is dropped (production defaults to info). The block form is only evaluated if the level is enabled.

Rails.logger.info "message"
Rails.logger.debug { expensive_string }

Prefixes every line inside the block with [tags]. Production already tags every request line with its request_id via config.log_tags.

Rails.logger.tagged("billing", "user:42") do
  Rails.logger.info "message"
end

The new first-party structured logging API. Events carry a payload, tags, context and source location, and are printed as JSON lines here. Rails emits its own request and job events through it too.

Rails.event.set_context(request_id: ...)
Rails.event.tagged("checkout") do
  Rails.event.notify("user.signed_up", user_id: 1)
end

How Rails produces its own log lines: instrument a block, and a LogSubscriber turns the event and its duration into a line.

ActiveSupport::Notifications.instrument("checkout.demo") do
  ...
end

# DemoLogSubscriber < ActiveSupport::LogSubscriber
def checkout(event) = info { "#{event.duration}ms" }

The standard interface for error trackers like Sentry or Nightwatch. It doesn't log on its own, so this app subscribes a logger to it.

Rails.error.report(error, handled: true, severity: :error)
Rails.error.handle { risky_call }

Raises from the controller. Rails logs the error with a multi-line backtrace and renders the 500 page. Use the browser back button to return.

raise RuntimeError, "boom"

Runs in-process on a background thread. Job lines are tagged [ActiveJob] [LogDemoJob] [job_id] and include enqueue, perform and failure lines.

LogDemoJob.perform_later("message")

Writes straight to the process streams. Checks whether the platform captures both, and whether it treats stderr as errors.

$stdout.puts "message"
$stderr.puts "message"
warn "message"