https://github.com/digma-ai/digma
🧑💻🔭 Digma helps you fix performance issues in your code by automatically profiling the code execution. Using APMs to identify code bottlenecks, query problems and scalability issues takes time and effort - Digma automates all of that. Digma is free for developers - get it here: https://digma.ai/get-digma/
https://github.com/digma-ai/digma
csharp developer-tools devops dotnet ebpf ebpf-programs intellisense jaeger observability opentelemetry python tracing
Last synced: 7 days ago
JSON representation
🧑💻🔭 Digma helps you fix performance issues in your code by automatically profiling the code execution. Using APMs to identify code bottlenecks, query problems and scalability issues takes time and effort - Digma automates all of that. Digma is free for developers - get it here: https://digma.ai/get-digma/
- Host: GitHub
- URL: https://github.com/digma-ai/digma
- Owner: digma-ai
- Created: 2021-12-26T15:17:29.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2025-04-01T10:00:54.000Z (14 days ago)
- Last Synced: 2025-04-01T10:11:07.498Z (14 days ago)
- Topics: csharp, developer-tools, devops, dotnet, ebpf, ebpf-programs, intellisense, jaeger, observability, opentelemetry, python, tracing
- Language: Shell
- Homepage: https://www.digma.ai/
- Size: 19 MB
- Stars: 396
- Watchers: 10
- Forks: 11
- Open Issues: 47
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-java - Digma
README
Use Preemptive Observability to Nip Production Issues in the Bud
[](https://medium.com/@roni-dover)
[](https://twitter.com/doppleware)
[](https://github.com/digma-ai)
## :raised_eyebrow: What is Digma
Digma is a tool that profiles your application execution in runtime and identifies critical performance issues. Digma is comprised of an analysis backend (running locally on containers) and an IDE plugin as the main front end (Jetbrains only for now). The plugin provides code-level insights related to performance, query issues, bottlenecks scaling problems, and more.
## :gear: How Digma works
Digma's backend receives OTEL data from your application (collected automatically when you run it locally), analyzes it, and identifies specific issues in the code execution. All of the data is handled locally in order to support compliance requirements and no code changes are required. Digma cam profile data from multiple environments, including dev, test, staging, production etc.
## 🚀 Getting started
### 1. Install the IDE Plugin
Get the Digma plugin from the [JetBrains marketplace](https://plugins.jetbrains.com/plugin/19470-digma-continuous-feedback). We currently support IntelliJ with either Java or Kotlin, support for additional IDEs is coming soon.
### 2. Follow the installation instructions in the plugin to get Digma up and running
**That's it!** :tada: As you start using your application and running your code, Digma will provide feedback and highlight issues over the code itself.
### Once you're up and running:
* #### Consider :star: this repo! It helps us know you care!
* Having issues? Questions? Want to suggest new ideas or discuss Digma with us? Join the [Digma community](https://continuous-feedback.slack.com/join/shared_invite/zt-2ebkq5qxs-Hpep2BFMfpxYTE9xq45w8A#/shared-invite/email)
## What does Digma look like?
You can check out some videos and more info on our [YouTube Channel](https://www.youtube.com/@digma1769/videos)!
In short, we can use existing logs, traces, and metrics to answer questions such as:
* What are the top bottlenecks slowing this code down?
* How will this function scale?
* Which slow queries have the most impact on my application performance?
* Are there any issues introduced by the ORMs or 3rd party libraries
More importantly, all of these insights should be directly accessible in the IDE so we can use them while coding.
## The story behind Digma: :man_technologist::woman_technologist:
We believe that unless the application profiling is **continuous** and **automatic** - much like testing it won't be effective. There are many observability tools out there, however, they all require actively and manually spending time, attention, and expertise to get results. It is not surprising that they are used only reactively when something terrible happens. The end goal of observability should not be creating dashboards but improving our application and code.
## How are you different from...
Well, we don't compete with any tool existing today because... There isn't any tool that aims to generate this type of feedback. We do work very well together with other tools looking at the same data, like Jaeger, Prometheus, and even traditional observability APMs like Datadog or Splunk.
We are also not a static analysis tool. We profile the application execution in runtime rather than looking at the code and generating a ton of styling and rule-based issues.
## How can I learn more about Digma?
We started publishing some more detailed blog posts explaining what we are trying to accomplish. Here are a few examples:
- [CI/CD/CF? — The DevOps toolchain’s “missing-link”](https://digma.ai/blog/ci-cd-cf-the-devops-toolchains-missing-link-continuous-feedback/)
- [Effective Java Observability](https://digma.ai/blog/coding-with-java-observability/)
- [The Observant Developer](https://digma.ai/blog/the-observant-developer-part-1/)
For the full list, you can check out our [website blog](https://digma.ai/blog/)
If you're interested in the specific capabilities, product features, and technical specifications - check out our [docs](https://docs.digma.ai/)!
## FAQ
* **Is this going to instrument my code and change it in creepy ways in production?** Absolutely not! We rely on the OpenTelemetry vanilla instrumentation with a few added attributes of our own. We leave your code untouched.
* **Do I need to make code changes to use Digma?** No! Digma will take care of collecting the observability data without any code changes.
* **Does Digma send data to the cloud** No! We purposely run everything locally to avoid any issues with compliance policies.
* **Which platforms/stacks do you currently support?** We currently focus on [Java](https://www.java.com/en/) and [Kotlin](https://kotlinlang.org/) with [IntelliJ](https://www.jetbrains.com/idea/). Support for [**.NET**](https://dotnet.microsoft.com/en-us/) using [**Rider IDE**](https://www.jetbrains.com/rider/) is currently in early access mode. We'll expand to additional IDEs and languages later this year.