Re: [PR] Adjust GcpLayout JSON to latest format [logging-log4j2]

[via GitHub]

ViliusS commented on PR #3586:
URL: https://github.com/apache/logging-log4j2/pull/3586#issuecomment-2772792644

   > @ViliusS,
   > 
   > Thanks for you contribution.
   > 
   > Did you test it on an actual Google Cloud instance? I am not a GCP user, 
but some of the changes you propose differ from the documented log format.
   
   Yes I did. Here are some screenshots.
   
   Exception caught because of the stack trace in message field:
   
![image](https://github.com/user-attachments/assets/1b5fc3e8-3f01-40b1-8353-a9c3bcafa3e3)
   Expanded jsonPayload fields in the logging:
   
![image](https://github.com/user-attachments/assets/039fdd90-a23e-428a-bccd-959f16f0fa2f)
   Proof about automatic timestamp mapping (previously this field was generated 
by Google and the one sent from Log4J lived in `jsonPayload.timestamp`:
   
![image](https://github.com/user-attachments/assets/10139b2a-1587-4a46-8c28-b5c7d7869182)
   
   The same error caught in Error Reporting UI:
   
![image](https://github.com/user-attachments/assets/9e2ce7df-2415-4ecf-b415-c5b602228b8b)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org