Digma Developer Guide
  • Welcome to the Digma Docs!
  • What is a Continuous Feedback platform?
  • Digma Quickstart
  • Installation
    • Local Install
      • Local Install Architecture
      • Installation Troubleshooting
    • Central (on-prem) Install
      • Resource Requirements
  • INSTRUMENTATION
    • Instrumenting your code for tracing
    • Java
      • Automatic Instrumentation in the IDE (IntelliJ)
      • Spring, Spring Boot, Dropwizard
        • Instrumenting your code in CI/Staging or the terminal
        • Instrumenting your application in Docker Compose
        • Instrumenting your application on Kubernetes
        • Covering more of your code with Observability
        • Using GitHub Actions (beta)
        • Using Micrometer Tracing (Spring Boot 3.x only)
        • Instrumenting code running in CLI
      • Quarkus, Micronaut, OpenLiberty
    • .NET
    • Correlating observability and source code commits
    • Sending Data to Digma using the OTEL Collector
    • Sending Data to Digma Using the Datadog agent
  • Use Cases
    • Design and write code more efficiently by understanding the system flows
    • Get early feedback on bottlenecks and code issues
    • Prioritize Technical Debt
  • Digma Core Concepts
    • Environments
    • Assets
    • Analytics vs. Issues
  • Digma Features
    • Issues
      • Suspected N+1
      • Excessive API calls (chatty API)
      • Bottleneck
      • Scaling Issue
      • Session In View Query Detected
      • Query Optimization Suggested
      • High number of queries
      • Slow Endpoint
    • Analytics
      • Top Usage
      • Request Breakdown
      • Duration
      • Code Nexus
      • Duration Breakdown
      • Endpoint Low/High Usage
    • Performance Impact
    • Test observability
    • Issue Criticality
  • Sample Projects
    • Spring Boot
  • Troubleshooting
    • Reporting Plugin Issues
    • Digma Overload Warning
Powered by GitBook
On this page
  • What is a performance impact?
  • Where can I see the performance impact of an asset?
  1. Digma Features

Performance Impact

PreviousEndpoint Low/High UsageNextTest observability

Last updated 1 year ago

Performance impact is a unique Digma feature that is only measured in real-world-like scenarios such as end-to-end testing and staging environments. Therefore, this feature is only activated once you install Digma in a

What is a performance impact?

Digma measures the performance of each asset, but looking at that number does not necessarily provide useful information about what requires optimization. For example, you may encounter queries that are pretty slow but are hardly used at all, or HTTP calls that take up a substantial amount but are called asynchronously or are a part of such a long operation that their effect on the whole request is negligible.

The performance impact analysis aims to answer this very question. Namely - "punch for the bucks" How much would I gain in optimizing this particular asset?

Where can I see the performance impact of an asset?

You can see the performance impact of each asset in the Assets tab, and even sort each category of assets based on that value to find the most impactful candidates for optimization.

You can also access the Digma dashboards via the Insights Panel to see a scoreboard for the most impactful client assets:

central environment.