From e791df0539d0dd396249929beb16835677580014 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Johannes=20Br=C3=A4uer?= Date: Mon, 23 Sep 2024 12:46:53 +0200 Subject: [PATCH] Provide introduction MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Johannes Bräuer --- microsite/blog/2024-09-24-dynatrace-adopter-spotlight.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/microsite/blog/2024-09-24-dynatrace-adopter-spotlight.mdx b/microsite/blog/2024-09-24-dynatrace-adopter-spotlight.mdx index d096c4c5dd..c401722d01 100644 --- a/microsite/blog/2024-09-24-dynatrace-adopter-spotlight.mdx +++ b/microsite/blog/2024-09-24-dynatrace-adopter-spotlight.mdx @@ -9,6 +9,11 @@ authorImageURL: https://avatars.githubusercontent.com/u/729071?v=4 **TL;DR** ![IMAGE-NEEDED](assets/2024-09-24/image-needed.svg) +To enhance the developer experience, Dynatrace adopted Backstage as its central developer portal and enhances Backstage entities with real-time data. This decision, along with the symbiosis between the Dynatrace platform and Backstage, has unlocked two significant opportunities. + +* First, centralizing all development-related artifacts and democratizing ownership have reduced onboarding time for our teams. +* Second, we enhanced the developer experience by integrating observability and security data into Backstage, offering seamless entry points to Dynatrace for in-depth analysis. + {/* truncate */} ## Why and how Dynatrace rolled out Backstage