gitlab-org--gitlab-foss/db/migrate/20151229112614_influxdb_remote_database_setting.rb

# rubocop:disable all
class InfluxdbRemoteDatabaseSetting < ActiveRecord::Migration[4.2]
  def change
    remove_column :application_settings, :metrics_database
  end
end
Enable RuboCop for migrations Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file. 2016-06-09 08:39:16 -04:00			`# rubocop:disable all`
Add version 4.2 to all existing migrations DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912 2018-11-13 02:27:31 -05:00			`class InfluxdbRemoteDatabaseSetting < ActiveRecord::Migration[4.2]`
Write to InfluxDB directly via UDP 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. 2015-12-29 07:40:42 -05:00			`def change`
			`remove_column :application_settings, :metrics_database`
			`end`
			`end`