frontend-request.logs are not parsing properly

[sergiocruzado]

I just found out that the logs parser for frontend-request.logs are not being parsed accordingly.

I am using this config for fluentd:
https://github.com/jfrog/log-analytics-datadog/blob/master/fluent.conf.rt

To reproduce the error you can use the following tool:

https://fluentular.herokuapp.com/

This is the same regexp for all request logs:

^(?[^ ])|(?<trace_id>[^\|])|(?<remote_address>[^\|])|(?[^\|])|(?<request_method>[^\|])|(?<request_url>[^\|])|(?<return_status>[^\|])|(?<response_content_length>[^\|])|(?<request_content_length>[^\|])|(?<request_duration>[^\|])|(?<request_user_agent>.+)$

These are the logs for frontend-request.logs

2021-08-17T10:53:01.427Z|2ab11e927753a3b |127.0.0.1|anonymous|GET|/api/v1/system/version|200|20|-|1.654|Chrome|92.0.4515.131|Windows|10

2021-08-17T10:53:01.509Z|70362cd9f01a74b9|127.0.0.1|[email protected]|GET|/api/v1/ui/storagesummary/projects|200|132|-|23.228|Chrome|92.0.4515.131|Windows|10

The first one has a space in the trace_id, and it is parsed properly
The second one is no being parsed properly

For the rest of request.logs (artifactory, metadata, event or access) logs are being parsed properly.

[benharosh]

Old issue. Was fixed in later versions. Closing.