Update PostgreSQL module with metrics.

Change Summary

This update introduces a new parameter to the PostgreSQL configuration within the main.tf file of the database module. Specifically, the metrics.enabled parameter has been added and set to true, enabling metrics collection for the PostgreSQL instance.

Technical Details

• File Modified: IaC/modules/database/main.tf
• Resource: argocd_application named postgresql
• Added Parameter:

  parameter {
    name  = "metrics.enabled"
    value = "true"
  }
  

  This change configures the PostgreSQL deployment to enable metrics, which is likely to be used for monitoring and observability purposes.

Key Learnings & Insights

• Monitoring Importance: Enabling metrics underscores the importance of monitoring database performance and health. It allows for better observability and proactive issue detection.
• Configuration Management: Using Infrastructure as Code (IaC) to manage configuration ensures consistency and reduces manual errors. This approach also makes it easier to version control and audit changes.
• Trade-offs: Enabling metrics may introduce additional resource usage (CPU, memory) and requires proper handling to ensure it does not impact the primary database operations negatively.

Impact Assessment

• Performance: There may be a minor performance overhead due to metrics collection, though this is typically negligible unless metrics are excessively verbose.
• Security: Ensure that the metrics endpoint is secured and not exposed to the public internet to prevent unauthorized access.
• Maintainability: This change improves maintainability by providing deeper insights into database performance, aiding in quicker issue resolution.

Developer Notes

• Gotchas: Ensure that the monitoring solution is properly configured to collect and store these metrics. Otherwise, enabling them might lead to unnecessary resource consumption without benefit.
• Future Improvements: Consider adding conditional logic to enable metrics only in specific environments (e.g., staging, production) to avoid overhead in development environments.
• Context: This change is part of an ongoing effort to enhance observability across all microservices, aligning with our DevOps practices.