Java agent error collector settings

Enable error collection.

Specified exception class names will be ignored and will not affect error rate or Apdex score, or be reported to APM. Cannot be specified by system property.

This setting is dynamic, so running agents will notice changes to newrelic.yml without a JVM restart.

For example:

error_collector:
  ignore_classes:
    - "com.example.MyException"
    - "com.example.DifferentException"

An environment variable can be used to list exception class names you want to be ignored:

NEW_RELIC_ERROR_COLLECTOR_IGNORE_CLASSES="[\"com.example.MyException\", \"com.example.DifferentException\"]"

Specify exception class names the agent should ignore. Ignored messages will not affect error rate or Apdex score, or be reported to APM. Contains yaml pairs consisting of:

• A fully qualified exception class name that should not be reported to APM

  AND

• A list of exception messages to match against (at least one is required)

  If the exception class name matches an error but the message does not, then that error will not be ignored. Message strings use contains for matching. A message cannot be provided on its own and must always be paired with a fully qualified class name. Cannot be specified by system property.

  This setting is dynamic, so running agents will notice changes to newrelic.yml without a JVM restart.

  For example:

  error_collector:
    ignore_messages:
      com.example.MyException:
        - "Some error message to ignore"
        - "Some other error message to ignore"
      com.example.DifferentException:
        - "Some different error message to ignore"

  Copiar

  An environment variable can be used to list exception class names and messages you want to be ignored:

  NEW_RELIC_ERROR_COLLECTOR_IGNORE_MESSAGES="{\"com.example.MyException\": [\"Some error message to ignore\", \"Some other error message to ignore\"], \"com.example.DifferentException\": [\"Some different error message to ignore\"]}"

  Copiar

A comma-separated list comprised of individual and dashed ranges of HTTP status codes that should not be treated as errors.

If this property is commented out in the newrelic.yml configuration file, then the 404 status code will automatically be ignored. When using server-side configuration, the status code 404 must be specified in order for it to be ignored.

This setting is dynamic, so running agents will notice changes to newrelic.yml without a JVM restart.

For example:

error_collector:
  ignore_status_codes: 404,507-511

Prevents specified exception classes from affecting error rate or Apdex score while still reporting the errors to APM. Cannot be specified by system property.

This setting is dynamic, so running agents will notice changes to newrelic.yml without a JVM restart.

For example:

error_collector:
  expected_classes:
    - "com.example.MyException"
    - "com.example.DifferentException"

An environment variable can be used to list expected exception class names:

NEW_RELIC_ERROR_COLLECTOR_EXPECTED_CLASSES="[\"com.example.MyException\", \"com.example.DifferentException\"]"

Contains yaml pairs consisting of a fully qualified exception class name that should be marked as expected and thus prevented from affecting error rate or Apdex score and a List of exception messages to match against, the latter of which at least one is required. If the exception class name matches an error but the message does not, then that error will not be marked as expected and therefore will affect error rate and Apdex score.

Message strings use contains for matching. A message cannot be provided on its own and must always be paired with a fully qualified class name. Cannot be specified by system property.

This setting is dynamic, so running agents will notice changes to newrelic.yml without a JVM restart.

For example:

error_collector:
  expected_messages:
    com.example.MyException:
      - "Some expected error message"
      - "Some other expected error message"
    com.example.DifferentException:
      - "Some different expected error message"

An environment variable can be used to list expected exception class names and messages:

NEW_RELIC_ERROR_COLLECTOR_EXPECTED_MESSAGES="{\"com.example.MyException\": [\"Some error message to ignore\", \"Some other error message to ignore\"], \"com.example.DifferentException\": [\"Some different error message to ignore\"]}"

A comma-separated list comprised of individual and dashed ranges of HTTP status codes to be marked as expected and thus prevented from affecting error rate or Apdex score.

This setting is dynamic, so running agents will notice changes to newrelic.yml without a JVM restart.

For example:

error_collector:
  expected_status_codes: 415,500-506

Expected status codes can also be with the NEW_RELIC_ERROR_COLLECTOR_EXPECTED_STATUS_CODES environment variable.

This setting can be used to turn on or off all attributes for traced errors. If attributes.enabled is false at the root level, then no attributes will be sent to traced errors regardless of how this property is set under error_collector.

If attributes are enabled for traced errors, all attribute keys found in this list will be sent to New Relic in traced errors. For more information, see the agent attribute rules.

Attribute keys found in this list will not be sent to New Relic in traced errors. For more information, see the agent attribute rules.

When multiple errors are noticed in a transaction, only the last error will be reported by default. Setting this property to false will instead report only the first error that is noticed. For more information, see the noticeError API. For example:

error_collector:
  ignoreErrorPriority: false

All specified exception class names specified will not be treated as errors. Deprecated as of Java agent 3.40.0 and replaced by ignore_classes.

For example:

error_collector:
  ignore_errors: some.other.MyException