ppkarwasz commented on code in PR #3586:
URL: https://github.com/apache/logging-log4j2/pull/3586#discussion_r2025672949
##
log4j-layout-template-json/src/main/resources/GcpLayout.json:
##
@@ -49,25 +55,15 @@
"key": "span_id"
},
"logging.googleapis.com/trace_sampled":
ppkarwasz commented on PR #3582:
URL: https://github.com/apache/logging-log4j2/pull/3582#issuecomment-2773819675
If we manage to learn how to use GitHub Projects (in the "Projects" tab,
currently team-private), we can keep track of the order in which PRs are
waiting for a review.
--
This
jvz commented on PR #3582:
URL: https://github.com/apache/logging-log4j2/pull/3582#issuecomment-2773260582
It won't end up being related to PR size or even making PRs. I would be
annoyed if my PRs sit unreviewed.
--
This is an automated message from the Apache Git Service.
To respond to t
github-actions[bot] merged PR #178:
URL: https://github.com/apache/logging-log4j-transform/pull/178
--
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: noti
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 fr
ViliusS commented on code in PR #3586:
URL: https://github.com/apache/logging-log4j2/pull/3586#discussion_r2024906218
##
log4j-layout-template-json/src/main/resources/GcpLayout.json:
##
@@ -49,25 +55,15 @@
"key": "span_id"
},
"logging.googleapis.com/trace_sampled": tr
ViliusS commented on code in PR #3586:
URL: https://github.com/apache/logging-log4j2/pull/3586#discussion_r2024891715
##
log4j-layout-template-json/src/main/resources/GcpLayout.json:
##
@@ -1,13 +1,18 @@
{
- "timestamp": {
+ "timestampSeconds": {
"$resolver": "timestamp"
github-actions[bot] commented on PR #3586:
URL: https://github.com/apache/logging-log4j2/pull/3586#issuecomment-2772587633
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
ViliusS opened a new pull request, #3586:
URL: https://github.com/apache/logging-log4j2/pull/3586
This is my first contribution to Log4J so I'm not 100% sure if I did
everything right, but here it goes.
This PR adjusts GcpLayout JSON formatting to match what is expected by GCP.
FreeAndNil commented on issue #234:
URL:
https://github.com/apache/logging-log4net/issues/234#issuecomment-2771832020
@lraulea it is possible to implement this feature inside log4net.
But it will take some time.
You can consider sponsoring me.
--
This is an automated message fro
lraulea commented on issue #234:
URL:
https://github.com/apache/logging-log4net/issues/234#issuecomment-2771803819
@FreeAndNil unfortunately not much better
I've noticed that these 191 bytes are actually empty files.
Quite many empty files are created, sometimes I get the impre
11 matches
Mail list logo
