Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
🧑💻🔭 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/
| Date | Stars |
|---|---|
| 2026-07-24 | 409 |
| 2026-07-25 | 409 |
| 2026-07-28 | 409 |
| 2026-07-30 | 409 |
| 2026-08-06 | 409 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
<p style="text-align: center;">
<img src="/images/bg.jpg" >
</p>
<h1 style="text-align: center;">
Use Preemptive Observability to Nip Production Issues in the Bud
</h1>
<!-- Place this tag in your head or just before your close body tag. -->
[](https://medium.com/@roni-dover)
[](https://twitter.com/doppleware)
[](https://github.com/digma-ai)
<p style="text-align: center;">
<a href="https://join.slack.com/t/continuous-feedback/shared_invite/zt-1hk5rbjow-yXOIxyyYOLSXpCZ4RXstgA" target="_blank">
<img src="https://img.shields.io/badge/Slack-4A154B?logo=slack&color=black&logoColor=white&style=for-the-badge alt="Join our Slack!" width="80" height="30">
</a>
</p>
## :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 anyExcerpt of 6,057 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:6ee15a756ea87d34, topic:observability, topic:tracing, topic:opentelemetry