Skip to main content
This page describes how Prophecy generates, stores, and shares audit logs for Prophecy deployments. Use this information to decide if you need to enable and export audit logs. Setting up audit logs requires collaboration with Prophecy. Contact Prophecy to:
  • Enable audit logging in Prophecy-managed storage.
  • Export audit logs on demand.
  • Configure automatic syncing to your own storage.
  • Set a custom retention period for stored logs (by default, logs are stored indefinitely).

Storage location

Prophecy stores audit logs in the same cloud platform as your deployment:
  • For AWS deployments, audit logs are stored in Amazon S3.
  • For Azure deployments, audit logs are stored in Azure Blob Storage.
  • For Google Cloud Platform deployments, audit logs are stored in Google Cloud Storage.

Audit event reference

When audit logs are enabled for your Prophecy deployment, they capture the following information:
  • User interactions with the Prophecy UI
  • GraphQL API calls
The following tables list the audit events that Prophecy logs, organized by entity type.
Prophecy uses GraphQL for API operations. Request and response parameters may vary depending on where you call the query.

Fabric

Project

Pipeline

Job

Dataset

Team

User

Git

Transpiler

Generic

Sync data to S3

If your Prophecy deployment is hosted on AWS, you can sync your Prophecy audit logs to your own Amazon S3 bucket. Follow these steps to configure your S3 bucket and grant Prophecy the required access.

1. Create the S3 bucket

  1. Open the Amazon S3 console and choose Create bucket.
  2. Enter a Bucket name, following the format prophecy-customer-backend-events-foo. Replace foo with an identifier for your organization.
  3. Choose a Region.
    • Prophecy recommends us-east-1 (N. Virginia) for best performance.
    • If you select a different region, contact Prophecy so we can accommodate this preference.
  4. Complete the remaining setup options as needed, then create the bucket.
  5. Set Object Ownership to ACLs disabled (recommended). You can apply this setting during bucket creation or by editing bucket permissions after creation.

2. Configure bucket permissions for Prophecy

  1. In the Amazon S3 console, open your bucket and choose the Permissions tab.
  2. Under Bucket policy, select Edit.
  3. Paste the following policy JSON, replacing the placeholders as described below.
To use this example JSON:
  • Replace all instances of prophecy-customer-backend-events-xyz with your bucket ARN.
  • The Prophecy IAM user s3access requires the DataSyncCreateS3Location role to create S3 locations in Prophecy’s account.
  • After applying the policy, contact Prophecy and provide:
    • Your bucket ARN
    • The AWS region
Prophecy will complete the configuration and enable syncing for your environment.