How open-telemetry/weaver works
Main Components Structure
• Create three main vertical layers representing the core functionalities:
a. Input Layer (Top)
b. Processing Layer (Middle)
c. Output Layer (Bottom)
a. Core Processing:
• weaver_resolver: Schema resolution component
• weaver_checker: Policy enforcement component
• weaver_forge: Documentation and code generation component
b. Supporting Components:
• weaver_semconv: Semantic convention handling
• weaver_cache: Caching functionality
• weaver_common: Shared utilities
• weaver_version: Version management
• Resolved Schemas
• Validation Reports
• Generated Documentation
• Generated Code
• Statistics Reports
Special Elements
• A "Cache Store" component connected to weaver_cache
• An "Error Handling & Diagnostics" component that spans across all layers
Component Details
• Input/Output formats
• Key responsibilities
• Dependencies on other components
Technical Stack Indicators
• Rust implementation
• Rego policy language
• Jinja2 templating
• JQ compatibility
Cross-Cutting Concerns
Vertical bars on the side showing:
• Memory Safety
• Error Reporting
• Parallel Processing
• Cross-Platform Support
Performance Characteristics
• Processing time indicators
• Memory usage patterns
• Scalability characteristics
• Input Components: #4A90E2
• Processing Components: #2ECC71
• Output Components: #E67E22
• Future Components: #95A5A6
• Critical Paths: #E74C3C
• Support Systems: #8E44AD