Opsera Brings DevOps Intelligence to GitHub Stocks


Opsera today announced that it has extended its DevOps intelligence gathering platform to include support for the continuous integration/continuous delivery (CI/CD) platform GitHub Actions.

Opsera CTO Kumar Chivukula said that as GitHub Actions becomes more widely adopted, there is a growing need to provide greater visibility into real-time Git-based workflows. A GitHub Actions Insights module for the Opsera platform helps track key performance indicators (KPIs) in these workflows, he added.

The goal is to simplify data-driven decision-making about how best to optimize these workflows by identifying bottlenecks, Chivukula noted.

The Opsera platform brings this intelligence to light by analyzing all repositories and branches, including commit history, and generating alerts and notifications whenever KPI thresholds or compliance requirements are exceeded. DevOps teams can also use the platform to assess their overall DevOps maturity using a set of Google-defined DevOps Research and Assessment (DORA) metrics. In the future, Opsera also plans to start showing metrics based on the Software Artifact Supply Chain Tiers (SLSA) framework to secure software supply chains also defined by Google.

Platforms like Opsera allow analytics to be applied to DevOps workflows as they become more complex. The number of dependencies that exist between various application modules, for example, makes it extremely difficult for DevOps teams to manually identify the impact that a delay in one project might have on a number of other downstream projects.

Additionally, many organizations are keen to learn what best practices should be adopted by other application development teams.

Finally, many developers tend to use a repository as a dumping ground for all sorts of software artifacts, Chivukula noted. DevOps teams need an intelligence tool to identify which of these artifacts are most critical to the business, he added. Otherwise, manually browsing a repository for artifacts becomes the DevOps equivalent of finding a needle in a haystack, Chivukula noted.

GitOps is essentially a more savvy approach to DevOps that relies on an instance of the open-source Git repository as the single source of truth about the environment rather than a set of application or server configuration files. GitHub sees GitOps as a way to extend a code repository in the realm of DevOps workflows using the GitHub Actions platform. It’s unclear how much GitHub Actions is gaining traction at the expense of other CI/CD platforms, but for organizations that are relatively new to DevOps and already using GitHub as a code repository, this presents a lesser path. resistance.

Whatever the reason for organizations to adopt a DevOps intelligence platform, the need to optimize workflow across tool chains becomes more pressing during an economic downturn. It is becoming increasingly clear that the cost of delayed application delivery has a direct impact on the level of revenue an organization generates in the era of digital business transformation.


Comments are closed.