You can ensure your gateway is actively exchanging messages with your local blockchain node and the BDN network by monitoring your gateway and inspecting logs.
Setting log level
Use the parameter log-file-level to configure the amount of data logged in the Gateway log file, and use log-level to configure the amount of data logged to standard output.
The Gateway’s common log levels and the possible values for these two flags are listed below in order from most verbose (TRACE) to least verbose (ERROR). The default log level is INFO.
TRACE, DEBUG, INFO, WARN, ERROR
Accessing the log files
The log files can be found in the logsdirectory of the Docker container (as specified with the Docker command or the startup script). The most recent log file is named gateway-[external port of gateway].log.
Older log files are named gateway-[external port of gateway]-[end timestamp].log.
Analyzing transaction receipt
Your Local Gateway includes a logging utility that helps you analyze when the gateway received important transactions and the source of such transactions.
For each transaction received, the utility records the time the transaction is first received by the gateway and the source from which the gateway received it. To enable this utility, add the parameter txtrace to your startup argument when you start the gateway.