#9842 docs: Clarify Google Cloud Logging severity mapping with Ops Agent Pull request opened by prajwalsanjayshinde Description This PR clarifies how Meltano logs behave when ingested into Google Cloud Logging (formerly Stackdriver). Specifically, it explains why Meltano logs may show

"level": "info"

even when warnings or errors occur, due to Meltano normalizing logs from plugins and subprocesses. The documentation now includes: • Clear explanation of the expected logging behavior in Google Cloud Logging • Guidance on why severity-based filtering may not work out of the box • A working example configuration using the Google Cloud Ops Agent to parse JSON logs and explicitly map log severity This should help users avoid confusion and correctly configure severity-based alerts and filters when running Meltano on GCP. Checklist • I have read the contribution guide Was generative AI tooling used to co-author this PR? • Yes (Chat GPT) Related Issues • Related to #9420 Summary by Sourcery Clarify how Meltano JSON logs are handled by Google Cloud Logging and document configuration to correctly map log severity when using the Google Cloud Ops Agent. Documentation: • Explain Meltano log normalization behavior and its impact on severity levels in Google Cloud Logging. • Document an example Google Cloud Ops Agent configuration to parse Meltano JSON logs and map severity for filtering and alerts. meltano/meltano