Skip to content
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.

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

🔧 centralize log path creation and improve logging #2385

Merged
merged 2 commits into from
Sep 23, 2024

Conversation

MrHinsh
Copy link
Member

@MrHinsh MrHinsh commented Sep 23, 2024

  • change the rolling interval on the main log to hourly, and to rollOnFileSizeLimit
  • change the rolling interval on the error log to daily
  • Added the log path to the output, beginning and end.

Refactor log path creation into a dedicated LogLocationService to centralize and simplify log path management. This change ensures consistent log path generation and usage across the application. Additionally, enhance logging by including log path information in log messages and enabling file size limits and rolling intervals for log files. This improves log management and helps in diagnosing issues by providing clear log locations.
@nkdagility-actions-bot
Copy link

Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2385.westeurope.5.azurestaticapps.net

@nkdagility-actions-bot
Copy link

Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2385.westeurope.5.azurestaticapps.net

@MrHinsh MrHinsh merged commit 2a81288 into main Sep 23, 2024
10 checks passed
@MrHinsh MrHinsh deleted the topic/output-log-location branch September 23, 2024 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This is an item for a Documentation enhancement enhancement enhancement-modern feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant