The controller and action the request was routed to, or the path of the URL if it wasn’t routed to a controller. The controller and action are displayed as they are when defining Rails routes—for example, the index action of UsersController would be users#index.

The full name of the controller the request was routed to. For example, UsersController. This field is empty for requests not routed to a controller.

The name of the action the request was routed to. This field is empty for requests not routed to a controller.

The path and query components of the URL.

The path component of the URL.

The query component of the URL.

The HTTP method of the request. For example, GET or POST.

The IP address the request originated from.

Whether the request is for a static asset (such as a stylesheet, script, or image) or a dynamic request served by the Rails application.

The Rails response format. For example, HTML or JS. This field is empty for requests not routed to a controller.

The HTTP response code and a textual description of the code, concatenated with an em dash. For example, 200 — OK. This field may be empty for requests where logging is interrupted—for example, certain routing errors.

The HTTP response code. This field may be empty for requests where logging is interrupted—for example, certain routing errors.

A textual description of the HTTP response code. This field may be empty for requests where logging is interrupted—for example, certain routing errors.

The total amount of time spent handling the request in seconds. This field may be empty for requests where logging is interrupted—for example, certain routing errors.

The time spent rendering views in seconds. This field may be empty for requests that don’t render views.

The time spent performing database operations in seconds. This field may be empty for requests that don’t perform database operations.

The date and time of the request.

An un-nested array of the request’s query parameters. See Parameters.

The request’s activities. See Activities.

The parameter’s name. Since the parameters collection is un-nested, any hash or array parameters will use their complete names including brackets—for example, user[address][city] or ids[].

The parameter’s value.

The type of activity. Possible values are:

• Message
• Query
• Render
• Error
• Stack Trace
• Mail
• Redirect
• Cache
• File
• Data
• Filter Chain Halt

A summary of the activity. Each type of activity includes different information in the summary:

Message

The message.

Query

The SQL of the query (querySQL).

Render

The template name (renderTemplate) with a parenthesized render count (renderCount) if rendered as a collection more than once. For example, users/user (×3). The render count is formatted according to your localization settings.

Error

The exception (errorException) and message (errorMessage) concatenated with an em dash. For example, ActiveRecord::RecordNotFound — Couldn't find User with id=1.

Stack Trace

The source file (stackTraceFile), line number (stackTraceLine), and method (stackTraceMethod) concatenated with an em dash and colon. For example, lib/active_record/relation/finder_methods.rb — line 198: raise_record_not_found_exception!. The line number is formatted according to your localization settings.

Mail

The mailer (mailMailer), subject (mailSubject), and to addresses (mailToAddresses) of the email concatenated with a colon and an em dash. For example, UserNotifier: A new user has signed up — admin@example.com, sales@example.com.

Redirect

The redirect URL (redirectURL).

Cache

The cache operation (cacheOperation) and key (cacheKey). For example, Read users/1.

File

The path of the file (filePath).

Data

The filename sent to the browser (dataFilename).

Filter Chain Halt

The name of the halting filter (filterChainHaltFilter).

Whether the activity originates in the Rails framework itself. This is relevant for filtering certain activities such as queries, renders, and stack traces where Rails itself may generating activities rather than your application directly.

A numeric representation of log level of the activity. This value is an integer so that inequalities can be used to filter activities—for example, you may want to see all activities with a log level greater than warnings. Possible values and the log levels they correspond to are:

• 0: Debug
• 1: Info
• 2: Warn
• 3: Error
• 4: Fatal
• 5: Unknown

The duration of the activity in seconds. This field may be empty for activities that don’t have a duration.

The name of the ActiveRecord model associated with the query. This field is empty for queries not associated with a model.

The query operation performed. Possible values are:

• Load
• Insert
• Update
• Delete
• Existence
• Count
• Calculation
• Transaction
• Schema
• Fixture
• Other

The complete SQL statement of the query.

Whether the query was in the Rails query cache.

The query’s explains. See Explains.

The path and name of the template rendered, as passed to a call to render. For example, users/user.

The full path and filename within the views directory of the template rendered.

The path and name of the layout used to render the template. For example, layouts/application. This field may be empty if no layout was used.

The full path and filename within the views directory of the layout used to render the template. This field may be empty if no layout was used.

Whether the template rendered was a partial.

The number of times the template was rendered if rendered as a collection.

The type of exception.

The message associated with the error.

The path of the file containing the source code for the stack frame.

The line number the stack frame is on.

The name of the method the stack frame is in.

The name of the gem the stack frame is in. This field may be empty if the stack frame is not within a gem.

The version of the gem the stack frame is in. This field may be empty if the stack frame is not within a gem.

The full name of the mailer that generated the email. For example, UserNotifier.

The subject of the email.

The full From header of the email. For example, John Doe <john@example.com>.

The email address from the From header of the email. For example, john@example.com.

The display name from the From header of the email. For example, John Doe.

The full To header of the email. For example, John Doe <john@example.com>, Jane Doe <jane@example.com>.

A comma separated list of the email addresses from the To header of the email. For example, john@example.com, jane@example.com.

A comma separated list of the display names from the To header of the email. For example, John Doe, Jane Doe.

The full CC header of the email.

A comma separated list of the email addresses from the CC header of the email.

A comma separated list of the display names from the CC header of the email.

The full BCC header of the email.

A comma separated list of the email addresses from the BCC header of the email.

A comma separated list of the display names from the BCC header of the email.

The plain text body of the email or the text/plain part of a multipart email.

The HTML body of the email or the text/html part of a multipart email.

The raw body of the email, including the headers and all parts of multipart emails.

The email’s headers. See Mail Headers.

The URL redirected to.

The type of cache operation performed. Possible values are:

• Read
• Write
• Expire
• Existence

The cache key operated on.

The path of the file being sent.

The filename the file is being sent to the browser with.

The HTTP content type of the file.

The way the file is being sent to the browser, either for display inline or as a download.

The filename the data is being sent to the browser with.

The HTTP content type of the data.

The way the data is being sent to the browser, either for display inline or as a download.

The name of the filter that halted the filter chain.

The textual information associated with the explain. This field is only relevant to Postgres and SQLite.

The table column of MySQL explains.

The key column of MySQL explains.

The rows column of MySQL explains.

The filtered column of MySQL explains represented as a percentage from 0 to 1. For example, 0.5 when 50% of rows are filtered.

The Extra column of MySQL explains.

The ref column of MySQL explains.

The key_len column of MySQL explains.

The possible_keys column of MySQL explains.

The type column of MySQL explains.

The select_type column of MySQL explains.

The selectid column of SQLite explains.

The from column of SQLite explains.

Child explains nested below this one. This field is only relevant to database adaptors that output nested explains (currently Postgres and SQLite).

The header’s name.

The header’s value.