project-report

Generate independent daily reports by aggregating bugs, tech requirements, Sentry exceptions, and SLS statistics into a timestamped Markdown file per project. Each project uses a dedicated YAML configuration file for customized data thresholds.

Yes, configurable SLS thresholds and Sentry parameters are supported per project. You define these custom settings in the config/{project}.yaml file, ensuring each daily report reflects project-specific monitoring rules.

Select specific data modules by passing the types parameter to output only designated non-empty modules. If left unspecified, the system automatically enables all available modules with valid Sentry or SLS configurations.

Project reports are output as UTF-8 encoded Markdown files. They are named using a {project}-{yyyy-mm-dd-hh-mm}.md timestamp format and saved directly to the report/temp/{project}/qa/ directory.

Yes, it uses pyyaml to parse per-project YAML configurations for analytics data sources. This setup allows flexible aggregation of bugs, tech requirements, Sentry, and SLS data into isolated Markdown outputs.

Data sources are skipped if their module configurations are empty or invalid. The report generator only executes modules where Sentry or SLS configurations exist and are non-empty, or when explicitly specified via the types parameter.