Skip to content

[PP-14099]: Handle transforming ADOT logs#49

Merged
jfharden merged 1 commit intomainfrom
pp-14099/handle-transforming-adot-logs
May 29, 2025
Merged

[PP-14099]: Handle transforming ADOT logs#49
jfharden merged 1 commit intomainfrom
pp-14099/handle-transforming-adot-logs

Conversation

@jfharden
Copy link
Contributor

Handle transforming the adot logs

Unfortunately ADOT logs in lots of formats, so lets not deal with any of it, instead lets just ship them as a generic log line, and set the timestamp (of which there are several formats, and many lines without a format) to the timestamp the log lines get in cloudwatch.

return extractAppLogTime(log)
case CloudWatchLogTypes.adot:
// Adot has many different time formats, so we'll rely on the cloudwatch timestamp instead
return undefined
Copy link
Contributor

Choose a reason for hiding this comment

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

We might want to remove console.log('Using cloudwatch event time') on line 129, as it will be logged for every adot log line.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As it happens though, with ADOT when you have the log level as WARN it basically only logs on startup and shutdown (unless things are going wrong I guess).

But I think you're still right, it might be good to gate the logs behind a debug flag like with the current lambdas, and the s3 to firehose one.

I'll do that as a follow on

@jfharden jfharden merged commit 70c769a into main May 29, 2025
4 checks passed
@jfharden jfharden deleted the pp-14099/handle-transforming-adot-logs branch May 29, 2025 08:28
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