Logging and Telemetry¶
JumpMind Commerce (JMC) provides various mechanisms for logging and collection of application telemetry data. The configuration of OpenTelemetry, while more complex than other options, provides full telemetry data including logging, tracing and metrics. If the retailer has no infrastructure to support OpenTelemetry, simple application logging, database query logging and service sample logging can be individually configured, captures and reviewed.
Application Logging¶
Application logging is provided and configured through Logback. Logback is a logging framework that provides a fast, reliable, and highly configurable solution for generating logs. Logback is one of the most widely used logging frameworks in the Java community. See the Application Logging page for additional information on configuring both server and client logging.
Database Query Logging¶
JMC provides a JDBC driver that wraps other database drivers and provides out of the box statement logging and logging for statements that run longer than a configured period. This type of logging can be helpful for troubleshooting database or environmental problems that can prevent the application from running optimally. See the Database Logging page for additional information on configuring and accessing database query logs.
Service Sampling¶
Core functionality in JMC is provided by services. Service sampling provides lightweight telemetry data about service calls within the application. This is not full-blown telemetry, but is a simple and easy way to get information specifically about service call timing. See the Service Sampling documentation page for additional information on configuring and accessing Service Sampling.
Detailed Telemetry through OpenTelemetry¶
JMC also supports OpenTelemetry (OTel). OTel is a vendor-neutral open source Observability framework for instrumenting, generating, collecting and exporting telemetry data such as traces, metrics and logs. As an industry-standard, OTel is supported by more than 40 observability vendors, integrated by many libraries, services and apps, and adopted by numerous end users.
Observability lets us understand the JMC application from the outside, by allowing the implementer to ask questions about the running application without knowing its inner workings. In addition, it allows us to easily troubleshoot and handle problems, and helps us answer the question, “Why is this happening?”
JumpMind supports this observability by properly instrumenting the application and emitting signals such as traces, metrics, and logs using and following the OTel tools and standards. Additional information on Otel can be found here. See the Open Telemetry page for additional information on configuring JMC for Otel.