> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/collect-data.md). # Collect Data - [BYOC - Bring Your Own Cloud](https://docs.groundcover.com/collect-data/byoc.md) - [Setup BYOC with AWS](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-aws.md) - [AWS PrivateLink Setup](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-aws/aws-privatelink-setup.md) - [EKS add-on](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-aws/eks-add-on.md) - [Setup BYOC with GCP](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-gcp.md) - [Running the groundcover sensor on GKE Autopilot](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-gcp/running-the-groundcover-sensor-on-gke-autopilot.md): Running the privileged groundcover sensor on GKE Autopilot requires an approved WorkloadAllowlist and Autopilot mode in the chart. - [Enable AI models for Agent Mode](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-gcp/enable-ai-models-for-agent-mode.md): Enable the Anthropic Claude models required for groundcover Agent in a GCP BYOC deployment. - [Setup BYOC with Azure](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-azure.md) - [Azure PrivateLink Setup](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-azure/azure-privatelink-setup.md) - [Enable AI models for Agent Mode](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-azure/enable-ai-models-for-agent-mode.md): Reference for the Azure resources groundcover provisions to power Agent Mode in an Azure BYOC deployment. - [High Availability](https://docs.groundcover.com/collect-data/byoc/high-availability.md) - [Disaster Recovery](https://docs.groundcover.com/collect-data/byoc/disaster-recovery.md) - [Ingestion Endpoints](https://docs.groundcover.com/collect-data/byoc/ingestion-endpoints.md) - [Deploying in Sensor-Only mode](https://docs.groundcover.com/collect-data/byoc/deploying-in-sensor-only-mode.md) - [OpenTelemetry](https://docs.groundcover.com/collect-data/opentelemetry.md): Ingest and visualize OTEL data with groundcover - [Sending from Kubernetes Pods](https://docs.groundcover.com/collect-data/opentelemetry/sending-from-kubernetes-pods.md) - [Sending from an OpenTelemetry Collector](https://docs.groundcover.com/collect-data/opentelemetry/sending-from-an-opentelemetry-collector.md) - [Sending from Standalone Applications](https://docs.groundcover.com/collect-data/opentelemetry/sending-from-standalone-hosts.md) - [Ingestion Keys](https://docs.groundcover.com/collect-data/ingestion-keys.md): Secure, write‑focused credentials for streaming data into groundcover - [Data Sources](https://docs.groundcover.com/collect-data/data-sources.md) - [AWS](https://docs.groundcover.com/collect-data/data-sources/aws.md): Ingesting CloudWatch data in groundcover - [Monitor Lambdas using OTEL Layers](https://docs.groundcover.com/collect-data/data-sources/aws/monitor-lambda-functions.md) - [Ingest CloudWatch Metrics](https://docs.groundcover.com/collect-data/data-sources/aws/ingest-cloudwatch-metrics.md) - [Ingest CloudWatch Logs](https://docs.groundcover.com/collect-data/data-sources/aws/ingest-cloudwatch-logs.md) - [Using CloudFormation For CloudWatch Logs Integration](https://docs.groundcover.com/collect-data/data-sources/aws/ingest-cloudwatch-logs/using-cloudformation-for-cloudwatch-logs-integration.md) - [Manual Setup Of The Integration](https://docs.groundcover.com/collect-data/data-sources/aws/ingest-cloudwatch-logs/manual-setup-of-the-integration.md) - [Ingest Logs Stored on S3](https://docs.groundcover.com/collect-data/data-sources/aws/ingest-logs-stored-on-s3.md) - [Integrate CloudWatch Grafana Datasource](https://docs.groundcover.com/collect-data/data-sources/aws/integrate-cloudwatch-grafana-datasource.md) - [Adding AWS Integration with a Backend on Another Cloud Provider](https://docs.groundcover.com/collect-data/data-sources/aws/adding-aws-integration-with-a-backend-on-another-cloud-provider.md) - [AWS Cost & Usage](https://docs.groundcover.com/collect-data/data-sources/aws/aws-cost-and-usage.md): Bring your AWS Cost and Usage Report (CUR) into groundcover. - [Monitor VPC, RDS & DynamoDB](https://docs.groundcover.com/collect-data/data-sources/aws/monitor-vpc-rds-dynamodb.md): Monitor AWS VPC subnets, RDS instances, and DynamoDB tables with a single consolidated integration. - [GCP](https://docs.groundcover.com/collect-data/data-sources/google-cloud-monitoring.md): Ingesting Google Cloud Monitoring data in groundcover - [Ingest Google Cloud Monitoring Metrics](https://docs.groundcover.com/collect-data/data-sources/google-cloud-monitoring/ingest-google-cloud-monitoring-metrics.md) - [Stream Logs using Pub/Sub](https://docs.groundcover.com/collect-data/data-sources/google-cloud-monitoring/stream-logs-using-pub-sub.md) - [Integrate Google Cloud Monitoring Grafana Datasource](https://docs.groundcover.com/collect-data/data-sources/google-cloud-monitoring/integrate-google-cloud-monitoring-grafana-datasource.md) - [Adding GCP Integration with a Backend on Another Cloud Provider](https://docs.groundcover.com/collect-data/data-sources/google-cloud-monitoring/adding-gcp-integration-with-a-backend-on-another-cloud-provider.md) - [Azure](https://docs.groundcover.com/collect-data/data-sources/azure.md) - [Collect Azure logs](https://docs.groundcover.com/collect-data/data-sources/azure/collect-application-insights-logs.md) - [Ingest Azure Monitor Metrics](https://docs.groundcover.com/collect-data/data-sources/azure/ingest-azure-monitor-metrics.md) - [Prometheus](https://docs.groundcover.com/collect-data/data-sources/prometheus.md): Integrate with Prometheus - [Scraping Metrics in Kubernetes](https://docs.groundcover.com/collect-data/data-sources/prometheus/scrape-using-sensor.md): Automatically scrape metrics from pods and other services - [Scraping Metrics in Standalone Hosts](https://docs.groundcover.com/collect-data/data-sources/prometheus/scraping-metrics-in-standalone-hosts.md): Automatically scrape metrics from processes running on standalone hosts - [Scraping Metrics from groundcover Backend](https://docs.groundcover.com/collect-data/data-sources/prometheus/scrape-using-sensor-1.md): Automatically scrape metrics from processes running on cloud hosts - [Pushing Metrics using Remote Write](https://docs.groundcover.com/collect-data/data-sources/prometheus/push-metrics-to-groundcover.md): Push Prometheus metrics directly to groundcover. - [DataDog](https://docs.groundcover.com/collect-data/data-sources/datadog.md): Learn how to ingest DataDog generated Traces & Metrics directly into groundcover - [Shipping from the DataDog Agent](https://docs.groundcover.com/collect-data/data-sources/datadog/shipping-from-the-datadog-agent.md) - [Sending Directly from Instrumented Services](https://docs.groundcover.com/collect-data/data-sources/datadog/sending-directly-from-instrumented-services.md) - [MongoDB Atlas](https://docs.groundcover.com/collect-data/data-sources/mongodb-atlas.md): Scrape metrics from your MongoDB Atlas - [MongoDB Atlas Metrics](https://docs.groundcover.com/collect-data/data-sources/mongodb-atlas/mongodb-atlas-metrics.md): Metrics groundcover collects from MongoDB Atlas. - [Redis Cloud](https://docs.groundcover.com/collect-data/data-sources/redis-cloud.md): Collect metrics from your Redis Cloud instances - [Redis Metrics](https://docs.groundcover.com/collect-data/data-sources/redis-cloud/redis-metrics.md): Metrics groundcover collects from Redis Cloud. - [RabbitMQ](https://docs.groundcover.com/collect-data/data-sources/rabbitmq.md): Collect metrics from your RabbitMQ nodes - [RabbitMQ Metrics](https://docs.groundcover.com/collect-data/data-sources/rabbitmq/rabbitmq-metrics.md): Metrics groundcover collects from RabbitMQ. - [ArgoCD](https://docs.groundcover.com/collect-data/data-sources/argocd.md): Collect metrics from your ArgoCD components - [ArgoCD Metrics](https://docs.groundcover.com/collect-data/data-sources/argocd/argocd-metrics.md): Metrics groundcover collects from ArgoCD. - [Confluent Cloud](https://docs.groundcover.com/collect-data/data-sources/confluent-cloud.md): Collect metrics from your Confluent Cloud Kafka clusters and connectors - [Profiling Endpoints](https://docs.groundcover.com/collect-data/data-sources/profiling-endpoints.md): Send or scrape application profiles and uncover performance bottlenecks - [ClickHouse Database Monitoring](https://docs.groundcover.com/collect-data/data-sources/clickhouse-database-monitoring.md): Collect ClickHouse health metrics and query-performance traces without running a separate exporter - [PostgreSQL Database Monitoring](https://docs.groundcover.com/collect-data/data-sources/postgresql-database-monitoring.md): Collect PostgreSQL health metrics and query-performance traces without running a separate exporter - [FluentBit](https://docs.groundcover.com/collect-data/data-sources/fluentbit.md) - [Fluentd](https://docs.groundcover.com/collect-data/data-sources/fluentd.md) - [JSON Logs](https://docs.groundcover.com/collect-data/data-sources/json-logs.md) - [Vector](https://docs.groundcover.com/collect-data/data-sources/vector.md): Send logs, traces, and metrics to groundcover using Vector - [Cloudflare](https://docs.groundcover.com/collect-data/data-sources/cloudflare.md) - [Enriching 3rd Party Data](https://docs.groundcover.com/collect-data/data-sources/enriching-3rd-party-data.md) - [AI Tools Observability](https://docs.groundcover.com/collect-data/data-sources/ai-tools-observability.md) - [Claude Code Metrics](https://docs.groundcover.com/collect-data/data-sources/ai-tools-observability/claude-code-metrics.md): Metrics groundcover collects from Claude Code. - [Istio](https://docs.groundcover.com/collect-data/data-sources/istio.md): Monitoring Istio Service Mesh with groundcover. - [CI/CD Integrations](https://docs.groundcover.com/collect-data/ci-cd-integrations.md) - [GitHub CI/CD Actions](https://docs.groundcover.com/collect-data/ci-cd-integrations/github-ci-cd-actions.md) - [Adding Source control context](https://docs.groundcover.com/collect-data/ci-cd-integrations/source-control-gitlab-github.md): Enrich traces with relevant source control metadata. - [Data Pipelines](https://docs.groundcover.com/collect-data/data-pipelines.md) - [Logs Pipeline](https://docs.groundcover.com/collect-data/data-pipelines/log-pipelines.md) - [Parsing Logs](https://docs.groundcover.com/collect-data/data-pipelines/log-pipelines/parsing-logs.md) - [Drop Logs](https://docs.groundcover.com/collect-data/data-pipelines/log-pipelines/drop-logs.md) - [Obfuscate Logs](https://docs.groundcover.com/collect-data/data-pipelines/log-pipelines/obfuscate-logs.md) - [Sensitive Attributes](https://docs.groundcover.com/collect-data/data-pipelines/log-pipelines/sensitive-attributes.md) - [Logs-to-Metrics](https://docs.groundcover.com/collect-data/data-pipelines/log-pipelines/logs-to-metrics.md) - [Merging Multiline Logs](https://docs.groundcover.com/collect-data/data-pipelines/log-pipelines/merging-multiline-logs.md) - [Metrics Aggregation](https://docs.groundcover.com/collect-data/data-pipelines/metrics-aggregation.md) - [Traces Pipeline](https://docs.groundcover.com/collect-data/data-pipelines/traces-pipeline.md) - [Filter Traces](https://docs.groundcover.com/collect-data/data-pipelines/traces-pipeline/filter-traces.md) - [Obfuscate Traces](https://docs.groundcover.com/collect-data/data-pipelines/traces-pipeline/obfuscate-traces.md) - [Span to Metrics](https://docs.groundcover.com/collect-data/data-pipelines/traces-pipeline/span-to-metrics.md) - [Customize deployment](https://docs.groundcover.com/collect-data/customize-deployment.md) - [Agents in host network mode](https://docs.groundcover.com/collect-data/customize-deployment/agents-in-host-network-mode.md) - [API Key Secret](https://docs.groundcover.com/collect-data/customize-deployment/api-key-secret.md) - [Argo CD](https://docs.groundcover.com/collect-data/customize-deployment/argo-cd.md) - [On-premise deployment](https://docs.groundcover.com/collect-data/customize-deployment/on-premise-deployment.md) - [Quay.io registry](https://docs.groundcover.com/collect-data/customize-deployment/quay.io-registry.md) - [Configuring sensor Deployment on Kubernetes](https://docs.groundcover.com/collect-data/customize-deployment/configuring-sensor-deployment-coverage.md) - [Enabling SSL Tracing in Java Applications](https://docs.groundcover.com/collect-data/customize-deployment/enabling-ssl-tracing-in-java-applications.md) - [Add custom environment labels](https://docs.groundcover.com/collect-data/customize-deployment/add-custom-environment-labels.md): Enhance your ability to easily monitor a group of clusters - [Telemetry](https://docs.groundcover.com/collect-data/customize-deployment/telemetry.md) - [Enrich workloads with service and team metadata](https://docs.groundcover.com/collect-data/enrich-workloads-with-service-and-team-metadata.md) - [Custom resource workloads](https://docs.groundcover.com/collect-data/custom-resource-workloads.md): How groundcover discovers Kubernetes Custom Resource Definitions and resolves matching instances to workloads. - [Monitor Data Sources Integrations](https://docs.groundcover.com/collect-data/monitor-data-sources-integrations.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.groundcover.com/collect-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.