---
schema_version: "1"
id: bdec3691f77b74fbefb751b9d6d5ff9e52250f54eb01180af1547ed1c5920d7e
title: Accessing Anypoint MQ Audit Logs
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mq/mq-audit-logs.md
canonical_url: https://docs.mulesoft.com/mq/mq-audit-logs
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 10252f4c160c4ce580d9074e5873ab21e5955253035ff0247b781dc5cead47b5
description: MuleSoft Documentation Site
latest: true
---
---
product: MQ
---

# Accessing Anypoint MQ Audit Logs

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The Anypoint Platform audit logging service logs Anypoint MQ actions on queues, exchanges, and
client applications.

With the **Organization Administrator** or **Audit Log Viewer** role, you can access the audit logs
relevant to your business group from the **Audit Log** page in Access Management or using the Audit
Log REST API.

For example, you might use the audit logs to determine:

- All Anypoint MQ actions of a user

- All Anypoint MQ actions on an object, such as a queue or exchange

> [!NOTE] The audit logging service doesn’t record these actions as auditable:
>
> - Sending, receiving, or browsing messages
>
> - Failed Anypoint MQ operations

## Access Anypoint MQ Audit Logs

To access Anypoint MQ audit logs:

1.  In Anypoint Platform, go to **Access Management**.

2.  From the **Access Management** navigation menu, select **Audit Logs**.

3.  Select filters and click **Apply filters**:

    Products

    **Anypoint MQ**

    Types

    **Binding**, **Client**, **Exchange**, **Queue**

    Actions

    - Binding: **Create binding**, **Delete binding**

    - Client: **Create client**, **Delete client**, **Regenerate client**

    - Exchange: **Create exchange**, **Delete exchange**, **Modify exchange**

    - Queue: **Create queue**, **Delete queue**, **Modify queue**, **Purge queue**

    You can also search by environment, object name, or user.

    The **Audit logs** page displays the logs:

    ![Filters, Apply filters button, current filters, and Download payload button on the Audit logs page](/mulesoft/current/en-us/mq/_images/mq-access-mgmt-audit-logs.png)

    <table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>Select filters.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>Apply filters.</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td>View current filters.</td></tr><tr><td><i data-value="4"></i><b>4</b></td><td>Download payload.</td></tr></tbody></table>

### Payloads

A _payload_ is a JSON-formatted text file that lists the Anypoint MQ settings in place when the
action occurs.

For each action on the **Audit Log** page, click the **Download payload** icon
(![](/mulesoft/current/en-us/mq/_images/icon-download-payload.png)) to download a payload file (`payload.txt`).

This example shows a formatted version of the contents of `payload.txt` after creating a queue:

```json
{
  "organizationId": "<organizationID>",
  "environmentId": "<enviromentID",
  "objectName": "testQ",
  "userName": "myUserName",
  "objectId": "testQ",
  "regionId": "us-east-1",
  "defaultTtlMillis": 604800000,
  "defaultLockTtlMillis": 180000,
  "encrypted": true,
  "deadLetterQueueId": "myDLQ",
  "maxDeliveries": 10,
  "fifo": false
}
```

The possible fields in `payload.txt` are:

<table><colgroup><col> <col></colgroup><thead><tr><th>Field</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p><code>organizationId</code></p></div></div></td><td><div><div><p>Organization ID for the current Anypoint Platform account</p></div><div><p>You can use the organization ID to access Anypoint MQ REST APIs.</p></div></div></td></tr><tr><td><div><div><p><code>environmentId</code></p></div></div></td><td><div><div><p>Environment ID for the current Anypoint Platform account</p></div><div><p>You can use the environment ID to access Anypoint MQ REST APIs.</p></div></div></td></tr><tr><td><div><div><p><code>objectName</code></p></div></div></td><td><div><div><p>Name of the queue, exchange, or client application</p></div></div></td></tr><tr><td><div><div><p><code>userName</code></p></div></div></td><td><div><div><p>Username for the Anypoint Platform account</p></div></div></td></tr><tr><td><div><div><p><code>objectId</code></p></div></div></td><td><div><div><p>Name of the queue, exchange, or client application</p></div><div><p>The <code>objectID</code> is the same value as <code>objectName</code>.</p></div></div></td></tr><tr><td><div><div><p><code>regionId</code></p></div></div></td><td><div><div><p>Region location where you process your Anypoint MQ connections</p></div></div></td></tr><tr><td><div><div><p><code>defaultTtlMillis</code></p></div></div></td><td><div><div><p>Default time to live (in milliseconds)</p></div><div><p>This value specifies how long unprocessed messages persist before being deleted.</p></div></div></td></tr><tr><td><div><div><p><code>defaultLockTtlMillis</code></p></div></div></td><td><div><div><p>Default lock time to live (in milliseconds) for the queue or exchange you create</p></div><div><p>This value specifies the duration that a message is unavailable to other applications before being put back into the queue.</p></div></div></td></tr><tr><td><div><div><p><code>encrypted</code></p></div></div></td><td><div><div><p>Whether the queue or message exchange is encrypted</p></div><div><p>If you configure Anypoint MQ queues for encryption at rest, the payloads are encrypted with the AES-256 GCM algorithm on the server side.</p></div><div><p>Anypoint MQ encrypts only the message body. Anypoint MQ does not encrypt the <code>headers</code> or <code>properties</code> of messages sent to exchanges and queues.</p></div></div></td></tr><tr><td><div><div><p><code>deadLetterQueueId</code></p></div></div></td><td><div><div><p>Name of the dead letter queue to which the current object is associated</p></div></div></td></tr><tr><td><div><div><p><code>maxDeliveries</code></p></div></div></td><td><div><div><p>How many times Anypoint MQ tries to deliver messages in the queue before rerouting the message to the dead letter queue</p></div></div></td></tr><tr><td><div><div><p><code>fifo</code></p></div></div></td><td><div><div><p>Whether the queue is a FIFO queue (<code>true</code>) or not (<code>false</code>)</p></div><div><div data-type="NOTE">This field is set to <code>true</code> at the time you create the FIFO queue. Subsequent changes to a FIFO queue set the <code>fifo</code> field to <code>null</code>.</div></div></div></td></tr></tbody></table>

## See Also

- [Audit Logging](https://docs.mulesoft.com/access-management/audit-logging)

- [FIFO Queues](https://docs.mulesoft.com/mq/mq-queues#fifoqueues)

- [Anypoint MQ REST APIs](https://docs.mulesoft.com/mq/mq-apis)

- [Audit Log Query API](https://dev-portal.mulesoft.com/apis/audit-log-query.html)