By enabling Heroku’s log runtime labs feature CPU samples will be periodically dumped into your logs. Timber recognizes and parses these events as event.server.cpu_sample.

source=web.1 dyno=heroku.2808254.d97d0ea7-cf3d-411b-b453-d2943a50b456 sample#load_avg_1m=2.46 sample#load_avg_5m=1.06 sample#load_avg_15m=0.99

Example JSON Structure

{
  "event": {
    "server": {
      "cpu_sample": {
        "load_avg_10m": 2.4,
        "load_avg_5m": 1.2,
        "load_avg_1m": 3.1
      }
    }
  }
}

Field descriptions

Name Type Description
load_avg_10m number The load average for the processor in the last 10 minutes. This reflects the number of CPU tasks that are in the ready queue (i.e. waiting to be processed). minimum: 0
load_avg_1m number The load average for the processor in the last 1 minute. This reflects the number of CPU tasks that are in the ready queue (i.e. waiting to be processed). minimum: 0
load_avg_5m number The load average for the processor in the last 5 minutes. This reflects the number of CPU tasks that are in the ready queue (i.e. waiting to be processed). minimum: 0

Using this data

Example queries:

  • Full path: event.server.cpu_sample.load_avg_1m:>100
  • Short path: cpu_sample.load_avg_1m:>100 - Short paths are aliases allowing for simpler access to these fields.
  • Only this event: has:cpu_sample

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