How bewuethr/slack-analyzer works
Main Components Identification
a. Input Sources:
• Slack Workspace (external system)
• GitHub Repository (hosting environment)
• Optional Telegram Channel (external system)
b. Core Processing Components:
• User Data Collector
• Message Analysis Engine
• Data Correction Handler
• Statistics Generator
• Visualization Engine
• Telegram Notification Service
External Services Layer
• ↕
Input Processing Layer
• ↕
Core Processing Layer
• ↕
Output Generation Layer
• ↕
Distribution Layer
Component Relationships
a. Data Flow:
• Slack API → User Data Collector (users.list endpoint)
• Slack API → Message Analysis Engine (search.messages endpoint)
• Data Correction Handler ← corrections.csv
• Statistics Generator → Visualization Engine
• Visualization Engine → Output Files
• Telegram Notification Service → Telegram Channel
Specific Implementation Details
Key elements:
• Input Configuration: GitHub Action inputs (tokens, workspace name)
• Data Processing Flow: Show how the data moves from raw Slack API responses to processed tenure information
• File Generation Pipeline: Illustrate the creation of various output files (README.md, TSV files, graphs)
• Correction Mechanism: Show how corrections.csv integrates with the main data flow
Important Notes
Annotations for:
• Rate limiting handling
• Retry mechanisms for API calls
• Optional components (Telegram integration)
• Data correction workflow
• File organization structure
Technical Details
Specific technical implementations:
• API Endpoints used (users.list, search.messages)
• Data formats (TSV, CSV, Markdown)
• Generated visualizations (turnover graph, boxplot)
• Directory structure for diffs (YYYY/MM/*.diff)