Download as
Browse Code »

Commit 12288a390a490c5bd97ddb86e08c0de45120a9ab

Authored by Marcin Ciunelis
1 parent f3aa7ac0
Exists in master and in 1 other branch production

new relic configuration added

Showing 4 changed files with 231 additions and 0 deletions   Show diff stats
.gitignore
  Diff comments   View file @12288a3
... ... @@ -6,6 +6,7 @@ config/config.yml
6 6 config/deploy.rb
7 7 config/deploy
8 8 config/mongoid.yml
  9 +config/newrelic.yml
9 10 .rvmrc
10 11 *~
11 12 *.rbc
... ...
Gemfile
  Diff comments   View file @12288a3
... ... @@ -18,6 +18,8 @@ gem 'inherited_resources'
18 18 gem 'SystemTimer', :platform => :ruby_18
19 19 gem 'hoptoad_notifier', "~> 2.4"
20 20 gem 'actionmailer_inline_css', "~> 1.3.0"
  21 +gem 'rpm_contrib'
  22 +gem 'newrelic_rpm'
21 23  
22 24 platform :ruby do
23 25 gem 'bson_ext', '~> 1.4.0'
... ...
Gemfile.lock
  Diff comments   View file @12288a3
... ... @@ -107,6 +107,7 @@ GEM
107 107 railties (>= 3.0.0)
108 108 multi_json (1.0.3)
109 109 multipart-post (1.1.3)
  110 + newrelic_rpm (3.2.0)
110 111 nokogiri (1.5.0)
111 112 octokit (0.6.4)
112 113 addressable (~> 2.2.6)
... ... @@ -156,6 +157,8 @@ GEM
156 157 rest-client (1.6.7)
157 158 mime-types (>= 1.16)
158 159 ri_cal (0.8.8)
  160 + rpm_contrib (2.1.4)
  161 + newrelic_rpm (>= 3.1.1)
159 162 rspec (2.6.0)
160 163 rspec-core (~> 2.6.0)
161 164 rspec-expectations (~> 2.6.0)
... ... @@ -226,12 +229,14 @@ DEPENDENCIES
226 229 lighthouse-api
227 230 mongoid (= 2.1.2)
228 231 mongoid_rails_migrations
  232 + newrelic_rpm
229 233 nokogiri
230 234 octokit
231 235 oruen_redmine_client
232 236 pivotal-tracker
233 237 rails (= 3.0.10)
234 238 ri_cal
  239 + rpm_contrib
235 240 rspec (~> 2.6)
236 241 rspec-rails (~> 2.6)
237 242 ruby-debug
... ...
config/newrelic.example.yml 0 → 100644
  Diff comments   View file @12288a3
... ... @@ -0,0 +1,223 @@
  1 +#
  2 +# This file configures the New Relic Agent. New Relic monitors
  3 +# Ruby, Java, .NET, PHP, and Python applications with deep visibility and low overhead.
  4 +# For more information, visit www.newrelic.com.
  5 +#
  6 +# Generated October 18, 2011
  7 +#
  8 +# This configuration file is custom generated for errbit
  9 +
  10 +# Here are the settings that are common to all environments:
  11 +common: &default_settings
  12 + # ============================== LICENSE KEY ===============================
  13 +
  14 + # You must specify the license key associated with your New Relic
  15 + # account. This key binds your Agent's data to your account in the
  16 + # New Relic service.
  17 + license_key: <%= ENV["NEW_RELIC_LICENSE_KEY"] %>
  18 +
  19 + # Agent Enabled (Ruby/Rails Only)
  20 + # Use this setting to force the agent to run or not run.
  21 + # Default is 'auto' which means the agent will install and run only
  22 + # if a valid dispatcher such as Mongrel is running. This prevents
  23 + # it from running with Rake or the console. Set to false to
  24 + # completely turn the agent off regardless of the other settings.
  25 + # Valid values are true, false and auto.
  26 + # agent_enabled: auto
  27 +
  28 + # Application Name
  29 + # Set this to be the name of your application as you'd like it show
  30 + # up in New Relic. New Relic will then auto-map instances of your application
  31 + # into a New Relic "application" on your home dashboard page. If you want
  32 + # to map this instance into multiple apps, like "AJAX Requests" and
  33 + # "All UI" then specify a semicolon-separated list of up to three
  34 + # distinct names. If you comment this out, it defaults to the
  35 + # capitalized RAILS_ENV (i.e., Production, Staging, etc)
  36 + app_name: <%= ENV["NEW_RELIC_APP_NAME"] %>
  37 +
  38 + # When "true", the agent collects performance data about your
  39 + # application and reports this data to the New Relic service at
  40 + # newrelic.com. This global switch is normally overridden for each
  41 + # environment below. (formerly called 'enabled')
  42 + monitor_mode: true
  43 +
  44 + # Developer mode should be off in every environment but
  45 + # development as it has very high overhead in memory.
  46 + developer_mode: false
  47 +
  48 + # The newrelic agent generates its own log file to keep its logging
  49 + # information separate from that of your application. Specify its
  50 + # log level here.
  51 + log_level: info
  52 +
  53 + # The newrelic agent communicates with the New Relic service via http by
  54 + # default. If you want to communicate via https to increase
  55 + # security, then turn on SSL by setting this value to true. Note,
  56 + # this will result in increased CPU overhead to perform the
  57 + # encryption involved in SSL communication, but this work is done
  58 + # asynchronously to the threads that process your application code,
  59 + # so it should not impact response times.
  60 + ssl: false
  61 +
  62 + # EXPERIMENTAL: enable verification of the SSL certificate sent by
  63 + # the server. This setting has no effect unless SSL is enabled
  64 + # above. This may block your application. Only enable it if the data
  65 + # you send us needs end-to-end verified certificates.
  66 + #
  67 + # This means we cannot cache the DNS lookup, so each request to the
  68 + # New Relic service will perform a lookup. It also means that we cannot
  69 + # use a non-blocking lookup, so in a worst case, if you have DNS
  70 + # problems, your app may block indefinitely.
  71 + # verify_certificate: true
  72 +
  73 + # Set your application's Apdex threshold value with the 'apdex_t'
  74 + # setting, in seconds. The apdex_t value determines the buckets used
  75 + # to compute your overall Apdex score.
  76 + # Requests that take less than apdex_t seconds to process will be
  77 + # classified as Satisfying transactions; more than apdex_t seconds
  78 + # as Tolerating transactions; and more than four times the apdex_t
  79 + # value as Frustrating transactions.
  80 + # For more about the Apdex standard, see
  81 + # http://support.newrelic.com/faqs/general/apdex
  82 + apdex_t: 0.5
  83 +
  84 + # Proxy settings for connecting to the New Relic server.
  85 + #
  86 + # If a proxy is used, the host setting is required. Other settings
  87 + # are optional. Default port is 8080.
  88 + #
  89 + # proxy_host: hostname
  90 + # proxy_port: 8080
  91 + # proxy_user:
  92 + # proxy_pass:
  93 +
  94 + # Tells transaction tracer and error collector (when enabled)
  95 + # whether or not to capture HTTP params. When true, frameworks can
  96 + # exclude HTTP parameters from being captured.
  97 + # Rails: the RoR filter_parameter_logging excludes parameters
  98 + # Java: create a config setting called "ignored_params" and set it to
  99 + # a comma separated list of HTTP parameter names.
  100 + # ex: ignored_params: credit_card, ssn, password
  101 + capture_params: false
  102 +
  103 + # Transaction tracer captures deep information about slow
  104 + # transactions and sends this to the New Relic service once a
  105 + # minute. Included in the transaction is the exact call sequence of
  106 + # the transactions including any SQL statements issued.
  107 + transaction_tracer:
  108 +
  109 + # Transaction tracer is enabled by default. Set this to false to
  110 + # turn it off. This feature is only available at the Professional
  111 + # product level.
  112 + enabled: true
  113 +
  114 + # Threshold in seconds for when to collect a transaction
  115 + # trace. When the response time of a controller action exceeds
  116 + # this threshold, a transaction trace will be recorded and sent to
  117 + # New Relic. Valid values are any float value, or (default) "apdex_f",
  118 + # which will use the threshold for an dissatisfying Apdex
  119 + # controller action - four times the Apdex T value.
  120 + transaction_threshold: apdex_f
  121 +
  122 + # When transaction tracer is on, SQL statements can optionally be
  123 + # recorded. The recorder has three modes, "off" which sends no
  124 + # SQL, "raw" which sends the SQL statement in its original form,
  125 + # and "obfuscated", which strips out numeric and string literals.
  126 + record_sql: obfuscated
  127 +
  128 + # Threshold in seconds for when to collect stack trace for a SQL
  129 + # call. In other words, when SQL statements exceed this threshold,
  130 + # then capture and send to New Relic the current stack trace. This is
  131 + # helpful for pinpointing where long SQL calls originate from.
  132 + stack_trace_threshold: 0.500
  133 +
  134 + # Determines whether the agent will capture query plans for slow
  135 + # SQL queries. Only supported in mysql and postgres. Should be
  136 + # set to false when using other adapters.
  137 + # explain_enabled: true
  138 +
  139 + # Threshold for query execution time below which query plans will not
  140 + # not be captured. Relevant only when `explain_enabled` is true.
  141 + # explain_threshold: 0.5
  142 +
  143 + # Error collector captures information about uncaught exceptions and
  144 + # sends them to New Relic for viewing
  145 + error_collector:
  146 +
  147 + # Error collector is enabled by default. Set this to false to turn
  148 + # it off. This feature is only available at the Professional
  149 + # product level.
  150 + enabled: true
  151 +
  152 + # Rails Only - tells error collector whether or not to capture a
  153 + # source snippet around the place of the error when errors are View
  154 + # related.
  155 + capture_source: true
  156 +
  157 + # To stop specific errors from reporting to New Relic, set this property
  158 + # to comma-separated values. Default is to ignore routing errors,
  159 + # which are how 404's get triggered.
  160 + ignore_errors: ActionController::RoutingError
  161 +
  162 + # (Advanced) Uncomment this to ensure the CPU and memory samplers
  163 + # won't run. Useful when you are using the agent to monitor an
  164 + # external resource
  165 + # disable_samplers: true
  166 +
  167 + # If you aren't interested in visibility in these areas, you can
  168 + # disable the instrumentation to reduce overhead.
  169 + #
  170 + # disable_view_instrumentation: true
  171 + # disable_activerecord_instrumentation: true
  172 + # disable_memcache_instrumentation: true
  173 + # disable_dj: true
  174 +
  175 + # Certain types of instrumentation such as GC stats will not work if
  176 + # you are running multi-threaded. Please let us know.
  177 + # multi_threaded = false
  178 +
  179 +# Application Environments
  180 +# ------------------------------------------
  181 +# Environment-specific settings are in this section.
  182 +# For Rails applications, RAILS_ENV is used to determine the environment.
  183 +# For Java applications, pass -Dnewrelic.environment <environment> to set
  184 +# the environment.
  185 +
  186 +# NOTE if your application has other named environments, you should
  187 +# provide newrelic configuration settings for these environments here.
  188 +
  189 +development:
  190 + <<: *default_settings
  191 + # Turn off communication to New Relic service in development mode (also
  192 + # 'enabled').
  193 + # NOTE: for initial evaluation purposes, you may want to temporarily
  194 + # turn agent communication on in development mode.
  195 + monitor_mode: false
  196 +
  197 + # Rails Only - when running in Developer Mode, the New Relic Agent will
  198 + # present performance information on the last 100 transactions you have
  199 + # executed since starting the app server.
  200 + # NOTE: There is substantial overhead when running in developer mode.
  201 + # Do not use for production or load testing.
  202 + developer_mode: true
  203 +
  204 + # Enable textmate links
  205 + # textmate: true
  206 +
  207 +test:
  208 + <<: *default_settings
  209 + # It almost never makes sense to turn on the agent when running
  210 + # unit, functional or integration tests or the like.
  211 + monitor_mode: false
  212 +
  213 +# Turn on the agent in production for 24x7 monitoring. New Relic
  214 +# testing shows an average performance impact of < 5 ms per
  215 +# transaction, so you can leave this on all the time without
  216 +# incurring any user-visible performance degradation.
  217 +production:
  218 + <<: *default_settings
  219 + monitor_mode: true
  220 +
  221 +# Many applications have a staging environment which behaves
  222 +# identically to production. Support for that environment is provided
  223 +# here. By default, the staging environment has the agent turned on.
... ...