# Vector

[Vector](https://vector.dev) is a lightweight, ultra-fast tool for building observability pipelines. groundcover can natively ingest data shipped from Vector using multiple protocols, making it easy to integrate Vector into your existing observability stack.

{% hint style="info" %}
This feature is only available for BYOC and On-Prem deployment modes.
{% endhint %}

## Overview

Vector supports a wide variety of sources, transforms, and sinks. You can configure Vector to send logs, traces, and metrics directly to groundcover's BYOC endpoints using the appropriate sink types:

| Data Type   | Vector Sink                                                                                                    | groundcover Endpoint                                                                                                              |
| ----------- | -------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **Logs**    | [HTTP sink](https://vector.dev/docs/reference/configuration/sinks/http/)                                       | [JSON Logs endpoint](https://docs.groundcover.com/integrations/data-sources/json-logs)                                            |
| **Traces**  | [OpenTelemetry sink](https://vector.dev/docs/reference/configuration/sinks/opentelemetry/)                     | [OTLP endpoint](https://docs.groundcover.com/integrations/data-sources/opentelemetry/opentelemetry-direct-to-byoc-endpoint)       |
| **Metrics** | [Prometheus Remote Write sink](https://vector.dev/docs/reference/configuration/sinks/prometheus_remote_write/) | [Prometheus Remote Write endpoint](https://docs.groundcover.com/integrations/data-sources/prometheus/push-metrics-to-groundcover) |

### Configure Vector Integration using the data source wizard

In the [data sources page](https://app.groundcover.com/data-sources), search for the Vector. Click on this entry and open the Vector wizard to see a step-by-step guidance.

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2FF729rxj7dO7hsBDeLfMc%2Fimage.png?alt=media&#x26;token=872a3721-0aeb-4b4c-91c7-9784a7f79903" alt=""><figcaption></figcaption></figure>

The backend endpoint will be pre-populated for you. You can either create a new ingestion key (recommended) or reuse an existing one.

We also recommend adding enrichment fields to make your logs easily tracked.

Apply the relevant configuration to your Vector pipeline and you're done!

## Monitoring Your Integration

Once the integration is live, you can verify data is being received:

* **Logs**: Check the [Logs](https://app.groundcover.com/logs) page or the [Explore](https://app.groundcover.com/explore/data-explorer) page
* **Traces**: View traces in the [Traces](https://app.groundcover.com/traces) page
* **Metrics**: Query metrics in the [Metrics](https://app.groundcover.com/metrics) page or Grafana

## Related Documentation

* [JSON Logs](https://docs.groundcover.com/integrations/data-sources/json-logs)
* [OpenTelemetry - Direct to BYOC Endpoint](https://docs.groundcover.com/integrations/data-sources/opentelemetry/opentelemetry-direct-to-byoc-endpoint)
* [Pushing Metrics using Remote Write](https://docs.groundcover.com/integrations/data-sources/prometheus/push-metrics-to-groundcover)
* [Enriching Data with Headers](https://github.com/groundcover-com/docs/blob/main/integrations/data-sources/enriching-data-with-headers.md)
* [Ingestion Keys](https://docs.groundcover.com/use-groundcover/remote-access-and-apis/ingestion-keys)