Send Docs Feedback

Enabling debug logging

Edge for Private Cloud v. 4.17.05

You can enable debug logging for several Edge components. When you enable debug logging, the component writes debug messages to its system.log file.

For example, if you enable debug logging for the Edge Router, the Router writes debug messages to:


Enabling debug logging can cause the system.log file for a component to grow very large in size, and can affect the overall system performance. It is recommended that you enable debug logging for only as long as necessary, and then disable it. 

Use the following API call to enable debug logging for a component:

curl -X POST "http://localhost:PORT/v1/logsessions?session=debug"

To disable debug logging:

curl -X DELETE "http://localhost:PORT/v1/logsessions/debug"

Notice that these two calls do not take credentials and refer to localhost. These API calls must be run on the server hosting the Edge components; they cannot be run remotely.  

Each Edge component that supports debug logging uses a different port number in the API call, as shown in the following table:



Log file

Management Server 8080 /opt/apigee/var/log/edge-management-server/logs/system.log
Router 8081 /opt/apigee/var/log/edge-router/logs/system.log
Message Processor 8082 /opt/apigee/var/log/edge-message-processor/logs/system.log
Qpid Server 8083 /opt/apigee/var/log/edge-qpid-server/logs/system.log
Postgres Server 8084 /opt/apigee/var/log/edge-postgres-server/logs/system.log


Help or comments?