The Architecture Behind the Future of an Open-Source Project

DebugProbe Architecture Overview

The diagram illustrates the vision behind DebugProbe Server and how it enables centralized monitoring across multiple environments and applications.

Current State

Today, DebugProbe.AspNetCore runs directly inside ASP.NET Core applications and provides a lightweight dashboard for inspecting:

• Requests
• Responses
• Exceptions
• Headers
• Query parameters
• Request and response bodies
• Performance information

This works well for individual applications, but as systems grow, teams often need a centralized view across multiple environments.

Introducing DebugProbe Server

DebugProbe Server acts as a central collection hub for all connected DebugProbe instances.

Instead of opening separate dashboards for Development, Staging, and Production, applications can send their captured data to a single DebugProbe Server instance.

The server becomes the central place where teams can:

• Monitor all environments
• Review requests and exceptions
• Compare behavior between environments
• Troubleshoot issues faster
• Manage multiple applications from one dashboard

Architecture Flow

                    debugprobe.server
                           │
        ┌──────────────────┼──────────────────┐
        │                  │                  │
   Development         Staging           Production
        │                  │                  │
   Client app         Client app         Client app  
        +                  +                  +
   debugprobe         debugprobe         debugprobe
  .aspnetcore        .aspnetcore        .aspnetcore

Each environment runs DebugProbe.AspNetCore locally and forwards diagnostic data to DebugProbe Server.

The server aggregates and displays all collected information through a unified dashboard.

Scaling Beyond One Application

The same architecture can support multiple applications.

                    debugprobe.server
                           │
        ┌──────────────────┴──────────────────┐
        │                                     │
      App 1                                App 2
  Dev / Stage / Prod                  Dev / Stage / Prod

This allows organizations to manage diagnostics for an entire portfolio of applications from a single platform.

Current Status

DebugProbe.AspNetCore

🟢 Available now and ready for production use.

Current Version: v1.6.2

Useful Links:

• Website: https://debugprobe.dev
• LiveDemo: https://demo.debugprobe.dev/debug
• Documentation: https://debugprobe.dev/docs
• GitHub: https://github.com/DebugProbe/DebugProbe
• NuGet: https://www.nuget.org/packages/DebugProbe.AspNetCore

DebugProbe.Server

🚧 Currently under active development.

The first alpha release will focus on:

• Centralized request collection
• Exception monitoring
• Environment management
• Cross-environment comparison
• Multi-application support

If you're interested in early access, you can subscribe via email on the DebugProbe website and get notified when alpha testing becomes available.

Goal

The goal is simple:

Keep DebugProbe.AspNetCore lightweight, simple, and easy to integrate while providing an optional server platform for teams that need centralized observability, environment comparison, and advanced diagnostics.