Beating Post-Launch Blues

Identifying and troubleshooting of defects/bugs and applying code fixes is one of the important tasks in software engineering and essential to maintain good quality software. Companies spend a lot of money to keep their software quality at highest levels. Engineers spend lot of their quality time pouring through tons of log files, gathering steps to reproduce the defect in local environments and troubleshooting in customer environments etc., to find root cause of the defect. If the broken function is critical and business impacting, then expect review meetings, war room exercises, post-mortem reports etc. These old-fashioned troubleshooting procedures need engineer’s experience, skill, time and resources to analyze the problem and lead to increased MTTR (mean time to repair).

MTTR is the average time required to fix a failed component or function and return it to production status. MTTR includes the time it takes to find out about the failure, diagnose the problem and repair it. MTTR is a basic measure of how maintainable an organization's software is and, ultimately, a reflection of how efficiently an organization can fix a problem. Hence companies strive hard to keep MTTR as low as possible.

How to improve MTTR

Modern monitoring technologies are an organization's best chance to reduce its mean time to repair. Monitoring can provide 24/7 insight into the health of the system. Using this real time information, an organization can establish its MTTR, allowing engineers to run preventative maintenance and to plan for repairs proactively.

The type of monitoring tools to use differs based on the type of issues you want to monitor. For performance and availability issues there are multiple APM solutions available to choose from such as AppDynamics, New Relic and Dynatrace. But if you want to monitor functional failures and bugs, your options are very very limited.

Seagence comes to rescue

Seagance automates Root Cause Analysis for functional failures in real time. It monitors production web applications real-time using patent-pending algorithms to identify functional failures and sends alerts with root cause within 5 seconds of the failure manifesting in production. What makes it a first of its kind solution is its ability to convert tens of thousands of errors/exceptions into a crisp actionable root cause. Engineers using Seagance no longer need to spend hours pouring through log files, gather data to reproduce the problem or troubleshoot in customer environments. Reducing MTTR, it helps enterprises avoid business loss, while simultaneously reducing support costs. It's ability to distinguish between a failed HTTP request and a successful HTTP request in real time makes it first of its kind solution.

Here is how Seagence works.

1) Seagence uses an agent to inject monitoring code using instrumentation into customer's application run-time.

2) Seagence’s Agent starts with customer application and continuously collects metadata from running application. This collected metadata is sent to Seagence Engine, which can be on-prem or on cloud, in real time.

3) Initial set of metadata received by Seagence Engine is used to build the knowledge.

4) After the knowledge is built, Seagence’s Analytics Engine will analyze incoming metadata for success / failure prediction in real time.

5) If Analytics Engine’s outcome is a failure, it will raise alert with root cause within 5 seconds of failure manifesting in production. Root cause includes the function/resource (URL) that has failed and exception stack trace that caused the failure along with additional debug information.

Interested? Request a demo Here.