How grafana/explore-profiles works
Main Components Architecture
a) Frontend Application Layer
• Sub-components:
• Pages Module (/src/pages)
• Shared Components (/src/shared)
• App Core (/src/app)
b) Integration Layer
• Plugin Registration (module.ts)
• Scene System Integration
• Data Source Integration
c) External Services
• Pyroscope Backend
• Grafana Core
• GitHub Integration (for code viewing)
Key Architectural Patterns to Highlight
a) Domain-Driven Design (DDD) Structure
• Domain logic (/domain folders)
• Infrastructure (/infrastructure folders)
• UI components (/ui folders)
b) Scene System Architecture
• Scene components hierarchy:
• SceneProfilesExplorer
• SceneByVariableRepeaterGrid
• SceneFlameGraph
• SceneFunctionDetailsPanel
Data Flow Patterns
a) Query Flow
• User Input → Query Builder → Data Source
• Data Source → Pyroscope Backend → Flame Graph Rendering
b) State Management Flow
• URL Parameters → Scene State → Component State
• User Interactions → Event System → State Updates
Integration Points
Connection points with:
a) Grafana Core
• Plugin API
• Data Source API
• Scene System
b) External Services
• GitHub API (for code viewing)
• Pyroscope API
• Faro Tracking
Component Details
a) Flame Graph Visualization
• Data Processing
• Rendering Pipeline
• Interaction Handlers
b) Query Builder
• State Machine
• Filter Management
• Auto-suggestion System