> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview/use-cases/central-logging/enable-non-default-tenant-logging.md).

# Enable Non-Default Tenant logging

Enable log collection for non-Default DuploCloud Tenants

Enable logging to deploy AWS Log Collector to collect logs for selected Tenant(s). Once logging is enabled for Tenant(s), you can configure log collection, tailoring your log data to display only relevant information.

## Prerequisites

* Before configuring logging per Tenant, [set up central logging](/docs/automation-platform/overview/use-cases/central-logging/central-logging-setup.md) for the Default Tenant.

## Enabling Logging for Non-Default Tenants

Configure AWS Log Collector to collect logs for non-Default Tenants.

1. From the DuploCloud Portal, navigate to **Administrator** -> **Observability** -> **Standard** -> **Settings**.
2. Select the **Logging** tab, and click **Add**. The **Enable Logging** pane displays.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FB2ra1eFYGgZBEBuZYUTA%2Fnewnew.png?alt=media&amp;token=306de51d-1532-449f-9dd5-7f8ee188caad" alt=""><figcaption><p>The <strong>Enable Logging</strong> pane in the DuploCloud Portal</p></figcaption></figure>

3. In the **Select Tenant** list box, select the Tenant for which you want to enable log collection.
4. In the **Cert ARN** list box, select the correct ARN.
5. In the **Log retention in Index(Days)** field, enter the number of days logs should be retained.
6. Click **Submit**. Log collection for the selected Tenant deploys based on the [Control Plane configuration](/docs/automation-platform/overview/use-cases/central-logging/custom-log-collection.md#updating-the-control-plane-by-editing-the-service-description).<br>

   <figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FSFS8l5an9jKL5VWdvJyE%2Fimage.png?alt=media&amp;token=580e27a3-3ed6-48c2-949f-c3ab8d065ee6" alt=""><figcaption><p>The <strong>Logging</strong> tab on the <strong>Observability Settings</strong> page in the DuploCloud Portal</p></figcaption></figure>

Once logging is enabled, you can [configure logging per Tenant](/docs/automation-platform/overview/use-cases/central-logging/configure-logging-per-tenant.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/automation-platform/overview/use-cases/central-logging/enable-non-default-tenant-logging.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.