- 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 made to the control plane.
- Actions performed directly on the execution plane, such as fabric, connection, deployment, pipeline run, and schedule operations.
Prophecy uses GraphQL for control plane 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
Execution plane events
Prophecy audit logs also capture actions performed directly on the execution plane (the orchestrator service running in your environment), not just control plane GraphQL calls. These events are recorded locally on the execution plane first, then forwarded to the control plane in batches (every 30 minutes by default). As a result, there’s a short delay between an execution action occurring and its event appearing in the central audit log.Execution plane events are identified by a fixed event type and category rather than a GraphQL query name.
Authentication and identity
Fabric
Connections and secrets
Deployment and pipeline runs
Schedules
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
- Open the Amazon S3 console and choose Create bucket.
-
Enter a Bucket name, following the format
prophecy-customer-backend-events-foo. Replacefoowith an identifier for your organization. -
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.
- Complete the remaining setup options as needed, then create the bucket.
- 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
- In the Amazon S3 console, open your bucket and choose the Permissions tab.
- Under Bucket policy, select Edit.
- Paste the following policy JSON, replacing the placeholders as described below.
- Replace all instances of
prophecy-customer-backend-events-xyzwith your bucket ARN. - The Prophecy IAM user
s3accessrequires theDataSyncCreateS3Locationrole to create S3 locations in Prophecy’s account. - After applying the policy, contact Prophecy and provide:
- Your bucket ARN.
- The AWS region.

