Improved CloudWatch logs ingestion​

The Cloud.gov team is updating how CloudWatch logs (e.g. brokered database logs) are ingested into Cloud.gov Logs. This change will provide quicker and more reliable access to CloudWatch logs and enable faster addition of new CloudWatch log groups for brokered services.

Temporary duplicate logs during transition​

To ensure a safe migration with no log outages, we will run both the old and new ingestion methods in parallel during the transition. This approach means you will temporarily see duplicate CloudWatch logs in your dashboards and searches.

How to identify the new logs​

The new CloudWatch logs can be identified by the @type: cloudwatch field. These logs will continue to appear in the logs-app* indices as before.

Timeline​

• Parallel ingestion period: The old and new ingestion methods will run simultaneously until November 12, 2025
• Old system shutdown: On November 12, 2025, the old ingestion method will be disabled

If any issues arise which require extending the parallel ingestion period, we will update this document.

Action required: Update your custom visualizations and dashboards​

During the transition period, please:

• Disregard duplicate logs in your searches and dashboards
• Update all visualizations and dashboards that use CloudWatch logs to reference the new logs (those with @type: cloudwatch)
• Prepare for the old duplicate logs to stop appearing after the transition period ends

For questions about this migration, please contact support@cloud.gov.