Commit 6a774881fafffda33222334f53716aed800937ed

Authored by Pius Uzamere
1 parent b62dbe79

config

Showing 2 changed files with 214 additions and 2 deletions   Show diff stats
config/database.yml
... ... @@ -2,8 +2,8 @@
2 2 # gem install sqlite3-ruby (not necessary on OS X Leopard)
3 3  
4 4 development: &default
5   - adapter: sqlite3
6   - database: db/development.sqlite3
  5 + adapter: mysql
  6 + database: rebirth_development
7 7 pool: 5
8 8 timeout: 5000
9 9  
... ...
config/newrelic.yml 0 → 100644
... ... @@ -0,0 +1,212 @@
  1 +#
  2 +# This file configures the NewRelic RPM Agent, NewRelic RPM monitors
  3 +# Rails applications with deep visibility and low overhead. For more
  4 +# information, visit www.newrelic.com.
  5 +#
  6 +# This configuration file is custom generated for citp
  7 +#
  8 +# here are the settings that are common to all environments
  9 +common: &default_settings
  10 + # ============================== LICENSE KEY ===============================
  11 +
  12 + # You must specify the licence key associated with your New Relic
  13 + # account. This key binds your Agent's data to your account in the
  14 + # New Relic RPM service.
  15 + license_key: 'c20a2aedef8b067cf389b85510fb17c1a4ba242e'
  16 +
  17 + # Agent Enabled (Rails Only)
  18 + # Use this setting to force the agent to run or not run.
  19 + # Default is 'auto' which means the agent will install and run only
  20 + # if a valid dispatcher such as Mongrel is running. This prevents
  21 + # it from running with Rake or the console. Set to false to
  22 + # completely turn the agent off regardless of the other settings.
  23 + # Valid values are true, false and auto.
  24 + # agent_enabled: auto
  25 +
  26 + # Application Name
  27 + # Set this to be the name of your application as you'd like it show
  28 + # up in RPM. RPM will then auto-map instances of your application
  29 + # into a RPM "application" on your home dashboard page. If you want
  30 + # to map this instance into multiple apps, like "AJAX Requests" and
  31 + # "All UI" then specify a semicolon separated list of up to three
  32 + # distinct names. This setting does not prevent you from manually
  33 + # defining applications.
  34 + app_name: My Application
  35 +
  36 + # When "true", the agent collects performance data about your
  37 + # application and reports this data to the NewRelic RPM service at
  38 + # newrelic.com. This global switch is normally overridden for each
  39 + # environment below.
  40 + enabled: true
  41 +
  42 + # Developer mode should be off in every enviornment but
  43 + # development as it has very high overhead in memory
  44 + developer: false
  45 +
  46 + # The newrelic agent generates its own log file to keep its logging
  47 + # information separate from that of your application. Specify its
  48 + # log level here.
  49 + log_level: info
  50 +
  51 + # The newrelic agent communicates with the RPM service via http by
  52 + # default. If you want to communicate via https to increase
  53 + # security, then turn on SSL by setting this value to true. Note,
  54 + # this will result in increased CPU overhead to perform the
  55 + # encryption involved in SSL communication, but this work is done
  56 + # asynchronously to the threads that process your application code,
  57 + # so it should not impact response times.
  58 + ssl: false
  59 +
  60 + # EXPERIMENTAL: enable verification of the SSL certificate sent by
  61 + # the server. This setting has no effect unless SSL is enabled
  62 + # above. This may block your application. Only enable it if the data
  63 + # you send us needs end-to-end verified certificates.
  64 + #
  65 + # This means we cannot cache the DNS lookup, so each request to the
  66 + # RPM service will perform a lookup. It also means that we cannot
  67 + # use a non-blocking lookup, so in a worst case, if you have DNS
  68 + # problems, your app may block indefinitely.
  69 + # verify_certificate: true
  70 +
  71 + # Set your application's Apdex threshold value with the 'apdex_t'
  72 + # setting, in seconds. The apdex_t value determines the buckets used
  73 + # to compute your overall Apdex score.
  74 + # Requests that take less than apdex_t seconds to process will be
  75 + # classified as Satisfying transactions; more than apdex_t seconds
  76 + # as Tolerating transactions; and more than four times the apdex_t
  77 + # value as Frustrating transactions.
  78 + # For more about the Apdex standard, see
  79 + # http://support.newrelic.com/faqs/general/apdex
  80 +
  81 + apdex_t: 0.5
  82 +
  83 + # Proxy settings for connecting to the RPM server.
  84 + #
  85 + # If a proxy is used, the host setting is required. Other settings
  86 + # are optional. Default port is 8080.
  87 + #
  88 + # proxy_host: hostname
  89 + # proxy_port: 8080
  90 + # proxy_user:
  91 + # proxy_pass:
  92 +
  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 +
  104 + # Transaction tracer captures deep information about slow
  105 + # transactions and sends this to the RPM service once a
  106 + # minute. Included in the transaction is the exact call sequence of
  107 + # the transactions including any SQL statements issued.
  108 + transaction_tracer:
  109 +
  110 + # Transaction tracer is enabled by default. Set this to false to
  111 + # turn it off. This feature is only available at the Silver and
  112 + # above product levels.
  113 + enabled: true
  114 +
  115 + # Threshold in seconds for when to collect a transaction
  116 + # trace. When the response time of a controller action exceeds
  117 + # this threshold, a transaction trace will be recorded and sent to
  118 + # RPM. Valid values are any float value, or (default) "apdex_f",
  119 + # which will use the threshold for an dissatisfying Apdex
  120 + # controller action - four times the Apdex T value.
  121 + transaction_threshold: apdex_f
  122 +
  123 + # When transaction tracer is on, SQL statements can optionally be
  124 + # recorded. The recorder has three modes, "off" which sends no
  125 + # SQL, "raw" which sends the SQL statement in its original form,
  126 + # and "obfuscated", which strips out numeric and string literals
  127 + record_sql: obfuscated
  128 +
  129 + # Threshold in seconds for when to collect stack trace for a SQL
  130 + # call. In other words, when SQL statements exceed this threshold,
  131 + # then capture and send to RPM the current stack trace. This is
  132 + # helpful for pinpointing where long SQL calls originate from
  133 + stack_trace_threshold: 0.500
  134 +
  135 + # Determines whether the agent will capture query plans for slow
  136 + # SQL queries. Only supported in mysql and postgres. Should be
  137 + # set to false when using other adapters.
  138 + # explain_enabled: true
  139 +
  140 + # Threshold for query execution time below which query plans will not
  141 + # not be captured. Relevant only when `explain_enabled` is true.
  142 + # explain_threshold: 0.5
  143 +
  144 + # Error collector captures information about uncaught exceptions and
  145 + # sends them to RPM for viewing
  146 + error_collector:
  147 +
  148 + # Error collector is enabled by default. Set this to false to turn
  149 + # it off. This feature is only available at the Silver and above
  150 + # product levels
  151 + enabled: true
  152 +
  153 + # Rails Only - tells error collector whether or not to capture a
  154 + # source snippet around the place of the error when errors are View
  155 + # related.
  156 + capture_source: true
  157 +
  158 + # To stop specific errors from reporting to RPM, set this property
  159 + # to comma separated values
  160 + #
  161 + #ignore_errors: ActionController::RoutingError, ...
  162 +
  163 + # (Advanced) Uncomment this to ensure the cpu and memory samplers
  164 + # won't run. Useful when you are using the agent to monitor an
  165 + # external resource
  166 + # disable_samplers: true
  167 +
  168 +
  169 +# Application Environments
  170 +# ------------------------------------------
  171 +# Environment specific settings are in this section.
  172 +# For Rails applications, RAILS_ENV is used to determine the environment
  173 +# For Java applications, pass -Dnewrelic.environment <environment> to set
  174 +# the environment
  175 +
  176 +# NOTE if your application has other named environments, you should
  177 +# provide newrelic conifguration settings for these enviromnents here.
  178 +
  179 +development:
  180 + <<: *default_settings
  181 + # Turn off communication to RPM service in development mode.
  182 + # NOTE: for initial evaluation purposes, you may want to temporarily
  183 + # turn the agent on in development mode.
  184 + enabled: false
  185 +
  186 + # Rails Only - when running in Developer Mode, the New Relic Agent will
  187 + # present performance information on the last 100 transactions you have
  188 + # executed since starting the mongrel. to view this data, go to
  189 + # http://localhost:3000/newrelic
  190 + developer: true
  191 +
  192 +test:
  193 + <<: *default_settings
  194 + # It almost never makes sense to turn on the agent when running
  195 + # unit, functional or integration tests or the like.
  196 + enabled: false
  197 +
  198 +# Turn on the agent in production for 24x7 monitoring. NewRelic
  199 +# testing shows an average performance impact of < 5 ms per
  200 +# transaction, you you can leave this on all the time without
  201 +# incurring any user-visible performance degredation.
  202 +production:
  203 + <<: *default_settings
  204 + enabled: true
  205 +
  206 +# Many applications have a staging environment which behaves
  207 +# identically to production. Support for that environment is provided
  208 +# here. By default, the staging environment has the agent turned on.
  209 +staging:
  210 + <<: *default_settings
  211 + enabled: true
  212 + app_name: My Application (Staging)
... ...