Nowhere for a problem to hide

Instrumentation and topology work for an application performance monitoring product whose customers were leaving blind spots when they configured it.

Talk to an engineer Managed services & FinOps

CRM platform Client

Managed services & FinOps Practice

March 2023 Published

01 — The challenge

Where it started.

Customers integrating the monitoring tool with their own applications were leaving configuration gaps, and the gaps sat precisely where distributed performance problems live.

The product was being judged on blind spots that came from configuration rather than from the product itself.

02 — What we built

The work itself.

Applications deployed across three agents. Representative applications built and run against the Java, Python and Node agents, to find where configuration actually breaks.

Custom scripts per stack. Instrumentation written for the technology combinations customers really use, rather than the reference one.

A redesigned topology view. The map of what calls what, presented so a gap is visible rather than implied.

03 — Results

What the client has now.

Recommendations incorporated into the product’s next release by the client’s own team. Application configuration reduced to a few clicks. Performance issues identifiable where previously they were inferred.

The rest of this study

What we built, what it produced, and the stack behind it.

We share the whole write-up — we would just like to know who is reading. One form opens every case study on the site for the next 30 days.

If this is your problem too

Start with a fixed-price pilot.

Two weeks on a real piece of your backlog, priced before we begin. You keep the output whether or not you continue.

Related work

Corporate wellness · Platform build

A wellness platform, from vision to live

Health insurance · CI/CD