Refactor flint log format

[noCharger]

Description

Standardize Flint log output format:

{
  "timestamp": "",
  "severityText": "INFO",
  "severityNumber": 2,
  "body": {
    "message": "",
    "statusCode": ""
  },
  "attributes": {
    "domainName": "",
    "clientId": "",
    "exception.type": "",
    "exception.message": "",
  }
}

Usage V2

1. Emit log using CustomLogging class

@Override
  public boolean test(T result) throws Throwable {
    int statusCode = ((HttpResponse) result).getStatusLine().getStatusCode();
    logInfo("Checking if status code is retryable: " + statusCode);

    boolean isRetryable = retryableStatusCodes.contains(statusCode);
    logInfo("Status code " + statusCode + " check result: " + isRetryable);
    return isRetryable;
  }

2. Example log

24/03/08 01:34:46 INFO OpenSearchUpdater: Checking if index exists: flint_ql_sessions
24/03/08 01:34:46 INFO CustomLogging: {"timestamp":1709861686263,"severityText":"INFO","severityNumber":9,"body":{"message":"Checking if status code is retryable: 200"},"attributes":{"clientId":"UNKNOWN","domainName":"UNKNOWN"}}
24/03/08 01:34:46 INFO CustomLogging: {"timestamp":1709861686270,"severityText":"INFO","severityNumber":9,"body":{"message":"Status code 200 check result: false"},"attributes":{"clientId":"UNKNOWN","domainName":"UNKNOWN"}}
24/03/08 01:34:47 INFO CustomLogging: {"timestamp":1709861687144,"severityText":"INFO","severityNumber":9,"body":{"message":"Checking if status code is retryable: 200"},"attributes":{"clientId":"UNKNOWN","domainName":"UNKNOWN"}}
24/03/08 01:34:47 INFO CustomLogging: {"timestamp":1709861687144,"severityText":"INFO","severityNumber":9,"body":{"message":"Status code 200 check result: false"},"attributes":{"clientId":"UNKNOWN","domainName":"UNKNOWN"}}

3. Contributor insights

Issues Resolved

#235

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[YANG-DB]

Hi
I suggest we follow the OTEL convention for such events - see https://opentelemetry.io/docs/specs/semconv/general/logs/

[penghuo]

1. do we need custom json layout? can we leverage Log4j json layout? https://logging.apache.org/log4j/2.x/manual/json-template-layout.html
2. can we leverage Log4j env lookup for domain_name, client_id? https://logging.apache.org/log4j/2.x/manual/lookups.html#EnvironmentLookup

[noCharger]

Hi I suggest we follow the OTEL convention for such events - see https://opentelemetry.io/docs/specs/semconv/general/logs/

Propose a new log format following OTEL convention

{
  "timestamp": "",
  "severityText": "INFO",
  "severityNumber": 2,
  "body": {
    "message": "",
    "statusCode": ""
  },
  "attributes": {
    "domainName": "",
    "clientId": "",
    "exception.type": "",
    "exception.message": "",
  }
}

cc: @YANG-DB @penghuo @dai-chen @vamsi-amazon

[YANG-DB]

Nice !
Can we also calculate the severityNumber ?

[noCharger]

To prevent overriding log4j properties, create a mock log file using the default pattern layout

[noCharger]

@YANG-DB @penghuo Resolved your comments. Please take another review. Thanks!