Previous Next JavaScript must be enabled to correctly display this content

## 4.1 Log Analysis

This topic describes the possible issues to use logs to analyze issues in a transaction using logs.

Error Message not shown

If there are any improper calls, check the ERTB_MSGS table of the respective schema to understand the cause of the error.

1. Press F12 to open the Networks.
2. Check the error code in the response.

Query: SELECT * FROM ERTB_MSGS WHERE ERR_CODE=’GCS_AUTH-03’

Figure 4-2 Error Code

Description of "Figure 4-2 Error Code"

Setting Log file path

Log generation path needs to be defined in PLATO_LOGGER_PARAM_CONFIG table of PLATO schema.

Query: Select * from PLATO_LOGGER_PARAM_CONFIG;

Figure 4-3 PLATO_LOGGER_PARAM_CONFIG

Description of "Figure 4-3 PLATO_LOGGER_PARAM_CONFIG"

Dynamic Log Generation Issues

For generating dynamic service logs, insert the data to PLATO_DEBUG_USERS table.

Query: Select * from PLATO_DEBUG_USERS;

Figure 4-4 Service Logs

Description of "Figure 4-4 Service Logs"

Logs are not generated

If you are not getting logs, put the loggers across API, hit through postman, and test again.

Figure 4-5 Postman

Description of "Figure 4-5 Postman"

404 Error

The possible causes for 404 error are as follows:

- Check service is not running on Eureka
- Check service is not deployed in Weblogic

500 Internal Error

The possible causes for 500 internal error are as follows:

- Issue with Plato entries
- Issue with Eureka
- Issue with any peace of code

The server-side debugging is needed for the above-mentioned issues, if it is not captured in logs.

Parent topic: Troubleshooting Functional Workflows