1. 19 8月, 2019 1 次提交
  2. 16 8月, 2019 1 次提交
  3. 09 8月, 2019 1 次提交
    • S
      Rename githost.log -> git_json.log · 0324028a
      Stan Hu 提交于
      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.
      0324028a
  4. 26 7月, 2019 1 次提交
  5. 24 7月, 2019 1 次提交
  6. 23 7月, 2019 1 次提交
  7. 06 7月, 2019 1 次提交
  8. 05 7月, 2019 1 次提交
  9. 28 6月, 2019 1 次提交
  10. 18 6月, 2019 1 次提交
  11. 31 5月, 2019 1 次提交
    • C
      Apply reviewer feedback · 69953223
      charlie ablett 提交于
      - 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
      69953223
  12. 30 5月, 2019 1 次提交
  13. 24 5月, 2019 1 次提交
  14. 27 3月, 2019 1 次提交
  15. 26 2月, 2019 1 次提交
  16. 12 2月, 2019 1 次提交
    • S
      Log queue duration in production_json.log · 51ca7922
      Stan Hu 提交于
      `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.
      51ca7922
  17. 27 11月, 2018 1 次提交
  18. 13 11月, 2018 1 次提交
  19. 29 10月, 2018 1 次提交
  20. 19 10月, 2018 1 次提交
    • S
      Add support for JSON logging for audit events · 143d0e26
      Stan Hu 提交于
      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"
      }
      143d0e26
  21. 25 9月, 2018 1 次提交
  22. 07 9月, 2018 1 次提交
  23. 31 8月, 2018 1 次提交
  24. 04 4月, 2018 1 次提交
  25. 02 4月, 2018 1 次提交
    • S
      Move Sidekiq exporter logs to log/sidekiq_exporter.log · 05e1cbc4
      Stan Hu 提交于
      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
      05e1cbc4
  26. 02 3月, 2018 1 次提交
  27. 20 2月, 2018 1 次提交
  28. 06 11月, 2017 1 次提交
  29. 22 10月, 2017 1 次提交
  30. 19 10月, 2017 1 次提交
  31. 09 8月, 2017 1 次提交
  32. 15 12月, 2016 2 次提交
  33. 04 11月, 2016 1 次提交
    • L
      Show log corresponding to env in admin/logs · e900e53a
      Lukas Erlacher 提交于
      No matter which environment Gitlab was running as, the admin/logs view
      always showed production.log. This commit selects the logfile based
      on Rails.env.
      
      - Rename ProductionLogger to EnvironmentLogger
      - Make EnvironmentLogger logfile depend on env
      - Update spinach test for log tabs
      e900e53a
  34. 16 6月, 2016 2 次提交
  35. 13 6月, 2016 1 次提交
  36. 03 6月, 2016 2 次提交
  37. 30 5月, 2016 1 次提交