Skip to content

Commit 10825b5

Browse files
authored
Update sql-database-audit-log-format.md
1 parent 1c1c692 commit 10825b5

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/sql-database/sql-database-audit-log-format.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ For example, for database `Database1` on `Server1` the following is a possible v
2626

2727
Server1/Database1/SqlDbAuditing_ServerAudit_NoRetention/2019-02-03/12_23_30_794_0.xel
2828

29+
Read-only Replica Audit logs are stored in the same container. The directory hierarchy within the container is of the form `<ServerName>/<DatabaseName>/<AuditName>/<Date>/RO/`. The Blob filename shares the same format.
30+
2931
### Event Hub
3032

3133
Audit events are written to the namespace and event hub that was defined during auditing configuration, and are captured in the body of [Apache Avro](https://avro.apache.org/) events and stored using JSON formatting with UTF-8 encoding. To read the audit logs, you can use [Avro Tools](https://docs.microsoft.com/azure/event-hubs/event-hubs-capture-overview#use-avro-tools) or similar tools that process this format.
@@ -84,4 +86,4 @@ Audit events are written to Log Analytics workspace defined during auditing conf
8486

8587
## Next Steps
8688

87-
Learn more about [Azure SQL Database auditing](sql-database-auditing.md).
89+
Learn more about [Azure SQL Database auditing](sql-database-auditing.md).

0 commit comments

Comments
 (0)