Heroku Logdrain

Note

COMING SOON! We’re currently transitioning to a multi-dimensional, tag-based data model. This integration is still under construction and will be available soon. Please let us know if you need this integration. It helps us prioritize our work.

Heroku native metrics, such as router, postgres, and per-dyno can be sent to a log drain hosted by Librato. This solution is ideal for users who want to aggregate metrics from multiple Heroku applications into one Librato account. NOTE: You must be logged into a direct Librato account in order for this integration to work properly (does not support Heroku Add-On accounts). Sign up for a Librato account here.

Heroku Add-On Metrics

Router Metrics

    1.  router.bytes
    2.  router.bytes.median
    3.  router.bytes.perc95
    4.  router.bytes.perc99
    5.  router.connect
    6.  router.connect.median
    7.  router.connect.perc95
    8.  router.connect.perc99
    9.  router.service
    10. router.service.median
    11. router.service.perc95
    12. router.service.perc99

Router Status code metrics
    13. router.status.2xx
    14. router.status.3xx
    15. router.status.4xx
    16. router.status.5xx

Postgres Metrics (depends on Heroku plan level)

1.  memory-postgres
2.  memory-free
3.  load-avg-1m
4.  load-avg-5m
5.  load-avg-15m
6.  Connections
7.  Waiting Connections
8.  Cache Hit Rate
9.  Database size
10. Table count
11. write-iops
12. read-iops

Runtime metrics

(User enabled via heroku labs:enable log-runtime-metrics)

1. Dyno Load Avg (1m)
2. Dyno Load Avg (5m)
3. Dyno Load Avg (15m)
4. Dyno Total Memory
5. Dyno Resident Memory
6. Dyno Swap Memory
7. Dyno Cache Memory
8. Dyno Pages Written to Disk
9. Dyno Pages Read from Disk

Heroku Error Codes

1.  errors.http.h10:     H10 - App crashed
2.  errors.http.h11:     H11 - Backlog too deep
3.  errors.http.h12:     H12 - Request timeout
4.  errors.http.h13:     H13 - Connection closed without response
5.  errors.http.h14:     H14 - No web dynos running
6.  errors.http.h15:     H15 - Idle connection
7.  errors.http.h16:     H16 - Redirect to herokuapp.com
8.  errors.http.h17:     H17 - Poorly formatted HTTP response
9.  errors.http.h18:     H18 - Server Request Interrupted
10. errors.http.h19:     H19 - Backend connection timeout
11. errors.http.h20:     H20 - App boot timeout
12. errors.http.h21:     H21 - Backend connection refused
13. errors.http.h22:     H22 - Connection limit reached
14. errors.http.h23:     H23 - Endpoint misconfigured
15. errors.http.h24:     H24 - Forced close
16. errors.http.h25:     H25 - HTTP Restriction
17. errors.http.h26:     H26 - Request Error
18. errors.http.h27:     H27 - Client Request Interrupted
19. errors.http.h28:     H28 - Client Connection Idle
20. errors.http.h80:     H80 - Maintenance mode
21. errors.http.h81:     H81 - Blank app
22. errors.http.h82:     H82 - Free dyno quota exhausted
23. errors.http.h99:     H99 - Platform error
24. errors.logging.l10:  L10 - Drain buffer overflow
25. errors.logging.l11:  L11 - Tail buffer overflow
26. errors.logging.l12:  L12 - Local buffer overflow
27. errors.logging.l13:  L13 - Local delivery error
28. errors.logging.l14:  L14 - Certificate validation error
29. errors.runtime.r10:  R10 - Boot timeout
30. errors.runtime.r12:  R12 - Exit timeout
31. errors.runtime.r13:  R13 - Attach error
32. errors.runtime.r14:  R14 - Memory quota exceeded
33. errors.runtime.r15:  R15 - Memory quota vastly exceeded
34. errors.runtime.r151: R151 - Platform memory error
35. errors.runtime.r16:  R16 – Detached
36. errors.runtime.r99:  R99 - Platform error

Dashboards we create:

  • Error Metrics
  • HTTP Status Codes
  • Overview
  • Postgres
  • Runtime Metrics
  • Runtime Metrics (Dynamic Source)