newrelic 13.1.0 → 13.2.0

package/lib/config/default.js

@@ -22,1750 +22,1752 @@ const pkgInstrumentation = require('./build-instrumentation-config')
  *
  * @returns {object} configuration definition
  */
-defaultConfig.definition = () => ({
-  newrelic_home: {
-    env: 'NEW_RELIC_HOME',
-    default: null
-  },
-
-  /**
-   * Array of application names.
-   */
-  app_name: {
-    formatter(val) {
-      return val.split(/[;,]/).map((k) => k.trim())
-    },
-    default: []
-  },
-  /**
-   * The user's license key. Must be set by per-app configuration file.
-   */
-  license_key: '',
-  /**
-   *
-   * Enables/Disables security policies.  Paste your security policies
-   * token from the New Relic Admin below.
-   */
-  security_policies_token: '',
-  /**
-   * Hostname for the New Relic collector proxy.
-   *
-   * You shouldn't need to change this.
-   */
-  host: '',
-  /**
-   * Endpoint to send OpenTelemetry spans to.
-   *
-   * This should be automatically deduced from your region and other
-   * settings, but if desired, you can override it.
-   */
-  otlp_endpoint: '',
-  /**
-   * The port on which the collector proxy will be listening.
-   *
-   * You shouldn't need to change this.
-   */
-  port: {
-    formatter: int,
-    default: 443
-  },
-  /**
-   * Whether or not to use SSL to connect to New Relic's servers.
-   *
-   * NOTE: This option can no longer be disabled.
-   */
-  ssl: {
-    env: 'NEW_RELIC_USE_SSL',
-    formatter(_, logger) {
-      logger.warn('SSL config key can no longer be disabled, not updating.')
-      return true
-    },
-    default: true
-  },
-  /**
-   * Proxy url
-   *
-   * A proxy url can be used in place of setting
-   * proxy_host, proxy_port, proxy_user, and proxy_pass.
-   *
-   * e.g. http://user:pass@host:port/
-   *
-   * Setting proxy will override other proxy settings.
-   */
-  proxy: {
-    env: 'NEW_RELIC_PROXY_URL',
-    default: ''
-  },
-  /**
-   * Proxy host to use to connect to the internet.
-   */
-  proxy_host: '',
-  /**
-   * Proxy port to use to connect to the internet.
-   */
-  proxy_port: '',
-  /**
-   * Proxy user name when required.
-   */
-  proxy_user: '',
-  /**
-   * Proxy password when required.
-   */
-  proxy_pass: '',
-  // Serverless DT config defaults
-  trusted_account_key: {
-    default: null
-  },
-  primary_application_id: {
-    default: null
-  },
-  account_id: {
-    default: null
-  },
-  /**
-   * Custom SSL certificates
-   *
-   * If your proxy uses a custom SSL certificate, you can add the CA text to
-   * this array, one entry per certificate.
-   *
-   * The easiest way to do this is with `fs.readFileSync` e.g.
-   *
-   * certificates: [
-   *   require('fs').readFileSync('custom.crt', 'utf8') // don't forget the utf8
-   * ]
-   *
-   */
-  certificates: {
-    formatter: array,
-    default: []
-  },
-  /**
-   * Whether the module is enabled.
-   */
-  agent_enabled: {
-    env: 'NEW_RELIC_ENABLED',
-    formatter: boolean,
-    default: true
-  },
-
-  /**
-   * Collects configuration related to New Relic Agent Control, i.e. centralized
-   * agent management in container based environments.
-   */
-  agent_control: {
-    /**
-     * Indicates that the agent is being managed by Agent Control. Must be set
-     * to true health monitoring.
-     */
-    enabled: {
-      formatter: boolean,
-      default: false
+defaultConfig.definition = () => {
+  return {
+    newrelic_home: {
+      env: 'NEW_RELIC_HOME',
+      default: null
     },
 
     /**
-     * Settings specific to the health monitoring aspect of Agent Control.
+     * Array of application names.
      */
-    health: {
-      /**
-       * A string file path to a directory that the agent is expected to write
-       * health status files to. Must be set for health monitoring to be
-       * enabled.
-       */
-      delivery_location: {
-        default: 'file:///newrelic/apm/health'
+    app_name: {
+      formatter(val) {
+        return val.split(/[;,]/).map((k) => k.trim())
       },
-
-      /**
-       * The time, in seconds, that the agent should wait between writing
-       * updates to its health status. The default interval is 5 seconds.
-       */
-      frequency: {
-        formatter: int,
-        default: 5
-      }
-    }
-  },
-
-  /**
-   * The default Apdex tolerating / threshold value for applications, in
-   * seconds. The default for Node is apdexT to 100 milliseconds, which is
-   * lower than New Relic standard, but Node.js applications tend to be more
-   * latency-sensitive than most.
-   *
-   * NOTE: This setting can not be modified locally. Use server-side configuration
-   * to change your application's apdex.
-   *
-   * @see https://docs.newrelic.com/docs/apm/new-relic-apm/apdex/changing-your-apdex-settings
-   */
-  apdex_t: {
-    formatter: float,
-    default: 0.1
-  },
-  /**
-   * When true, all request headers except for those listed in attributes.exclude
-   * will be captured for all traces, unless otherwise specified in a destination's
-   * attributes include/exclude lists.
-   */
-  allow_all_headers: {
-    formatter: boolean,
-    default: false
-  },
-
-  /**
-   * If the data compression threshold is reached in the payload, the
-   * agent compresses data, using gzip compression by default. The
-   * config option `compressed_content_encoding` can be set to 'deflate'
-   * to use deflate compression.
-   */
-  compressed_content_encoding: 'gzip',
-
-  /**
-   * Attributes are key-value pairs containing information that determines
-   * the properties of an event or transaction.
-   */
-  attributes: {
-    /**
-     * If `true`, enables capture of attributes for all destinations.
-     * If there are specific parameters you want ignored, use `attributes.exclude`.
-     */
-    enabled: {
-      formatter: boolean,
-      default: true
+      default: []
     },
-
     /**
-     * Defines the number of characters allowed for each individual attribute's
-     * value. The default is 256 characters, with a maximum of 4,096.
+     * The user's license key. Must be set by per-app configuration file.
      */
-    value_size_limit: {
-      formatter: int,
-      /**
-       * Maximum value is 4,096.
-       */
-      default: 256
-    },
-
+    license_key: '',
     /**
-     * Prefix of attributes to exclude from all destinations. Allows * as wildcard at end.
      *
-     * NOTE: If excluding headers, they must be in camelCase form to be filtered.
+     * Enables/Disables security policies.  Paste your security policies
+     * token from the New Relic Admin below.
      */
-    exclude: {
-      formatter: array,
-      default: []
-    },
-
+    security_policies_token: '',
     /**
-     * Prefix of attributes to include in all destinations. Allows * as wildcard at end.
+     * Hostname for the New Relic collector proxy.
      *
-     * NOTE: If including headers, they must be in camelCase form to be filtered.
+     * You shouldn't need to change this.
      */
-    include: {
-      formatter: array,
-      default: []
-    },
-
+    host: '',
     /**
-     * If `true`, patterns may be added to the `attributes.include`
-     * list.
+     * Endpoint to send OpenTelemetry spans to.
+     *
+     * This should be automatically deduced from your region and other
+     * settings, but if desired, you can override it.
      */
-    include_enabled: {
-      formatter: boolean,
-      default: true
-    },
-
+    otlp_endpoint: '',
     /**
-     * Controls how many attribute include/exclude rule results are cached by
-     * the filter. Increasing this limit will cause greater memory usage and is
-     * only necessary if you have an extremely high variety of attributes.
+     * The port on which the collector proxy will be listening.
+     *
+     * You shouldn't need to change this.
      */
-    filter_cache_limit: {
+    port: {
       formatter: int,
-      default: 1000
-    }
-  },
-  logging: {
-    /**
-     * Verbosity of the module's logging. This module uses bunyan
-     * (https://github.com/trentm/node-bunyan) for its logging, and as such the
-     * valid logging levels are 'fatal', 'error', 'warn', 'info', 'debug' and
-     * 'trace'. Logging at levels 'info' and higher is very terse. For support
-     * requests, attaching logs captured at 'trace' level are extremely helpful
-     * in chasing down bugs.
-     */
-    level: {
-      default: 'info',
-      env: 'NEW_RELIC_LOG_LEVEL'
-    },
-    /**
-     * Where to put the log file -- by default just uses process.cwd +
-     * 'newrelic_agent.log'. A special case is a filepath of 'stdout',
-     * in which case all logging will go to stdout, or 'stderr', in which
-     * case all logging will go to stderr.
-     */
-    filepath: {
-      default: require('path').join(process.cwd(), 'newrelic_agent.log'),
-      env: 'NEW_RELIC_LOG'
-    },
-    /**
-     * Whether to write to a log file at all
-     */
-    enabled: {
-      formatter: boolean,
-      default: true,
-      env: 'NEW_RELIC_LOG_ENABLED'
-    },
-
-    /**
-     * Enables extra debugging at `warn` level. No need to enable except under
-     * specific debugging conditions.
-     */
-    diagnostics: {
-      formatter: boolean,
-      deafult: false
-    }
-  },
-  audit_log: {
-    /**
-     * Enables logging of out bound traffic from the Agent to the Collector.
-     * This field is ignored if trace level logging is enabled.
-     * With trace logging, all traffic is logged.
-     */
-    enabled: {
-      formatter: boolean,
-      default: false
+      default: 443
     },
-
     /**
-     * Specify which methods are logged. Used in conjunction with the audit_log flag
-     * If audit_log is enabled and this property is empty, all methods will be logged
-     * Otherwise, if the audit log is enabled, only the methods specified
-     * in the filter will be logged
-     * Methods include: error_data, metric_data, and analytic_event_data
+     * Whether or not to use SSL to connect to New Relic's servers.
+     *
+     * NOTE: This option can no longer be disabled.
      */
-    endpoints: {
-      formatter: array,
-      default: []
-    }
-  },
-  /**
-   * Whether to collect & submit error traces to New Relic.
-   */
-  error_collector: {
-    attributes: {
-      /**
-       * If `true`, the agent captures attributes from error collection.
-       */
-      enabled: {
-        formatter: boolean,
-        default: true
+    ssl: {
+      env: 'NEW_RELIC_USE_SSL',
+      formatter(_, logger) {
+        logger.warn('SSL config key can no longer be disabled, not updating.')
+        return true
       },
-      /**
-       * Prefix of attributes to exclude from error collection.
-       * Allows * as wildcard at end.
-       */
-      exclude: {
-        formatter: array,
-        default: []
-      },
-      /**
-       * Prefix of attributes to include in error collection.
-       * Allows * as wildcard at end.
-       */
-      include: {
-        formatter: array,
-        default: []
-      }
-    },
-    /**
-     * Disabling the error tracer just means that errors aren't collected
-     * and sent to New Relic -- it DOES NOT remove any instrumentation.
-     */
-    enabled: {
-      formatter: boolean,
       default: true
     },
     /**
-     * List of HTTP error status codes the error tracer should disregard.
-     * Ignoring a status code means that the transaction is not renamed to
-     * match the code, and the request is not treated as an error by the error
-     * collector.
+     * Proxy url
      *
-     * NOTE: This configuration value has no effect on errors recorded using
-     * `noticeError()`.
+     * A proxy url can be used in place of setting
+     * proxy_host, proxy_port, proxy_user, and proxy_pass.
      *
-     * Defaults to 404 NOT FOUND.
-     */
-    ignore_status_codes: {
-      env: 'NEW_RELIC_ERROR_COLLECTOR_IGNORE_ERROR_CODES',
-      formatter: array,
-      default: [404]
-    },
-    /**
-     * Whether error events are collected.
-     */
-    capture_events: {
-      formatter: boolean,
-      default: true
-    },
-    /**
-     * The agent will collect all error events up to this number per minute.
-     * If there are more than that, a statistical sampling will be collected.
-     * Currently this uses a priority sampling algorithm.
+     * e.g. http://user:pass@host:port/
      *
-     * By increasing this setting you are both increasing the memory
-     * requirements of the agent as well as increasing the payload to the New
-     * Relic servers. The memory concerns are something you should consider for
-     * your own server's sake. The payload of events is compressed, but if it
-     * grows too large the New Relic servers may reject it.
+     * Setting proxy will override other proxy settings.
      */
-    max_event_samples_stored: {
-      formatter: int,
-      default: 100
-    },
-
-    expected_classes: {
-      formatter: array,
-      default: [],
-      env: 'NEW_RELIC_ERROR_COLLECTOR_EXPECTED_ERRORS'
-    },
-    expected_messages: {
-      formatter: object,
-      default: {}
-    },
-    expected_status_codes: {
-      formatter: array,
-      default: [],
-      env: 'NEW_RELIC_ERROR_COLLECTOR_EXPECTED_ERROR_CODES'
-    },
-    ignore_classes: {
-      formatter: array,
-      default: [],
-      env: 'NEW_RELIC_ERROR_COLLECTOR_IGNORE_ERRORS'
+    proxy: {
+      env: 'NEW_RELIC_PROXY_URL',
+      default: ''
     },
-    ignore_messages: {
-      formatter: object,
-      default: {}
-    }
-  },
-  /**
-   * Error message redaction
-   *
-   * Options regarding how the agent handles the redaction of error messages.
-   *
-   */
-  strip_exception_messages: {
     /**
-     * When `true`, the agent will redact the messages of captured
-     * errors.
+     * Proxy host to use to connect to the internet.
      */
-    enabled: {
-      formatter: boolean,
-      default: false
-    }
-  },
-  cloud: {
-    aws: {
-      /**
-       * The AWS account ID for the AWS account associated with this app.
-       */
-      account_id: {
-        formatter: int,
-        default: null
-      }
-    }
-  },
-  /**
-   * Options regarding collecting system information. Used for system
-   * utilization based pricing scheme.
-   */
-  utilization: {
+    proxy_host: '',
     /**
-     * This flag dictates whether the agent attempts to reach out to AWS
-     * to get info about the vm the process is running on.
+     * Proxy port to use to connect to the internet.
      */
-    detect_aws: {
-      formatter: boolean,
-      default: true
-    },
+    proxy_port: '',
     /**
-     * This flag dictates whether the agent attempts to detect if the
-     * the process is running on Pivotal Cloud Foundry.
+     * Proxy user name when required.
      */
-    detect_pcf: {
-      formatter: boolean,
-      default: true
-    },
+    proxy_user: '',
     /**
-     * This flag dictates whether the agent attempts to reach out to Azure to
-     * get info about the vm the process is running on.
+     * Proxy password when required.
      */
-    detect_azure: {
-      formatter: boolean,
-      default: true
+    proxy_pass: '',
+    // Serverless DT config defaults
+    trusted_account_key: {
+      default: null
     },
-    /**
-     * This flag dictates whether the agent attempts to read environment variables
-     * and invocation context to get info about the Azure Function called.
-     */
-    detect_azurefunction: {
-      formatter: boolean,
-      default: true
+    primary_application_id: {
+      default: null
+    },
+    account_id: {
+      default: null
     },
     /**
-     * This flag dictates whether the agent attempts to read files
-     * to get info about the container the process is running in.
+     * Custom SSL certificates
+     *
+     * If your proxy uses a custom SSL certificate, you can add the CA text to
+     * this array, one entry per certificate.
+     *
+     * The easiest way to do this is with `fs.readFileSync` e.g.
+     *
+     * certificates: [
+     *   require('fs').readFileSync('custom.crt', 'utf8') // don't forget the utf8
+     * ]
      *
-     * env NEW_RELIC_UTILIZATION_DETECT_DOCKER
      */
-    detect_docker: {
-      formatter: boolean,
-      default: true
+    certificates: {
+      formatter: array,
+      default: []
     },
-
     /**
-     * This flag dictates whether the agent attempts to reach out to GCP
-     * to get info about the vm the process is running on.
+     * Whether the module is enabled.
      */
-    detect_gcp: {
+    agent_enabled: {
+      env: 'NEW_RELIC_ENABLED',
       formatter: boolean,
       default: true
     },
 
     /**
-     * This flag dictates whether the agent attempts to reach out to
-     * Kubernetes to get info about the container the process is running on.
+     * Collects configuration related to New Relic Agent Control, i.e. centralized
+     * agent management in container based environments.
      */
-    detect_kubernetes: {
-      formatter: boolean,
-      default: true
-    },
-    logical_processors: {
-      formatter: float,
-      default: null
-    },
-    billing_hostname: {
-      default: null
-    },
-    total_ram_mib: {
-      formatter: int,
-      default: null
-    },
-
+    agent_control: {
     /**
-     * When enabled, it will use GCP metadata id
-     * to set the hostname of the running application.
+     * Indicates that the agent is being managed by Agent Control. Must be set
+     * to true health monitoring.
      */
-    gcp_use_instance_as_host: {
-      default: true,
-      formatter: boolean
-    }
-  },
-  transaction_tracer: {
-    attributes: {
-      /**
-       * If `true`, the agent captures attributes from transaction traces.
-       */
       enabled: {
         formatter: boolean,
-        default: true
+        default: false
       },
+
       /**
-       * Prefix of attributes to exclude from transaction traces.
-       * Allows * as wildcard at end.
+       * Settings specific to the health monitoring aspect of Agent Control.
        */
-      exclude: {
-        formatter: array,
-        default: []
-      },
+      health: {
       /**
-       * Prefix of attributes to include in transaction traces.
-       * Allows * as wildcard at end.
+       * A string file path to a directory that the agent is expected to write
+       * health status files to. Must be set for health monitoring to be
+       * enabled.
        */
-      include: {
-        formatter: array,
-        default: []
+        delivery_location: {
+          default: 'file:///newrelic/apm/health'
+        },
+
+        /**
+         * The time, in seconds, that the agent should wait between writing
+         * updates to its health status. The default interval is 5 seconds.
+         */
+        frequency: {
+          formatter: int,
+          default: 5
+        }
       }
     },
+
     /**
-     * Whether to collect & submit slow transaction traces to New Relic. The
-     * instrumentation is loaded regardless of this setting, as it's necessary
-     * to gather metrics. Disable the agent to prevent the instrumentation from
-     * loading.
-     */
-    enabled: {
-      formatter: boolean,
-      default: true,
-      env: 'NEW_RELIC_TRACER_ENABLED'
-    },
-    /**
-     * Sets the time, in seconds, for a transaction to be considered slow.
-     * When a transaction exceeds this threshold, a transaction trace will be recorded. When set to 'apdex_f', the threshold will be set to
-     * 4 * apdex_t, which with a default apdex_t value of 500 milliseconds will
-     * be 2 seconds.
+     * The default Apdex tolerating / threshold value for applications, in
+     * seconds. The default for Node is apdexT to 100 milliseconds, which is
+     * lower than New Relic standard, but Node.js applications tend to be more
+     * latency-sensitive than most.
+     *
+     * NOTE: This setting can not be modified locally. Use server-side configuration
+     * to change your application's apdex.
      *
-     * If a number is provided, it is set in seconds.
+     * @see https://docs.newrelic.com/docs/apm/new-relic-apm/apdex/changing-your-apdex-settings
      */
-    transaction_threshold: {
+    apdex_t: {
       formatter: float,
-      default: 'apdex_f',
-      env: 'NEW_RELIC_TRACER_THRESHOLD'
+      default: 0.1
     },
     /**
-     * Increase this parameter to increase the diversity of the slow
-     * transaction traces recorded by your application over time. Confused?
-     * Read on.
-     *
-     * Transactions are named based on the request (see the README for the
-     * details of how requests are mapped to transactions), and top_n refers to
-     * the "top n slowest transactions" grouped by these names. The module will
-     * only replace a recorded trace with a new trace if the new trace is
-     * slower than the previous slowest trace of that name. The default value
-     * for this setting is 20, as the transaction trace view page also defaults
-     * to showing the 20 slowest transactions.
-     *
-     * If you want to record the absolute slowest transaction over the last
-     * minute, set top_n to 0 or 1. This used to be the default, and has a
-     * problem in that it will allow one very slow route to dominate your slow
-     * transaction traces.
-     *
-     * The module will always record at least 5 different slow transactions in
-     * the reporting periods after it starts up, and will reset its internal
-     * slow trace aggregator if no slow transactions have been recorded for the
-     * last 5 harvest cycles, restarting the aggregation process.
-     *
-     * env NEW_RELIC_TRACER_TOP_N
+     * When true, all request headers except for those listed in attributes.exclude
+     * will be captured for all traces, unless otherwise specified in a destination's
+     * attributes include/exclude lists.
      */
-    top_n: {
-      formatter: int,
-      default: 20,
-      env: 'NEW_RELIC_TRACER_TOP_N'
+    allow_all_headers: {
+      formatter: boolean,
+      default: false
     },
 
     /**
-     * This option affects both slow-queries and record_sql for transaction
-     * traces.  It can have one of 3 values: 'off', 'obfuscated' or 'raw'
-     * When it is 'off' no slow queries will be captured, and backtraces
-     * and sql will not be included in transaction traces.  If it is 'raw'
-     * or 'obfuscated' and other criteria (slow_sql.enabled etc) are met
-     * for a query. The raw or obfuscated sql will be included in the
-     * transaction trace and a slow query sample will be collected.
+     * If the data compression threshold is reached in the payload, the
+     * agent compresses data, using gzip compression by default. The
+     * config option `compressed_content_encoding` can be set to 'deflate'
+     * to use deflate compression.
      */
-    record_sql: {
-      formatter: allowList.bind(null, ['off', 'obfuscated', 'raw']),
-      default: 'obfuscated',
-      env: 'NEW_RELIC_RECORD_SQL'
-    },
+    compressed_content_encoding: 'gzip',
 
     /**
-     * This option affects both slow-queries and record_sql for transaction
-     * traces.  This is the minimum duration a query must take (in ms) for it
-     * to be considered for for slow query and inclusion in transaction traces.
-     */
-    explain_threshold: {
-      formatter: int,
-      default: 500,
-      env: 'NEW_RELIC_EXPLAIN_THRESHOLD'
-    }
-  },
-  /**
-   * Rules for naming or ignoring transactions.
-   */
-  rules: {
-    /**
-     * A list of rules of the format {pattern: 'pattern', name: 'name'} for
-     * matching incoming request URLs and naming the associated New Relic
-     * transactions. Both pattern and name are required. Additional attributes
-     * are ignored. Patterns may have capture groups (following JavaScript
-     * conventions), and names will use $1-style replacement strings. See
-     * the documentation for addNamingRule for important caveats.
+     * Attributes are key-value pairs containing information that determines
+     * the properties of an event or transaction.
      */
-    name: {
-      formatter: objectList,
-      default: [],
-      env: 'NEW_RELIC_NAMING_RULES'
-    },
+    attributes: {
     /**
-     * A list of patterns for matching incoming request URLs to be ignored by
-     * the agent. Patterns may be strings or regular expressions.
-     *
-     * By default, socket.io long-polling is ignored.
-     *
-     * env NEW_RELIC_IGNORING_RULES
+     * If `true`, enables capture of attributes for all destinations.
+     * If there are specific parameters you want ignored, use `attributes.exclude`.
      */
-    ignore: {
-      formatter: array,
-      default: ['^/socket.io/.*/xhr-polling/'],
-      env: 'NEW_RELIC_IGNORING_RULES'
-    }
-  },
-  /**
-   * By default, any transactions that are not affected by other bits of
-   * naming logic (the API, rules, or metric normalization rules) will
-   * have their names set to 'NormalizedUri/*'. Setting this value to
-   * false will set them instead to Uri/path/to/resource. Don't change
-   * this setting unless you understand the implications of New Relic's
-   * metric grouping issues and are confident your application isn't going
-   * to run afoul of them. Your application could end up getting blocked!
-   * Nobody wants that.
-   */
-  enforce_backstop: {
-    formatter: boolean,
-    default: true
-  },
-  /**
-   * Browser Monitoring
-   *
-   * Browser monitoring lets you correlate transactions between the server and browser
-   * giving you accurate data on how long a page request takes, from request,
-   * through the server response, up until the actual page render completes.
-   */
-  browser_monitoring: {
-    attributes: {
-      /**
-       * If `true`, the agent captures attributes from browser monitoring.
-       */
       enabled: {
         formatter: boolean,
-        default: false
+        default: true
       },
+
+      /**
+       * Defines the number of characters allowed for each individual attribute's
+       * value. The default is 256 characters, with a maximum of 4,096.
+       */
+      value_size_limit: {
+        formatter: int,
+        /**
+         * Maximum value is 4,096.
+         */
+        default: 256
+      },
+
       /**
-       * Prefix of attributes to exclude from browser monitoring.
-       * Allows * as wildcard at end.
+       * Prefix of attributes to exclude from all destinations. Allows * as wildcard at end.
+       *
+       * NOTE: If excluding headers, they must be in camelCase form to be filtered.
        */
       exclude: {
         formatter: array,
         default: []
       },
+
       /**
-       * Prefix of attributes to include in browser monitoring.
-       * Allows * as wildcard at end.
+       * Prefix of attributes to include in all destinations. Allows * as wildcard at end.
+       *
+       * NOTE: If including headers, they must be in camelCase form to be filtered.
        */
       include: {
         formatter: array,
         default: []
-      }
-    },
-    /**
-     * Enable browser monitoring header generation.
-     *
-     * This does not auto-instrument, rather it enables the agent to generate headers.
-     * The newrelic module can generate the appropriate <script> header, but you must
-     * inject the header yourself, or use a module that does so.
-     *
-     * Usage:
-     *
-     *     var newrelic = require('newrelic');
-     *
-     *     router.get('/', function (req, res) {
-     *       var header = newrelic.getBrowserTimingHeader();
-     *       res.write(header)
-     *       // write the rest of the page
-     *     });
-     *
-     * This generates the <script>...</script> header necessary for Browser Monitoring
-     * This script must be manually injected into your templates, as high as possible
-     * in the header, but _after_ any X-UA-COMPATIBLE HTTP-EQUIV meta tags.
-     * Otherwise you may hurt IE!
-     *
-     * This method must be called _during_ a transaction, and must be called every
-     * time you want to generate the headers.
-     *
-     * Do *not* reuse the headers between users, or even between requests.
-     */
-    enable: {
-      formatter: boolean,
-      default: true,
-      env: 'NEW_RELIC_BROWSER_MONITOR_ENABLE'
+      },
+
+      /**
+       * If `true`, patterns may be added to the `attributes.include`
+       * list.
+       */
+      include_enabled: {
+        formatter: boolean,
+        default: true
+      },
+
+      /**
+       * Controls how many attribute include/exclude rule results are cached by
+       * the filter. Increasing this limit will cause greater memory usage and is
+       * only necessary if you have an extremely high variety of attributes.
+       */
+      filter_cache_limit: {
+        formatter: int,
+        default: 1000
+      }
     },
+    logging: {
     /**
-     * Request un-minified sources from the server.
-     */
-    debug: {
-      formatter: boolean,
-      default: false,
-      env: 'NEW_RELIC_BROWSER_MONITOR_DEBUG'
-    }
-  },
-  /**
-   * API Configuration
-   *
-   * Some API end points can be turned off via configuration settings to
-   * allow for more flexible security options. All API configuration
-   * options are disabled when high-security mode is enabled.
-   */
-  api: {
-    /**
-     * Controls for the `API.addCustomAttribute` method.
+     * Verbosity of the module's logging. This module uses bunyan
+     * (https://github.com/trentm/node-bunyan) for its logging, and as such the
+     * valid logging levels are 'fatal', 'error', 'warn', 'info', 'debug' and
+     * 'trace'. Logging at levels 'info' and higher is very terse. For support
+     * requests, attaching logs captured at 'trace' level are extremely helpful
+     * in chasing down bugs.
      */
-    custom_attributes_enabled: {
-      formatter: boolean,
-      default: true,
-      env: 'NEW_RELIC_API_CUSTOM_ATTRIBUTES'
+      level: {
+        default: 'info',
+        env: 'NEW_RELIC_LOG_LEVEL'
+      },
+      /**
+       * Where to put the log file -- by default just uses process.cwd +
+       * 'newrelic_agent.log'. A special case is a filepath of 'stdout',
+       * in which case all logging will go to stdout, or 'stderr', in which
+       * case all logging will go to stderr.
+       */
+      filepath: {
+        default: require('path').join(process.cwd(), 'newrelic_agent.log'),
+        env: 'NEW_RELIC_LOG'
+      },
+      /**
+       * Whether to write to a log file at all
+       */
+      enabled: {
+        formatter: boolean,
+        default: true,
+        env: 'NEW_RELIC_LOG_ENABLED'
+      },
+
+      /**
+       * Enables extra debugging at `warn` level. No need to enable except under
+       * specific debugging conditions.
+       */
+      diagnostics: {
+        formatter: boolean,
+        deafult: false
+      }
     },
+    audit_log: {
     /**
-     * Controls for the `API.recordCustomEvent` method.
+     * Enables logging of out bound traffic from the Agent to the Collector.
+     * This field is ignored if trace level logging is enabled.
+     * With trace logging, all traffic is logged.
      */
-    custom_events_enabled: {
-      formatter: boolean,
-      default: true,
-      env: 'NEW_RELIC_API_CUSTOM_EVENTS'
+      enabled: {
+        formatter: boolean,
+        default: false
+      },
+
+      /**
+       * Specify which methods are logged. Used in conjunction with the audit_log flag
+       * If audit_log is enabled and this property is empty, all methods will be logged
+       * Otherwise, if the audit log is enabled, only the methods specified
+       * in the filter will be logged
+       * Methods include: error_data, metric_data, and analytic_event_data
+       */
+      endpoints: {
+        formatter: array,
+        default: []
+      }
     },
     /**
-     * Controls for the `API.noticeError` method.
+     * Whether to collect & submit error traces to New Relic.
      */
-    notice_error_enabled: {
-      formatter: boolean,
-      default: true,
-      env: 'NEW_RELIC_API_NOTICE_ERROR'
-    }
-  },
-  /**
-   * Transaction Events
-   *
-   * Transaction events are sent to New Relic Insights. This event data
-   * includes transaction timing, transaction name, and any custom parameters.
-   *
-   * Read more here: http://newrelic.com/insights
-   */
-  transaction_events: {
-    attributes: {
+    error_collector: {
+      attributes: {
       /**
-       * If `true`, the agent captures attributes from transaction events.
+       * If `true`, the agent captures attributes from error collection.
+       */
+        enabled: {
+          formatter: boolean,
+          default: true
+        },
+        /**
+         * Prefix of attributes to exclude from error collection.
+         * Allows * as wildcard at end.
+         */
+        exclude: {
+          formatter: array,
+          default: []
+        },
+        /**
+         * Prefix of attributes to include in error collection.
+         * Allows * as wildcard at end.
+         */
+        include: {
+          formatter: array,
+          default: []
+        }
+      },
+      /**
+       * Disabling the error tracer just means that errors aren't collected
+       * and sent to New Relic -- it DOES NOT remove any instrumentation.
        */
       enabled: {
         formatter: boolean,
         default: true
       },
       /**
-       * Prefix of attributes to exclude in transaction events.
-       * Allows * as wildcard at end.
+       * List of HTTP error status codes the error tracer should disregard.
+       * Ignoring a status code means that the transaction is not renamed to
+       * match the code, and the request is not treated as an error by the error
+       * collector.
        *
-       * env NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_EXCLUDE
+       * NOTE: This configuration value has no effect on errors recorded using
+       * `noticeError()`.
+       *
+       * Defaults to 404 NOT FOUND.
        */
-      exclude: {
+      ignore_status_codes: {
+        env: 'NEW_RELIC_ERROR_COLLECTOR_IGNORE_ERROR_CODES',
         formatter: array,
-        default: []
+        default: [404]
+      },
+      /**
+       * Whether error events are collected.
+       */
+      capture_events: {
+        formatter: boolean,
+        default: true
       },
       /**
-       * Prefix of attributes to include in transaction events.
-       * Allows * as wildcard at end.
+       * The agent will collect all error events up to this number per minute.
+       * If there are more than that, a statistical sampling will be collected.
+       * Currently this uses a priority sampling algorithm.
        *
-       * env NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_INCLUDE
+       * By increasing this setting you are both increasing the memory
+       * requirements of the agent as well as increasing the payload to the New
+       * Relic servers. The memory concerns are something you should consider for
+       * your own server's sake. The payload of events is compressed, but if it
+       * grows too large the New Relic servers may reject it.
        */
-      include: {
+      max_event_samples_stored: {
+        formatter: int,
+        default: 100
+      },
+
+      expected_classes: {
         formatter: array,
-        default: []
+        default: [],
+        env: 'NEW_RELIC_ERROR_COLLECTOR_EXPECTED_ERRORS'
+      },
+      expected_messages: {
+        formatter: object,
+        default: {}
+      },
+      expected_status_codes: {
+        formatter: array,
+        default: [],
+        env: 'NEW_RELIC_ERROR_COLLECTOR_EXPECTED_ERROR_CODES'
+      },
+      ignore_classes: {
+        formatter: array,
+        default: [],
+        env: 'NEW_RELIC_ERROR_COLLECTOR_IGNORE_ERRORS'
+      },
+      ignore_messages: {
+        formatter: object,
+        default: {}
       }
     },
     /**
-     * If this is disabled, the agent does not collect, nor try to send,
-     * analytic data.
-     */
-    enabled: {
-      formatter: boolean,
-      default: true
-    },
-    /**
-     * The agent will collect all events up to this number per minute. If
-     * there are more than that, a statistical sampling will be collected.
-     */
-    max_samples_stored: {
-      formatter: int,
-      default: 10000
-    }
-  },
-  /**
-   * Custom Insights Events
-   *
-   * Custom insights events are JSON object that are sent to New Relic
-   * Insights. You can tell the agent to send your custom events via the
-   * `newrelic.recordCustomEvent()` API. These events are sampled once the max
-   * queue size is reached. You can tune this setting below.
-   *
-   * Read more here: http://newrelic.com/insights
-   */
-  custom_insights_events: {
-    /**
-     * If this is disabled, the agent does not collect, nor try to send, custom
-     * event data.
-     */
-    enabled: {
-      formatter: boolean,
-      default: true
-    },
-    /**
-     * The agent will collect all events up to this number per minute. If there
-     * are more than that, a statistical sampling will be collected. Currently
-     * this uses a priority sampling algorithm.
+     * Error message redaction
+     *
+     * Options regarding how the agent handles the redaction of error messages.
      *
-     * By increasing this setting you are both increasing the memory
-     * requirements of the agent as well as increasing the payload to the New
-     * Relic servers. The memory concerns are something you should consider for
-     * your own server's sake. The payload of events is compressed, but if it
-     * grows too large the New Relic servers may reject it.
      */
-    max_samples_stored: {
-      formatter: int,
-      default: 3000
-    }
-  },
-  /**
-   * This is used to configure properties about the user's host name.
-   */
-  process_host: {
+    strip_exception_messages: {
     /**
-     * Configurable display name for hosts
+     * When `true`, the agent will redact the messages of captured
+     * errors.
      */
-    display_name: '',
+      enabled: {
+        formatter: boolean,
+        default: false
+      }
+    },
+    cloud: {
+      aws: {
+      /**
+       * The AWS account ID for the AWS account associated with this app.
+       */
+        account_id: {
+          formatter: int,
+          default: null
+        }
+      }
+    },
     /**
-     * ip address preference when creating hostnames
+     * Options regarding collecting system information. Used for system
+     * utilization based pricing scheme.
      */
-    ipv_preference: {
-      formatter: allowList.bind(null, ['4', '6']),
-      default: '4',
-      env: 'NEW_RELIC_IPV_PREFERENCE'
-    }
-  },
-  /**
-   * High Security
-   *
-   * High security mode (v2) is a setting which prevents any sensitive data from
-   * being sent to New Relic. The local setting must match the server setting.
-   * If there is a mismatch the agent will log a message and act as if it is
-   * disabled.
-   *
-   * Attributes of high security mode (when enabled):
-   *  requires SSL
-   *  does not allow capturing of http params
-   *  does not allow custom params
-   *
-   * To read more see: https://docs.newrelic.com/docs/subscriptions/high-security
-   */
-  high_security: {
-    formatter: boolean,
-    default: false
-  },
-
-  /**
-   * Labels
-   *
-   * An object of label names and values that will be applied to the data sent
-   * from this agent. Both label names and label values have a maximum length of
-   * 255 characters. This object should contain at most 64 labels.
-   */
-  labels: {
-    default: {}
-  },
-  /**
-   * These options control behavior for slow queries, but do not affect sql
-   * nodes in transaction traces.
-   */
-  slow_sql: {
+    utilization: {
     /**
-     * Enables and disables `slow_sql` recording.
+     * This flag dictates whether the agent attempts to reach out to AWS
+     * to get info about the vm the process is running on.
      */
-    enabled: {
-      formatter: boolean,
-      default: false
-    },
+      detect_aws: {
+        formatter: boolean,
+        default: true
+      },
+      /**
+       * This flag dictates whether the agent attempts to detect if the
+       * the process is running on Pivotal Cloud Foundry.
+       */
+      detect_pcf: {
+        formatter: boolean,
+        default: true
+      },
+      /**
+       * This flag dictates whether the agent attempts to reach out to Azure to
+       * get info about the vm the process is running on.
+       */
+      detect_azure: {
+        formatter: boolean,
+        default: true
+      },
+      /**
+       * This flag dictates whether the agent attempts to read environment variables
+       * and invocation context to get info about the Azure Function called.
+       */
+      detect_azurefunction: {
+        formatter: boolean,
+        default: true
+      },
+      /**
+       * This flag dictates whether the agent attempts to read files
+       * to get info about the container the process is running in.
+       *
+       * env NEW_RELIC_UTILIZATION_DETECT_DOCKER
+       */
+      detect_docker: {
+        formatter: boolean,
+        default: true
+      },
 
-    /**
-     * Sets the maximum number of slow query samples that will be collected in a
-     * single harvest cycle.
-     *
-     * env NEW_RELIC_MAX_SQL_SAMPLES
-     */
-    max_samples: {
-      formatter: int,
-      default: 10,
-      env: 'NEW_RELIC_MAX_SQL_SAMPLES'
-    }
-  },
-  /**
-   * Controls behavior of datastore instance metrics.
-   *
-   * @property {object} instance_reporting container around enabling flag
-   * @property {boolean} [instance_reporting.enabled=true]
-   *  Enables reporting the host and port/path/id of database servers. Default
-   *  is `true`.
-   * @property {object} database_name_reporting container around enabling flag
-   * @property {boolean} [database_name_reporting.enabled=true]
-   *  Enables reporting of database/schema names. Default is `true`.
-   */
-  datastore_tracer: {
-    instance_reporting: {
-      enabled: {
+      /**
+       * This flag dictates whether the agent attempts to reach out to GCP
+       * to get info about the vm the process is running on.
+       */
+      detect_gcp: {
         formatter: boolean,
+        default: true
+      },
+
+      /**
+       * This flag dictates whether the agent attempts to reach out to
+       * Kubernetes to get info about the container the process is running on.
+       */
+      detect_kubernetes: {
+        formatter: boolean,
+        default: true
+      },
+      logical_processors: {
+        formatter: float,
+        default: null
+      },
+      billing_hostname: {
+        default: null
+      },
+      total_ram_mib: {
+        formatter: int,
+        default: null
+      },
+
+      /**
+       * When enabled, it will use GCP metadata id
+       * to set the hostname of the running application.
+       */
+      gcp_use_instance_as_host: {
         default: true,
-        env: 'NEW_RELIC_DATASTORE_INSTANCE_REPORTING_ENABLED'
+        formatter: boolean
       }
     },
-    database_name_reporting: {
+    transaction_tracer: {
+      attributes: {
+      /**
+       * If `true`, the agent captures attributes from transaction traces.
+       */
+        enabled: {
+          formatter: boolean,
+          default: true
+        },
+        /**
+         * Prefix of attributes to exclude from transaction traces.
+         * Allows * as wildcard at end.
+         */
+        exclude: {
+          formatter: array,
+          default: []
+        },
+        /**
+         * Prefix of attributes to include in transaction traces.
+         * Allows * as wildcard at end.
+         */
+        include: {
+          formatter: array,
+          default: []
+        }
+      },
+      /**
+       * Whether to collect & submit slow transaction traces to New Relic. The
+       * instrumentation is loaded regardless of this setting, as it's necessary
+       * to gather metrics. Disable the agent to prevent the instrumentation from
+       * loading.
+       */
       enabled: {
         formatter: boolean,
         default: true,
-        env: 'NEW_RELIC_DATASTORE_DATABASE_NAME_REPORTING_ENABLED'
+        env: 'NEW_RELIC_TRACER_ENABLED'
+      },
+      /**
+       * Sets the time, in seconds, for a transaction to be considered slow.
+       * When a transaction exceeds this threshold, a transaction trace will be recorded. When set to 'apdex_f', the threshold will be set to
+       * 4 * apdex_t, which with a default apdex_t value of 500 milliseconds will
+       * be 2 seconds.
+       *
+       * If a number is provided, it is set in seconds.
+       */
+      transaction_threshold: {
+        formatter: float,
+        default: 'apdex_f',
+        env: 'NEW_RELIC_TRACER_THRESHOLD'
+      },
+      /**
+       * Increase this parameter to increase the diversity of the slow
+       * transaction traces recorded by your application over time. Confused?
+       * Read on.
+       *
+       * Transactions are named based on the request (see the README for the
+       * details of how requests are mapped to transactions), and top_n refers to
+       * the "top n slowest transactions" grouped by these names. The module will
+       * only replace a recorded trace with a new trace if the new trace is
+       * slower than the previous slowest trace of that name. The default value
+       * for this setting is 20, as the transaction trace view page also defaults
+       * to showing the 20 slowest transactions.
+       *
+       * If you want to record the absolute slowest transaction over the last
+       * minute, set top_n to 0 or 1. This used to be the default, and has a
+       * problem in that it will allow one very slow route to dominate your slow
+       * transaction traces.
+       *
+       * The module will always record at least 5 different slow transactions in
+       * the reporting periods after it starts up, and will reset its internal
+       * slow trace aggregator if no slow transactions have been recorded for the
+       * last 5 harvest cycles, restarting the aggregation process.
+       *
+       * env NEW_RELIC_TRACER_TOP_N
+       */
+      top_n: {
+        formatter: int,
+        default: 20,
+        env: 'NEW_RELIC_TRACER_TOP_N'
+      },
+
+      /**
+       * This option affects both slow-queries and record_sql for transaction
+       * traces.  It can have one of 3 values: 'off', 'obfuscated' or 'raw'
+       * When it is 'off' no slow queries will be captured, and backtraces
+       * and sql will not be included in transaction traces.  If it is 'raw'
+       * or 'obfuscated' and other criteria (slow_sql.enabled etc) are met
+       * for a query. The raw or obfuscated sql will be included in the
+       * transaction trace and a slow query sample will be collected.
+       */
+      record_sql: {
+        formatter: allowList.bind(null, ['off', 'obfuscated', 'raw']),
+        default: 'obfuscated',
+        env: 'NEW_RELIC_RECORD_SQL'
+      },
+
+      /**
+       * This option affects both slow-queries and record_sql for transaction
+       * traces.  This is the minimum duration a query must take (in ms) for it
+       * to be considered for for slow query and inclusion in transaction traces.
+       */
+      explain_threshold: {
+        formatter: int,
+        default: 500,
+        env: 'NEW_RELIC_EXPLAIN_THRESHOLD'
       }
-    }
-  },
-  /**
-   * Controls behavior of gRPC server instrumentation.
-   */
-  grpc: {
+    },
     /**
-     * Enables recording of non-zero gRPC status codes. Default is `true`.
+     * Rules for naming or ignoring transactions.
+     */
+    rules: {
+    /**
+     * A list of rules of the format {pattern: 'pattern', name: 'name'} for
+     * matching incoming request URLs and naming the associated New Relic
+     * transactions. Both pattern and name are required. Additional attributes
+     * are ignored. Patterns may have capture groups (following JavaScript
+     * conventions), and names will use $1-style replacement strings. See
+     * the documentation for addNamingRule for important caveats.
+     */
+      name: {
+        formatter: objectList,
+        default: [],
+        env: 'NEW_RELIC_NAMING_RULES'
+      },
+      /**
+       * A list of patterns for matching incoming request URLs to be ignored by
+       * the agent. Patterns may be strings or regular expressions.
+       *
+       * By default, socket.io long-polling is ignored.
+       *
+       * env NEW_RELIC_IGNORING_RULES
+       */
+      ignore: {
+        formatter: array,
+        default: ['^/socket.io/.*/xhr-polling/'],
+        env: 'NEW_RELIC_IGNORING_RULES'
+      }
+    },
+    /**
+     * By default, any transactions that are not affected by other bits of
+     * naming logic (the API, rules, or metric normalization rules) will
+     * have their names set to 'NormalizedUri/*'. Setting this value to
+     * false will set them instead to Uri/path/to/resource. Don't change
+     * this setting unless you understand the implications of New Relic's
+     * metric grouping issues and are confident your application isn't going
+     * to run afoul of them. Your application could end up getting blocked!
+     * Nobody wants that.
      */
-    record_errors: {
+    enforce_backstop: {
       formatter: boolean,
       default: true
     },
     /**
-     * List of gRPC error status codes the error tracer should disregard.
-     * Ignoring a status code means that the transaction is not renamed to
-     * match the code, and the request is not treated as an error by the error
-     * collector.
+     * Browser Monitoring
      *
-     * NOTE: This configuration value has no effect on errors recorded using
-     * `noticeError()`.
+     * Browser monitoring lets you correlate transactions between the server and browser
+     * giving you accurate data on how long a page request takes, from request,
+     * through the server response, up until the actual page render completes.
+     */
+    browser_monitoring: {
+      attributes: {
+      /**
+       * If `true`, the agent captures attributes from browser monitoring.
+       */
+        enabled: {
+          formatter: boolean,
+          default: false
+        },
+        /**
+         * Prefix of attributes to exclude from browser monitoring.
+         * Allows * as wildcard at end.
+         */
+        exclude: {
+          formatter: array,
+          default: []
+        },
+        /**
+         * Prefix of attributes to include in browser monitoring.
+         * Allows * as wildcard at end.
+         */
+        include: {
+          formatter: array,
+          default: []
+        }
+      },
+      /**
+       * Enable browser monitoring header generation.
+       *
+       * This does not auto-instrument, rather it enables the agent to generate headers.
+       * The newrelic module can generate the appropriate <script> header, but you must
+       * inject the header yourself, or use a module that does so.
+       *
+       * Usage:
+       *
+       *     var newrelic = require('newrelic');
+       *
+       *     router.get('/', function (req, res) {
+       *       var header = newrelic.getBrowserTimingHeader();
+       *       res.write(header)
+       *       // write the rest of the page
+       *     });
+       *
+       * This generates the <script>...</script> header necessary for Browser Monitoring
+       * This script must be manually injected into your templates, as high as possible
+       * in the header, but _after_ any X-UA-COMPATIBLE HTTP-EQUIV meta tags.
+       * Otherwise you may hurt IE!
+       *
+       * This method must be called _during_ a transaction, and must be called every
+       * time you want to generate the headers.
+       *
+       * Do *not* reuse the headers between users, or even between requests.
+       */
+      enable: {
+        formatter: boolean,
+        default: true,
+        env: 'NEW_RELIC_BROWSER_MONITOR_ENABLE'
+      },
+      /**
+       * Request un-minified sources from the server.
+       */
+      debug: {
+        formatter: boolean,
+        default: false,
+        env: 'NEW_RELIC_BROWSER_MONITOR_DEBUG'
+      }
+    },
+    /**
+     * API Configuration
      *
-     * Defaults to no codes ignored.
+     * Some API end points can be turned off via configuration settings to
+     * allow for more flexible security options. All API configuration
+     * options are disabled when high-security mode is enabled.
      */
-    ignore_status_codes: {
-      formatter: array,
-      default: []
-    }
-  },
-  /**
-   * Controls the behavior of span events produced by the agent.
-   */
-  span_events: {
+    api: {
     /**
-     * Enables/disables span event generation
+     * Controls for the `API.addCustomAttribute` method.
      */
-    enabled: {
-      formatter: boolean,
-      default: true
-    },
-
-    attributes: {
+      custom_attributes_enabled: {
+        formatter: boolean,
+        default: true,
+        env: 'NEW_RELIC_API_CUSTOM_ATTRIBUTES'
+      },
       /**
-       * If `true`, the agent captures attributes from span events.
+       * Controls for the `API.recordCustomEvent` method.
        */
-      enabled: {
+      custom_events_enabled: {
         formatter: boolean,
-        default: true
+        default: true,
+        env: 'NEW_RELIC_API_CUSTOM_EVENTS'
       },
       /**
-       * Prefix of attributes to exclude in span events.
-       * Allows * as wildcard at end.
+       * Controls for the `API.noticeError` method.
        */
-      exclude: {
-        formatter: array,
-        default: []
+      notice_error_enabled: {
+        formatter: boolean,
+        default: true,
+        env: 'NEW_RELIC_API_NOTICE_ERROR'
+      }
+    },
+    /**
+     * Transaction Events
+     *
+     * Transaction events are sent to New Relic Insights. This event data
+     * includes transaction timing, transaction name, and any custom parameters.
+     *
+     * Read more here: http://newrelic.com/insights
+     */
+    transaction_events: {
+      attributes: {
+      /**
+       * If `true`, the agent captures attributes from transaction events.
+       */
+        enabled: {
+          formatter: boolean,
+          default: true
+        },
+        /**
+         * Prefix of attributes to exclude in transaction events.
+         * Allows * as wildcard at end.
+         *
+         * env NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_EXCLUDE
+         */
+        exclude: {
+          formatter: array,
+          default: []
+        },
+        /**
+         * Prefix of attributes to include in transaction events.
+         * Allows * as wildcard at end.
+         *
+         * env NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_INCLUDE
+         */
+        include: {
+          formatter: array,
+          default: []
+        }
+      },
+      /**
+       * If this is disabled, the agent does not collect, nor try to send,
+       * analytic data.
+       */
+      enabled: {
+        formatter: boolean,
+        default: true
       },
       /**
-       * Prefix of attributes to include in span events.
-       * Allows * as wildcard at end.
+       * The agent will collect all events up to this number per minute. If
+       * there are more than that, a statistical sampling will be collected.
        */
-      include: {
-        formatter: array,
-        default: []
+      max_samples_stored: {
+        formatter: int,
+        default: 10000
       }
     },
     /**
-     * The agent will collect all events up to this number per minute. If
-     * there are more than that, a statistical sampling will be collected.
+     * Custom Insights Events
+     *
+     * Custom insights events are JSON object that are sent to New Relic
+     * Insights. You can tell the agent to send your custom events via the
+     * `newrelic.recordCustomEvent()` API. These events are sampled once the max
+     * queue size is reached. You can tune this setting below.
+     *
+     * Read more here: http://newrelic.com/insights
+     */
+    custom_insights_events: {
+    /**
+     * If this is disabled, the agent does not collect, nor try to send, custom
+     * event data.
      */
-    max_samples_stored: {
-      formatter: int,
-      default: 2000
-    }
-  },
-  /**
-   * Controls the behavior of transaction segments produced by the agent.
-   */
-  transaction_segments: {
-    attributes: {
-      /**
-       * If `true`, the agent captures attributes from transaction segments.
-       */
       enabled: {
         formatter: boolean,
         default: true
       },
       /**
-       * Prefix of attributes to exclude in transaction segments.
-       * Allows * as wildcard at end.
+       * The agent will collect all events up to this number per minute. If there
+       * are more than that, a statistical sampling will be collected. Currently
+       * this uses a priority sampling algorithm.
+       *
+       * By increasing this setting you are both increasing the memory
+       * requirements of the agent as well as increasing the payload to the New
+       * Relic servers. The memory concerns are something you should consider for
+       * your own server's sake. The payload of events is compressed, but if it
+       * grows too large the New Relic servers may reject it.
        */
-      exclude: {
-        formatter: array,
-        default: []
-      },
+      max_samples_stored: {
+        formatter: int,
+        default: 3000
+      }
+    },
+    /**
+     * This is used to configure properties about the user's host name.
+     */
+    process_host: {
+    /**
+     * Configurable display name for hosts
+     */
+      display_name: '',
       /**
-       * Prefix of attributes to include in transaction segments.
-       * Allows * as wildcard at end.
+       * ip address preference when creating hostnames
        */
-      include: {
-        formatter: array,
-        default: []
+      ipv_preference: {
+        formatter: allowList.bind(null, ['4', '6']),
+        default: '4',
+        env: 'NEW_RELIC_IPV_PREFERENCE'
       }
-    }
-  },
-
-  /**
-   * Controls the method of cross agent tracing in the agent.
-   * Distributed tracing lets you see the path that a request takes through your
-   * distributed system. Enabling distributed tracing changes the behavior of some
-   * New Relic features, so carefully consult the transition guide before you enable
-   * this feature: https://docs.newrelic.com/docs/transition-guide-distributed-tracing
-   * Default is true.
-   */
-  distributed_tracing: {
+    },
     /**
-     * Enables/disables distributed tracing.
+     * High Security
+     *
+     * High security mode (v2) is a setting which prevents any sensitive data from
+     * being sent to New Relic. The local setting must match the server setting.
+     * If there is a mismatch the agent will log a message and act as if it is
+     * disabled.
+     *
+     * Attributes of high security mode (when enabled):
+     *  requires SSL
+     *  does not allow capturing of http params
+     *  does not allow custom params
+     *
+     * To read more see: https://docs.newrelic.com/docs/subscriptions/high-security
      */
-    enabled: {
+    high_security: {
       formatter: boolean,
-      default: true
+      default: false
     },
 
     /**
-     * Excludes New Relic format distributed tracing header (`newrelic`) on
-     * outbound requests when set to `true`. By default (when false)
-     * both W3C TraceContext (`traceparent`, `tracecontext`) and
-     * New Relic formats will be sent.
+     * Labels
+     *
+     * An object of label names and values that will be applied to the data sent
+     * from this agent. Both label names and label values have a maximum length of
+     * 255 characters. This object should contain at most 64 labels.
      */
-    exclude_newrelic_header: {
-      formatter: boolean,
-      default: false
+    labels: {
+      default: {}
     },
-
     /**
-     * Controls whether the agent will generate spans for in-process actions.
-     * When disabled, this will only create spans for entry and exit spans.
-     * entry spans - initial actions for web servers and messsage queue consumption.
-     * exit spans - all outgoing calls to external services(external and database calls)
+     * These options control behavior for slow queries, but do not affect sql
+     * nodes in transaction traces.
+     */
+    slow_sql: {
+    /**
+     * Enables and disables `slow_sql` recording.
      */
-    in_process_spans: {
       enabled: {
         formatter: boolean,
-        default: true
-      }
-    },
+        default: false
+      },
 
-    sampler: {
       /**
-       * When set to `always_on`, the sampled flag in the `traceparent` header
-       * being set to "true" will result in the local transaction being sampled
-       * with a priority value of "2". When set to `always_off`, the local
-       * transaction will never be sampled. At the default setting, the sampling
-       * decision will be determined according to the normal algorithm.
+       * Sets the maximum number of slow query samples that will be collected in a
+       * single harvest cycle.
        *
-       * This setting takes precedence over the `remote_parent_not_sampled`
-       * setting.
+       * env NEW_RELIC_MAX_SQL_SAMPLES
        */
-      remote_parent_sampled: {
-        formatter: allowList.bind(null, ['always_on', 'always_off', 'default']),
-        default: 'default'
+      max_samples: {
+        formatter: int,
+        default: 10,
+        env: 'NEW_RELIC_MAX_SQL_SAMPLES'
+      }
+    },
+    /**
+     * Controls behavior of datastore instance metrics.
+     *
+     * @property {object} instance_reporting container around enabling flag
+     * @property {boolean} [instance_reporting.enabled=true]
+     *  Enables reporting the host and port/path/id of database servers. Default
+     *  is `true`.
+     * @property {object} database_name_reporting container around enabling flag
+     * @property {boolean} [database_name_reporting.enabled=true]
+     *  Enables reporting of database/schema names. Default is `true`.
+     */
+    datastore_tracer: {
+      instance_reporting: {
+        enabled: {
+          formatter: boolean,
+          default: true,
+          env: 'NEW_RELIC_DATASTORE_INSTANCE_REPORTING_ENABLED'
+        }
+      },
+      database_name_reporting: {
+        enabled: {
+          formatter: boolean,
+          default: true,
+          env: 'NEW_RELIC_DATASTORE_DATABASE_NAME_REPORTING_ENABLED'
+        }
+      }
+    },
+    /**
+     * Controls behavior of gRPC server instrumentation.
+     */
+    grpc: {
+    /**
+     * Enables recording of non-zero gRPC status codes. Default is `true`.
+     */
+      record_errors: {
+        formatter: boolean,
+        default: true
       },
-
       /**
-       * When set to `always_on`, the local transaction will be sampled with a
-       * priority of "2".
-       * When set to `always_off`, the local transaction will never be sampled.
-       * At the default setting, the sampling decision will be determined
-       * according to the normal algorithm.
+       * List of gRPC error status codes the error tracer should disregard.
+       * Ignoring a status code means that the transaction is not renamed to
+       * match the code, and the request is not treated as an error by the error
+       * collector.
        *
-       * This setting only affects decisions when the traceparent sampled flag
-       * is set to 0.
+       * NOTE: This configuration value has no effect on errors recorded using
+       * `noticeError()`.
+       *
+       * Defaults to no codes ignored.
        */
-      remote_parent_not_sampled: {
-        formatter: allowList.bind(null, ['always_on', 'always_off', 'default']),
-        default: 'default'
+      ignore_status_codes: {
+        formatter: array,
+        default: []
       }
-    }
-  },
-
-  /**
-   * Controls the use of cross-application tracing.
-   *
-   * @property {boolean} [enabled=false]
-   * Enables tracing transactions across multiple applications. Default is `false`.
-   * This feature has been deprecated in favor of Distributed Tracing (DT).
-   * To fully enable this feature, you must also disable DT in your configuration.
-   */
-  cross_application_tracer: {
-    enabled: {
-      formatter: boolean,
-      default: false
-    }
-  },
-  /**
-   * Controls behavior of message broker tracing.
-   *
-   * @property {object} segment_parameters property around enabling flag
-   * @property {boolean} [segment_parameters.enabled=true]
-   *  Enables reporting parameters on message broker segments.
-   */
-  message_tracer: {
-    segment_parameters: {
+    },
+    /**
+     * Controls the behavior of span events produced by the agent.
+     */
+    span_events: {
+    /**
+     * Enables/disables span event generation
+     */
       enabled: {
         formatter: boolean,
         default: true
-      }
-    }
-  },
-  /**
-   * Controls the use of infinite tracing.
-   */
-  infinite_tracing: {
-    trace_observer: {
-      /**
-       * The URI HOST of the observer.  Setting this enables infinite tracing.
-       */
-      host: '',
-      /**
-       * The URI PORT of the observer.
-       */
-      port: {
-        formatter: int,
-        default: 443
       },
+
+      attributes: {
       /**
-       * For testing only. This allows the connection to an insecure gRPC server.
+       * If `true`, the agent captures attributes from span events.
        */
-      insecure: {
-        formatter: boolean,
-        default: false
+        enabled: {
+          formatter: boolean,
+          default: true
+        },
+        /**
+         * Prefix of attributes to exclude in span events.
+         * Allows * as wildcard at end.
+         */
+        exclude: {
+          formatter: array,
+          default: []
+        },
+        /**
+         * Prefix of attributes to include in span events.
+         * Allows * as wildcard at end.
+         */
+        include: {
+          formatter: array,
+          default: []
+        }
       },
-    },
-    span_events: {
       /**
-       * The amount of spans to hold onto before dropping them
+       * The agent will collect all events up to this number per minute. If
+       * there are more than that, a statistical sampling will be collected.
        */
-      queue_size: {
+      max_samples_stored: {
         formatter: int,
-        default: 10000
-      },
+        default: 2000
+      }
+    },
+    /**
+     * Controls the behavior of transaction segments produced by the agent.
+     */
+    transaction_segments: {
+      attributes: {
       /**
-       * Size of batches to post to 8T server
+       * If `true`, the agent captures attributes from transaction segments.
        */
-      batch_size: {
-        formatter: int,
-        default: 750
+        enabled: {
+          formatter: boolean,
+          default: true
+        },
+        /**
+         * Prefix of attributes to exclude in transaction segments.
+         * Allows * as wildcard at end.
+         */
+        exclude: {
+          formatter: array,
+          default: []
+        },
+        /**
+         * Prefix of attributes to include in transaction segments.
+         * Allows * as wildcard at end.
+         */
+        include: {
+          formatter: array,
+          default: []
+        }
       }
     },
-    batching: {
-      formatter: boolean,
-      default: true
-    },
-    compression: {
-      formatter: boolean,
-      default: true
-    }
-  },
-
-  /**
-   * When `true`, the AWS Lambda instrumentation will add the necessary
-   * data to support the new (as of 2025) unified APM UI.
-   */
-  apm_lambda_mode: {
-    default: false,
-    formatter: boolean
-  },
-
-  /**
-   * Specifies whether the agent will be used to monitor serverless functions.
-   * For example: AWS Lambda
-   */
-  serverless_mode: {
-    enabled: {
-      formatter: boolean,
-      default: process.env.AWS_LAMBDA_FUNCTION_NAME != null
-    }
-  },
-  plugins: {
+
     /**
-     * Controls usage of the native metrics module which samples VM and event
-     * loop data.
+     * Controls the method of cross agent tracing in the agent.
+     * Distributed tracing lets you see the path that a request takes through your
+     * distributed system. Enabling distributed tracing changes the behavior of some
+     * New Relic features, so carefully consult the transition guide before you enable
+     * this feature: https://docs.newrelic.com/docs/transition-guide-distributed-tracing
+     * Default is true.
      */
-    native_metrics: {
-      enabled: {
-        formatter: boolean,
-        default: true,
-        env: 'NEW_RELIC_NATIVE_METRICS_ENABLED'
-      }
-    }
-  },
-  /**
-   *
-   * Controls the behavior of Logs in Context within agent
-   */
-  application_logging: {
+    distributed_tracing: {
     /**
-     * Toggles the ability for all application logging features to be enabled.
+     * Enables/disables distributed tracing.
      */
-    enabled: {
-      formatter: boolean,
-      default: true
-    },
-    forwarding: {
-      /**
-       * Toggles whether the agent gathers log records for sending to New Relic.
-       */
       enabled: {
         formatter: boolean,
         default: true
       },
+
       /**
-       * Number of log records to send per minute to New Relic.
+       * Excludes New Relic format distributed tracing header (`newrelic`) on
+       * outbound requests when set to `true`. By default (when false)
+       * both W3C TraceContext (`traceparent`, `tracecontext`) and
+       * New Relic formats will be sent.
        */
-      max_samples_stored: {
-        formatter: int,
-        default: 10000
+      exclude_newrelic_header: {
+        formatter: boolean,
+        default: false
       },
-      labels: {
-        /**
-         * If `true`, the agent attaches labels to log records.
-         */
+
+      /**
+       * Controls whether the agent will generate spans for in-process actions.
+       * When disabled, this will only create spans for entry and exit spans.
+       * entry spans - initial actions for web servers and messsage queue consumption.
+       * exit spans - all outgoing calls to external services(external and database calls)
+       */
+      in_process_spans: {
         enabled: {
           formatter: boolean,
-          default: false
+          default: true
+        }
+      },
+
+      sampler: {
+      /**
+       * When set to `always_on`, the sampled flag in the `traceparent` header
+       * being set to "true" will result in the local transaction being sampled
+       * with a priority value of "2". When set to `always_off`, the local
+       * transaction will never be sampled. At the default setting, the sampling
+       * decision will be determined according to the normal algorithm.
+       *
+       * This setting takes precedence over the `remote_parent_not_sampled`
+       * setting.
+       */
+        remote_parent_sampled: {
+          formatter: allowList.bind(null, ['always_on', 'always_off', 'default']),
+          default: 'default'
         },
+
         /**
-         * A case-insensitive array containing the labels to exclude from log records.
+         * When set to `always_on`, the local transaction will be sampled with a
+         * priority of "2".
+         * When set to `always_off`, the local transaction will never be sampled.
+         * At the default setting, the sampling decision will be determined
+         * according to the normal algorithm.
+         *
+         * This setting only affects decisions when the traceparent sampled flag
+         * is set to 0.
          */
-        exclude: {
-          formatter: array,
-          default: []
+        remote_parent_not_sampled: {
+          formatter: allowList.bind(null, ['always_on', 'always_off', 'default']),
+          default: 'default'
         }
       }
     },
-    metrics: {
-      /**
-       * Toggles whether the agent gathers logging metrics.
-       */
-      enabled: {
-        formatter: boolean,
-        default: true
-      }
-    },
-    local_decorating: {
-      /**
-       * Toggles whether the agent performs log decoration on standard log output.
-       */
+
+    /**
+     * Controls the use of cross-application tracing.
+     *
+     * @property {boolean} [enabled=false]
+     * Enables tracing transactions across multiple applications. Default is `false`.
+     * This feature has been deprecated in favor of Distributed Tracing (DT).
+     * To fully enable this feature, you must also disable DT in your configuration.
+     */
+    cross_application_tracer: {
       enabled: {
         formatter: boolean,
         default: false
       }
-    }
-  },
-  /**
-   * You may want more control over how your agent is configured and want to
-   * disallow the use of New Relic's server-side configuration for agents.
-   * To do so, set this to true.
-   *
-   * env NEW_RELIC_IGNORE_SERVER_SIDE_CONFIG
-   */
-  ignore_server_configuration: {
-    formatter: boolean,
-    default: false,
-    env: 'NEW_RELIC_IGNORE_SERVER_SIDE_CONFIG'
-  },
-
-  /**
-   * Toggles whether to capture code.* attributes on spans
-   */
-  code_level_metrics: {
-    enabled: {
-      formatter: boolean,
-      default: true
-    }
-  },
-
-  /**
-   * Obfuscates URL parameters
-   * for outgoing and incoming requests
-   * for distrubuted tracing attributes - both transaction and span attributes
-   * for transaction trace transaction details
-   */
-  url_obfuscation: {
+    },
     /**
-     * Toggles whether to obfuscate URL parameters
+     * Controls behavior of message broker tracing.
+     *
+     * @property {object} segment_parameters property around enabling flag
+     * @property {boolean} [segment_parameters.enabled=true]
+     *  Enables reporting parameters on message broker segments.
      */
-    enabled: {
-      formatter: boolean,
-      default: false
+    message_tracer: {
+      segment_parameters: {
+        enabled: {
+          formatter: boolean,
+          default: true
+        }
+      }
     },
-
-    regex: {
+    /**
+     * Controls the use of infinite tracing.
+     */
+    infinite_tracing: {
+      trace_observer: {
       /**
-       * A regular expression to match URL parameters to obfuscate
+       * The URI HOST of the observer.  Setting this enables infinite tracing.
        */
-      pattern: {
-        formatter: regex,
-        default: null
+        host: '',
+        /**
+         * The URI PORT of the observer.
+         */
+        port: {
+          formatter: int,
+          default: 443
+        },
+        /**
+         * For testing only. This allows the connection to an insecure gRPC server.
+         */
+        insecure: {
+          formatter: boolean,
+          default: false
+        },
       },
-
+      span_events: {
       /**
-       * A string containing RegEx flags to use when matching URL parameters
+       * The amount of spans to hold onto before dropping them
        */
-      flags: {
-        default: ''
+        queue_size: {
+          formatter: int,
+          default: 10000
+        },
+        /**
+         * Size of batches to post to 8T server
+         */
+        batch_size: {
+          formatter: int,
+          default: 750
+        }
       },
-
-      /**
-       * A string containing a replacement value for URL parameters
-       * can contain refferences to capture groups in the pattern
-       */
-      replacement: {
-        default: ''
+      batching: {
+        formatter: boolean,
+        default: true
+      },
+      compression: {
+        formatter: boolean,
+        default: true
       }
-    }
-  },
-  /**
-   * Security agent configurations
-   */
-  security: {
+    },
+
     /**
-     * Toggles the generation of security events by the security agent.
+     * When `true`, the AWS Lambda instrumentation will add the necessary
+     * data to support the new (as of 2025) unified APM UI.
      */
-    enabled: {
-      formatter: boolean,
-      default: false
+    apm_lambda_mode: {
+      default: false,
+      formatter: boolean
     },
 
     /**
-     * Flag to tell the Node.js agent to load the security agent.
-     * This property is read only once at application start.
+     * Specifies whether the agent will be used to monitor serverless functions.
+     * For example: AWS Lambda
      */
-    agent: {
+    serverless_mode: {
       enabled: {
         formatter: boolean,
-        default: false
+        default: process.env.AWS_LAMBDA_FUNCTION_NAME != null
       }
     },
-
+    plugins: {
     /**
-     *  Security agent provides two modes: IAST and RASP. Default is IAST.
+     * Controls usage of the native metrics module which samples VM and event
+     * loop data.
      */
-    mode: {
-      formatter: allowList.bind(null, ['IAST', 'RASP']),
-      default: 'IAST'
+      native_metrics: {
+        enabled: {
+          formatter: boolean,
+          default: true,
+          env: 'NEW_RELIC_NATIVE_METRICS_ENABLED'
+        }
+      }
     },
-
     /**
-     * Security agent validator URL. Must be prefixed with wss://.
+     *
+     * Controls the behavior of Logs in Context within agent
      */
-    validator_service_url: {
-      default: 'wss://csec.nr-data.net'
-    },
-
+    application_logging: {
     /**
-     * Provide ability to toggle sending security events for the following rules.
+     * Toggles the ability for all application logging features to be enabled.
      */
-    detection: {
-      rci: {
+      enabled: {
+        formatter: boolean,
+        default: true
+      },
+      forwarding: {
+      /**
+       * Toggles whether the agent gathers log records for sending to New Relic.
+       */
         enabled: {
           formatter: boolean,
           default: true
+        },
+        /**
+         * Number of log records to send per minute to New Relic.
+         */
+        max_samples_stored: {
+          formatter: int,
+          default: 10000
+        },
+        labels: {
+        /**
+         * If `true`, the agent attaches labels to log records.
+         */
+          enabled: {
+            formatter: boolean,
+            default: false
+          },
+          /**
+           * A case-insensitive array containing the labels to exclude from log records.
+           */
+          exclude: {
+            formatter: array,
+            default: []
+          }
         }
       },
-      rxss: {
+      metrics: {
+      /**
+       * Toggles whether the agent gathers logging metrics.
+       */
         enabled: {
           formatter: boolean,
           default: true
         }
       },
-      deserialization: {
+      local_decorating: {
+      /**
+       * Toggles whether the agent performs log decoration on standard log output.
+       */
         enabled: {
           formatter: boolean,
-          default: true
+          default: false
         }
       }
     },
+    /**
+     * You may want more control over how your agent is configured and want to
+     * disallow the use of New Relic's server-side configuration for agents.
+     * To do so, set this to true.
+     *
+     * env NEW_RELIC_IGNORE_SERVER_SIDE_CONFIG
+     */
+    ignore_server_configuration: {
+      formatter: boolean,
+      default: false,
+      env: 'NEW_RELIC_IGNORE_SERVER_SIDE_CONFIG'
+    },
 
     /**
-     * Unique test identifier when runnning IAST with CI/CD
+     * Toggles whether to capture code.* attributes on spans
      */
-    iast_test_identifier: '',
+    code_level_metrics: {
+      enabled: {
+        formatter: boolean,
+        default: true
+      }
+    },
 
     /**
-     * IAST scan controllers to get more control over IAST analysis
+     * Obfuscates URL parameters
+     * for outgoing and incoming requests
+     * for distrubuted tracing attributes - both transaction and span attributes
+     * for transaction trace transaction details
      */
-    scan_controllers: {
-      /**
-       * The maximum number of analysis probes or requests
-       * that can be sent to the application in one minute.
-       */
-      iast_scan_request_rate_limit: {
-        formatter: int,
-        default: 3600
+    url_obfuscation: {
+    /**
+     * Toggles whether to obfuscate URL parameters
+     */
+      enabled: {
+        formatter: boolean,
+        default: false
       },
+
+      regex: {
       /**
-       * The number of application instances for a specific entity where IAST analysis is performed.
-       *  Values are 0 or 1, 0 signifies run on all application instances
+       * A regular expression to match URL parameters to obfuscate
        */
-      scan_instance_count: {
-        formatter: int,
-        default: 0
+        pattern: {
+          formatter: regex,
+          default: null
+        },
+
+        /**
+         * A string containing RegEx flags to use when matching URL parameters
+         */
+        flags: {
+          default: ''
+        },
+
+        /**
+         * A string containing a replacement value for URL parameters
+         * can contain refferences to capture groups in the pattern
+         */
+        replacement: {
+          default: ''
+        }
       }
     },
     /**
-     * Schedule start and stop of IAST scan
+     * Security agent configurations
      */
-    scan_schedule: {
+    security: {
+    /**
+     * Toggles the generation of security events by the security agent.
+     */
+      enabled: {
+        formatter: boolean,
+        default: false
+      },
+
       /**
-       * The delay field specifies the time in minutes
-       * before an IAST scan begins after the application starts
+       * Flag to tell the Node.js agent to load the security agent.
+       * This property is read only once at application start.
        */
-      delay: {
-        formatter: int,
-        default: 0
+      agent: {
+        enabled: {
+          formatter: boolean,
+          default: false
+        }
       },
+
       /**
-       * The duration field specifies the amount of
-       * time in minutes that the IAST scan will run
+       *  Security agent provides two modes: IAST and RASP. Default is IAST.
        */
-      duration: {
-        formatter: int,
-        default: 0
+      mode: {
+        formatter: allowList.bind(null, ['IAST', 'RASP']),
+        default: 'IAST'
       },
+
       /**
-       * The schedule field specifies a unix cron expression that defines when the IAST scan should run.
-       * By default, schedule is disabled
-       *
+       * Security agent validator URL. Must be prefixed with wss://.
        */
-      schedule: '',
+      validator_service_url: {
+        default: 'wss://csec.nr-data.net'
+      },
+
       /**
-       * Allows IAST to actively collect trace data in the background
-       * and the security agent will use this collected data to perform
-       * an IAST scan at the scheduled time
+       * Provide ability to toggle sending security events for the following rules.
        */
-      always_sample_traces: {
-        formatter: boolean,
-        default: false
-      }
-    },
+      detection: {
+        rci: {
+          enabled: {
+            formatter: boolean,
+            default: true
+          }
+        },
+        rxss: {
+          enabled: {
+            formatter: boolean,
+            default: true
+          }
+        },
+        deserialization: {
+          enabled: {
+            formatter: boolean,
+            default: true
+          }
+        }
+      },
 
-    /**
-     * The exclude from IAST scan setting allows to exclude specific APIs,
-     * vulnerability categories, and parameters from IAST analysis.
-     */
-    exclude_from_iast_scan: {
       /**
-       * Ignore specific APIs from IAST analysis.
-       * The regex pattern should provide a full match for the URL without the endpoint.
+       * Unique test identifier when runnning IAST with CI/CD
        */
-      api: {
-        formatter: array,
-        default: []
-      },
+      iast_test_identifier: '',
+
       /**
-       * Ignore specific HTTP request parameters from IAST analysis.
+       * IAST scan controllers to get more control over IAST analysis
        */
-      http_request_parameters: {
-        header: {
-          formatter: array,
-          default: []
-        },
-        query: {
-          formatter: array,
-          default: []
+      scan_controllers: {
+      /**
+       * The maximum number of analysis probes or requests
+       * that can be sent to the application in one minute.
+       */
+        iast_scan_request_rate_limit: {
+          formatter: int,
+          default: 3600
         },
-        body: {
-          formatter: array,
-          default: []
+        /**
+         * The number of application instances for a specific entity where IAST analysis is performed.
+         *  Values are 0 or 1, 0 signifies run on all application instances
+         */
+        scan_instance_count: {
+          formatter: int,
+          default: 0
         }
       },
       /**
-       *  Allows users to specify categories of vulnerabilities
-       *  for which IAST analysis will be applied or ignored.
+       * Schedule start and stop of IAST scan
        */
-      iast_detection_category: {
-        insecure_settings: {
-          formatter: boolean,
-          default: false
-        },
-        invalid_file_access: {
-          formatter: boolean,
-          default: false
-        },
-        sql_injection: {
-          formatter: boolean,
-          default: false
-        },
-        nosql_injection: {
-          formatter: boolean,
-          default: false
-        },
-        ldap_injection: {
-          formatter: boolean,
-          default: false
-        },
-        javascript_injection: {
-          formatter: boolean,
-          default: false
+      scan_schedule: {
+      /**
+       * The delay field specifies the time in minutes
+       * before an IAST scan begins after the application starts
+       */
+        delay: {
+          formatter: int,
+          default: 0
         },
-        command_injection: {
-          formatter: boolean,
-          default: false
+        /**
+         * The duration field specifies the amount of
+         * time in minutes that the IAST scan will run
+         */
+        duration: {
+          formatter: int,
+          default: 0
         },
-        xpath_injection: {
+        /**
+         * The schedule field specifies a unix cron expression that defines when the IAST scan should run.
+         * By default, schedule is disabled
+         *
+         */
+        schedule: '',
+        /**
+         * Allows IAST to actively collect trace data in the background
+         * and the security agent will use this collected data to perform
+         * an IAST scan at the scheduled time
+         */
+        always_sample_traces: {
           formatter: boolean,
           default: false
+        }
+      },
+
+      /**
+       * The exclude from IAST scan setting allows to exclude specific APIs,
+       * vulnerability categories, and parameters from IAST analysis.
+       */
+      exclude_from_iast_scan: {
+      /**
+       * Ignore specific APIs from IAST analysis.
+       * The regex pattern should provide a full match for the URL without the endpoint.
+       */
+        api: {
+          formatter: array,
+          default: []
         },
-        ssrf: {
-          formatter: boolean,
-          default: false
+        /**
+         * Ignore specific HTTP request parameters from IAST analysis.
+         */
+        http_request_parameters: {
+          header: {
+            formatter: array,
+            default: []
+          },
+          query: {
+            formatter: array,
+            default: []
+          },
+          body: {
+            formatter: array,
+            default: []
+          }
         },
-        rxss: {
-          formatter: boolean,
-          default: false
+        /**
+         *  Allows users to specify categories of vulnerabilities
+         *  for which IAST analysis will be applied or ignored.
+         */
+        iast_detection_category: {
+          insecure_settings: {
+            formatter: boolean,
+            default: false
+          },
+          invalid_file_access: {
+            formatter: boolean,
+            default: false
+          },
+          sql_injection: {
+            formatter: boolean,
+            default: false
+          },
+          nosql_injection: {
+            formatter: boolean,
+            default: false
+          },
+          ldap_injection: {
+            formatter: boolean,
+            default: false
+          },
+          javascript_injection: {
+            formatter: boolean,
+            default: false
+          },
+          command_injection: {
+            formatter: boolean,
+            default: false
+          },
+          xpath_injection: {
+            formatter: boolean,
+            default: false
+          },
+          ssrf: {
+            formatter: boolean,
+            default: false
+          },
+          rxss: {
+            formatter: boolean,
+            default: false
+          }
         }
       }
-    }
-  },
-
-  /**
-   * When enabled, it will use `process.env.DYNO`
-   * to set the hostname of the running application
-   */
-  heroku: {
-    use_dyno_names: {
-      default: true,
-      formatter: boolean
-    }
-  },
-
-  /**
-   * When enabled, it will allow loading of the agent
-   * in worker threads.
-   *
-   * In 11.0.0 we added code to prevent loading in worker threads
-   * to cut down on unnecessary overhead of the agent.  We have found
-   * in testing that traces and spans were useless unless work was
-   * completely self contained in the worker thread.
-   */
-  worker_threads: {
-    enabled: {
-      formatter: boolean,
-      default: false
-    }
-  },
+    },
 
-  /**
-   * When enabled, instrumentation of supported AI libraries will be in
-   * effect.
-   */
-  ai_monitoring: {
     /**
-     * Toggles the generation of AI monitoring events by the agent.
+     * When enabled, it will use `process.env.DYNO`
+     * to set the hostname of the running application
      */
-    enabled: {
-      formatter: boolean,
-      default: false
+    heroku: {
+      use_dyno_names: {
+        default: true,
+        formatter: boolean
+      }
     },
 
     /**
-     * When enabled, the content of LLM messages will be included in the
-     * recorded spans (i.e. delivered to the New Relic collector). This is
-     * enabled by default.
+     * When enabled, it will allow loading of the agent
+     * in worker threads.
+     *
+     * In 11.0.0 we added code to prevent loading in worker threads
+     * to cut down on unnecessary overhead of the agent.  We have found
+     * in testing that traces and spans were useless unless work was
+     * completely self contained in the worker thread.
      */
-    record_content: {
+    worker_threads: {
       enabled: {
         formatter: boolean,
-        default: true
+        default: false
       }
     },
 
     /**
-     * Toggles the capturing of Llm events when using streaming
-     * based methods in AIM supported libraries(i.e.- openai, AWS bedrock, langchain)
+     * When enabled, instrumentation of supported AI libraries will be in
+     * effect.
+     */
+    ai_monitoring: {
+    /**
+     * Toggles the generation of AI monitoring events by the agent.
      */
-    streaming: {
       enabled: {
         formatter: boolean,
-        default: true
+        default: false
+      },
+
+      /**
+       * When enabled, the content of LLM messages will be included in the
+       * recorded spans (i.e. delivered to the New Relic collector). This is
+       * enabled by default.
+       */
+      record_content: {
+        enabled: {
+          formatter: boolean,
+          default: true
+        }
+      },
+
+      /**
+       * Toggles the capturing of Llm events when using streaming
+       * based methods in AIM supported libraries(i.e.- openai, AWS bedrock, langchain)
+       */
+      streaming: {
+        enabled: {
+          formatter: boolean,
+          default: true
+        }
       }
-    }
-  },
-  /**
-   * Stanza that contains all keys to disable core & 3rd party package instrumentation(i.e. dns, http, mongodb, pg, redis, etc)
-   * **Note**: Disabling a given library may affect the instrumentation of libraries used after
-   * the disabled library. Use at your own risk.
-   */
-  instrumentation: pkgInstrumentation,
-
-  /**
-   * Governs the various OpenTelemetry based features provided by the
-   * agent.
-   *
-   * NOTICE: this configuration is subject to change while the OTEL
-   * feature set is in development.
-   */
-  opentelemetry_bridge: {
+    },
     /**
-     * Global switch for the whole OpenTelemetry feature. If it is set to
-     * `false`, any other sub-feature, e.g. `traces`, will not be enabled
-     * regardless of that specific sub-feature setting.
+     * Stanza that contains all keys to disable core & 3rd party package instrumentation(i.e. dns, http, mongodb, pg, redis, etc)
+     * **Note**: Disabling a given library may affect the instrumentation of libraries used after
+     * the disabled library. Use at your own risk.
      */
-    enabled: { default: false, formatter: boolean },
+    instrumentation: pkgInstrumentation,
 
     /**
-     * `traces` are instrumentations, e.g. `@fastify/otel`. Enabling `traces`
-     * enables bridging OpenTelemetry instrumentations into the New Relic
+     * Governs the various OpenTelemetry based features provided by the
      * agent.
-     */
-    traces: {
-      enabled: { default: false, formatter: boolean }
-    },
-
-    /**
-     * `logs` governs automatic configuration of the OpenTelemetry logs API.
-     * When true, the agent will automatically configure the logs API to send
-     * logs emitted through the OTEL specific API to New Relic.
      *
-     * This feature is dependent on application logs forwarding. Thus,
-     * application logs forwarding must be enabled as well.
+     * NOTICE: this configuration is subject to change while the OTEL
+     * feature set is in development.
      */
-    logs: {
-      enabled: { default: false, formatter: boolean }
-    },
-
+    opentelemetry_bridge: {
     /**
-     * `metrics` governs automatic configuration of the OpenTelemetry
-     * metrics API. When `true`, the agent will automatically configure the
-     * metrics API to send metrics to New Relic and attach them to the
-     * application entity that is instrumented by the New Relic agent.
+     * Global switch for the whole OpenTelemetry feature. If it is set to
+     * `false`, any other sub-feature, e.g. `traces`, will not be enabled
+     * regardless of that specific sub-feature setting.
      */
-    metrics: {
       enabled: { default: false, formatter: boolean },
 
       /**
-       * `exportInterval` defines the number of milliseconds between each
-       * attempt to ship metrics to New Relic. This value must be equal to
-       * or greater than the value of `exportTimeout`.
+       * `traces` are instrumentations, e.g. `@fastify/otel`. Enabling `traces`
+       * enables bridging OpenTelemetry instrumentations into the New Relic
+       * agent.
+       */
+      traces: {
+        enabled: { default: false, formatter: boolean }
+      },
+
+      /**
+       * `logs` governs automatic configuration of the OpenTelemetry logs API.
+       * When true, the agent will automatically configure the logs API to send
+       * logs emitted through the OTEL specific API to New Relic.
+       *
+       * This feature is dependent on application logs forwarding. Thus,
+       * application logs forwarding must be enabled as well.
        */
-      exportInterval: {
-        default: 60_000,
-        formatter: int
+      logs: {
+        enabled: { default: false, formatter: boolean }
       },
 
       /**
-       * `exportTimeout` defines the number of milliseconds an export operation
-       * is allowed in order to successfully complete. If the timeout is
-       * exceeded, it will be reported via the OpenTelemetry diagnostics
-       * API.
+       * `metrics` governs automatic configuration of the OpenTelemetry
+       * metrics API. When `true`, the agent will automatically configure the
+       * metrics API to send metrics to New Relic and attach them to the
+       * application entity that is instrumented by the New Relic agent.
        */
-      exportTimeout: {
-        default: 30_000,
-        formatter: int
+      metrics: {
+        enabled: { default: false, formatter: boolean },
+
+        /**
+         * `exportInterval` defines the number of milliseconds between each
+         * attempt to ship metrics to New Relic. This value must be equal to
+         * or greater than the value of `exportTimeout`.
+         */
+        exportInterval: {
+          default: 60_000,
+          formatter: int
+        },
+
+        /**
+         * `exportTimeout` defines the number of milliseconds an export operation
+         * is allowed in order to successfully complete. If the timeout is
+         * exceeded, it will be reported via the OpenTelemetry diagnostics
+         * API.
+         */
+        exportTimeout: {
+          default: 30_000,
+          formatter: int
+        }
       }
     }
   }
-})
+}
 
 /**
  * Creates a new default config