Hi @kapa.ai, we recently upgraded our airbyte platform version to 1.8.5. Deployment is working smoothly though we did notice that the UI is only outputting logs from the upgrade onward (i.e., older logs, while still existing in the postgresql DB, are not being displayed in the new airbyte server UI). Is this due to changes in the log format (previously it was plain text file while the new ones are json)?

The knowledge sources don't contain enough specific information to definitively confirm the root cause of your issue, but based on what's available, your hypothesis is plausible. Starting with data plane Helm chart version 2.1.0, structured JSON logging to stdout is enabled by default (

PLATFORM_LOG_FORMAT=json

). Earlier chart versions emit plaintext logs, and the log format setting is not propagated to all containers in those older versions. [Log Collection] This format change could explain why the UI is unable to parse and display older plaintext logs — if the new Airbyte server expects JSON-formatted log entries, it may simply not be able to render the legacy plaintext format correctly. A few things worth noting: • The logs themselves are not stored in PostgreSQL — Airbyte stores logs in blob storage (e.g., MinIO, S3, GCS). The PostgreSQL database stores metadata about jobs and connections, not the raw log content. So the issue is likely about how the UI reads and renders log files from blob storage, not about DB access. • There was a known issue with MinIO logging being broken in Helm chart 1.2.0, though that was a different scenario. [MinIO Logging Issue] • There is also an open issue about stack traces being logged as arrays in JSON mode, which can cause problems when shipping logs to external systems. [JSON Logging Issue] Recommended next steps: 1. Verify your blob storage configuration is intact and that old log files are still accessible at their original paths. 2. Check whether the log file format (plaintext vs. JSON) changed between your old and new versions, and whether the new UI log viewer expects a specific format. 3. Review the Airbyte server and worker pod logs for any errors related to log retrieval or parsing. For a more definitive answer, I'd recommend reaching out on the Airbyte Community Slack or opening a GitHub issue with your specific version details, as this appears to be a nuanced upgrade scenario not fully covered in the available documentation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.