Skip to content

chore: update cluster to fix logging issues#16701

Merged
alexghr merged 1 commit intonextfrom
ag/logs
Sep 2, 2025
Merged

chore: update cluster to fix logging issues#16701
alexghr merged 1 commit intonextfrom
ag/logs

Conversation

@alexghr
Copy link
Copy Markdown
Contributor

@alexghr alexghr commented Sep 1, 2025

Close TMNT-236

@alexghr alexghr enabled auto-merge September 1, 2025 21:22
@alexghr alexghr changed the title chore: drop timestamp in favour of GCP's field chore: update cluster to fix logging issues Sep 2, 2025
Comment on lines -16 to -19
// Same as pino.stdTimeFunctions.isoTime but uses "timestamp" key instead of "time"
timestamp(): string {
return `,"timestamp":"${new Date(Date.now()).toISOString()}"`;
},
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't work as expected. GKE adds its own timestamp field.
Screenshot 2025-09-02 at 14 17 45

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just wondering: should we keep the system timestamp as well, so we know the exact time from the perspective of the node process for the log?

Comment on lines -16 to -19
// Same as pino.stdTimeFunctions.isoTime but uses "timestamp" key instead of "time"
timestamp(): string {
return `,"timestamp":"${new Date(Date.now()).toISOString()}"`;
},
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just wondering: should we keep the system timestamp as well, so we know the exact time from the perspective of the node process for the log?

@alexghr alexghr added this pull request to the merge queue Sep 2, 2025
Merged via the queue into next with commit 1bae740 Sep 2, 2025
16 checks passed
@alexghr alexghr deleted the ag/logs branch September 2, 2025 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants