Service endpoints inside the cluster
Last updated
Last updated
Some of the integrations available in groundcover require finding our services' endpoints. In this section, we list these services and provide instructions on how to find the required configuration.
The DaemonSet which is responsible for most of the data collection inside a k8s cluster is called sensor
. It exposes several ingestion endpoints:
DataDog Traces
OpenTelemetry Traces & Logs
Zipkin Traces
Ingesting the above using Sensor is the preferred method, if possible, as it allows groundcover to enrich the ingested data with relevant Kubernetes metadata.
Custom Metrics
is a deployment which is responsible for and also serves as an endpoint for pushing metrics, for example
Depending on your installation type, follow the instructions below
groundcover includes an out-of-the-box, enabling integration with every receiver, processor and exporter supported by the Open Telemetry stack.
groundcover uses as a key component in the ingestion pipeline. In addition, it's used for supporting several integrations such as .