# Audit Logs and Connector Events Billing Confluent Cloud audit logs and [connector events](../../connectors/logging-cloud-connectors.md#ccloud-connector-logging) are both captured in the `confluent-audit-log-events` topic on an independent Audit Log cluster. Because they share that topic, Confluent bills them together as a single dimension. | Dimension | Unit of measure | |---------------------------------|------------------------------------------------| | Audit logs and connector events | Cost per GB of data read from audit log topics | You’re charged for data you read from the audit log topic, not for the events Confluent Cloud writes to it. Consumption charges for connector events and audit logging are combined on your bill. Confluent Cloud keeps audit log records for a default of seven days. Extending retention means exporting the records to an external Apache Kafka® cluster or other data store, typically with a self-managed sink connector. That export counts as a read from the audit log topic, and the destination cluster incurs its own ingress and storage charges. For more information, see [Retain Audit Log Records on Confluent Cloud](../../monitoring/audit-logging/retain-audit-logs.md#retain-audit-log-records). ## Related content - [Audit Logs overview](../../monitoring/audit-logging/cloud-audit-log-concepts.md#cloud-audit-logs) - [View Connector Events](../../connectors/logging-cloud-connectors.md#ccloud-connector-logging) - [FAQ for Confluent Cloud Billing](../billing-faq.md#billing-faq)