mozilla
/
treeherder
зеркало из https://github.com/mozilla/treeherder.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
treeherder/newrelic.ini

34 строки
1.6 KiB
INI
Исходник Обычный вид История

Bug 1182425 - Add a config file for the New Relic Python agent The settings for the New Relic Python agent are defined via the following methods (later items override the earlier ones): 1. Agent defaults 2. Environment variables 3. Local agent configuration file (iff `NEW_RELIC_CONFIG_FILE` set) 4. Server-side configuration (ie via the New Relic website) 5. Per-request configuration Some settings can only be controlled by a subset of these methods, eg the more security-sensitive ones (like whether request parameters should be recorded) must be set via [3]. In addition, once [4] is activated, *all* settings that can be set via their website will override those from 1-3, even if they are set to the empty string. As such, it's recommended to *only* use the local agent config file for settings that are unavailable on the website. Stage/prod do currently have their own config file (managed via puppet, forked from the standard IT config), however it turns out it's unused since `NEW_RELIC_CONFIG_FILE` isn't defined. This explains why bug 1141036 didn't actually make any difference. To change New Relic settings (that can't be set via the website) on Heroku, we're going to need to commit a config file to the repo anyway, so we might as well use that same file for stage/prod too, so we can modify the config there without requiring puppet changes. I've not copied the unused stage/prod config file from puppet, since it's crufty and mostly contains defaults. This commit is a no-op until `NEW_RELIC_CONFIG_FILE` is defined in each environment. The `log_file` setting within will make the NEW_RELIC_LOG environment variable redundant. That variable is currently set to 'stderr' for stage/prod and 'stdout' for Heroku, so I've settled on 'stdout'. In later bugs (eg for bug 1223496) more useful options will be added, but we'll at least be able to start pointing at the config file using `NEW_RELIC_CONFIG_FILE` in the meantime. For the agent defaults and more info, see: https://docs.newrelic.com/docs/agents/python-agent/installation-configuration/python-agent-configuration
2015-11-17 21:27:06 +03:00
# Options that can be set via the New Relic website (which is most of them)
# override any listed here, so this file should only be used for settings
# that are not available on the website to avoid confusion. See:
# https://docs.newrelic.com/docs/agents/python-agent/installation-configuration/python-agent-configuration
# The NEW_RELIC_CONFIG_FILE environment variable must point at this file,
Bug 1338359 - Set NEW_RELIC_CONFIG_FILE in the Vagrant environment too So that `newrelic.ini` is picked up when using the newrelic-admin wrapper, for parity with production and to ease agent debugging locally.
2017-02-10 02:50:09 +03:00
# and both NEW_RELIC_APP_NAME + NEW_RELIC_LICENSE_KEY be set appropriately,
# unless NEW_RELIC_DEVELOPER_MODE is set.
Bug 1182425 - Add a config file for the New Relic Python agent The settings for the New Relic Python agent are defined via the following methods (later items override the earlier ones): 1. Agent defaults 2. Environment variables 3. Local agent configuration file (iff `NEW_RELIC_CONFIG_FILE` set) 4. Server-side configuration (ie via the New Relic website) 5. Per-request configuration Some settings can only be controlled by a subset of these methods, eg the more security-sensitive ones (like whether request parameters should be recorded) must be set via [3]. In addition, once [4] is activated, *all* settings that can be set via their website will override those from 1-3, even if they are set to the empty string. As such, it's recommended to *only* use the local agent config file for settings that are unavailable on the website. Stage/prod do currently have their own config file (managed via puppet, forked from the standard IT config), however it turns out it's unused since `NEW_RELIC_CONFIG_FILE` isn't defined. This explains why bug 1141036 didn't actually make any difference. To change New Relic settings (that can't be set via the website) on Heroku, we're going to need to commit a config file to the repo anyway, so we might as well use that same file for stage/prod too, so we can modify the config there without requiring puppet changes. I've not copied the unused stage/prod config file from puppet, since it's crufty and mostly contains defaults. This commit is a no-op until `NEW_RELIC_CONFIG_FILE` is defined in each environment. The `log_file` setting within will make the NEW_RELIC_LOG environment variable redundant. That variable is currently set to 'stderr' for stage/prod and 'stdout' for Heroku, so I've settled on 'stdout'. In later bugs (eg for bug 1223496) more useful options will be added, but we'll at least be able to start pointing at the config file using `NEW_RELIC_CONFIG_FILE` in the meantime. For the agent defaults and more info, see: https://docs.newrelic.com/docs/agents/python-agent/installation-configuration/python-agent-configuration
2015-11-17 21:27:06 +03:00
[newrelic]
Bug 1483301 - Raise the New Relic Python agent's shutdown_timeout (#3922) So that the agent has longer to upload the final submission when Heroku restarts gunicorn (eg daily restarts or deploys). See: https://docs.newrelic.com/docs/agents/python-agent/configuration/python-agent-configuration#shutdown-timeout
2018-08-15 12:35:14 +03:00
Bug 1182425 - Add a config file for the New Relic Python agent The settings for the New Relic Python agent are defined via the following methods (later items override the earlier ones): 1. Agent defaults 2. Environment variables 3. Local agent configuration file (iff `NEW_RELIC_CONFIG_FILE` set) 4. Server-side configuration (ie via the New Relic website) 5. Per-request configuration Some settings can only be controlled by a subset of these methods, eg the more security-sensitive ones (like whether request parameters should be recorded) must be set via [3]. In addition, once [4] is activated, *all* settings that can be set via their website will override those from 1-3, even if they are set to the empty string. As such, it's recommended to *only* use the local agent config file for settings that are unavailable on the website. Stage/prod do currently have their own config file (managed via puppet, forked from the standard IT config), however it turns out it's unused since `NEW_RELIC_CONFIG_FILE` isn't defined. This explains why bug 1141036 didn't actually make any difference. To change New Relic settings (that can't be set via the website) on Heroku, we're going to need to commit a config file to the repo anyway, so we might as well use that same file for stage/prod too, so we can modify the config there without requiring puppet changes. I've not copied the unused stage/prod config file from puppet, since it's crufty and mostly contains defaults. This commit is a no-op until `NEW_RELIC_CONFIG_FILE` is defined in each environment. The `log_file` setting within will make the NEW_RELIC_LOG environment variable redundant. That variable is currently set to 'stderr' for stage/prod and 'stdout' for Heroku, so I've settled on 'stdout'. In later bugs (eg for bug 1223496) more useful options will be added, but we'll at least be able to start pointing at the config file using `NEW_RELIC_CONFIG_FILE` in the meantime. For the agent defaults and more info, see: https://docs.newrelic.com/docs/agents/python-agent/installation-configuration/python-agent-configuration
2015-11-17 21:27:06 +03:00
log_file = stdout
Bug 1483301 - Raise the New Relic Python agent's shutdown_timeout (#3922) So that the agent has longer to upload the final submission when Heroku restarts gunicorn (eg daily restarts or deploys). See: https://docs.newrelic.com/docs/agents/python-agent/configuration/python-agent-configuration#shutdown-timeout
2018-08-15 12:35:14 +03:00
Bug 1223496 - Make New Relic capture request parameters too See: https://docs.newrelic.com/docs/agents/python-agent/attributes/python-agent-attributes#requestParameters https://docs.newrelic.com/docs/agents/python-agent/attributes/python-attribute-examples#ex_req_params
2015-11-18 03:51:13 +03:00
# Turn on the capturing of request parameters.
attributes.include = request.parameters.*
Bug 1483301 - Raise the New Relic Python agent's shutdown_timeout (#3922) So that the agent has longer to upload the final submission when Heroku restarts gunicorn (eg daily restarts or deploys). See: https://docs.newrelic.com/docs/agents/python-agent/configuration/python-agent-configuration#shutdown-timeout
2018-08-15 12:35:14 +03:00
Bug 1250573 - Explicitly disable New Relic browser monitoring It's been switched off via the New Relic web UI config page for some time, however it makes sense to explicitly turn it off via the agent config (which cannot then be overridden by the web UI).
2016-05-03 19:38:29 +03:00
# Disable client-side monitoring JS injection, due to there being no way for
# users to opt-out. See:
# https://groups.google.com/forum/#!topic/mozilla.dev.webdev/ragGTzhyY2w
browser_monitoring.enabled = false
Bug 1340203 - Make some Django management commands report to New Relic The name of suitable (finite duration) management commands have to be defined in the New Relic config file, since Django management commands are not annotated by default: https://docs.newrelic.com/docs/agents/python-agent/supported-features/python-background-tasks#django We'll likely want to expand this list in the future, particularly if we switch from celery beat schedules and towards the Heroku scheduler in bug 1176492 (since it will run management commands directly, outside of Celery).
2017-02-16 20:04:08 +03:00
Bug 1483301 - Raise the New Relic Python agent's shutdown_timeout (#3922) So that the agent has longer to upload the final submission when Heroku restarts gunicorn (eg daily restarts or deploys). See: https://docs.newrelic.com/docs/agents/python-agent/configuration/python-agent-configuration#shutdown-timeout
2018-08-15 12:35:14 +03:00
# Raise the maximum time allowed for the agent's final upload upon exit (default 2.5s),
# to make it less likely that New Relic submissions can get lost. The duration must be
# less than gunicorn's `graceful_timeout` (30 seconds).
shutdown_timeout = 15
Bug 1340203 - Make some Django management commands report to New Relic The name of suitable (finite duration) management commands have to be defined in the New Relic config file, since Django management commands are not annotated by default: https://docs.newrelic.com/docs/agents/python-agent/supported-features/python-background-tasks#django We'll likely want to expand this list in the future, particularly if we switch from celery beat schedules and towards the Heroku scheduler in bug 1176492 (since it will run management commands directly, outside of Celery).
2017-02-16 20:04:08 +03:00
[import-hook:django]
Bug 1483301 - Raise the New Relic Python agent's shutdown_timeout (#3922) So that the agent has longer to upload the final submission when Heroku restarts gunicorn (eg daily restarts or deploys). See: https://docs.newrelic.com/docs/agents/python-agent/configuration/python-agent-configuration#shutdown-timeout
2018-08-15 12:35:14 +03:00
Bug 1340203 - Make some Django management commands report to New Relic The name of suitable (finite duration) management commands have to be defined in the New Relic config file, since Django management commands are not annotated by default: https://docs.newrelic.com/docs/agents/python-agent/supported-features/python-background-tasks#django We'll likely want to expand this list in the future, particularly if we switch from celery beat schedules and towards the Heroku scheduler in bug 1176492 (since it will run management commands directly, outside of Celery).
2017-02-16 20:04:08 +03:00
# The agent doesn't annotate Django management commands by default:
# https://docs.newrelic.com/docs/agents/python-agent/supported-features/python-background-tasks#django
# List finite-duration commands here to enable their annotation by the agent.
Bug 1340216 - Make pulse_listener_{pushes,jobs} report to New Relic (#4745) Since these Django management commands are infinite duration (they run continuously listening for Pulse messages), they cannot be added to the list of Django management commands in `newrelic.ini` that are automatically tracked by the New Relic Python agent. Instead, we need to wrap the finite duration function within the Pulse listener command that represents a discrete unit of work that New Relic can report as an individual non-web transaction. See: https://docs.newrelic.com/docs/agents/python-agent/supported-features/python-background-tasks#wrapping
2019-03-04 19:10:58 +03:00
# For infinite duration commands (such as `pulse_listener_*`) see:
# https://docs.newrelic.com/docs/agents/python-agent/supported-features/python-background-tasks#wrapping
Bug 1508228 - Remove Intermittents Commenter celery task (#4300) Remove celery task and change Commenter weekly_mode default arg in preparation for the move to the heroku scheduler
2018-11-28 01:14:38 +03:00
instrumentation.scripts.django_admin = check cycle_data load_initial_data migrate update_bugscache run_intermittents_commenter