-
Notifications
You must be signed in to change notification settings - Fork 293
[ROB-3081] Add GCP alerts webhook documentation #2001
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Add documentation for setting up a webhook notification channel in GCP Cloud Monitoring to forward alerts to Robusta. This covers creating a managed webhook channel with basic authentication using the Robusta account ID and API key.
Alerts must include a cluster or cluster_name label for Robusta to properly route them. Added instructions for setting this via custom labels in the alerting policy's Documentation section.
|
❌ Docker build failed for |
WalkthroughAdds a new GCP Cloud Monitoring webhook integration doc and updates documentation navigation to include the new page. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/configuration/alertmanager-integration/gcp-monitoring.rst`:
- Around line 45-56: Update "Step 3: Use the Webhook in Alerting Policies" to
instruct users to add the cluster_name as an Alert Policy User Label (structured
key/value) instead of placing it in the policy's Documentation section;
specifically, replace the bullet that tells them to add the label in
Documentation with instructions to add a User Label key: cluster_name and value:
your cluster name (or external), and mention that this label will be delivered
in the webhook JSON under incident.policy_user_labels so Robusta can read it.
🧹 Nitpick comments (1)
docs/index.rst (1)
43-43: Consider alphabetical ordering of entries.The new "GCP Cloud Monitoring" entry is placed after "Google Managed Prometheus" (line 42), but alphabetically "GCP" should come before "Google" (G-C-P vs G-o-o-g-l-e).
📝 Suggested alphabetical ordering
Embedded Prometheus Stack <configuration/alertmanager-integration/embedded-prometheus> - Google Managed Prometheus <configuration/alertmanager-integration/google-managed-prometheus> GCP Cloud Monitoring <configuration/alertmanager-integration/gcp-monitoring> + Google Managed Prometheus <configuration/alertmanager-integration/google-managed-prometheus> Grafana - Self-Hosted <configuration/alertmanager-integration/grafana-self-hosted>
No description provided.