The Dgraph creates several logs, although some of these logs depend on your implementation and the components that you may be using. This topic provides a summary of these logs.
You can use these Dgraph logs to troubleshoot queries, or to track performance of particular queries or updates.
The Dgraph request log is always created. You can use it to debug both requests and update processing. It contains one entry for each request processed. The requests are sorted by their timestamp.
The name of the Dgraph request log is dataStoreName.reqlog (where dataStoreName is the name of the Endeca data store that the Dgraph is servicing). By default, the request logs are stored in the Endeca Server's logs directory. Note that you can customize the location of the logs directory. The /admin/dataStoreName?op=logroll command forces a request log roll, with the side effect of remapping it.
By default, the Dgraph truncates the contents of the body for POST requests at 64K. This default setting saves disk space in the log, especially during the process of adding large numbers of records to the data store. If you need to review the log for the full contents of the POST request body, contact Endeca Support.
The name of the Dgraph stdout/stderr log is dataStoreName.out. By default, the stdout/stderr logs are also stored in the Endeca Server's logs directory.
The Dgraph stdout/stderr log includes startup messages as well as warning and error messages. You can increase the verbosity of the log via the Dgraph -v flag.