> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/salesforce-b2b/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/salesforce-b2b/2.1.0/integrating-the-digital-river-salesforce-b2b-commerce-app/step-14-configure-the-digital-river-app-logs.md).

# Step 14: Configure the Salesforce B2B Commerce app logs

All the Salesforce B2B Commerce app application logs are logged to a custom object called **DCM Application Logs “digitalriverv2\_\_DCM\_Application\_Log\_\_c**”. The default logging level is always set to **DEBUG**. It is recommended to switch it to **ERROR** for production, that is, to only log errors.

To configure the default logging level for the app:

1. From the Setup menu, open Custom Metadata Types, then click to open the DCM Application Log Configuration type.\
   ![](/files/-MSnrBC6tcof7CFBHy_z)
2. Click **Manage DCM Application Log Configurations**. \
   ![](/files/-MRVVKfw2N2FaZWgpBlG)
3. Click the **Default App Log Config**. \
   ![](/files/-MRVVSnWssgB6r7jDuJO)
4. Configure the default logging level for the app logging in the **Logging Level** field.\
   ![](/files/-MRVVbjnrN3Ceg3p-7D7) \
   **Note:** There is another **Log Level** field that is deprecated and should no longer be used.
5. Add all the users, including the storefront user, to the DRB2B Permission Set so they can log to the DCM Application Log object. The DCM Application Log Cleanup job uses the **Delete Logs Older Than** field to clean up old logs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/salesforce-b2b/2.1.0/integrating-the-digital-river-salesforce-b2b-commerce-app/step-14-configure-the-digital-river-app-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.