Nobl9 Adds Hydrogen Platform to Surface Tech Debt Problems


Nobl9 today unveiled a Hydrogen platform that makes it easier for DevOps teams to identify technical debt issues when they manage service level objectives (SLOs) as code.

Hydrogen allows DevOps teams to define SLOs using a simple wizard or by embedding code into their application as part of a DevOps workflow. This code is then used to automatically collect data from platforms such as Datadog, New Relic, Prometheus, Splunk, and others that require additional instrumentation.

Nobl9 COO Kit Merker said that this approach also helps to highlight the technical debt that is preventing these goals from being achieved through the Hydrogen platform. Armed with this information, it then becomes easier for DevOps teams to focus on reducing or eliminating this technical debt, as Hydrogen automatically generates a ticket in the Jira project management application, which is widely used by teams. DevOps, to make sure the issue is resolved. Otherwise, in the heat of DevOps, the issue may be forgotten as the app development project continues to move forward, Merker noted.

The ability to identify this technical debt is a consequence of the ability to manage SLOs as code that is activated by the main Software as a Service (SaaS) platform Nobl9. Hydrogen extends this capability by automating workflows whenever a specific service indicates it cannot meet targets due to a dependency on an existing platform that needs to be upgraded, Merker added.

There’s also a Service Health Dashboard that organizes SLOs into logical groups mapped to features via labels, which Merker says allows multiple stakeholders to easily identify the issues that most affect a particular service. . Hydrogen can also trigger a variety of automated workflows to trigger additional investigations that escalate as services deteriorate.

Overall, Hydrogen is designed to provide engineering teams with a more precise context that can be used to prioritize the issues that need to be addressed first during any technical debt planning cycle, Merker said. Hydrogen may enforce code release policies based on technical debt budgets which are enforced through integrations with continuous integration / continuous delivery (CI / CD) platforms.

Technical debt generally refers to any code change needed to optimize a service that is not immediately addressed. The more legacy platforms there are in an IT environment, the higher the technical debt tends to become. In an age where more organizations are building and deploying microservice-based applications, this technical debt, over time, tends to negatively affect applications that rely much more on external services than a traditional monolithic application. . A single technical debt issue can cascading impact across multiple microservice-based applications that would otherwise be difficult to detect.

The challenge, of course, is that technical debt doesn’t always get the attention it deserves when most of the IT team is focused on deploying the next big application. However, as application environments become more complex, it may only be a matter of time before all the accumulated technical debt becomes unsustainable.

Source link


About Author

Comments are closed.