LogoLogo
Log in|Playground
  • Welcome
    • Introduction
    • FAQ
  • Capabilities
    • Log Management
    • Infrastructure Monitoring
    • Application Performance Monitoring (APM)
      • Application Metrics
      • Traces
      • Supported Technologies
    • Real User Monitoring (RUM)
  • Getting Started
    • Requirements
      • Kubernetes requirements
      • Kernel requirements for eBPF sensor
      • CPU architectures
      • ClickHouse resources
    • Installation & updating
    • Connect Linux hosts
    • Connect RUM
    • 5 quick steps to get you started
    • groundcover MCP
      • Configure groundcover's MCP Server
      • Getting-started Prompts
      • Real-world Use Cases
  • Use groundcover
    • Monitors
      • Create a new Monitor
      • Issues page
      • Monitor List page
      • Silences page
      • Monitor Catalog page
      • Monitor YAML structure
      • Embedded Grafana Alerts
        • Create a Grafana alert
    • Dashboards
      • Create a dashboard
      • Embedded Grafana Dashboards
        • Create a Grafana dashboard
        • Build alerts & dashboards with Grafana Terraform provider
        • Using groundcover datasources in a Self-hosted Grafana
    • Insights
    • Explore & Monitors query builder
    • Workflows
      • Create a new Workflow
      • Workflow Examples
      • Alert Structure
    • Search & Filter
    • Issues
    • Role-Based Access Control (RBAC)
    • Service Accounts
    • API Keys
    • APIs
    • Log Patterns
    • Drilldown
    • Scraping custom metrics
      • Operator based metrics
      • kube-state-metrics
      • cadvisor metrics
    • Backup & Restore Metrics
    • Metrics & Labels
    • Add custom environment labels
    • Configuring Pipelines
      • Writing Remap Transforms
      • Logs Pipeline Examples
      • Traces Pipeline Examples
      • Logs to Events Pipeline Examples
      • Logs/Traces Sensitive Data Obfuscation
      • Sensitive Data Obfuscation using OTTL
      • Log Filtering using OTTL
    • Querying your groundcover data
      • Query your logs
        • Example queries
        • Logs alerting
      • Query your metrics
      • Querying you data using an API
      • Using KEDA autoscaler with groundcover
  • Log Parsing with OpenTelemetry Pipelines
  • Log and Trace Correlation
  • RUM
  • Customization
    • Customize deployment
      • Agents in host network mode
      • API Key Secret
      • Argo CD
      • On-premise deployment
      • Quay.io registry
      • Configuring sensor deployment coverage
      • Enabling SSL Tracing in Java Applications
    • Customize usage
      • Filtering Kubernetes entities
      • Custom data retention
      • Sensitive data obfuscation
      • Custom storage
      • Custom logs collection
      • Custom labels and annotations
        • Enrich logs and traces with pod labels & annotations
        • Enrich metrics with node labels
      • Disable tracing for specific protocols
      • Tuning resources
      • Controlling the eBPF sampling mechanism
  • Integrations
    • Overview
    • Workflow Integrations
      • Slack Webhook Integration
      • Opsgenie Integration
      • Webhook Integration
        • Incident.io
      • PagerDuty Integration
      • Jira Webhook Integration
      • Send groundcover Alerts to Email via Zapier
    • Data sources
      • OpenTelemetry
        • Traces & Logs
        • Metrics
      • Istio
      • AWS
        • Ingest CloudWatch Metrics
        • Ingest CloudWatch Logs
        • Ingest Logs Stored on S3
        • Integrate CloudWatch Grafana Datasource
      • GCP
        • Ingest Google Cloud Monitoring Metrics
        • Stream Logs using Pub/Sub
        • Integrate Google Cloud Monitoring Grafana Datasource
      • Azure
        • Ingest Azure Monitor Metrics
      • DataDog
        • Traces
        • Metrics
      • FluentBit
      • Fluentd
      • JSON Logs
    • 3rd-party metrics
      • ActiveMQ
      • Aerospike
      • Cassandra
      • CloudFlare
      • Consul
      • CoreDNS
      • Etcd
      • HAProxy
      • Harbor
      • JMeter
      • K6
      • Loki
      • Nginx
      • Pi-hole
      • Postfix
      • RabbitMQ
      • Redpanda
      • SNMP
      • Solr
      • Tomcat
      • Traefik
      • Varnish
      • Vertica
      • Zabbix
    • Source control (Gitlab/Github)
  • Architecture
    • Overview
    • inCloud Managed
      • Setup inCloud Managed with AWS
        • AWS PrivateLink Setup
        • EKS add-on
      • Setup inCloud Managed with GCP
      • Setup inCloud Managed with Azure
      • High Availability
      • Disaster Recovery
      • Ingestion Endpoints
      • Deploying in Sensor-Only mode
    • Security considerations
      • Okta SSO - onboarding
    • Service endpoints inside the cluster
  • Product Updates
    • What's new?
    • Earlier updates
      • 2025
        • Mar 2025
        • Feb 2025
        • Jan 2025
      • 2024
        • Dec 2024
        • Nov 2024
        • Oct 2024
        • Sep 2024
        • Aug 2024
        • July 2024
        • May 2024
        • Apr 2024
        • Mar 2024
        • Feb 2024
        • Jan 2024
      • 2023
        • Dec 2023
        • Nov 2023
        • Oct 2023
Powered by GitBook
On this page
  • Basic Prompts to Try
  • Pull Logs
  • Get K8s Resource Specs
  • Find Slow Workloads
  • Investigate Issues
  • Paste an Issue Link
  • Investigate Multiple Issues
  • Automate Coding & Debugging
  • Iterate Over Test Results
  • Deploy & Verify
Export as PDF
  1. Getting Started
  2. groundcover MCP

Getting-started Prompts

Once your MCP server is connected, you can dive right in.

Here are a few prompts to try. They work out of the box with agents like Cursor, Claude, or VS Code:

💡 Starting your request with “Use groundcover” is a helpful nudge - it pushes the agent toward MCP tools and context.

Basic Prompts to Try

MCP supports complex, multi-step flows, but starting simple is the best way to ramp up.

Pull Logs

Prompt:

Use groundcover to get 5 logs from the workload news-service from the past 15 minutes.

Expected behavior: The agent should call query_logs and show recent logs for that workload.

Get K8s Resource Specs

Prompt:

Use groundcover to get the spec of the chat-app deployment.

Expected behavior: The agent should call get_k8s_object_yaml and return the YAML or a summary of it.

Find Slow Workloads

Prompt:

Use groundcover to show the top 5 workloads by P95 latency.

Expected behavior: The agent should call get_workloads and return the relevant workloads with their P95 latency.

Investigate Issues

When something breaks, your agent can help investigate and make sense of it.

Paste an Issue Link

Prompt:

I got an alert for this critical groundcover issue. Can you investigate it?
https://app.groundcover.com/monitors/issues?...

Expected behavior: The agent should use query_monitors_issues, pull issue details, and kick off a relevant investigation using logs, traces, and metadata.

Investigate Multiple Issues

Prompt:

I got multiple alerts in the staging-env namespace. Can you help me look into them using groundcover?

Expected behavior: The agent should use query_monitors_issues to pull all related issues and start going through them one by one.

Automate Coding & Debugging

groundcover’s MCP can also be your coding sidekick. Instead of digging through tests and logs manually, deploy your changes and let the agent take over.

Iterate Over Test Results

Prompt:

Use groundcover to debug this code. For each test, print relevant logs with test_id, and dive into any error logs.

Expected behavior: The agent should update the code with log statements, deploy it, and use query_logs to trace and debug.

Deploy & Verify

Prompt:

Please deploy this service and verify everything works using groundcover.

Expected behavior: The agent should assist with deployment, then check for issues, error logs, and traces via groundcover.

Last updated 2 days ago