GitLab wird am Donnerstag, den 09. Dezember, zwischen 08:00 und 10:00 Uhr wegen wichtigen Wartungsarbeiten nicht zur Verfügung stehen.

  1. 21 Mar, 2018 1 commit
  2. 01 Feb, 2017 1 commit
  3. 06 Jan, 2017 1 commit
  4. 14 Jan, 2016 1 commit
  5. 29 Dec, 2015 1 commit
    • Yorick Peterse's avatar
      Write to InfluxDB directly via UDP · 620e7bb3
      Yorick Peterse authored
      This removes the need for Sidekiq and any overhead/problems introduced
      by TCP. There are a few things to take into account:
      1. When writing data to InfluxDB you may still get an error if the
         server becomes unavailable during the write. Because of this we're
         catching all exceptions and just ignore them (for now).
      2. Writing via UDP apparently requires the timestamp to be in
         nanoseconds. Without this data either isn't written properly.
      3. Due to the restrictions on UDP buffer sizes we're writing metrics one
         by one, instead of writing all of them at once.
  6. 17 Dec, 2015 1 commit
    • Yorick Peterse's avatar
      Storing of application metrics in InfluxDB · 141e946c
      Yorick Peterse authored
      This adds the ability to write application metrics (e.g. SQL timings) to
      InfluxDB. These metrics can in turn be visualized using Grafana, or
      really anything else that can read from InfluxDB. These metrics can be
      used to track application performance over time, between different Ruby
      versions, different GitLab versions, etc.
      == Transaction Metrics
      Currently the following is tracked on a per transaction basis (a
      transaction is a Rails request or a single Sidekiq job):
      * Timings per query along with the raw (obfuscated) SQL and information
        about what file the query originated from.
      * Timings per view along with the path of the view and information about
        what file triggered the rendering process.
      * The duration of a request itself along with the controller/worker
        class and method name.
      * The duration of any instrumented method calls (more below).
      == Sampled Metrics
      Certain metrics can't be directly associated with a transaction. For
      example, a process' total memory usage is unrelated to any running
      transactions. While a transaction can result in the memory usage going
      up there's no accurate way to determine what transaction is to blame,
      this becomes especially problematic in multi-threaded environments.
      To solve this problem there's a separate thread that takes samples at a
      fixed interval. This thread (using the class Gitlab::Metrics::Sampler)
      currently tracks the following:
      * The process' total memory usage.
      * The number of file descriptors opened by the process.
      * The amount of Ruby objects (using ObjectSpace.count_objects).
      * GC statistics such as timings, heap slots, etc.
      The default/current interval is 15 seconds, any smaller interval might
      put too much pressure on InfluxDB (especially when running dozens of
      == Method Instrumentation
      While currently not yet used methods can be instrumented to track how
      long they take to run. Unlike the likes of New Relic this doesn't
      require modifying the source code (e.g. including modules), it all
      happens from the outside. For example, to track `User.by_login` we'd add
      the following code somewhere in an initializer:
            instrument_method(User, :by_login)
      to instead instrument an instance method:
            instrument_instance_method(User, :save)
      Instrumentation for either all public model methods or a few crucial
      ones will be added in the near future, I simply haven't gotten to doing
      so just yet.
      == Configuration
      By default metrics are disabled. This means users don't have to bother
      setting anything up if they don't want to. Metrics can be enabled by
      editing one's gitlab.yml configuration file (see
      config/gitlab.yml.example for example settings).
      == Writing Data To InfluxDB
      Because InfluxDB is still a fairly young product I expect the worse.
      Data loss, unexpected reboots, the database not responding, you name it.
      Because of this data is _not_ written to InfluxDB directly, instead it's
      queued and processed by Sidekiq. This ensures that users won't notice
      anything when InfluxDB is giving trouble.
      The metrics worker can be started in a standalone manner as following:
          bundle exec sidekiq -q metrics
      The corresponding class is called MetricsWorker.
  7. 03 Dec, 2015 1 commit
  8. 02 Dec, 2015 1 commit
  9. 26 Nov, 2015 1 commit
  10. 26 Aug, 2015 1 commit
  11. 19 Aug, 2015 3 commits
  12. 31 Mar, 2015 1 commit
  13. 29 Dec, 2014 1 commit
  14. 10 Sep, 2014 1 commit
  15. 04 Jul, 2014 1 commit
  16. 08 Apr, 2014 1 commit
  17. 07 Apr, 2014 1 commit
  18. 20 Mar, 2014 1 commit
  19. 08 Jul, 2013 1 commit
  20. 04 Apr, 2013 1 commit
  21. 11 Feb, 2013 1 commit
  22. 28 Jan, 2013 1 commit
  23. 25 Jan, 2013 1 commit
  24. 14 Jan, 2013 1 commit
  25. 09 Jan, 2013 3 commits
  26. 09 Jan, 2012 1 commit
  27. 08 Jan, 2012 1 commit