Labsco
digma-ai logo

Digma

โ˜… 11

from digma-ai

A code observability MCP enabling dynamic code analysis based on OTEL/APM data to assist in code reviews, issues identification and fix, highlighting risky code etc.

๐Ÿ”ฅ๐Ÿ”ฅ๐Ÿ”ฅโœ“ VerifiedFreeQuick setup

Digma Code Observability MCP Server

A Model Context Protocol (MCP) server implementation for enabling agents to access observability insights using Digma for code observability and dynamic code analysis

Key Features ๐Ÿš€

  • ๐Ÿ—ฃ๏ธ Observability-assisted code reviews: Check the PR branch for any issues discovered by pre-prod observability.
  • ๐Ÿ”Ž Find code inefficiencies with dynamic code analysis: Identify issues in the code/queries that are slowing the app down
  • ๐Ÿ”ญ Utilize code runtime usage data from distributed tracing: Check for breaking changes or generated relevant tests

Example prompts ๐Ÿ’ฌ

  • help me review the code changes in this branch by looking at related runtime issues
  • I want to improve the performance of this app. What are the three most severe issues I can fix?
  • I'm making changes to this function, based on runtime data. What other services and code would be affected?
  • Are there any new issues in this code based on the Staging environment?
  • Which database queries have the most impact on the application performance?

See it in action ๐Ÿ“บ

Code review with Digma MCP


Get early access ๐Ÿ‘€

Digma pre-processes your observability data to identify issues, track code performance and runtime data - for dynamic code analysis. Visit our MCP page to sign up for early access to our MCP server.

Using rules ๐Ÿ‘จโ€๐Ÿ’ผ

The agent is autonomous and selects when to use the data provided by Digma as needed, however, some clients allow setting rules and policies to set a more structured process. Here is an example rules file which you can add to your cursor .cursor/rules directory

# Digma Memory File - Code Review Instructions

## Runtime Analysis Settings

- Environment: TEST

## Code Review Protocol

1. For any code or branch review request:
   - Get the list of changed files and methods in the current branch using `git diff`
   - Check for ALL runtime issues in TEST environment (not just for the method in context)
   - Check if any runtime issue may be related to the changed code
   - Check the runtime usage of the changed methods (based on the `git diff`)
   - Check if any of the changed methods (based on the `git diff`) have a high risk based on their performance impact 
   - Synthesize the data with standard code review analysis

## Note

This file is used by the AI assistant to maintain consistent review protocols across sessions.