Analytics Service Initialization + Docker Cleanup

[UZ9]

Adds analytics service skeleton with healthcheck, healthcheck to email services, and sentry logging for analytics./

[greptile-apps]

Disclaimer: This comment was AI-generated and is not necessarily completely accurate. Please take code comments with a grain of salt.

Greptile Summary

This PR introduces a new analytics-service to the Juno microservices architecture and adds health check functionality to the email service. The analytics service follows the established patterns from other services in the codebase, including NestJS structure, gRPC communication, Sentry integration, and Docker containerization.

Analytics Service Implementation:
The new analytics service includes all foundational components: AppController, AppService, HealthModule with gRPC health checks, Sentry error filtering, TypeScript configuration, Jest testing setup, and proper Docker integration. The service structure mirrors existing services like auth-service and email-service, maintaining architectural consistency across the microservices ecosystem.

Email Service Enhancement:
The email service has been enhanced with health check capabilities by adding a HealthModule and HealthController that implement the gRPC health checking protocol. This brings the email service in line with other services that already have health monitoring functionality.

Docker Infrastructure Updates:
Docker configurations have been updated to support the new analytics service across development and production environments. This includes additions to docker-compose-dev.yml, Dockerfile, Dockerfile.dev, and live package configurations. The changes also standardize Docker syntax by converting lowercase 'as' to uppercase 'AS' throughout the Dockerfiles.

Development Tooling:
The root package.json has been updated with analytics service test scripts and consolidated formatting commands. All services now include the ANALYTICS_SERVICE_ADDR environment variable for inter-service communication.

The implementation demonstrates a well-structured approach to adding new microservices to the platform while maintaining consistency with existing architectural patterns.

Confidence score: 2/5

• This PR contains several critical configuration errors that will prevent the analytics service from starting and running correctly
• Score lowered due to incorrect environment variable usage (FILE_COMMAND instead of ANALYTICS_COMMAND) in multiple Docker and package.json configurations
• Pay close attention to docker-compose-dev.yml, package.json test scripts, and potential port conflicts across services

PR Checklist Score: 78/100

Areas needing improvement:

General

• Functions have been modularized appropriately
• Some unused dependencies present (@sendgrid/mail, axios in analytics-service package.json)
• Missing @sentry/node dependency that other services include

Backend

• Critical configuration errors: FILE_COMMAND used instead of ANALYTICS_COMMAND in docker-compose-dev.yml and package.json
• Health controllers have unimplemented Watch methods that throw errors
• Potential port conflicts with multiple services using port 5000
• Missing environment variable validation in main.ts files

_{27 files reviewed, 5 comments}

_{Edit Code Review Bot Settings | Greptile}