> 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/~/revisions/1mY0CQn12Klyi0QiItHv/integrations/data-sources.md). # Data Sources The groundcover platform was built to be an all-in-one observability solution for cloud-native environments. It was built to ingest any data source directly into groundcover's in-cloud backend using any protocol supported by OpenTelemetry or Prometheus. It supports any log stream from sources like Fluentd, Fluentbit, Logstash, or CloudWatch logs. Metrics can be ingested via Prometheus remote-write or directly from agents like StatsD and Telegraf. Traces can be ingested from any application instrumented with OpenTelemetry or Datadog’s SDK.


Traces	All your traces are sourced out-of-the-box
Logs	All your logs are sourced out-of-the-box
Metrics	All your metrics are built out-of-the-box
	Integrate with OpenTelemetry	OpenTelemetry	OpenTelemetry
	Scrape your Prometheus custom metrics	Prometheus	Prometheus
	Ingest your data from Amazon CloudWatch	AWS	AWS
	Automatically ingest Datadog traces & metrics	DataDog	DataDog
	Integrate Istio distributed tracing and custom metrics	Istio	Istio
	Ingest data from Google Cloud Monitoring Google Cloud Monitoring		GCP
	Import all your logs from fluentbit	FluentBit	FluentBit
	Ingest your data from fluentd
	Import your logs from logstash
	Import all your metrics from StatsD
	Ingest your metrics directly from telegraf

--- # 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/~/revisions/1mY0CQn12Klyi0QiItHv/integrations/data-sources.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.