feat: add transform to field details

[victorhos]

What is being delivered?

• Added a change to the details field redirected to the Dynatrace data.details field.

Motivation:

• This test is necessary to increase the logs that are sent from Auth0 with errors to improve troubleshooting.

Evidences:

Read listening: Link:

1. Test full log:

• log ingest:

  {
    "log_id":"requested",
    "data":{
       "_id":"_id6",
       "date":"2023-10-19T14:05:43",
       "description":"test detail full",
       "details":{
          "request":{
             "method":"data_details_request_method",
             "path":"data_details_request_path"
          },
          "response":{
             "body":"data_details_response_body",
             "statusCode":400
          }
       },
       "log_id":"log_id",
       "type":"type_custom"
    }
  }

• log in Dynatrace:
  
  

2. Test without details key should return N/A

• log ingest:

  {
     "log_id":"requested",
     "data":{
        "_id":"_id7",
        "date":"2023-10-19T14:15:43",
        "description":"test detail n/a",
        "log_id":"log_id",
        "type":"type_custom"
     }
  }

• log in Dynatrace:
  
  

---

2 - What is being delivered?
An error occurred when running pre-commit with the Docker command. To solve this, add permissions for the root user in the main folder:

root@29c0c90ea5bc:/app# pre-commit run --all-files
An error has occurred: FatalError: git failed. Is it installed, and are you in a Git repository directory?
Check the log at /root/.cache/pre-commit/pre-commit.log
root@29c0c90ea5bc:/app# cat /root/.cache/pre-commit/pre-commit.log
### version information

'''
pre-commit version: 3.5.0
git --version: git version 2.30.2
sys.version:
    3.9.2 (default, Feb 28 2021, 17:03:44) 
    [GCC 10.2.1 20210110]
sys.executable: /usr/bin/python3
os.name: posix
sys.platform: linux
'''

### error information

'''
An error has occurred: FatalError: git failed. Is it installed, and are you in a Git repository directory?
'''

'''
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/pre_commit/git.py", line 58, in get_root
    cmd_output('git', 'rev-parse', '--show-cdup')[1].strip(),
  File "/usr/local/lib/python3.9/dist-packages/pre_commit/util.py", line 116, in cmd_output
    returncode, stdout_b, stderr_b = cmd_output_b(*cmd, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/pre_commit/util.py", line 110, in cmd_output_b
    raise CalledProcessError(returncode, cmd, stdout_b, stderr_b)
pre_commit.util.CalledProcessError: command: ('/usr/bin/git', 'rev-parse', '--show-cdup')
return code: 128
stdout: (none)
stderr:
    fatal: detected dubious ownership in repository at '/app'
    To add an exception for this directory, call:
    
    	git config --global --add safe.directory /app

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/pre_commit/error_handler.py", line 73, in error_handler
    yield
  File "/usr/local/lib/python3.9/dist-packages/pre_commit/main.py", line 370, in main
    _adjust_args_and_chdir(args)
  File "/usr/local/lib/python3.9/dist-packages/pre_commit/main.py", line 180, in _adjust_args_and_chdir
    toplevel = git.get_root()
  File "/usr/local/lib/python3.9/dist-packages/pre_commit/git.py", line 64, in get_root
    raise FatalError(
pre_commit.errors.FatalError: git failed. Is it installed, and are you in a Git repository directory?
'''
root@29c0c90ea5bc:/app# pwd

[willianantunes]

question: The guide says you can use one of the four keys to store content. I don't think it says you can use two or even four of them to store the content. For example, I understand this is a valid example:

[
    {
        "content": "Exception: Did you throw you television on me?",
        "log.source": "cockatiel",
        "timestamp": "2022-11-21T16:15:40.0000",
        "severity": "error",
        "service.name": "cockatiel-sniffer",
        "service.namespace": "dev-stage-salt-mustache-cluster",
        "custom.attribute": "attribute value"
    }
]

This is one invalid because it uses two keys to store content:

[
    {
        "content": "Exception: Did you throw you television on me?",
        "body": "Exception: Did you throw you television on me?",
        "log.source": "cockatiel",
        "timestamp": "2022-11-21T16:15:40.0000",
        "severity": "error",
        "service.name": "cockatiel-sniffer",
        "service.namespace": "dev-stage-salt-mustache-cluster",
        "custom.attribute": "attribute value"
    }
]

Also, the Log Monitoring API has the following rule:

Content. If the content key is not set, the whole JSON is parsed as the content.

Did you test your solution in an actual Dynatrace Environment? How did it behave?