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
  • Step 1 - Install the Digma plugin
  • Step 2 - Just Run your Code
  • Where to see the data?
  • Bonus Steps:

Digma Quickstart

Couch to Continuous Feedback in less than five minutes

PreviousWhat is a Continuous Feedback platform?NextLocal Install

Last updated 1 year ago

Step 1 - Install the Digma plugin

You can find the Digma Plugin in the IntelliJ Plugin Marketplace in your IDE by searching for Digma or visit the to get it directly from there.

Installing the plugin will also kick off the Digma Local Engine installation. If you have Docker installed and running on your machine that should happen automatically! You can also run Digma yourself using a simple Docker Compose file. See Local Installfor more info.

Step 2 - Just Run your Code

Actually, that's it! The Digma plugin will take care of adding the instrumentation to your code, you can control this behavior with a simple toggle:

Where to see the data?

Digma has three main areas in the IDE where it makes the observability analysis available.

The Observability Panel

This panel will show the latest traces picked up by Digma and is a great place to check and see if everything is working end-to-end. As you are debugging, testing, or running your code, you should always see the observability panel updated with the latest feedback and analysis results.

The Insights Panel

This panel is dedicated to a more in-depth analysis of each code location, asset, db query endpoint, etc. It interacts with the code in the IDE and can either take you to the relevant code locations or show the insights (issues and analytics) related to the currently selected code:

Code lens on the code itself

With the plugin installed, you'll be able to see new code lens overlayed on the code itself indicating runtime usage, dead code, and critical insights:

Bonus Steps:

Digma will provide more insights as more data becomes available to it. There are multiple way to increase your observability coverage:

  • Covering more of your code with Observability

  • Instrumenting your code in CI/Staging or the terminal

plugin page