This article explains how to temporarily change how much information a LiveEdge device records in its logs.
Use this feature when troubleshooting an active issue and the normal logs do not provide enough information. You can change logging for the whole device, a device area such as inputs or outputs, or a specific component. The REST API calls this setting verbosity.
Changes made through the API take effect while the device is running and are cleared after a reboot.
Supported products
LiveEdge® Max, LiveEdge® Max 2, LiveEdge® Node.
Requirements
A supported Videon device running firmware V12.1.0 or later
Network access to the device
Postman installed on your machine
A way to view or collect the device logs
The V2 REST API base URL is:
http://[DEVICE-IP-ADDRESS]:2020/v2
Table of contents
Logging levels
Log Level |
Use |
| FATAL | Most severe failures only (lowest level of detail) |
| ERROR | Error-level entries only |
| WARN | Warnings + errors |
| INFO | Normal operational information (Default configuration) |
| DEBUG | Additional troubleshooting details |
| TRACE | Highest level of detail |
DEBUG and TRACE produce more log output.Change the logging level with Postman
Use Postman to temporarily increase logging for the device area related to the issue.
Check the current logging level
Open Postman.
Select New, then select HTTP Request.
Set the method to GET.
Enter:
http://[DEVICE-IP-ADDRESS]:2020/v2/debug_verbosity
Select Send.
Example response:
{ "verbosity": "INFO" }
Record the current value before making changes.
View the current scope settings
Create a new HTTP request.
Set the method to GET.
Enter:
http://[DEVICE-IP-ADDRESS]:2020/v2/debug_verbosity/scopes
Select Send.
The response shows the current level for each fixed scope:
buffer_flowencodersh2cinputsoutputs
It also shows any active settings under scope_overrides.
Set a scope to DEBUG
The following example enables additional input-related debug logging to increase the amount of input details that are printed within the logs.
Create a new HTTP request.
Set the method to PUT.
Enter:
http://[DEVICE-IP-ADDRESS]:2020/v2/debug_verbosity/scopes
Select the Body tab.
Select raw
Set the body format to JSON.
Enter:
{ "scopes": { "inputs": "DEBUG" } }
Confirm that Postman added this header:
Content-Type: application/json
Select Send.
A 200 OK response indicates that the request was accepted.
Use the scope that matches the issue:
Issue |
Scope |
| Input signal or source | inputs |
| Encoder behavior | encoders |
| Output or stream delivery | outputs |
| Buffer or data flow | buffer_flow |
| H2C-related input troubleshooting | h2c |
Confirm the change
Return to the GET request for:
http://[DEVICE-IP-ADDRESS]:2020/v2/debug_verbosity/scopes
Select Send again.
Confirm that the selected scope shows DEBUG and appears under scope_overrides.
Example:
{ "scopes": { "inputs": "DEBUG" }, "scope_overrides": { "inputs": "DEBUG" } }
Reproduce the issue
Begin collecting the device logs.
Reproduce the issue.
Note the approximate time it occurred.
Save the relevant logs.
The amount of additional information depends on the selected scope and the activity being tested.
Remove the temporary setting
Create a new HTTP request.
Set the method to DELETE.
Enter:
http://[DEVICE-IP-ADDRESS]:2020/v2/debug_verbosity/scopes/inputs
Replace inputs with the scope you changed.
Do not include a request body.
Select Send.
Confirm removal
Run the scopes GET request again:
http://[DEVICE-IP-ADDRESS]:2020/v2/debug_verbosity/scopes
Confirm that the scope returned to the default level and no longer appears under scope_overrides.
Changes made through these REST endpoints are temporary and are also cleared when the device reboots.
Recommended workflow
Check the current logging level.
Enable
DEBUGfor the affected device area.Begin collecting the device logs.
Reproduce the issue
Save the relevant logs.
Remove the temporary setting.
Confirm that logging returned to normal.
Troubleshooting
Problem |
Resolution |
The API returns 404 Not Found
|
Include port 2020 in the REST API URL |
| Logs remain detailed after lowering the global level of verbosity | Check for an active scope or component setting that increases the verbosity of logs |
| A log verbosity setting disappears after reboot | This is expected; REST logging changes are only intended to be temporary |
| A component name is rejected | Retrieve the current list with GET :2020/v2/debug_verbosity/components
|
| Too many logs are produced | Remove the override or use a lower logging level |
Best practices
Prefer a specific scope instead of setting the whole device to
TRACE.Use
DEBUGorTRACEonly while reproducing an issue.Remove temporary settings after collecting logs.
Restrict REST API access to trusted users and networks.
Review logs for sensitive information before sharing them
FAQ
Q: Do logging changes remain after reboot?
A: No. A reboot clears changes made through these REST endpoints and restores the startup logging level.
Q: Does changing the logging level interrupt an active stream?
A: The logging controls do not change the normal stream or encode path.
Q: Why do I still see DEBUG messages after changing the whole device to ERROR?
A: A more specific scope or component setting may still be set to DEBUG.
Q: Should I use TRACE?
A: Use TRACE only when necessary because it creates the most log output and may include sensitive detail.