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
  • Why it's important to have more than one environment
  • The default environment
  • Private vs. Shared Environments
  • How to create environments
  • Tagging the application data to the new environment
  1. Digma Core Concepts

Environments

Environments represent different deployment stages or scopes. Typical environments would include - local development, load testing, CI, staging, or production.

PreviousPrioritize Technical DebtNextAssets

Last updated 11 months ago

Why it's important to have more than one environment

Digma excels in analyzing observability data, detecting changes, and measuring baselines. Lumping together data from dev, test, load testing, and production would create a huge mess with many strange statistical artifacts. Each time you run a load test you'll notice huge performance degradations while running in debug mode would manifest bugs in code that hasn't yet been checked in.

To bring some order into this chaos, Digma uses environments as an abstraction to measure data from different deployment stages and use cases separately.

The default environment

By default, all observability data received by the Digma Analytics Engine is lumped in the LOCALor LOCAL_TESTS environments if you've installed Digma locally on your machine. The latter environment will automatically ingest any observability from your local test runs in the IDE.

Once you've installed Digma centrally all untagged traces will immediately be lumped under the UNSET environment. However, this should be a temporary state and we strongly recommend to create named environments for each of your observability sources.

Private vs. Shared Environments

Private environments are environments only you have access to. If you're running Digma locally this is also the only environment you can create - seeing as you're also the only user!

Once you've installed Digma centrally you can create shared environments that are accessible to multiple users. A good example would be setting up a Digma environment for your CI or Staging.

How to create environments

Beyond the default environments, creating additional private or shared environments requires registering for a Digma Account (which is free and available at this ).

Private environments are easy to create in your local deployment from the Observability Panel and through the Add Environment button.

Tagging the application data to the new environment

To learn how to save the application observability data under the environment you've created, click on the 'How to setup' option in the environment tab context menu:

link