Skip to content

[Release-3.14.1][Bug] Fix incorrect timestamp parsing for chef-client.log in CloudWatch Agent #3061

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hehe7318 merged 3 commits into from
Dec 16, 2025
+3 −1
Merged

[Release-3.14.1][Bug] Fix incorrect timestamp parsing for chef-client.log in CloudWatch Agent #3061

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f415f1d
Fix incorrect timestamp parsing for chef-client.log in CloudWatch Agent
hehe7318 Dec 9, 2025
4a68a7f
Merge branch 'release-3.14' into wip/fix-log-timestamp-3141
hehe7318 Dec 15, 2025
5d46547
Remove the detail about the timestamp format.
hehe7318 Dec 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ This file is used to list changes made in each version of the AWS ParallelCluste
- Open MPI: openmpi40-aws-4.1.7-2 and openmpi50-aws-5.0.8-11

**BUG FIXES**
- Fix incorrect timestamp parsing for chef-client.log in CloudWatch Agent configuration.
- Prevent cluster readiness check failures due to instances launched while the check is in progress.
- Fix race condition where compute nodes could deploy the wrong cluster config version after an update failure.

Expand Down
3 changes: 2 additions & 1 deletion cookbooks/aws-parallelcluster-environment/files/cloudwatch/cloudwatch_agent_config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@
"default": "%Y-%m-%d %H:%M:%S,%f",
"bracket_default": "[%Y-%m-%d %H:%M:%S]",
"slurm": "%Y-%m-%dT%H:%M:%S.%f",
"chef": "[%Y-%m-%dT%H:%M:%S",
Copy link
Contributor

@gmarciani gmarciani Dec 15, 2025

Choose a reason for hiding this comment

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

Missing final square bracket?

Copy link
Contributor

@gmarciani gmarciani Dec 15, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

According to the description this is intentional:

(Note: CloudWatch Agent's %z only supports timezone without colon like -0700, but Chef outputs +02:00 format. We only match up to seconds and let CloudWatch handle the rest.)

I'm ok with the current approach. However, did you check if chef allows to write the offset in the format accepted by CW?

Copy link
Contributor Author

@hehe7318 hehe7318 Dec 16, 2025

Choose a reason for hiding this comment

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

We have synced, that we do have a way to customize the chef timestamp format, but it doesn't worth the effort. So we will accept the current approach.

"json": ""
},
"log_configs": [
Expand Down Expand Up @@ -82,7 +83,7 @@
"feature_conditions": []
},
{
"timestamp_format_key": "default",
"timestamp_format_key": "chef",
"file_path": "/var/log/chef-client.log",
"log_stream_name": "chef-client",
"schedulers": [
Expand Down
Loading