A customer has reported an issue regarding the aggregated log viewer for a specific pod.

1. The logs are initially displayed in JSON format when the view is first loaded.
2. However, when the user refreshes the view or changes the time interval, the logs switch to a completely raw/unformatted output.

The expected behavior is that the JSON format should persist after refresh or interval changes.

The customer has not yet confirmed the exact version of their COO (Cluster Observability Operator). However, upon testing this behavior on our lab cluster running COO v1.3.0, the issue is present and reproducible.

As a workaround, we found that appending `| json` to the log query successfully resolves the issue by forcing the output back into the correct format.