Alert

[Bonusree]

Summary by CodeRabbit

• Documentation
  • Added/expanded a PostgreSQL monitoring and alerting guide covering Prometheus and Grafana setup for a managed PostgreSQL instance, including verification steps, an end-to-end “simulate a firing alert” walkthrough, a detailed alert reference (severity/duration/meaning), how to customize alert thresholds/enablement, and cleanup instructions.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d0eebafd-c32b-4d61-957a-a44f9e10dcaa

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

A new documentation file docs/guides/postgres/monitoring/alerting.md is added, providing a complete guide for configuring Prometheus-based alerting on a KubeDB-managed PostgreSQL instance, including prerequisites, Helm chart installation, end-to-end verification, alert simulation walkthrough, alert reference table, threshold customization, and cleanup instructions.

Changes

PostgreSQL Prometheus Alerting Guide

Layer / File(s)	Summary
Front-matter, prerequisites, and architecture overview docs/guides/postgres/monitoring/alerting.md	Adds page navigation front-matter, introductory guidance for new KubeDB users, prerequisites list, and an alerting architecture diagram.
Deploy PostgreSQL with Prometheus monitoring enabled docs/guides/postgres/monitoring/alerting.md	Documents the example PostgreSQL CR manifest with exporter, ServiceMonitor, and Prometheus label settings, plus commands to apply and verify readiness.
Install postgres-alerts and kubedb-grafana-dashboards Helm charts docs/guides/postgres/monitoring/alerting.md	Documents Helm install and verification commands for the postgres-alerts chart (PrometheusRule label requirements) and the kubedb-grafana-dashboards chart (Grafana token creation, feature gate, CRD verification).
End-to-end verification checks docs/guides/postgres/monitoring/alerting.md	Documents steps to confirm exporter reachability, Prometheus target UP status, initial alert inactivity, AlertManager inspection, and Grafana dashboard exploration.
Alert simulation walkthrough and alert reference docs/guides/postgres/monitoring/alerting.md	Procedures to simulate a firing PostgresqlDown alert via StatefulSet scaling, observe state transitions in Prometheus and AlertManager, restore the instance, and a complete enumeration of alert groups with per-alert severity, duration, and meaning.
Customization, cleanup, and next steps docs/guides/postgres/monitoring/alerting.md	Shows how to customize alert thresholds via custom Helm values and helm upgrade, provides full cleanup commands for charts and instances, and links to related guides.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 Hop hop, the docs are here at last,
A guide to alerts, from future to past!
PrometheusRules labeled just right,
Grafana dashboards glowing with light.
Clean up when done — no mess shall remain,
The rabbit hops onward to document again! 🌟

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Alert' is vague and overly generic, failing to convey meaningful information about the substantial documentation addition for PostgreSQL alerting configuration.	Revise the title to be more descriptive, such as 'Add PostgreSQL monitoring alerting guide with Prometheus and Grafana setup' or similar, to clearly communicate the primary change.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch alert

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Visit the preview URL for this PR (updated for commit f437734):

https://kubedb-v2-hugo--pr907-alert-0http5ep.web.app

_{(expires Fri, 31 Jul 2026 10:01:15 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 0f29ae8ae0bd54a99bf2b223b6833be47acd5943}

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
34854333	Triggered	Curl Username Password	df23449	docs/guides/neo4j/monitoring/alerting.md	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[fr-sarker]

update this line:
Note that Neo4j High CPU Usage shows "No data" on clusters without cAdvisor's container_cpu_usage_seconds_total metric exposed (common on some k3s setups) — this is an environment limitation, not a chart bug.

[fr-sarker]

update this
The previous section showed that all genuine health alerts (everything except the buggy disk rules) are INACTIVE while the cluster is healthy. This section deliberately triggers the KubeDBNeo4jPhaseNotReady critical alert so you can observe the full alert lifecycle — from firing in Prometheus through to the AlertManager dashboard — and then resolve it.