Skip to content

Update configuration in monitoring HTTP access logs#11606

Open
Dimagidhp wants to merge 1 commit into
wso2:4.5.0from
Dimagidhp:fixing-issue-10768-4.5.0
Open

Update configuration in monitoring HTTP access logs#11606
Dimagidhp wants to merge 1 commit into
wso2:4.5.0from
Dimagidhp:fixing-issue-10768-4.5.0

Conversation

@Dimagidhp

Copy link
Copy Markdown

Purpose

Resolves #10768

Goals

Ensure users following the 4.5.0 docs enable HTTP servlet access logging with the correct useLogger = true setting and see correctly rendered config blocks.

Approach

  • Replaced the incorrect enabled = true property with the correct useLogger = true under the [http_access_log] section in deployment.toml (step 2), as enabled = true is not required and is on by default.
  • Fixed indentation of the sub-content under step 3 so it's nested under the ordered list item instead of breaking out into a new block.

User stories

N/A

Release note

Fixed incorrect HTTP access log configuration key in the monitoring documentation.

Documentation

This PR is the documentation change:
en/docs/monitoring/observability/logs/monitoring-http-access-logs.md

Training

N/A

Certification

N/A – no impact on certification exams.

Marketing

N/A

Automation tests

  • Unit tests

    N/A – documentation-only change.

  • Integration tests

    N/A – documentation-only change.

Security checks

Samples

N/A

Related PRs

Migrations (if applicable)

N/A

Test environment

Verified the corrected configuration against WSO2 API Manager 4.7.0 – confirmed the HTTP_ACCESS log4j2 appender writes access log entries as documented.

Learning

N/A

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fbf6c69a-5ba9-4d23-ac3d-9f67f9bab6b8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Praveena Hennadige seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@Dimagidhp Dimagidhp force-pushed the fixing-issue-10768-4.5.0 branch from 0244e68 to 02ffbb9 Compare July 12, 2026 07:46
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