How do people measure their product health currently? I'm thinking of things like message handlers and systems. What sort of initiatives do you plan to increase the measures? 

2.4k viewscircle icon2 Upvotescircle icon2 Comments
Sort by:
Engineer in Softwarea year ago

Have you looked into observability? e.g.

https://www.redhat.com/en/topics/devops/what-is-observability

Director of Corporate Developmenta year ago

Product health can be interpreted in various ways, depending on the perspective. One approach is to use Service Level Agreements (SLAs) as a benchmark to evaluate how often the product meets or exceeds these requirements. This provides a clear indication of the product's health from a service delivery standpoint.

Another perspective involves monitoring the resource consumption of individual products or applications. This helps gauge the efficiency and sustainability of the product. Tools like APIM can manage SLAs, while monitoring tools can track resource consumption trends.

Runtime characteristics, such as the frequency of crashes and the product's scalability, are also crucial indicators of health. These metrics can uncover underlying issues that might not be evident through SLA measurements alone.

Additionally, the ease of enhancing the product and its security score are vital measures of its health. A product that is straightforward to enhance and has a high security score is likely to be healthier.

Technical debt is another significant factor. High levels of technical debt can impede a product's evolution and maintenance, affecting its long-term health.

Product health should consider multiple dimensions, including SLA performance, resource consumption, runtime characteristics, ease of enhancement, security, and technical debt. Each of these aspects provides valuable insights that contribute to a holistic understanding of the product's robustness.

Content you might like

Very positive39%

Somewhat positive41%

Neutral13%

Somewhat negative6%

Very negative

View Results

0-3 months12%

4-6 months42%

6-12 months27%

Longer than 1 year7%

Have not seen a return on our test automation investment5%

Don't know3%

View Results