Developer-Portal

This is the final post in the Backstage Tech Insights series. Over the past eight posts, we went from “what is Tech Insights?” to setting up plugins, retrievers, checks, scorecards, custom retrievers, and production troubleshooting. Here is everything we covered, with links to each post. The series Introduction to Backstage Tech Insights: What Tech Insights is, why it matters, and how it fits into your developer portal. Covers the core concepts: fact retrievers, checks, and scorecards. ...

In the previous post, we looked at what Tech Insights is and why it is useful. Now let’s get it running. This post walks through the backend installation and configuration of the Tech Insights plugin. Prerequisites Before you start, make sure you have: Node.js and Yarn installed A working Backstage instance Access to the Backstage codebase If you do not have a Backstage instance yet, the official getting started guide is the best place to begin. ...

If you are running Backstage as your internal developer portal, you have the software catalog in place, you can easily discover services but you have probably dealt with this question at some point: How do we know if our services are following the standards we agreed on? Maybe you want to check whether every service has a README. Maybe you want to ensure all services have CI configured. Or perhaps you want to verify that a particular annotation is present on the components or their Kubernetes resources. ...