Welcome to our November update roundup! This month, we've made Rely.io more efficient and insightful for developers and teams, adding new features that enhance engineering performance tracking, improve usability, and expand our plugin ecosystem. Let’s dive in!

In the context of high pace delivery, increased compliance expectations and even often budget contractions, Engineering Leaders are mandated to “to do better with less”. The first step on this journey to drive efficiency up is to start with measuring and tracking Engineering Performance across different dimensions (teams, systems, services, domains, etc).

Using Rely.io’s Software Catalog for the key entities (Teams, Services, Systems etc.), you can already access the relevant performance metrics and Scorecards that are either provided out-of-the-box or that you customized. So when looking at a specific entity (e.g. Team:Backend) you can track effortlessly and assess their performance trend.

However, to actually assess performance of a given Team or Service, looking at their metrics on their own is often not enough:

• What is the baseline this value should be compared to?
• How does this specific entity fare compared to other similar entities? (e.g. other backend teams)

With the new Engineering Performance view, you can now also track and compare these metrics between Teams or Services, all in one single page:

Engineering Leaders can decide which entities to look at (Services, Teams, etc.) and filter them to focus on a desired scope (e.g. to only show the ones they are responsible for).

With all the teams of interest in on view, assessing their performance in the broader context within the Organization becomes seamless.

It also means the views can be more easily shared internally when building reports, preparing OKRs or communicating them to each team.

The Engineering Performance views are already available in Beta.

If you want to try them for your organization, let us know!

As the adoption of modern CI/CD practices (like GitOps) is on the rise, it becomes increasingly harder to track code once it has been pushed.

Whether it’s for visibility purposes within a team (to track ongoing deployment, fix failing ones, etc.) or for Engineering Leaders to accurately keep track of performance metrics impacted by deployments (Deployment Frequency, LtfC, etc.), or an accurate representation of the SDLC.

With the new FluxCD plugin you can now track your code journey from commit or merge (thanks to the Git integrations like Github, Gitlab or Bitbucket) to its actual deployment in your various environments (dev, staging, production, etc.).

The FluxCD plugin is already generally available as part of our open source integration framework, Galaxy.