As the operator is level 5 certified, the system expose various metrics about its operand i.e. FEP containers.
FEP generates lot of useful database statistics via various views. The default statistics can be further augmented by using extensions like pg_stat_statements.
FEPExporter container by default is configured to extract useful database statistics and make the metrcs available to Prometheus on the platform. External components and utilities can be used to visualise, analyse, trigger alerts and take operational decision based on exposed metrics.
FEPExporter also sets defalt alert rules based on Prometheus metrics which are useful for active monitoring of FEP cluster.
Refer to "FEPExporter Custom Resource" in the Reference for FEPExporter Custom Resource parameters.
Custom queries to scrape metrics can be added in CR in optional section.
Custom Prometheus alert rules are created by user manually.
User may define pgMetricsUser, pgMetricsPassword and pgMetricsUserTls in target FEPCluster. If it is defined, FEPExporter will use metrics user details to connect to FEP cluster machines. All metrics user fields are optional and can be omitted in FEPCluster.
Refer to "FEPCluster Parameter" in the Reference for FEPCluster parameters.
User may define enableMonitoring flag as part of FEPCluster CR to monitor FEPCluster. It will automatically create FEPCluster specific FEPExporter so matrics scraping for FEPCluster will work.
Refer to "FEPCluster Parameter" in the Reference for FEPCluster parameters.
FEPExporter will be named as <cluster-name>-fepexporter.
Once FEPExporter created automatically, user can modify it manually from FEPExporter CR.
If FEPCluster will be deleted, it will delete dependent FEPExporter as well.
MTLS for FEPExporter will only supported when tls configuration defined for both Prometheus & FEPExporter specs.
