1. 21 Feb, 2020 2 commits
  2. 20 Feb, 2020 2 commits
  3. 17 Feb, 2020 3 commits
  4. 14 Feb, 2020 1 commit
  5. 13 Feb, 2020 2 commits
  6. 10 Feb, 2020 3 commits
  7. 06 Feb, 2020 2 commits
  8. 05 Feb, 2020 1 commit
  9. 29 Jan, 2020 2 commits
  10. 09 Jan, 2020 2 commits
  11. 08 Jan, 2020 1 commit
  12. 24 Dec, 2019 1 commit
  13. 19 Dec, 2019 4 commits
  14. 10 Dec, 2019 2 commits
  15. 09 Dec, 2019 5 commits
  16. 06 Dec, 2019 1 commit
    • Stan Hu's avatar
      Log duration_ms when Workhorse hits a bad gateway · 43ce41ec
      Stan Hu authored
      Previously when the upstream application (e.g. Unicorn) timed out,
      Workhorse would report an error message of the form:
      
      ```json
      {
        "correlation_id": "k4mKg0snXG3",
        "error": "badgateway: failed after 61s: EOF",
        "level": "error",
        "method": "GET",
        "msg": "error",
        "time": "2019-12-02T22:05:09-08:00",
        "uri": "/admin"
      }
      ```
      
      Since Sentry attempts to group similar events by some fingerprint that
      includes the message, the changes in timings would trick Sentry into
      creating a new event. To avoid that, the new log message now looks like:
      
      ```json
      {
        "correlation_id": "k4mKg0snXG3",
        "duration_ms": 60599,
        "error": "badgateway: failed to receive response: EOF",
        "level": "error",
        "method": "GET",
        "msg": "error",
        "time": "2019-12-02T22:05:09-08:00",
        "uri": "/admin"
      }
      ```
      
      The inclusion of `duration_ms` and the standardized `error` message makes
      it easier for users to filter and parse this error.
      43ce41ec
  17. 03 Dec, 2019 1 commit
  18. 27 Nov, 2019 5 commits