# Audit Logs **Sync Type: Incremental** ## Overview The Akuity Audit Logs input collects comprehensive audit trail data from your Akuity Platform organization, providing visibility into organizational events, user actions, and system changes. This integration captures detailed logs including resource modifications, user activities, access patterns, timestamps, and actor information across your Akuity Portal. ## Prerequisites ### 1. Akuity Platform Account You must have access to an **Akuity Platform Account** with appropriate permissions to create API keys and access audit logs for your organization. **Important Security Note:** Audit logs contain sensitive organizational data including user actions, resource changes, and system events. Ensure proper access controls are in place when configuring this integration and follow the principle of least privilege when creating API keys. ## API Key Setup 1. **Navigate to Organization Settings** - Log into your [Akuity Platform](https://akuity.cloud). - Select your organization from the dropdown menu in the top navigation bar. - Click on **Organization** in the left navigation panel. 2. **Access API Keys Section** - Navigate to the **API Keys** tab within Settings 3. **Create New API Key** - Click the **+ New Key** button. - Provide a descriptive name for the key (e.g., "Monad Audit Logs Integration"). - Optionally add a description explaining the key's purpose. - Assign an appropriate role with permissions to read audit logs. 4. **Save and Store Credentials** - After creation, copy both the **API Key ID** and **API Key Secret**. - Store these credentials securely - the secret will not be displayed again. - Both values are required for authentication. ## Configuration ### Settings | Setting | Type | Required | Description | |---------|------|----------|-------------| | Organization ID | string | true | The unique identifier of your Akuity organization. Found in the organization settings or URL. | | Backfill Start Time | string | No | The date to start fetching data from. If not specified, no past records will be fetched. | | API Rate Limit | object | No | Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See [API Rate Limiting](../../../guides/rate-limiting) for the field format, limits, and how to choose a value. | ### Secrets | Setting | Type | Required | Description | |---------|------|----------|-------------| | API Key ID | string | true | The API Key ID from your Akuity Platform API key | | API Key Secret | string | true | The API Key Secret from your Akuity Platform API key | ## Authentication This integration uses HTTP Basic Authentication with the Akuity Platform API: - **Username:** API Key ID - **Password:** API Key Secret The credentials are automatically encoded and sent in the `Authorization` header as `Basic `. ## Data Collection - Audit logs are collected incrementally based on timestamp. - Logs include actions such as resource creation, deletion, updates, and access events. - Each log entry contains timestamp, action type, actor information, and affected resources. ## Related Articles - [Akuity Platform API Documentation](https://docs.akuity.io/api/) - [Akuity Platform API Keys](https://docs.akuity.io/organizations/api-keys) ## Sample Record ```json { "action": "deleted", "actor": { "id": "Sarah Brown@akuity.io", "ip": "132.226.61.247", "type": "api_key" }, "count": 9, "details": { "actionType": "DELETE", "message": "Resource successfully created", "patch": "" }, "lastOccurredTimestamp": "2025-11-21 16:26:40.13921 +0000 UTC", "object": { "id": { "group": "argoproj.io", "kind": "Cluster", "name": "dev-team" }, "parentId": { "applicationName": "web-app", "name": "", "parentName": "" }, "type": "custom_role" }, "timestamp": "2025-11-21 16:26:40.13921 +0000 UTC" }