elastic-apm 3.15.0 → 4.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ee845be05bcd6dbd56efb3f21372b0abfede8c37b4c7f9580b82ea6a24238fc5
-  data.tar.gz: 46365fa74214843bc882163c917b429beba61d35f65032f45321ce0e128ecf38
+  metadata.gz: b9c57d8f754de9ab6d024f95f2822b0eae82f17a00cd3edae13d290c9b850393
+  data.tar.gz: 4d32a175d46dac86cabdf97de023a49e7e5eb155a21be11eb227bf61afdb8ffc
 SHA512:
-  metadata.gz: 821287e4a80cdf707c6bcddb50ff1cf9592e5410c99e09b69dbebbcc4915a9aae968f8bc1704454ad06a964f173e49b8534a5923d059ef4a70417b74b2b285e8
-  data.tar.gz: 5344fb235b378cff3610c0e49771737ba4c906343025110eb38e277f0cb27a6419e76834baf275ebfb2d59ea8e4b94298b65ebe757dcd7fd9cd0d63727a4fe77
+  metadata.gz: '09cddb89d0d5265c7c12e8838702cde336754e197d8f4e6647f3885ccde3f6fc806f91b22ab054cf8c5c465373e34bf0f46580a2ab01513da5246d9ea443bb2c'
+  data.tar.gz: 10732912f09d131204363dd0191e59f689d9560935af8df0b195cd4a145e9402c4a5f3cc3ed136399471f1a406efd7202a7d8384772bc6356b4a64752333cd03

data/.ci/.jenkins_exclude.yml

@@ -34,6 +34,19 @@ exclude:
     FRAMEWORK: rails-4.2
   - RUBY_VERSION: docker.elastic.co/observability-ci/jruby:9.2-8-jdk
     FRAMEWORK: rails-4.2
+  # sinatra-1.4 exclusions
+  - RUBY_VERSION: ruby:3.0
+    FRAMEWORK: sinatra-1.4
+  - RUBY_VERSION: ruby:2.7
+    FRAMEWORK: sinatra-1.4
+  - RUBY_VERSION: jruby:9.2
+    FRAMEWORK: sinatra-1.4
+  - RUBY_VERSION: docker.elastic.co/observability-ci/jruby:9.2-13-jdk
+    FRAMEWORK: sinatra-1.4
+  - RUBY_VERSION: docker.elastic.co/observability-ci/jruby:9.2-11-jdk
+    FRAMEWORK: sinatra-1.4
+  - RUBY_VERSION: docker.elastic.co/observability-ci/jruby:9.2-8-jdk
+    FRAMEWORK: sinatra-1.4
 
   # rails-6.0 and rails-6.1 exclusions
   # Don't test on ruby 2.4

data/.ci/.jenkins_ruby.yml

@@ -4,7 +4,6 @@ RUBY_VERSION:
   - ruby:2.6
   - ruby:2.5
   - ruby:2.4
-  - ruby:2.3
   - jruby:9.2
   - docker.elastic.co/observability-ci/jruby:9.2-13-jdk
   - docker.elastic.co/observability-ci/jruby:9.2-11-jdk

data/.ci/Jenkinsfile

@@ -389,6 +389,7 @@ def runScript(Map params = [:]){
       dir("${BASE_DIR}"){
         sleep randomNumber(min:10, max: 30)
         dockerLogin(secret: "${DOCKER_SECRET}", registry: "${DOCKER_REGISTRY}")
+        sh(label: "Run BDD tests", script: "./spec/scripts/features.sh ${ruby}")
         sh("./spec/scripts/spec.sh ${ruby} ${framework}")
       }
     }

data/.github/dependabot.yml

@@ -0,0 +1,16 @@
+version: 2
+updates:
+- package-ecosystem: bundler
+  directory: "/"
+  schedule:
+    interval: daily
+  open-pull-requests-limit: 10
+  ignore:
+  - dependency-name: sucker_punch
+    versions:
+    - "> 2.0"
+  - dependency-name: i18n
+    versions:
+    - 1.8.10
+    - 1.8.8
+    - 1.8.9

data/.rubocop.yml

@@ -132,10 +132,3 @@ Style/StringConcatenation:
 
 Style/DocumentDynamicEvalDefinition:
   Enabled: false
-
-# Applies to > ruby 2.3, enable when 2.3 support is dropped
-Performance/RegexpMatch:
-  Enabled: false
-
-Style/HashTransformValues:
-  Enabled: false

data/CHANGELOG.asciidoc

@@ -32,6 +32,73 @@ endif::[]
 ==== Unreleased
 ////
 
+[[release-notes-4.x]]
+=== Ruby Agent version 4.x
+
+[[release-notes-4.1.0]]
+==== 4.1.0
+
+[float]
+===== Added
+
+- Azure App Services instance metadata {pull}1007[#1007]
+
+[float]
+===== Changed
+
+- `hostname` is now reported split by `configured_hostname` and `detected_hostname` {pull}1009[#1009]
+
+[float]
+===== Fixed
+- `service_node_name` is now correctly reported as `service.node.configured_name` {pull}1009[#1009]
+- Fix JSON parsing when using yajl-ruby {pull}1012[#1012]
+- Fix SpanHelpers when methods take blocks {pull}1013[#1013]
+- Fix missing `environment` param when fetching from Central Config {pull}1014[#1014]
+
+[[release-notes-4.0.0]]
+==== 4.0.0
+
+[float]
+===== Upgrading
+
+Be aware that this release changes the agent's general approach to instrumenting third
+party libraries.
+It now uses `Module#prepend` over alias method chaining.
+
+This doesn't necessarily impact your application but it could if you are using other gems
+that use the old approach to patch the same method.
+Mixing the two approaches can lead to infinite recursion.
+
+[float]
+===== Removed
+
+- Removed support for Ruby 2.3 and JRuby 9.1 {pull}901[#901]
+- Config option `active`, see `enabled` {pull}900[#900]
+- Config option `custom_key_filters`, see `sanitize_field_names` {pull}900[#900]
+- Config option `default_tags`, see `global_labels` {pull}900[#900]
+- Config option `default_labels`, see `global_labels` {pull}900[#900]
+- Config option `ignore_url_patterns`, see `transaction_ignore_urls` {pull}900[#900]
+- Config option `use_legacy_sql_parser`, legacy parser no longer included {pull}900[#900]
+
+[float]
+===== Changed
+
+- Integrations (Spies) use Module#prepend over class_eval {pull}890[#890]
+- The secrets filter no longer filters based on values, see `sanitize_field_names` {pull}900[#900]
+- The secrets filter is aligned with other agents, see `sanitize_field_names` {pull}900[#900]
+
+[float]
+===== Added
+
+- Added `set_service` API {pull}1006[#1006]
+
+[float]
+===== Fixed
+
+- AWS S3 spy accepts symbol bucket names {pull}998[#998]
+- AWS S3 spy passing on blocks {pull}998[#998]
+- SQL scanner now recognizes CQL style comments {pull}1004[#1004]
+
 [[release-notes-3.x]]
 === Ruby Agent version 3.x
 

data/Gemfile

@@ -26,6 +26,8 @@ gem 'cucumber', require: false
 gem 'rack-test'
 gem 'rspec', '~> 3'
 gem 'rspec-its'
+gem 'rubocop', require: false
+gem 'rubocop-performance', require: false
 gem 'timecop'
 gem 'webmock'
 
@@ -91,7 +93,7 @@ frameworks_versions.each do |framework, version|
 end
 
 if frameworks_versions.key?('rails')
-  unless frameworks_versions['rails'] =~ /^(main|6)/
+  unless /^(main|6)/.match?(frameworks_versions['rails'])
     gem 'delayed_job', require: nil
   end
 end

data/README.md

@@ -52,15 +52,27 @@ The official Rubygem for [Elastic][] [APM][].
   <li>
     <a href="https://www.elastic.co/guide/en/apm/agent/ruby/current/opentracing.html">OpenTracing API</a>
   </li>
+  <li>
+    <a href="https://www.elastic.co/guide/en/apm/agent/ruby/current/graphql.html">GraphQL</a>
+  </li>
   <li>
     <a href="https://www.elastic.co/guide/en/apm/agent/ruby/current/log-correlation.html">Log correlation</a>
   </li>
+  <li>
+    <a href="https://www.elastic.co/guide/en/apm/agent/ruby/current/tuning-and-overhead.html">Performance tuning</a>
+  </li>
   <li>
     <a href="https://www.elastic.co/guide/en/apm/agent/ruby/current/debugging.html">Troubleshooting</a>
   </li>
+  <li>
+    <a href="https://www.elastic.co/guide/en/apm/agent/ruby/current/upgrading.html">Upgrading</a>
+  </li>
   <li class="collapsible">
     <a href="https://www.elastic.co/guide/en/apm/agent/ruby/current/release-notes.html">Release notes</a>
     <ul>
+      <li>
+        <a href="https://www.elastic.co/guide/en/apm/agent/ruby/current/release-notes-4.x.html">Ruby Agent version 4.x</a>
+      </li>
       <li>
         <a href="https://www.elastic.co/guide/en/apm/agent/ruby/current/release-notes-3.x.html">Ruby Agent version 3.x</a>
       </li>

data/bench/report.rb

@@ -18,7 +18,7 @@ end
 meta = {
   executed_at: Time.new.iso8601,
   'git.commit' => git_sha,
-  'git.date' => String(git_date).strip != '' && Time.parse(git_date).iso8601,
+  'git.date' => (String(git_date).strip != '' && Time.parse(git_date).iso8601) || Time.now.iso8601,
   'git.subject' => git_msg,
   hostname: `hostname`.chomp,
   engine: RUBY_ENGINE,

data/bin/run-bdd

@@ -0,0 +1,17 @@
+#!/bin/bash
+set -e
+
+specific_feature=$1
+
+export CUCUMBER_PUBLISH_QUIET=true
+
+if [[ $specific_feature = '' ]]; then
+  echo 'Running all features'
+
+  echo "========================================"
+  cucumber
+else
+  echo "Running only $specific_feature"
+
+  cucumber $specific_feature
+fi

data/bin/run-tests

@@ -29,5 +29,5 @@ if [[ $specific_spec = '' ]]; then
 else
   echo "Running only $specific_spec"
 
-  runRspec $1
+  runRspec $specific_spec
 fi

data/docs/configuration.asciidoc

@@ -1,14 +1,14 @@
 ifdef::env-github[]
 NOTE: For the best reading experience,
 please view this documentation at
-https://www.elastic.co/guide/en/apm/agent/ruby/current/introduction.html[elastic.co]
+https://www.elastic.co/guide/en/apm/agent/ruby/current/introduction.html[elastic.co].
 endif::[]
 
 [[configuration]]
 == Configuration
 
 There are several ways to configure how Elastic APM behaves.
-The recommended way is to specify options in a `config/elastic_apm.yml` file:
+We recommend using a `config/elastic_apm.yml` file:
 
 [source,yaml]
 ----
@@ -24,7 +24,7 @@ When using this method, strings are split by comma, e.g.,
 [[configuration-precedence]]
 === Configuration precedence
 
-Options are applied in the following order (last one wins):
+Options are applied in the following order (last one wins): 
 
 1. Defaults
 2. Arguments to `ElasticAPM.start` / `Config.new`
@@ -71,7 +71,7 @@ ElasticAPM.start(
 )
 ----
 
-Alternatively, you can use the `ElasticAPM::Sinatra.start` API:
+Alternatively, use the `ElasticAPM::Sinatra.start` API:
 
 [source,ruby]
 ----
@@ -87,7 +87,7 @@ See <<getting-started-rack>>.
 [float]
 === Grape and Rack
 
-When using Grape and Rack (without Rails), you can configure when starting
+When using Grape and Rack (without Rails), configure when starting
 the agent:
 
 [source,ruby]
@@ -114,7 +114,7 @@ See <<getting-started-rack>>.
 | `ELASTIC_APM_CONFIG_FILE` | `config_file` | `config/elastic_apm.yml`
 |============
 
-Path to the configuration YAML-file.
+The path to the configuration YAML-file.
 Elastic APM will load config options from this if the file exists.
 The file will be evaluated as ERB, so you can include `ENV` variables like in
 your `database.yml`, eg:
@@ -150,7 +150,7 @@ and port.
 
 This string is used to ensure that only your agents can send data to your APM server.
 Both the agents and the APM server have to be configured with the same secret token.
-One example to generate a secure secret token is:
+Here's an example that generates a secure secret token:
 
 [source,bash]
 ----
@@ -170,24 +170,9 @@ WARNING: Secret tokens only provide any real security if your APM server uses TL
 |============
 
 This base64-encoded string is used to ensure that only your agents can send data to your APM server.
-You must have created the api key using the APM server command line tool. Please see the APM server
-documentation for details on how to do that. Please note that this feature is experimental in the
-APM server in version 7.6.
+The API key must be created using the {apm-server-ref-v}/api-key.html[APM server command-line tool]. 
 
-WARNING: Api keys only provide any real security if your APM server uses TLS.
-
-[float]
-[[config-active]]
-==== `active` deprecated:[3.7.0,See <<config-enabled>> instead.]
-|============
-| Environment          | `Config` key | Default
-| `ELASTIC_APM_ACTIVE` | `active`     | `true`
-|============
-
-Whether or not to start the agent.
-If `active` is `false`, `ElasticAPM.start` will do nothing and all calls to the root API will return `nil`.
-
-NOTE: This option is being removed. See <<config-enabled>> instead.
+WARNING: API keys only provide any real security if your APM server uses TLS.
 
 [float]
 [[config-api-buffer-size]]
@@ -197,12 +182,11 @@ NOTE: This option is being removed. See <<config-enabled>> instead.
 | `ELASTIC_APM_API_BUFFER_SIZE` | `api_buffer_size` | `256`
 |============
 
-Maximum amount of objects kept in queue, before sending to APM Server.
+The maximum amount of objects kept in queue before sending to APM Server.
 
-If you hit this limit you either have to increase the agent's
-<<config-pool-size,worker pool size>> or it could mean the agent has trouble
-connecting to APM Server. The <<config-log-path,logs>> should tell you what
-went wrong.
+If you hit the limit, consider increasing the agent's <<config-pool-size,worker pool size>>.
+If you don't, the agent may have trouble connecting to APM Server.
+The <<config-log-path,logs>> should tell you what went wrong.
 
 [float]
 [[config-api-request-size]]
@@ -215,10 +199,9 @@ went wrong.
 | `ELASTIC_APM_API_REQUEST_SIZE` | `api_request_size` | `"750kb"`
 |============
 
-Maximum amount of bytes sent over one request to APM Server. When reached the agent
-will open a new request.
+The maximum amount of bytes sent over one request to APM Server. The agent will open a new request when this limit is reached. 
 
-It has to be provided in *<<config-format-size, size format>>*.
+This must be provided in *<<config-format-size, size format>>*.
 
 [float]
 [[config-api-request-time]]
@@ -231,12 +214,11 @@ It has to be provided in *<<config-format-size, size format>>*.
 | `ELASTIC_APM_API_REQUEST_TIME` | `api_request_time` | `"10s"`
 |============
 
-Maximum duration of a single streaming request to APM Server before opening
+The maximum duration of a single streaming request to APM Server before opening
 a new one.
 
-APM Server has its own limit of 30 seconds before it will close requests.
-
-It has to be provided in *<<config-format-duration, duration format>>*.
+The APM Server has its own limit of 30 seconds before it will close requests.
+This must be provided in *<<config-format-duration, duration format>>*.
 
 [float]
 [[config-breakdown-metrics]]
@@ -246,8 +228,8 @@ It has to be provided in *<<config-format-duration, duration format>>*.
 | `ELASTIC_APM_BREAKDOWN_METRICS` | `breakdown_metrics` | `true`
 |============
 
-Enable/disable the tracking and collection of breakdown metrics.
-By setting this to `False`, tracking this metric is completely disabled, which can reduce the overhead of the agent.
+Enable or disable the tracking and collection of breakdown metrics.
+Setting this to `False` disables the tracking of breakdown metrics, which can reduce the overhead of the agent.
 
 NOTE: This feature requires APM Server and Kibana >= 7.3.
 
@@ -262,14 +244,13 @@ NOTE: This feature requires APM Server and Kibana >= 7.3.
 | `ELASTIC_APM_CAPTURE_BODY` | `capture_body` | `"off"` | `"all"`
 |============
 
-For transactions that are HTTP requests,
-the Ruby agent can optionally capture the request body (e.g. `POST` variables or JSON data).
+The Ruby agent can optionally capture the request body (e.g. `POST` variables or JSON data) for transactions that are HTTP requests.
 
 Possible values: `"errors"`, `"transactions"`, `"all"`, `"off"`.
 
 If the request has a body and this setting is disabled, the body will be shown as `[SKIPPED]`.
 
-WARNING: request bodies often contain sensitive values like passwords, credit card numbers etc.
+WARNING: Request bodies often contain sensitive values like passwords and credit card numbers.
 We try to strip sensitive looking data from form bodies but don't touch text bodies like JSON.
 If your service handles data like this, we advise to only enable this feature with care.
 
@@ -285,7 +266,7 @@ If your service handles data like this, we advise to only enable this feature wi
 | `ELASTIC_APM_CAPTURE_HEADERS` | `capture_headers` | `true`
 |============
 
-Whether or not to attach the request headers to transactions and errors.
+This indicates whether or not to attach the request headers to transactions and errors.
 
 [float]
 [[config-capture-elasticsearch-queries]]
@@ -295,7 +276,7 @@ Whether or not to attach the request headers to transactions and errors.
 | `ELASTIC_APM_CAPTURE_ELASTICSEARCH_QUERIES` | `capture_elasticsearch_queries` | `false`
 |============
 
-Whether or not to capture the body from requests in Elasticsearch.
+This indicates whether or not to capture the body from requests in Elasticsearch.
 
 [float]
 [[config-capture-env]]
@@ -305,7 +286,7 @@ Whether or not to capture the body from requests in Elasticsearch.
 | `ELASTIC_APM_CAPTURE_ENV` | `capture_env` | `true`
 |============
 
-Whether or not to attach `ENV` from Rack to transactions and errors.
+This indicates whether or not to attach `ENV` from Rack to transactions and errors.
 
 [float]
 [[config-central-config]]
@@ -315,10 +296,10 @@ Whether or not to attach `ENV` from Rack to transactions and errors.
 | `ELASTIC_APM_CENTRAL_CONFIG` | `central_config` | `true`
 |============
 
-Enables {apm-app-ref}/agent-configuration.html[APM Agent Configuration via Kibana].
+This enables {apm-app-ref}/agent-configuration.html[APM Agent Configuration via Kibana].
 If set to `true`, the client will poll the APM Server regularly for new agent configuration.
 
-Usually APM Server determines how often to poll, but if not the default interval is 5 minutes.
+Usually APM Server determines how often to poll, but if not, set the default interval is 5 minutes.
 
 NOTE: This feature requires APM Server v7.3 or later and that the APM Server is configured with `kibana.enabled: true`.
 
@@ -331,7 +312,7 @@ NOTE: This feature requires APM Server v7.3 or later and that the APM Server is
 |============
 
 Specify the cloud provider for metadata collection.
-Defaults to `"auto"`, which means the agent uses trial and
+This defaults to `"auto"`, which means the agent uses trial and
 error to collect metadata from all supported cloud providers.
 
 Valid options are `"auto"`, `"aws"`, `"gcp"`, `"azure"`, and `"none"`.
@@ -339,57 +320,6 @@ If set to `"none"`, no cloud metadata will be collected.
 If set to any of `"aws"`, `"gcp"`, or `"azure"`,
 attempts to collect metadata will only be performed from the chosen provider.
 
-[float]
-[[config-custom-key-filters]]
-==== `custom_key_filters` deprecated:[3.5.0,See <<config-sanitize-field-names>> instead.]
-[options="header"]
-|============
-| Environment                      | `Config` key         | Default | Example
-| `ELASTIC_APM_CUSTOM_KEY_FILTERS` | `custom_key_filters` | `[]`    | `['MyAuthHeader']`
-|============
-
-Elastic APM strips
-https://github.com/elastic/apm-agent-ruby/blob/1.x/lib/elastic_apm/filters/secrets_filter.rb[
-what looks like confidential information] from the request/response headers.
-Use this option to add your own custom header keys to the list of filtered keys.
-
-When setting this option via `ENV`, use a comma separated string.
-Eg. `ELASTIC_APM_CUSTOM_KEY_FILTERS="a,b" # => [/a/, /b/]`
-
-NOTE: This option is being removed. See <<config-sanitize-field-names>> instead.
-
-[float]
-[[config-default-tags]]
-==== `default_tags`
-
-[options="header"]
-|============
-| Environment                  | `Config` key     | Default | Example
-| `ELASTIC_APM_DEFAULT_LABELS` | `default_labels` | `{}`    | `region=us1`
-|============
-
-Add default labels to every transaction. Note that this will eventually be deprecated in favor of `global_labels`.
-
-WARNING: Be aware that labels are indexed in Elasticsearch. Using too many unique keys will result in *https://www.elastic.co/blog/found-crash-elasticsearch#mapping-explosion[Mapping explosion]*.
-
-NOTE: `global_labels` are supported as of APM server version 7.2. `default_tags` and `default_labels` will eventually be
-deprecated so please transition to using `global_labels` instead. In the meantime, any `default_labels`
-that are set will override `global_labels`.
-
-[options="header"]
-|============
-| Environment                | `Config` key   | Default | Example
-| `ELASTIC_APM_DEFAULT_TAGS` | `default_tags` | `{}`    | `region=us1`
-|============
-
-Add default tags to add to every transaction. Note that this option has been deprecated in favor of `default_labels`.
-
-WARNING: Be aware that tags are indexed in Elasticsearch. Using too many unique keys will result in *https://www.elastic.co/blog/found-crash-elasticsearch#mapping-explosion[Mapping explosion]*.
-
-NOTE: `global_labels` are supported as of APM server version 7.2. `default_tags` and `default_labels` will eventually be
-deprecated so please transition to using `global_labels` instead. In the meantime, any `default_tags`
-that are set will override `global_labels`.
-
 [float]
 [[config-disable_metrics]]
 ==== `disable_metrics`
@@ -400,7 +330,7 @@ that are set will override `global_labels`.
 
 A comma-separated list of dotted metrics names that should not be sent to the APM Server.
 You can use `*` to match multiple metrics.
-Matching is case-insensitive.
+Matching is not case sensitive.
 
 [float]
 [[config-disable-send]]
@@ -410,7 +340,7 @@ Matching is case-insensitive.
 | `ELASTIC_APM_DISABLE_SEND` | `disable_send` | `false`
 |============
 
-Disables sending payloads to APM Server.
+This disables sending payloads to APM Server.
 
 [float]
 [[config-disable-start-message]]
@@ -420,7 +350,7 @@ Disables sending payloads to APM Server.
 | `ELASTIC_APM_DISABLE_START_MESSAGE` | `disable_start_message` | `false`
 |============
 
-Disables the agent's startup message announcing itself.
+This disables the agents startup message announcing itself.
 
 [float]
 [[config-disabled-instrumentations]]
@@ -432,7 +362,7 @@ Disables the agent's startup message announcing itself.
 | `ELASTIC_APM_DISABLE_INSTRUMENTATIONS` | `disable_instrumentations` | `['json']`
 |============
 
-Elastic APM automatically instruments select third party libraries.
+Elastic APM automatically instruments select third-party libraries.
 Use this option to disable any of these.
 
 Get an array of enabled instrumentations with `ElasticAPM.agent.config.enabled_instrumentations`.
@@ -446,7 +376,7 @@ Get an array of enabled instrumentations with `ElasticAPM.agent.config.enabled_i
 | `ELASTIC_APM_ENABLED` | `enabled`     | `true`
 |============
 
-Whether or not to start the agent.
+Indicates whether or not to start the agent.
 If `enabled` is `false`, `ElasticAPM.start` will do nothing and all calls to the root API will return `nil`.
 
 [float]
@@ -463,7 +393,7 @@ The name of the environment this service is deployed in,
 e.g. "production" or "staging".
 
 Environments allow you to easily filter data on a global level in the APM app.
-It's important to be consistent when naming environments across agents.
+Be consistent when naming environments across agents.
 See {apm-app-ref}/filters.html#environment-selector[environment selector] in the APM app for more information.
 
 Defaults to `ENV['RAILS_ENV'] || ENV['RACK_ENV']`.
@@ -490,7 +420,7 @@ Use this to filter error tracking for specific error constants.
 | `ELASTIC_APM_FRAMEWORK_NAME` | `framework_name` | Depending on framework
 |============
 
-Name of the used framework.
+The name of the used framework.
 For Rails or Sinatra, this defaults to `Ruby on Rails` and `Sinatra` respectively,
 otherwise defaults to `nil`.
 
@@ -503,7 +433,7 @@ otherwise defaults to `nil`.
 | `ELASTIC_APM_FRAMEWORK_VERSION` | `framework_version` | Depending on framework
 |============
 
-Version number of the used framework.
+The version number of the used framework.
 For Ruby on Rails and Sinatra, this defaults to the used version of the framework,
 otherwise, the default is `nil`.
 
@@ -520,9 +450,7 @@ otherwise, the default is `nil`.
 Labels added to all events, with the format key=value[,key=value[,...]].
 
 NOTE: This option requires APM Server 7.2 or greater, and will have no effect when using older
-server versions. `default_tags` will eventually be deprecated but in the meantime, their value
-will override any `global_labels`. Please transition to using `global_labels` instead of
-`default_tags` in light of this deprecation.
+server versions.
 
 [float]
 [[config-hostname]]
@@ -545,12 +473,12 @@ The host name to use when sending error and transaction data to the APM server.
 | `ELASTIC_APM_IGNORE_URL_PATTERNS` | `ignore_url_patterns` | `[]`    | `['^/ping', %r{^/admin}]`
 |============
 
-Use this option to ignore certain URL patterns eg. healthchecks or admin sections.
+Use this option to ignore certain URL patterns such as healthchecks or admin sections.
 
 _Ignoring_ in this context means _don't wrap in a <<api-transaction,Transaction>>_.
 Errors will still be reported.
 
-When setting this option via `ENV`, use a comma separated string.
+Use a comma separated string when setting this option via `ENV`.
 Eg. `ELASTIC_APM_IGNORE_URL_PATTERNS="a,b" # => [/a/, /b/]`
 
 [float]
@@ -562,7 +490,7 @@ Eg. `ELASTIC_APM_IGNORE_URL_PATTERNS="a,b" # => [/a/, /b/]`
 | `ELASTIC_APM_INSTRUMENT` | `instrument` | `true`  | `0`
 |============
 
-Use this option to ignore certain URL patterns eg. healthchecks or admin sections.
+Use this option to ignore certain URL patterns such as healthchecks or admin sections.
 
 [float]
 [[config-instrumented-rake-tasks]]
@@ -574,7 +502,7 @@ Use this option to ignore certain URL patterns eg. healthchecks or admin section
 | `ELASTIC_APM_INSTRUMENTED_RAKE_TASKS` | `instrumented_rake_tasks` | `[]`    | `['my_task']`
 |============
 
-Elastic APM can instrument your Rake tasks but given that they are used for a multitude of sometimes very different and not always relevant things, this is opt in.
+Elastic APM can instrument your Rake tasks. Theis is an opt-in field, as they are used are for a multitude of things. 
 
 [float]
 [[config-log-level]]
@@ -604,7 +532,7 @@ A path to a log file.
 
 By default Elastic APM logs to `stdout` or uses `Rails.log` when used with Rails.
 
-Should support both absolute and relative paths. Just make sure the directory exists.
+This should support both absolute and relative paths. Please be sure the directory exists.
 
 [float]
 [[config-logger]]
@@ -618,7 +546,7 @@ Should support both absolute and relative paths. Just make sure the directory ex
 
 By default Elastic APM logs to `stdout` or uses `Rails.log` when used with Rails.
 
-Use this to provide another logger. Expected to have the same API as Ruby's built-in `Logger`.
+Use this to provide another logger. This is expected to have the same API as Ruby's built-in `Logger`.
 
 [float]
 [[config-metrics-interval]]
@@ -632,7 +560,7 @@ Use this to provide another logger. Expected to have the same API as Ruby's buil
 
 Specify the interval for reporting metrics to APM Server.
 The interval should be in seconds,
-or should include a time suffix.
+or include a time suffix.
 
 To disable metrics reporting,
 set the interval to `0`.
@@ -691,7 +619,7 @@ See https://github.com/httprb/http/wiki/Proxy-Support[Http.rb's docs].
 |============
 
 Enable or disable the recording of events.
-If set to false, then the agent does not create or send any events to the Elastic APM server,
+If set to `false`, then the agent does not create or send any events to the Elastic APM server,
 and instrumentation overhead is minimized. The agent continues to poll the server for configuration changes
 when this option is false.
 
@@ -701,13 +629,13 @@ when this option is false.
 
 [options="header"]
 |============
-| Environment                        | `Config` key           | Default | Example
-| `ELASTIC_APM_SANITIZE_FIELD_NAMES` | `sanitize_field_names` | `[]`    | `Auth*tion,abc*,*xyz`
+| Environment                        | `Config` key           | Default                                                                                        | Example
+| `ELASTIC_APM_SANITIZE_FIELD_NAMES` | `sanitize_field_names` | `"password,passwd,pwd,secret,*key,*token*,*session*,*credit*,*card*,authorization,set-cookie"` | `Auth*tion,abc*,*xyz`
 |============
 
-Sometimes it is necessary to sanitize the data sent to Elastic APM, e.g. remove sensitive data.
+Sometimes it is necessary to sanitize the data sent to Elastic APM to remove sensitive values.
 
-Configure a list of wildcard patterns of field names which should be sanitized. These apply to HTTP headers and bodies (if you're capturing those.)
+Configure a list of wildcard patterns of field names which should be sanitized. These apply to HTTP headers and bodies, if they're being captured.
 
 Supports the wildcard `*`, which matches zero or more characters.
 Examples: `/foo/*/bar/*/baz*`, `*foo*`.
@@ -723,16 +651,15 @@ Matching is case insensitive.
 | `ELASTIC_APM_SERVICE_NAME` | `service_name` | App's name | `MyApp`
 |============
 
-The name of your service.
-This is used to keep all the errors and transactions of your service together and is
+The name of your service. This is used to group the errors and transactions of your service and is
 the primary filter in the Elastic APM user interface.
 
 If you're using Ruby on Rails this will default to your app's name.
 If you're using Sinatra it will default to the name of your app's class.
 
 NOTE: The service name must conform to this regular expression: `^[a-zA-Z0-9 _-]+$`.
-In layman's terms: Your service name must only contain characters from the ASCII
-alphabet, numbers, dashes, underscores and spaces.
+In other words, it must only contain characters from the ASCII
+alphabet, numbers, dashes, underscores, and spaces.
 
 [float]
 [[config-service-node-name]]
@@ -745,11 +672,10 @@ alphabet, numbers, dashes, underscores and spaces.
 |============
 
 The name of the given service node. This is optional, and if omitted, the APM
-Server will fall back on `system.container.id` if available, and finally
+Server will fall back on `system.container.id` if available, and
 `host.name` if necessary.
 
-This option allows you to set the node name manually to ensure uniqueness and
-meaningfulness.
+This option allows you to set the node name manually to ensure it's unique and meaningful. 
 
 [float]
 [[config-service-version]]
@@ -760,8 +686,8 @@ meaningfulness.
 | `ELASTIC_APM_SERVICE_VERSION`  | `service_version` | `git` sha | A string indicating the version of the deployed service
 |============
 
-Deployed version of your service.
-Defaults to `git rev-parse --verify HEAD`.
+The deployed version of your service.
+This defaults to `git rev-parse --verify HEAD`.
 
 [float]
 [[config-source-lines-error-app-frames]]
@@ -785,7 +711,7 @@ Defaults to `git rev-parse --verify HEAD`.
 |============
 
 By default, the APM agent collects source code snippets for errors.
-With the above settings, you can modify how many lines of source code is collected.
+Use the above settings to modify how many lines of source code are collected.
 
 We differ between errors and spans, as well as library frames and app frames.
 
@@ -803,7 +729,7 @@ storage use in your Elasticsearch cluster.
 | `ELASTIC_APM_SPAN_FRAMES_MIN_DURATION` | `span_frames_min_duration` | `"5ms"`
 |============
 
-Use this to disable stacktrace frame collection for spans with a duration shorter
+Use this to disable stack trace frame collection for spans with a duration shorter
 than or equal to the given amount of milleseconds.
 
 The default is `"5ms"`.
@@ -870,18 +796,7 @@ To reduce overhead and storage requirements, you can set the sample rate to a va
 between `0.0` and `1.0`.
 We still record overall time and the result for unsampled transactions, but no
 context information, tags, or spans.
-Note that the sample rate will be rounded to 4 digits of precision.
-
-[float]
-[[config-use-experimental-sql-parser]]
-==== `use_legacy_sql_parser`
-|============
-| Environment                         | `Config` key            | Default
-| `ELASTIC_APM_USE_LEGACY_SQL_PARSER` | `use_legacy_sql_parser` | `false`
-|============
-
-Use the older, less precise approach to generating summaries of your app's SQL statements.
-Try this if you're experiencing trouble using the new default.
+The sample rate will be rounded to 4 digits of precision.
 
 [float]
 [[config-verify-server-cert]]
@@ -934,14 +849,14 @@ The unit is provided as suffix directly after the number, without any separation
  * `mb` (megabytes)
  * `gb` (gigabytes)
 
-NOTE: we use the power-of-two sizing convention, e.g. `1 kilobyte == 1024 bytes`
+NOTE: We use the power-of-two sizing convention, e.g. `1 kilobyte == 1024 bytes`.
 
 [float]
 [[special-configuration]]
 === Special configuration
 
-Elastic APM patches `Kernel#require` to auto-detect and instrument supported third party libraries. It does so with the utmost care but in rare cases it can conflict with some libraries.
+Elastic APM patches `Kernel#require` to auto-detect and instrument supported third-party libraries. It does so with the utmost care but in rare cases, it can conflict with some libraries.
 
 To get around this patch, set the environment variable `ELASTIC_APM_SKIP_REQUIRE_PATCH` to `"1"`.
 
-If you choose to do so, the agent might need some additional tweaking to make sure the third party libraries are picked up and instrumented. Make sure you require the agent _after_ you require your other dependencies.
+The agent might need some additional tweaking to make sure the third-party libraries are picked up and instrumented. Make sure you require the agent _after_ you require your other dependencies.