Log Management
When API logging is enabled, the original request/response data is saved for each API call and can be viewed in the console.
Use Cases
- API Error Debugging - Analyze error causes by reviewing original request/response data
- Player History Tracking - Track API call history for specific players
- Failure Analysis - Analyze the causes of failed API calls
info
Logs are retained for 35 days and automatically deleted afterward.
Recorded Data
The following data is recorded for each API call.
| Field | Description |
|---|---|
| API Code | The called API code (e.g., storage_load) |
| Player ID | The requesting player ID |
| Log File | Original request/response JSON |
| Log Size | Log file size (KB) |
| Status | success or fail |
| IP | Request IP |
| Date | Request time |
Search Conditions
| Field | Description |
|---|---|
| API Code | Select the API code to look up. (Required, categorized by service) |
| Player ID | Enter the UUID to look up logs for a specific player. (Required) |
| Search Period | Select the start and end dates for the log search. (Required) |
Log Details
Click the log file to view Request, Response, and Error information in a popup window.
| Field | Description |
|---|---|
| Request | API request data (Pretty Mode supported, clipboard copy available) |
| Response | API response data (Pretty Mode supported, clipboard copy available) |
| Error | Error information when an error occurs |
info
Enabling Pretty Mode displays data in an easy-to-read formatted layout. You can download log data as a JSON file using the JSON Download button.