Databases
StackOverflow2013
Postsdbo
POHeroku: see params and sql activity in logs?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHeroku: see params and sql activity in logs?
    primarykey
    data
    text
    <p>When i view my heroku logs on the server (with <code>heroku logs --tail --app myapp</code>) i see something like this:</p> <pre><code>2011-06-21T14:09:25+00:00 app[web.1]: Started PUT "/reports/19.xml" for 77.89.149.137 at 2011-06-21 07:09:25 -0700 2011-06-21T14:09:25+00:00 heroku[router]: PUT myapp.heroku.com/reports/19.xml dyno=web.1 queue=0 wait=0ms service=7ms status=401 bytes=28 2011-06-21T14:09:26+00:00 heroku[nginx]: PUT /reports/19.xml HTTP/1.1 | 77.89.149.137 | 656 | http | 401 </code></pre> <p>While in my local log i'd see something like this:</p> <pre><code>Started PUT "/reports/19" for 127.0.0.1 at 2011-06-21 15:27:01 +0100 Processing by ReportsController#update as XML Parameters: {"report"=&gt;{"workflow_status"=&gt;"3"}, "id"=&gt;"19"} Person Load (0.9ms) SELECT "people".* FROM "people" WHERE "people"."email" = 'madeupemai@lkklj.com' LIMIT 1 Report Load (0.4ms) SELECT "reports".* FROM "reports" WHERE "reports"."id" = 19 LIMIT 1 DEPRECATION WARNING: Object#returning has been deprecated in favor of Object#tap. (called from update_report at /home/max/work/rails_apps/flamingo_container/flamingo/vendor/plugins/resource_this/lib/resource_this.rb:135) Creating scope :open. Overwriting existing method Task.open. Task Load (2.0ms) SELECT "tasks".* FROM "tasks" WHERE "tasks"."id" = 14 LIMIT 1 Completed 200 OK in 1648ms (Views: 568.2ms | ActiveRecord: 3.2ms) </code></pre> <p>Ie with a lot more information, particularly the params, info from the router, generated sql, any templates rendered etc etc.</p> <p>Does anyone know how i can get my heroku log to be as verbose as my development one? I've done the following already:</p> <p>1) Set the log level in the relevant (rails 3) environment file:</p> <pre><code>config.log_level = :debug </code></pre> <p>2) Told heroku to use a different logger level, as described on <a href="http://devcenter.heroku.com/articles/logging">http://devcenter.heroku.com/articles/logging</a></p> <pre><code>heroku config:add LOG_LEVEL=DEBUG --app myapp #from CLI </code></pre> <p>Neither has made any difference...any ideas anyone?<br> thanks, max</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMax Williams
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHeroku: see params and sql activity in logs?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHeroku: see params and sql activity in logs?
      1. USNicolas Lauquin
      1. VTFavorite
    3. VO
      singulars
      1. POHeroku: see params and sql activity in logs?
      1. USPeter Ehrlich
      1. VTBountyStart
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload