fix: remove timestamp rounding in TerseJsonFormatter

The round(record.created, 2) call limits timestamps generated by
TerseJsonFormatter to 10ms precision. This can cause log ordering issues
in log aggregators like Loki when multiple events occur within the same
10ms window.

The rounding was introduced in the original structured logging PR and,
to my knowledge, has no technical benefit.

changelog.d/19297.misc

@@ -0,0 +1 @@
+Log the original bind exception when encountering `Failed to listen on 0.0.0.0, continuing because listening on [::]`.

synapse/app/__init__.py

@@ -54,7 +54,9 @@ def check_bind_error(
     """
     if address == "0.0.0.0" and "::" in bind_addresses:
         logger.warning(
-            "Failed to listen on 0.0.0.0, continuing because listening on [::]"
+            "Failed to listen on 0.0.0.0, continuing because listening on [::]. Original exception: %s: %s",
+            type(e).__name__,
+            str(e),
         )
     else:
         raise e

synapse/logging/_terse_json.py

@@ -89,7 +89,7 @@ class TerseJsonFormatter(JsonFormatter):
             "log": record.getMessage(),
             "namespace": record.name,
             "level": record.levelname,
-            "time": round(record.created, 2),
+            "time": record.created,
         }
 
         return self._format(record, event)