FAQ #

Project #

What is this project? #

This project was initiated by Qonto’s SRE engineers to share and improve database monitoring systems.

Is there similar intiatives? #

Yes, we took lots of inspiration on Prometheus-operator runbook, which provides similar experience for Prometheus & Kubernetes technologies.

Deployment #

Can I deploy the database monitoring framework on Prometheus standalone deployment? #

Project was designed for Kubernetes deployment using Prometheus operator, but you can use for standalone deployment.

Use the format=PrometheusConfigurationFile Helm parameter to render rules as Prometheus rule files.

Alerts #

Customize alerts #

All alerts can be customized by overriding rules in Helm chart values.

Example to override priority severity for RDSExporterErrors alert of RDS exporter alerts:

1. Create a custom_values.yaml file with your overrided settings

   # custom_values.yaml
   rules:
     RDSExporterErrors:
       severity: critical # Override priority for RDSExporterErrors alert
   

2. Install (or update) deployment with overridden values

   helm upgrade --install prometheus-rds-alerts-chart oci://public.ecr.aws/qonto/prometheus-rds-alerts-chart:latest --values custom_values.yaml
   

Disable an alert #

If an alert is not relevant for your environment, you can disable using enabled

rules:
  RDSCPUUtilization:
    enabled: false

Pint comments #

If you are using Pint as Prometheus rule linter/validator, you can add pint comments to alert using the pintComments parameter.

Recommendation

Pint ignore comments should be set only on alerts that are relevant for your environment otherwise you should disable the rule.

Example to add pint disable promql/series on PostgreSQLInvalidIndex rule:

rules:
  PostgreSQLInvalidIndex:
    pintComments:
      - disable promql/series

Will be render as:

...
- alert: "PostgreSQLInvalidIndex"
  # pint disable promql/series
  expr: |
    ...