Read about our upcoming Code of Conduct on this issue

This instance will be upgraded to Heptapod 0.28.1 on 2022-01-26 at 16:00 UTC+1 (a few minutes of down time)

  1. 07 Jan, 2020 1 commit
  2. 20 Dec, 2019 1 commit
  3. 16 Dec, 2019 1 commit
  4. 12 Dec, 2019 1 commit
  5. 22 Nov, 2019 1 commit
  6. 18 Nov, 2019 1 commit
  7. 08 Oct, 2019 1 commit
  8. 04 Oct, 2019 1 commit
  9. 26 Sep, 2019 1 commit
  10. 18 Sep, 2019 2 commits
  11. 05 Sep, 2019 1 commit
  12. 04 Sep, 2019 1 commit
  13. 28 Aug, 2019 1 commit
  14. 20 Aug, 2019 1 commit
  15. 18 Aug, 2019 1 commit
  16. 16 Aug, 2019 1 commit
  17. 08 Aug, 2019 1 commit
    • Stan Hu's avatar
      Rename githost.log -> git_json.log · e7602f2191cd
      Stan Hu authored
      The githost.log name was often confused with GitHost.io. Rename this to
      git_json.log to make it clear it's coming from Git and that it's JSON
      data.
      e7602f2191cd
  18. 25 Jul, 2019 1 commit
  19. 24 Jul, 2019 1 commit
  20. 22 Jul, 2019 1 commit
  21. 05 Jul, 2019 1 commit
  22. 04 Jul, 2019 1 commit
  23. 28 Jun, 2019 1 commit
  24. 18 Jun, 2019 1 commit
  25. 31 May, 2019 1 commit
    • charlie ablett's avatar
      Apply reviewer feedback · 6844226659f5
      charlie ablett authored
      - Comply doc with guidelines
      - Improve tests for readability and completeness
      - Separate out phases visually with newlines
      - Add `format_message` test
      - test readability
      - code and test structure/styling
      - static query analyzers
      - call `as_json` on `provided_variables`
      - add exception handling
      6844226659f5
  26. 30 May, 2019 1 commit
  27. 24 May, 2019 1 commit
  28. 27 Mar, 2019 1 commit
  29. 25 Feb, 2019 1 commit
  30. 12 Feb, 2019 1 commit
    • Stan Hu's avatar
      Log queue duration in production_json.log · ae297671a91b
      Stan Hu authored
      `queue_duration` is a useful metric that is currently in api_json.log
      but not in production_json.log. We should add it because it tells us how
      long the request sat in Workhorse before Unicorn processed it. Having
      this field enables the support team to better troubleshoot when delays
      began to happen.
      ae297671a91b
  31. 27 Nov, 2018 1 commit
  32. 13 Nov, 2018 1 commit
  33. 29 Oct, 2018 1 commit
  34. 18 Oct, 2018 1 commit
    • Stan Hu's avatar
      Add support for JSON logging for audit events · d5c73b94326b
      Stan Hu authored
      This will add audit_json.log that writes one line per audit event. For
      example:
      
      {
             "severity":"INFO",
             "time":"2018-10-17T17:38:22.523Z",
             "author_id":3,
             "entity_id":2,
             "entity_type":"Project",
             "change":"visibility",
             "from":"Private",
             "to":"Public",
             "author_name":"John Doe4",
             "target_id":2,
             "target_type":"Project",
             "target_details":"namespace2/project2"
      }
      d5c73b94326b
  35. 25 Sep, 2018 1 commit
  36. 06 Sep, 2018 1 commit
  37. 30 Aug, 2018 1 commit
  38. 04 Apr, 2018 1 commit
  39. 02 Apr, 2018 1 commit
    • Stan Hu's avatar
      Move Sidekiq exporter logs to log/sidekiq_exporter.log · d3ce1e361f4b
      Stan Hu authored
      The Sidekiq exporter logs were mixing with the normal Sidekiq logs. In order
      to support structured logging in Sidekiq, we either need to split this data
      out or convert the exporter to produce structured logs. Since Sidekiq job
      processing is fundamentally different information from Web server traffic,
      it seems cleaner to move the metrics traffic into a separate file, where they
      can be parsed by a different filter if needed.
      
      Relates to #20060
      d3ce1e361f4b