From 13aa55a2e27562d642b3b7e33be8b279bef253ef Mon Sep 17 00:00:00 2001 From: Peter Burkholder Date: Fri, 22 Nov 2024 10:33:46 -0500 Subject: [PATCH] trim intro so full URL is in summary (#2571) --- _posts/2024-11-21-new-logging-system.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2024-11-21-new-logging-system.md b/_posts/2024-11-21-new-logging-system.md index 753002479..86c2c5e74 100644 --- a/_posts/2024-11-21-new-logging-system.md +++ b/_posts/2024-11-21-new-logging-system.md @@ -8,7 +8,7 @@ excerpt: The Cloud.gov is upgrading the current application logging system in De # Cloud.gov customer notice: Major upgrade of application logging system in December -Cloud.gov is upgrading the current application logging system, , with a more capable and performant system in December 2024. We're excited by the new capabilities this logging system affords, and we're confident our customers will appreciate the improved performance and new features. +Cloud.gov is upgrading our logging system, , with a more capable and performant system in December 2024. We're excited by the new capabilities this logging system affords, and we're confident our customers will appreciate the improved performance and new features. The significance of the update requires a cutover from the current system to the new one that will take place on the following timeline: @@ -53,4 +53,4 @@ We recommend you take the following actions: ## Deprecation notice -The [Cloud.gov deprecation policy](http://cloud.gov) calls for a longer transition period between services than we're employing here, unless continuing that service poses risks to the platform. Since the current logging system uses components that are reaching EOL, continued operation poses security and compliance risks, and we are moving to decommission the service by January 10, 2025. \ No newline at end of file +The [Cloud.gov deprecation policy](http://cloud.gov) calls for a longer transition period between services than we're employing here, unless continuing that service poses risks to the platform. Since the current logging system uses components that are reaching EOL, continued operation poses security and compliance risks, and we are moving to decommission the service by January 10, 2025.