lalithadevi commited on
Commit
e957836
1 Parent(s): f7374b3

Upload newrelic.ini

Browse files
Files changed (1) hide show
  1. newrelic.ini +255 -0
newrelic.ini ADDED
@@ -0,0 +1,255 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # ---------------------------------------------------------------------------
2
+
3
+ #
4
+ # This file configures the New Relic Python Agent.
5
+ #
6
+ # The path to the configuration file should be supplied to the function
7
+ # newrelic.agent.initialize() when the agent is being initialized.
8
+ #
9
+ # The configuration file follows a structure similar to what you would
10
+ # find for Microsoft Windows INI files. For further information on the
11
+ # configuration file format see the Python ConfigParser documentation at:
12
+ #
13
+ # http://docs.python.org/library/configparser.html
14
+ #
15
+ # For further discussion on the behaviour of the Python agent that can
16
+ # be configured via this configuration file see:
17
+ #
18
+ # https://docs.newrelic.com/docs/apm/agents/python-agent/configuration/python-agent-configuration/
19
+ #
20
+
21
+ # ---------------------------------------------------------------------------
22
+
23
+ # Here are the settings that are common to all environments.
24
+
25
+ [newrelic]
26
+
27
+ # You must specify the license key associated with your New
28
+ # Relic account. This may also be set using the NEW_RELIC_LICENSE_KEY
29
+ # environment variable. This key binds the Python Agent's data to
30
+ # your account in the New Relic service. For more information on
31
+ # storing and generating license keys, see
32
+ # https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/#ingest-license-key
33
+
34
+
35
+ # The application name. Set this to be the name of your
36
+ # application as you would like it to show up in New Relic UI.
37
+ # You may also set this using the NEW_RELIC_APP_NAME environment variable.
38
+ # The UI will then auto-map instances of your application into a
39
+ # entry on your home dashboard page. You can also specify multiple
40
+ # app names to group your aggregated data. For further details,
41
+ # please see:
42
+ # https://docs.newrelic.com/docs/apm/agents/manage-apm-agents/app-naming/use-multiple-names-app/
43
+ app_name = news_backend
44
+
45
+ # When "true", the agent collects performance data about your
46
+ # application and reports this data to the New Relic UI at
47
+ # newrelic.com. This global switch is normally overridden for
48
+ # each environment below. It may also be set using the
49
+ # NEW_RELIC_MONITOR_MODE environment variable.
50
+ monitor_mode = true
51
+
52
+ # Sets the name of a file to log agent messages to. Whatever you
53
+ # set this to, you must ensure that the permissions for the
54
+ # containing directory and the file itself are correct, and
55
+ # that the user that your web application runs as can write out
56
+ # to the file. If not able to out a log file, it is also
57
+ # possible to say "stderr" and output to standard error output.
58
+ # This would normally result in output appearing in your web
59
+ # server log. It can also be set using the NEW_RELIC_LOG
60
+ # environment variable.
61
+ log_file = stdout
62
+
63
+ # Sets the level of detail of messages sent to the log file, if
64
+ # a log file location has been provided. Possible values, in
65
+ # increasing order of detail, are: "critical", "error", "warning",
66
+ # "info" and "debug". When reporting any agent issues to New
67
+ # Relic technical support, the most useful setting for the
68
+ # support engineers is "debug". However, this can generate a lot
69
+ # of information very quickly, so it is best not to keep the
70
+ # agent at this level for longer than it takes to reproduce the
71
+ # problem you are experiencing. This may also be set using the
72
+ # NEW_RELIC_LOG_LEVEL environment variable.
73
+ log_level = info
74
+
75
+ # High Security Mode enforces certain security settings, and prevents
76
+ # them from being overridden, so that no sensitive data is sent to New
77
+ # Relic. Enabling High Security Mode means that request parameters are
78
+ # not collected and SQL can not be sent to New Relic in its raw form.
79
+ # To activate High Security Mode, it must be set to 'true' in this
80
+ # local .ini configuration file AND be set to 'true' in the
81
+ # server-side configuration in the New Relic user interface. It can
82
+ # also be set using the NEW_RELIC_HIGH_SECURITY environment variable.
83
+ # For details, see
84
+ # https://docs.newrelic.com/docs/subscriptions/high-security
85
+ high_security = false
86
+
87
+ # The Python Agent will attempt to connect directly to the New
88
+ # Relic service. If there is an intermediate firewall between
89
+ # your host and the New Relic service that requires you to use a
90
+ # HTTP proxy, then you should set both the "proxy_host" and
91
+ # "proxy_port" settings to the required values for the HTTP
92
+ # proxy. The "proxy_user" and "proxy_pass" settings should
93
+ # additionally be set if proxy authentication is implemented by
94
+ # the HTTP proxy. The "proxy_scheme" setting dictates what
95
+ # protocol scheme is used in talking to the HTTP proxy. This
96
+ # would normally always be set as "http" which will result in the
97
+ # agent then using a SSL tunnel through the HTTP proxy for end to
98
+ # end encryption.
99
+ # See https://docs.newrelic.com/docs/apm/agents/python-agent/configuration/python-agent-configuration/#proxy
100
+ # for information on proxy configuration via environment variables.
101
+ # proxy_scheme = http
102
+ # proxy_host = hostname
103
+ # proxy_port = 8080
104
+ # proxy_user =
105
+ # proxy_pass =
106
+
107
+ # Capturing request parameters is off by default. To enable the
108
+ # capturing of request parameters, first ensure that the setting
109
+ # "attributes.enabled" is set to "true" (the default value), and
110
+ # then add "request.parameters.*" to the "attributes.include"
111
+ # setting. For details about attributes configuration, please
112
+ # consult the documentation.
113
+ # attributes.include = request.parameters.*
114
+
115
+ # The transaction tracer captures deep information about slow
116
+ # transactions and sends this to the UI on a periodic basis. The
117
+ # transaction tracer is enabled by default. Set this to "false"
118
+ # to turn it off.
119
+ transaction_tracer.enabled = true
120
+
121
+ # Threshold in seconds for when to collect a transaction trace.
122
+ # When the response time of a controller action exceeds this
123
+ # threshold, a transaction trace will be recorded and sent to
124
+ # the UI. Valid values are any positive float value, or (default)
125
+ # "apdex_f", which will use the threshold for a dissatisfying
126
+ # Apdex controller action - four times the Apdex T value.
127
+ transaction_tracer.transaction_threshold = apdex_f
128
+
129
+ # When the transaction tracer is on, SQL statements can
130
+ # optionally be recorded. The recorder has three modes, "off"
131
+ # which sends no SQL, "raw" which sends the SQL statement in its
132
+ # original form, and "obfuscated", which strips out numeric and
133
+ # string literals.
134
+ transaction_tracer.record_sql = obfuscated
135
+
136
+ # Threshold in seconds for when to collect stack trace for a SQL
137
+ # call. In other words, when SQL statements exceed this
138
+ # threshold, then capture and send to the UI the current stack
139
+ # trace. This is helpful for pinpointing where long SQL calls
140
+ # originate from in an application.
141
+ transaction_tracer.stack_trace_threshold = 0.5
142
+
143
+ # Determines whether the agent will capture query plans for slow
144
+ # SQL queries. Only supported in MySQL and PostgreSQL. Set this
145
+ # to "false" to turn it off.
146
+ transaction_tracer.explain_enabled = true
147
+
148
+ # Threshold for query execution time below which query plans
149
+ # will not not be captured. Relevant only when "explain_enabled"
150
+ # is true.
151
+ transaction_tracer.explain_threshold = 0.5
152
+
153
+ # Space separated list of function or method names in form
154
+ # 'module:function' or 'module:class.function' for which
155
+ # additional function timing instrumentation will be added.
156
+ transaction_tracer.function_trace =
157
+
158
+ # The error collector captures information about uncaught
159
+ # exceptions or logged exceptions and sends them to UI for
160
+ # viewing. The error collector is enabled by default. Set this
161
+ # to "false" to turn it off. For more details on errors, see
162
+ # https://docs.newrelic.com/docs/apm/agents/manage-apm-agents/agent-data/manage-errors-apm-collect-ignore-or-mark-expected/
163
+ error_collector.enabled = true
164
+
165
+ # To stop specific errors from reporting to the UI, set this to
166
+ # a space separated list of the Python exception type names to
167
+ # ignore. The exception name should be of the form 'module:class'.
168
+ error_collector.ignore_classes =
169
+
170
+ # Expected errors are reported to the UI but will not affect the
171
+ # Apdex or error rate. To mark specific errors as expected, set this
172
+ # to a space separated list of the Python exception type names to
173
+ # expected. The exception name should be of the form 'module:class'.
174
+ error_collector.expected_classes =
175
+
176
+ # Browser monitoring is the Real User Monitoring feature of the UI.
177
+ # For those Python web frameworks that are supported, this
178
+ # setting enables the auto-insertion of the browser monitoring
179
+ # JavaScript fragments.
180
+ browser_monitoring.auto_instrument = true
181
+
182
+ # A thread profiling session can be scheduled via the UI when
183
+ # this option is enabled. The thread profiler will periodically
184
+ # capture a snapshot of the call stack for each active thread in
185
+ # the application to construct a statistically representative
186
+ # call tree. For more details on the thread profiler tool, see
187
+ # https://docs.newrelic.com/docs/apm/apm-ui-pages/events/thread-profiler-tool/
188
+ thread_profiler.enabled = true
189
+
190
+ # Your application deployments can be recorded through the
191
+ # New Relic REST API. To use this feature provide your API key
192
+ # below then use the `newrelic-admin record-deploy` command.
193
+ # This can also be set using the NEW_RELIC_API_KEY
194
+ # environment variable.
195
+ # api_key =
196
+
197
+ # Distributed tracing lets you see the path that a request takes
198
+ # through your distributed system. For more information, please
199
+ # consult our distributed tracing planning guide.
200
+ # https://docs.newrelic.com/docs/transition-guide-distributed-tracing
201
+ distributed_tracing.enabled = true
202
+
203
+ # This setting enables log decoration, the forwarding of log events,
204
+ # and the collection of logging metrics if these sub-feature
205
+ # configurations are also enabled. If this setting is false, no
206
+ # logging instrumentation features are enabled. This can also be
207
+ # set using the NEW_RELIC_APPLICATION_LOGGING_ENABLED environment
208
+ # variable.
209
+ # application_logging.enabled = true
210
+
211
+ # If true, the agent captures log records emitted by your application
212
+ # and forwards them to New Relic. `application_logging.enabled` must
213
+ # also be true for this setting to take effect. You can also set
214
+ # this using the NEW_RELIC_APPLICATION_LOGGING_FORWARDING_ENABLED
215
+ # environment variable.
216
+ # application_logging.forwarding.enabled = true
217
+
218
+ # If true, the agent decorates logs with metadata to link to entities,
219
+ # hosts, traces, and spans. `application_logging.enabled` must also
220
+ # be true for this setting to take effect. This can also be set
221
+ # using the NEW_RELIC_APPLICATION_LOGGING_LOCAL_DECORATING_ENABLED
222
+ # environment variable.
223
+ # application_logging.local_decorating.enabled = true
224
+
225
+ # If true, the agent captures metrics related to the log lines
226
+ # being sent up by your application. This can also be set
227
+ # using the NEW_RELIC_APPLICATION_LOGGING_METRICS_ENABLED
228
+ # environment variable.
229
+ # application_logging.metrics.enabled = true
230
+
231
+
232
+ # ---------------------------------------------------------------------------
233
+
234
+ #
235
+ # The application environments. These are specific settings which
236
+ # override the common environment settings. The settings related to a
237
+ # specific environment will be used when the environment argument to the
238
+ # newrelic.agent.initialize() function has been defined to be either
239
+ # "development", "test", "staging" or "production".
240
+ #
241
+
242
+ [newrelic:development]
243
+ monitor_mode = false
244
+
245
+ [newrelic:test]
246
+ monitor_mode = false
247
+
248
+ [newrelic:staging]
249
+ app_name = (Staging)
250
+ monitor_mode = true
251
+
252
+ [newrelic:production]
253
+ monitor_mode = true
254
+
255
+ # ---------------------------------------------------------------------------