Skip to content

docs(medic/cht-core#10357): document LOG_LEVEL env variable for Docker deployments#2172

Merged
sugat009 merged 6 commits intomainfrom
10357-docs-loglevel-v2
Apr 2, 2026
Merged

docs(medic/cht-core#10357): document LOG_LEVEL env variable for Docker deployments#2172
sugat009 merged 6 commits intomainfrom
10357-docs-loglevel-v2

Conversation

@sugat009
Copy link
Copy Markdown
Member

Summary

  • Documents the LOG_LEVEL environment variable for controlling log verbosity in api and sentinel containers
  • Recommends the .env file approach (consistent with CHT deployment conventions) instead of shell export
  • Clarifies that docker compose up -d (not docker compose restart) is required to pick up env var changes
  • Notes that from CHT 5.1.0 onward, NODE_ENV no longer affects logging detail

Supersedes #2030 (taking over from @AmirSaudagar55).

Linked issue

medic/cht-core#10357

Test plan

  • Verify the "Setting log level" section renders correctly
  • Confirm supported log level values match Winston logger defaults in shared-libs/logger/src/node-logger.js
  • Confirm .env file approach is consistent with existing CHT Docker deployment docs

@sugat009 sugat009 changed the title docs(medic#10357): document LOG_LEVEL env variable for Docker deployments docs(medic/cht-core#10357): document LOG_LEVEL env variable for Docker deployments Mar 30, 2026
@sugat009 sugat009 requested a review from jkuester March 30, 2026 13:15
@sugat009 sugat009 self-assigned this Mar 30, 2026
@sugat009
Copy link
Copy Markdown
Member Author

sugat009 commented Mar 30, 2026

@jkuester I created another PR to make a few changes w.r.t. medic/cht-core#10583. Would appreciate a review. Thanks!

Copy link
Copy Markdown
Contributor

@jkuester jkuester left a comment

Choose a reason for hiding this comment

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

LGTM!


**Supported values:**

- `error` — Only error messages (production use)
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.

Minor, but it seems a bit confusing to put "production use" here and then also say "recommended for production" below for info. Probably okay to just remove the "production use" from this one... 🤷

@sugat009 sugat009 merged commit 465441f into main Apr 2, 2026
2 checks passed
@sugat009 sugat009 deleted the 10357-docs-loglevel-v2 branch April 2, 2026 05:08
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.

3 participants