Today, we launched Harness Continuous Error Tracking (CET) for public preview to provide developer-first observability for modern applications. As the latest module in the Harness Platform, CET helps developers proactively identify and resolve errors across the entire software delivery lifecycle (SDLC).
While developers today spend up to 75% of their time debugging code, most observability solutions focus on production monitoring for Site Reliability Engineering (SRE) teams. This leaves developers with limited visibility into application behavior during the development and deployment phases of software delivery.
As a developer-first observability solution, CET gives developers end-to-end visibility, so they can observe errors, debug code, and create quality gates during continuous integration and continuous delivery. By correlating these errors with those observed in production, developers can prioritize remediation efforts and ensure faster time-to-resolution. This innovative approach empowers developers to deliver higher quality applications and significantly reduces the time and effort required for troubleshooting and debugging, making Harness CET a valuable tool for any modern application development team.
When developers are spending the majority of their time debugging code and teams are stressing about whether or not each release is introducing new errors, there’s clearly room to improve efficiency. With complete visibility into errors across development pipelines, developers can find and fix errors faster and release more confidently.
Here are several ways developers can use CET to do so:
Eliminate Manual Troubleshooting
By automating troubleshooting of exceptions in development, testing, and production environments, toil is reduced, so developers spend less time troubleshooting, and more time coding.
Solve Customer Issues Faster
Code-level snapshots containing every exception’s source code, variables, and environment state can be used to reproduce and resolve errors quickly. If a customer issue arises, teams can resolve it faster and minimize its impact.
Minimize Escaped Defects
Developers can proactively identify new and critical exceptions and prevent them from getting promoted to staging or production. This minimizes the chances of issues negatively impacting customers.
Developers sometimes spend weeks on error resolution, which is a frustrating use of time. By providing a list of all the exceptions that are happening along with the frequency at which they’re occurring, CET helps developers prioritize remediation efforts, so they can focus on the most important issues first. Plus, having the complete code-level snapshot significantly reduces the time and effort spent on troubleshooting and debugging.
Here’s a closer look at CET’s key features:
Runtime Code Analysis
Gain a complete picture of every exception, so developers can reproduce and resolve errors faster with visibility into every exception’s source code, variables, and environment state. Route issues to the correct developer, so they can be resolved faster. By capturing state across the entire call stack, CET gives you the full context of each error, including code variables and objects up to 10 levels into the heap—more than any other developer observability solution.
Code Quality Gates
Stop bad code and unreliable releases from being promoted to staging and production using quality gates in CI/CD pipelines. By providing guardrails, CET only allows high-quality code to advance.
Stay on top of release quality by comparing current and past releases. This helps developers identify and understand trends in new, critical, and resurfaced errors.
Harness CET integrates with popular monitoring solutions, such as AppDynamics, Dynatrace, DataDog, NewRelic, and Splunk, so developers can continue to use their preferred tools while gaining a more complete picture of exceptions. CET natively integrates into Harness Continuous Integration, as well as other third party CI/CD solutions.
Enjoyed reading this blog post or have questions or feedback?
Share your thoughts by creating a new topic in the Harness community forum.