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
  • Prerequisites
  • 1. Install the Digma plugin in the IDE marketplace
  • 2. Setup the Digma Analytics Engine
  • How do I know Digma is Running?
  1. Installation

Local Install

Installing Digma locally is pretty straightforward, you can choose whether you want Digma to install its Analytics Engine for you or do it on your own.

PreviousDigma QuickstartNextLocal Install Architecture

Last updated 1 year ago

Prerequisites

  1. Community or Ultimate Edition (2022.3 and up are supported, though latest is recommended)

  2. An application running or code

  3. Docker installed and running - Can be either , , or

Note to Colima Users

Please make sure to set the memory size to at least 3GB as we've had complaints of issues with memory sizes smaller than that.

colima start --memory 3

1. Install the Digma plugin in the IDE marketplace

The Digma Plugin is available on the IntelliJ Marketplace.

2. Setup the Digma Analytics Engine

Digma runs locally on your machine. To process all of the captured traces, analyze them, detect issues, and provide analytics, Digma relies on Docker containers. When not ingesting any traces, these containers are completely idle.

After the plugin installs you'll get to choose the preferred way to install the Digma Engine. Several options are available:

Auto install (Default)

This is the default option. After installation, the plugin will try to start the Digme Engine containers on your local Docker environment and will offer clear controls to allow you to Stop Start or Remove it. The benefit of using this approach is that Digma will be able to also update the Engine automatically when a new release becomes available.

Install Digma via Docker Compose

You can simply install Digma yourself using the Docker Compose file.

Simply select the Docker Compose tab from the onboarding page and follow the instructions to download the Docker Compose file and run it locally.

Install the Docker Extension

Digma also comes bundled as a Docker Extension. If you're using Docker Desktop you can deploy the Digma Engine straight from the Docker Extensions Marketplace. The benefit is that the Engine will run in its own system space and will not create any confusion with the rest of the containers you may be running for other use cases.

  1. (Optional) If you have a product key please enter it in the configuration stage of the onboarding process along with your email

How do I know Digma is Running?

If you've run Digma via any of the first two options, you can check that the Analytics Engine containers are up and running. In the IDE you should see both the Observability side panel and the Insights side panel showing up with no errors and waiting to receive data.

You can install the plugin from your IDE or open the plugin in your browser.

Notice that you can use this method to deploy to other Docker platforms Both Rancher Desktop and Podman support the Docker Compose spec so you can use or respectively.

You can install the Digma Extension from the Docker Marketplace or by visiting the .

page
Rancher Compose
Podman Compose
extension page
IntelliJ
Java
Kotlin
Docker Desktop
Podman
Rancher Desktop
Colima