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

{% hint style="info" %}
The endpoints depend on the namespace and release name that were used when installing groundcover. By default, both of these values are `groundcover` - make sure to adjust them if needed. Need help? Contact us [on slack](https://www.groundcover.com/join-slack)!
{% endhint %}

### 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 & Metrics)
* Zipkin Traces

{% hint style="success" %}
Ingesting the above using Sensor is the preferred method, if possible, as it allows groundcover to enrich the ingested data with relevant Kubernetes metadata.
{% endhint %}

#### 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](https://docs.victoriametrics.com/vmagent/) deployment which is responsible for [scraping custom metrics](broken://pages/kmBDsiOYlDknlDDj6Azb) and also serves as an endpoint for pushing metrics, for example [in the OTLP format.](broken://pages/X68dkW73WBvPgjjWojhz)

#### 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](https://opentelemetry.io/docs/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](https://vector.dev/) as a key component in the ingestion pipeline. In addition, it's used for supporting several integrations such as [DogStatsD ingestion](broken://pages/CNAzaqW2XDMH3kdAGCFh#redirecting-the-datadog-sdk).

#### Finding the endpoint

```
<release_name>-vector.<namespace>.svc.cluster.local

// For default installation values:
groundcover-vector.groundcover.svc.cluster.local
```


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://docs.groundcover.com/~/revisions/wppaVAUQcsAgts3lmC6b/architecture/service-endpoints-inside-the-cluster.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.