← All updates Databricks Update One-Pager Navy version
databricks Platform · Updated Jun 1, 2025

The sourceIpAddress field in audit logs will no longer include a port number

Due to a bug, certain authorization and authentication audit logs include a port number in addition to the IP in the sourceIPAddress field (for example, "sourceIPAddress":"10.2.91.100:0").

What it does

Due to a bug, certain authorization and authentication audit logs include a port number in addition to the IP in the sourceIPAddress field (for example, "sourceIPAddress":"10.2.91.100:0"). The port number, which is logged as 0, does not provide any real value and is inconsistent with the rest of the Databricks audit logs. To enhance the consistency of audit logs, Databricks plans to change the format of the IP address for these audit log events.

Why it matters

Reduces operational overhead and unlocks new capabilities for data teams on Databricks.

Architecture
Databricks Platform → Platform
In short

Due to a bug, certain authorization and authentication audit logs include a port number in addition to the IP in the sourceIPAddress field (for example, "sourceIPAddress":"10.2.91.100:0"). The port number, which is logged as 0, does not provide any real…

Read the full documentation ↗
Key takeaway
Due to a bug, certain authorization and authentication audit logs include a port number in addition to the IP in the sourceIPAddress field (for example, "sourceIPAddress":"10.2.91.100:0").
2025-06-01-the-sourceipaddress-field-in-audit-logs-will-no-longer-include-a-port-number Generated by the Databricks Updates Agent · browse all updates