BDT Logging
Logs contain information about the events happening inside your application. Logs can be very helpful when trying to troubleshoot a problem. The BDT logging framework is designed in such a way that it can be integrated with most of the third-party external loggers such as Splunk and Datadog. The BDT logs are captured on the console. Users are free to choose any logging agent that works with the containerized solutions. A logging agent fetches the logs from the BDT console and pushes them to the user configured environment.
Application logs: Capture implementation level details required by the developer to understand what happened or how the application responded during a specific event. The application logs are printed in text format. Click here to know more.
Log level specifies the level of logging to be performed by the application. Following table describes the supported log levels with their description.
| Log Level | Description |
|---|---|
| INFO | Records error messages, warnings, and informational messages. |
| WARN | Records error messages and warnings. |
| ERROR | Records only error messages. |
| DEBUG | Records diagnostic information. |
These log levels are configurable and can be changed from the CipherTrust Manager UI.
Format of Application Log
The log format determines how the contents of a log should be interpreted. Below is the sample of an application log:
bdt | 2025-01-15 08:53:30:577 INFO [main] - BDT is registered successfully on key manager
bdt | 2025-01-15 08:53:30:578 WARN [main] - Connection not secure
bdt | 2025-01-15 08:53:30:598 INFO [main] - Started HTTP server on port 80
