> 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/data-sources/profiling-endpoints.md).

# Profiling Endpoints

Send application profiles to groundcover and uncover performance bottlenecks

groundcover accepts raw pprof and OTLP Profiles over HTTP and gRPC. Send profiles generated inside your Kubernetes cluster to the sensor. Send profiles generated outside the cluster to your BYOC endpoint. Profile ingestion is enabled by default and requires no additional Helm configuration.

{% hint style="info" %}
Profile ingestion requires groundcover sensor version **1.13.1** or later.
{% endhint %}

## Where to send profiles

| Profiles generated             | Endpoint                                           | Authentication |
| ------------------------------ | -------------------------------------------------- | -------------- |
| Inside the Kubernetes cluster  | `groundcover-sensor.groundcover.svc.cluster.local` | Not required   |
| Outside the Kubernetes cluster | `{BYOC_ENDPOINT}`                                  | Ingestion key  |

Replace the service name or `groundcover` namespace if you use a different Helm release name or namespace. See [Ingestion Endpoints](/collect-data/byoc/ingestion-endpoints.md) for authentication methods and instructions for finding your BYOC endpoint.

## Accepted formats

* **Raw pprof:** A Google pprof protobuf body, uncompressed or gzip-compressed. Send it with `POST /profiling/upload` over HTTP port `8028` in-cluster or HTTPS port `443` externally. Include either the `workload` or `serviceName` query parameter.
* **OTLP Profiles over HTTP:** A protobuf-encoded OTLP `ExportProfilesServiceRequest` with `Content-Type: application/x-protobuf`. Send it with `POST /v1development/profiles` over HTTP port `4318` in-cluster or HTTPS port `443` externally.
* **OTLP Profiles over gRPC:** An OTLP Profiles export using `opentelemetry.proto.collector.profiles.v1development.ProfilesService/Export` on port `4317` in-cluster or port `443` externally.

{% hint style="info" %}
Raw pprof uploads are limited to 32 MiB before and after decoding. Each pprof can contain up to 64 sample types and 10,000 decoded sample rows.
{% endhint %}


---

# 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 dynamically 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/data-sources/profiling-endpoints.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.