LogoLogo
  • Digital River commercetools 1.0
    • System Requirements
    • Upgrade path
  • Understand the Digital River commercetools integration
    • Understand the integration workflow
    • Features
    • What’s new for Digital River's commercetools integration 1.0
  • Install and configure the Digital River commercetools integration
  • Create integration access keys
  • Configure the integration
    • Configure Digital River in Dashboard
    • Configure commercetools
    • Map shared data used in the integration
  • Deploy the integration
    • Understand integration environment variables
  • Use the commercetools Merchant Center custom application
    • Install and deploy the Merchant Center custom application
    • Configure the Merchant Center custom application
    • Integrate with a store for payments
    • Configure shipping methods
    • Enable customer management options
    • Understand integration logs
    • Merchant Center custom application user guide
      • Authorize a payment
      • Cancel an authorization
      • Capture a payment
      • Use the demo store custom application
      • Refund a payment
  • Support
Powered by GitBook
On this page
  • Use standard logging
  • Use enhanced logging
  1. Use the commercetools Merchant Center custom application

Understand integration logs

Learn how commercetools logging works with Digital River.

The integration supports both standard and enhanced logging.

Use standard logging

The following shows an example of the log activity resulting from a request made by the integration to the Digital River API:

DR API POST to https://api.digitalriver.com/drop-in/checkout-sessions returned 201
Headers: Accept=[application/json], Authorization=**redacted**, Content-Type=[application/json]
Request id: [8fee28ff-9c04-44d9-8264-96d5c7f23711]

The Request id can be used to cross-reference with the Digital River API logs.

Use enhanced logging

You can also log the request and response payloads by setting the log level property or an environment variable.

The following is an example of using the log level property to set the logging level:

quarkus.log.category."com.e2x.digitalriverct.digitalriver.client.filter".level

The following example uses an environment variable to set the level to DEBUG:

QUARKUS_LOG_CATEGORY__COM_E2X_DIGITALRIVERCT_DIGITALRIVER_CLIENT_FILTER__LEVEL

This example MUST NOT be enabled in production as the payloads will contain PII.

PreviousEnable customer management optionsNextMerchant Center custom application user guide

Last updated 2 years ago