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

[IS-KM 5.10.0] Database Calls Not Logged in Correlation Logs #21132

Open
Pratheesha97 opened this issue Sep 19, 2024 · 0 comments
Open

[IS-KM 5.10.0] Database Calls Not Logged in Correlation Logs #21132

Pratheesha97 opened this issue Sep 19, 2024 · 0 comments

Comments

@Pratheesha97
Copy link

Describe the issue:
After updating WSO2 IS-KM from update level 276 to 277 via the WSO2 Updates 2.0 tool, database calls are no longer being logged in the correlation logs. Only network calls are being captured, as shown in the sample log below:

2024-09-19 12:09:35,527|16ecb5e5-ce8d-4c41-bcac-e81a55a90209|https-jsse-nio-9443-exec-48|0|HTTP-In-Request|1726758575527|POST|null|/oauth2/token
2024-09-19 12:09:35,772|16ecb5e5-ce8d-4c41-bcac-e81a55a90209|https-jsse-nio-9443-exec-48|245|HTTP-In-Response|1726758575772|POST|null|/oauth2/token

How to reproduce:

  1. Enable correlation logs by following the steps outlined in the documentation [1].
  2. Start the server with the flag -DenableCorrelationLogs=true.
  3. Observe that database call logs are missing from the correlation logs while network calls are logged correctly.

[1] - https://is.docs.wso2.com/en/5.10.0/setup/working-with-product-observability/#configuring-product-observability

Expected behavior:
Database calls should be logged in the correlation logs along with network calls.

Environment information:

  • Product Version: IS-KM 5.10.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant