Mendix default log levels (like webservices, REST Consume, REST Publish) missing on local console post upgrade from 10.12.5 to 10.24.2

0
Hello Experts, All Mendix default log levels (like webservices, REST Consume, REST Publish) are not visible on local console Advance Log level setting after upgrading from Mendix 10.12.5 to 10.24.2 LTS. I am not able to trace any API call locally. Any suggestions.  Refer the screenshot
asked
2 answers
0

The above is not correct. It is a bug and Mendix is working on a fix for this. 

Regards,

Ronald

 

answered
-1

Hi Subhalaxmi,

 

This is a common observation after upgrading to Mendix version 10.24.2 especially when coming from older LTS versions like 10.12.5 Mendix has restructured or renamed several internal log nodes and in some cases disabled certain log levels by default for better performance and security

 

Why default log levels are missing

 

In newer versions of Mendix certain default log nodes such as REST Consume REST Publish and Webservices may no longer appear automatically in the Advanced Log Levels list unless they are triggered at runtime or explicitly configured

 

Recommended steps to resolve the issue

1. Trigger the Services Once Run a microflow or operation that calls a REST service or webservice This can cause Mendix to register the corresponding log node dynamically and make it appear in the console

2. Manually Add Log Levels Go to Settings > Runtime > Custom Log Levels in your Mendix Studio Pro

  • Manually add log levels such as:

    • RestConsume

    • RestPublish

    • WebServices

    • Connector

  • Set their log level to Trace or Debug depending on how much detail you want

3. Check the Release Notes Mendix may have renamed or deprecated certain log categories so reviewing the release notes between 10.12.5 and 10.24.2 can provide insight into changes that affect logging

 

If you do not see any logs even after triggering services manually it's possible that a new permission or runtime setting is preventing logs from being captured Check if the logging framework or any custom settings are interfering

 

Best Regards

Saqlein

 

answered