Groundcover

Connect Cased to Groundcover for Kubernetes monitoring and observability

Groundcover

Groundcover is a Kubernetes monitoring and observability platform that provides comprehensive insights into your cluster’s health, performance, and resource utilization. Cased integrates with Groundcover to help you query cluster information, discover resources, and monitor node metrics.

Available Actions

With Groundcover connected, Cased agents can handle:

• Cluster Discovery: List and explore Kubernetes clusters monitored by Groundcover
• Resource Discovery: List namespaces, workloads, deployments, and nodes in your cluster
• Node Monitoring: Query resource utilization metrics (CPU, memory, capacity) for cluster nodes
• Cluster Topology: Understand cluster organization and resource structure
• Troubleshooting: Investigate node resource pressure and capacity issues

Setup

To connect Groundcover to Cased, you’ll need an API Key and Backend ID.

Step 1: Create an API Key

1. In Groundcover, click the settings button in the bottom left corner
2. Select “Access” from the sidebar menu
3. Click on the “API Keys” tab
4. Create a new API key and assign it to a service account with appropriate RBAC permissions
5. Copy the API key (it will only be displayed once)

Step 2: Find Your Backend ID

1. In Groundcover, go to Settings → Access → API Keys
2. Your Backend ID (cluster identifier) is displayed on this page
3. Copy the Backend ID

Alternatively, for multi-backend setups:

• Open Data Explorer in Groundcover
• Click the Backend picker in the top-right corner
• Copy the backend’s name/ID

Connect to Cased

1. Go to app.cased.com/connections/groundcover
2. Enter your API Key and Backend ID
3. Cased agent will start using the Groundcover connection

Workflow Triggers

Cased can automatically trigger workflows when Groundcover alerts fire. This enables automated incident response for Kubernetes issues like:

• Pod crashes and CrashLoopBackOff
• Resource exhaustion (OOMKilled, CPU throttling)
• Configuration errors (missing secrets, invalid image references)
• Node pressure and capacity issues

Setting Up Webhook Triggers

1. Get your Cased webhook URL:

   • Go to your organization’s settings in Cased
   • Find your API key
   • Your webhook URL is: https://app.cased.com/webhooks/<YOUR_API_KEY>/groundcover/

2. Configure Groundcover to send alerts:

   • In Groundcover, go to Settings → Integrations → Notifications
   • Click “Webhook” to create a new webhook integration
   • Give it a name (e.g., cased)
   • Enter your webhook URL: https://app.cased.com/webhooks/<YOUR_API_KEY>/groundcover/
   • No additional headers are required
   • Click Save

3. Create a workflow in Cased:

   • Go to app.cased.com/agents
   • Click “Create Agent”
   • Under triggers, select “Groundcover” and choose “Alert fired”
   • Configure your workflow instructions

Pre-built Workflow Template

Cased includes a Kubernetes Error Analyzer template that automatically:

• Classifies alerts (configuration errors, resource exhaustion, runtime issues)
• Gathers diagnostic information from kubectl and monitoring tools
• Identifies root cause and impacted resources
• Reports findings to Slack
• Spawns fix sessions for configuration errors

To use the template, select “Kubernetes Error Analyzer” when creating a new workflow.

Alert Context

When a Groundcover alert triggers a workflow, Cased provides the following context variables:

Variable	Description
alert_title	The alert title
alert_name	The alertname label
severity	Alert severity (critical, warning, info)
cluster_id	The Groundcover backend/cluster ID
description	Alert description from annotations
labels	All alert labels
annotations	All alert annotations