How to use traces to avoid breaking changes - Digma
digma.ai
Using traces to observe how different parts of a program work together helps prevent problems...

Tracing in Context Tracing main components How tracing works in more technical detail How tracing enhances system visibility and performance The most famous and widely used distributed tracing libraries Detecting API usages using the insights provided by Digma Usage Analysis Top Usage Endpoint Low/High Usage

  • Kissaki@programming.devEnglish
    0·
    3 months ago

    First half is a general introduction, second half is an introduction to their product Digma, which is limited to Java and IntelliJ.

    Currently, Digma fully supports Java and IntelliJ, along with related frameworks such as Spring, Spring Boot, Dropwizard, and Micronaut. If you’re interested in other languages, you can find more information here.

    Overall it feels shallow to me.

    From what I see they didn’t even support the claims they set out to present. They show a few screens of their tool, but never how that would “avoid breaking changes”. The conclusion is incredibly generic. Feels like publicity/promotion and keywords content was the goal rather than actually sharing information. OP only posting their Digma content fits the impression of PR too.