The controller_call event represents an invocation of your controller within the HTTP request cycle. The order of events generally looks like:

Started Get "/"
Processing by WelcomeController#index as html <-------------------------
Rendered welcome/index.html.erb within layouts/application (0.2ms)
Completed 200 OK in 2.46ms

Example JSON Structure

  "event": {
    "server_side_app": {
      "controller_call": {
        "controller": "WelcomeController",
        "action": "index",
        "params_json": "{\"id\": 2, \"type\": \"user\"}"

Field descriptions

Name Type Description
controller string The class name of the controller called.
action string The action name of the controller action called.
params_json string A JSON representation of the parsed parameters sent to the controller. This is great for request inspect to ensure the data being sent to your controllers is correct.

Using this data

Example queries:

  • Full path: event.server_side_app.controller_call.controller:WeclomeController
  • Short path: controller_call.controller:WelcomeController - Short paths are aliases allowing for simpler access to these fields.
  • Only this event: is:controller_call

See our doc on using context & event data.

Questions? Need help?

Chat with us, just click the talk button in the bottom right of this page.

Chat with us

Start a trial - 15 days free

Log better and solve problems faster, today. Less than 1 minutes to install.

Start a trial