anchor.diff:  
   By default, we use the function or class name of the view as the transaction name.
   Starting with Django 2.2, Django makes the route (e.g. `users/<int:user_id>/`) available on the `request.resolver_match` object.
  -If you want to use the route instead of the view name as the transaction name, you can set this config option to `true`.
  +If you want to use the route instead of the view name as the transaction name, set this config option to `true`.
   
   NOTE: in versions previous to Django 2.2, changing this setting will have no effect.
   
  
positive.code: 
  For requests with a content type of `multipart/form-data`,
  any uploaded files will be referenced in a special `_files` key.
  It contains the name of the field, and the name of the uploaded file, if provided.
  
  WARNING: request bodies often contain sensitive values like passwords, credit card numbers etc.
  If your service handles data like this, we advise to only enable this feature with care.
  
  [float]
  
negative.code: 
  Possible values: `true`, `false`
  
  WARNING: Request headers often contain sensitive values like session IDs and cookies.
  See <<sanitizing-data,sanitizing data>> for more information on how to filter out sensitive data.
  
  [float]
  [[config-transaction-max-spans]]
  