Service endpoints inside the cluster
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.
Sensor
Sensor
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.
Finding the endpoint
<release_name>-sensor.<namespace>.svc.cluster.local
// For default installation values:
groundcover-sensor.groundcover.svc.cluster.local
Custom Metrics
Custom Metrics
is a VMAgent deployment which is responsible for scraping custom metrics and also serves as an endpoint for pushing metrics, for example in the OTLP format.
Finding the endpoint
<release_name>-custom-metrics.<namespace>.svc.cluster.local
// For default installation values:
groundcover-custom-metrics.groundcover.svc.cluster.local
OpenTelemetry Collector
groundcover includes an open telemetry collector out-of-the-box, enabling integration with every receiver, processor and exporter supported by the Open Telemetry stack.
Depending on your installation type, follow the instructions below
Finding the endpoint
<release_name>-opentelemetry-collector.<namespace>.svc.cluster.local
// For default installation values:
groundcover-opentelemetry-collector.groundcover.svc.cluster.local
Vector
groundcover uses Vector as a key component in the ingestion pipeline. In addition, it's used for supporting several integrations such as DogStatsD ingestion.
Finding the endpoint
<release_name>-vector.<namespace>.svc.cluster.local
// For default installation values:
groundcover-vector.groundcover.svc.cluster.local
Last updated