.err logs have no timestamp

[daviftorres]

The required feature described as a wish

It is very hard to troubleshoot by looking at the .err files of management server, agent, or usage if they do not have timestamps.

[github-actions]

🏷️ Issue Triaged

Hi @daviftorres! I've categorized this issue as enhancement based on the following analysis:

Reasoning: This request improves existing logging functionality by adding timestamps to .err files, making troubleshooting easier. It enhances the observability of the system rather than fixing a broken feature.

View Triage Details

Analysis

• Keywords detected: "feature", "wish", "troubleshoot", ".err files", "timestamps"
• Issue type indicators: Request for improved logging capabilities in existing error log files (management server, agent, usage)
• Confidence: High

Recommended Next Steps

• Consider implementing timestamps in a consistent format across all .err log files
• Evaluate if this should apply to other log files as well for consistency
• This could be a good opportunity to standardize logging format across CloudStack components

References: Triage run §23546481442

Generated by Issue Triage Agent

To install this workflow, run gh aw add github/gh-aw/.github/workflows/issue-triage-agent.md@94662b1dee8ce96c876ba9f33b3ab8be32de82a4. View source at https://github.com/github/gh-aw/tree/94662b1dee8ce96c876ba9f33b3ab8be32de82a4/.github/workflows/issue-triage-agent.md.

[dheeraj12347]

Hi, I’d like to work on this.

I plan to identify where .err logs are generated (management server, agent, usage) and ensure timestamps are consistently included in the logging output.

Please let me know if there are any preferred logging formats or existing configurations I should follow.

[daviftorres]

Dear @dheeraj12347, thank you for volunteering to help so quickly.

I’m not a developer, so I may not be able to give detailed instructions. However, I suggest following the same format used for the .log file and applying it to the .err file.

Regards,

[dheeraj12347]

Hi all,
I’ve opened PR #12967 to address this issue by adding %d{DEFAULT} timestamps to the CONSOLE appenders in the management server, client and agent log4j-cloud.xml.in files, so that .err logs now follow the same timestamped pattern as the .log files.

This replaces my earlier PR #12896, which had unrelated changes. The new PR is limited to just the three logging config files.

When you have a moment, could you please review PR #12967 and let me know if any further adjustments are needed?