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.

Profile ingestion requires groundcover sensor version 1.13.1 or later.

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 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.

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.