Heroku event reference

Events parsed from your Heroku log drain: router request lines and Heroku Postgres metrics. Each entry lists the event's fields with their types, and links to its raw JSON Schema.

2 events emitted by heroku.

---

postgres

A Heroku Postgres log line from a Heroku log drain. Honeybadger recognizes it by proc_id == 'heroku-postgres'.

Field	Type	Description
event_type	string
proc_id	string	Heroku process identifier. Always 'heroku-postgres' for this event. Allowed value: heroku-postgres.
source	string	Postgres source identifier, e.g. "HEROKU_POSTGRESQL_CRIMSON".
addon	string	Add-on name.
active_connections	integer	Number of active database connections.
waiting_connections	integer	Number of connections waiting on a lock.
index_cache_hit_rate	number	Index cache hit rate (0.0–1.0).
table_cache_hit_rate	number	Table cache hit rate (0.0–1.0).
load_avg_1m	number	1-minute load average.
load_avg_5m	number	5-minute load average.
load_avg_15m	number	15-minute load average.
read_iops	number	Read I/O operations per second.
write_iops	number	Write I/O operations per second.
tmp_disk_used	integer	Bytes used on temporary disk.
tmp_disk_available	integer	Bytes available on temporary disk.
memory_total	integer	Total memory in bytes.
memory_free	integer	Free memory in bytes.
memory_cached	integer	Cached memory in bytes.
memory_postgres	integer	Memory used by Postgres in bytes.

Example

{
  "event_type": "logplex",
  "proc_id": "heroku-postgres",
  "source": "HEROKU_POSTGRESQL_CRIMSON",
  "addon": "postgresql-curved-12345",
  "active_connections": 12,
  "waiting_connections": 0,
  "index_cache_hit_rate": 0.99957,
  "table_cache_hit_rate": 0.98309,
  "load_avg_1m": 0.31,
  "load_avg_5m": 0.28,
  "load_avg_15m": 0.25,
  "read_iops": 12.5,
  "write_iops": 35.625,
  "tmp_disk_used": 33849344,
  "tmp_disk_available": 72944943104,
  "memory_total": 8589934592,
  "memory_free": 1342177280,
  "memory_cached": 5368709120,
  "memory_postgres": 1610612736
}

router

A Heroku router log line from a Heroku log drain. Honeybadger recognizes it by proc_id == 'router'.

Field	Type	Description
event_type	string
proc_id	string	Heroku process identifier. Always 'router' for this event. Allowed value: router.
method	string	HTTP method, e.g. "GET", "POST".
path	string	Request path.
host	string	Request host header.
fwd	string	Forwarded client IP address.
dyno	string	Dyno that handled the request, e.g. "web.1".
connect	number	Time in milliseconds to establish the connection.
service	number	Time in milliseconds the dyno spent processing the request.
status	integer	HTTP response status code.
bytes	integer	Number of bytes returned in the response.
protocol	string	Protocol used, e.g. "https".

Example

{
  "event_type": "logplex",
  "proc_id": "router",
  "method": "GET",
  "path": "/users/123",
  "host": "www.example.com",
  "fwd": "203.0.113.42",
  "dyno": "web.1",
  "connect": 1,
  "service": 45,
  "status": 200,
  "bytes": 15342,
  "protocol": "https"
}