Learn how to configure a Grepr OpenTelemetry integration to connect with Grafana Cloud, enabling you to ingest logs to a Grepr pipeline for processing and send the processed logs to your Grafana Cloud instance. # Configure Grafana Cloud connections with a Grepr integration To connect Grepr to Grafana Cloud, use the Grepr OpenTelemetry integration to ingest logs into your Grepr pipelines for processing and send the processed logs to an OTLP endpoint in your Grafana Cloud account. To send logs to a Grepr pipeline before forwarding them to Grafana Cloud, you change your collector configuration to send the logs to a Grepr endpoint URL instead of the Grafana Cloud OTLP endpoint. The Grepr OpenTelemetry integration supports several Grafana-compatible collectors, including the Grafana Alloy collector, the OpenTelemetry Collector, and Grafana Agent (EOL). You can use the Grepr UI or REST API to create an OpenTelemetry integration configured for Grafana Cloud. To learn how to create an OpenTelemetry integration in the Grepr UI and configure collectors to send logs to Grepr, see [Use an OpenTelemetry integration in a Grepr pipeline](#use-otel-integration-with-grafana). > Although this page describes using an integration to create a pipeline for sourcing and sending data with a single observability platform, your pipelines can use multiple integrations to source and sink data for different platforms. For example, you can create a pipeline with a Datadog integration that's used to source data from Datadog agents, and a Splunk integration and sink that sends the pipeline output to Splunk. ## Requirements To connect Grepr with Grafana Cloud using an OpenTelemetry integration, you need: * A Grafana Cloud Access Policy token with write access to logs. See [Grafana Cloud Access Policies](https://grafana.com/docs/grafana-cloud/security-and-account-management/authentication-and-permissions/access-policies/). * A Grafana Cloud OTLP Endpoint. See [Send data to the Grafana Cloud OTLP endpoint](https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/). ## Use an OpenTelemetry integration with Grafana in a Grepr pipeline \[#use-otel-integration-with-grafana] ### Step 1: Create an OpenTelemetry integration To create an OpenTelemetry integration configured for Grafana Cloud in the Grepr UI: 1. Go to the **Integrations** page in the Grepr UI and click **Add new** next to **Observability Vendors**. 2. In the **Add Observability Vendor** dialog: * In the **Type** menu, select **Open Telemetry**. * In the **Name** field, enter a name for the integration. Grepr recommends naming it descriptively so it's easy to identify. For example, `grafana-cloud-prod-logs`. * In the **Base Endpoint URL** field, enter your Grafana Cloud OTLP endpoint URL. * Click **Add Header**. * In the **Header Name** field, enter `Authorization`. * In the **Header Value** field, enter `Bearer `. Replace `` with the token generated from your Grafana Cloud Access Policy. * Select the **Make header secret** checkbox. 3. Click **Create**. 4. Save the `GREPR TOKEN` displayed in the confirmation dialog securely. #### Optional: Grant team access to the integration When you have teams in your Grepr organization, you can grant access to the integration to one or more of those teams. To configure team access when you create or edit an integration: 1. In the **Grant Team Access** section, click the plus sign icon (+). 2. Select the team or teams that should be granted access to the integration. 3. Click **Create**. To learn more, see [Manage teams in the Grepr platform](/admin/manage-teams) and [Permissions in the Grepr platform](/grepr-platform/permissions). ### Step 2: Add a source to your pipeline To add a source to your pipeline that uses the OpenTelemetry integration: 1. In the Grepr UI, go to the details page of an existing pipeline or create a new pipeline from the homepage. 2. In the left-hand navigation menu, click **Sources**. 3. In the **Add source** dialog, select your OpenTelemetry integration in the **Source** menu. 4. Click **Submit**. ### Step 3: Configure log forwarding to Grepr To send data to Grepr, you configure your collector or agent to send it to the ingestion URL for your Grepr integration, rather than to your observability vendor's platform. To find the ingestion URL when using the Grepr UI to configure your pipeline, go to the details page for the pipeline, click **Sources** in the left pane, and copy the **Ingest URL**. If you connect to Grepr through AWS PrivateLink, copy the private ingestion URL and use it in place of the public ingestion URL. To learn more about sending data to Grepr over AWS PrivateLink, see [Securely forward observability data to Grepr with AWS PrivateLink](/admin/private-link). When you use the API, you can construct the ingestion URL using the following format: `https://-.ingest.grepr.ai/otlp` Replace `` with the identifier of the vendor integration used by your pipeline and replace `` with the identifier for your organization. To use the PrivateLink endpoint service, insert `.private` after the `ingest` host segment. Although all sources created from the same integration share the same ingestion URL, you can use a single integration to create sources for multiple pipelines. The Grepr platform ensures events are routed to the correct pipelines. Authenticate by sending the Grepr token in the `x-grepr-token` header. Replace `` in the examples below with the token you saved after creating the OpenTelemetry integration in Step 1. To see more information and configuration examples, select the tab for your preferred log collector: Grafana Alloy is the recommended collector for connecting to Grafana Cloud. It replaces the end-of-life Grafana Agent and provides enhanced performance and capabilities. To configure Grafana Alloy to send logs to Grepr, use the OTLP exporter pointing to Grepr's ingestion endpoint. Configuration (`config.alloy`): ```shell otelcol.exporter.otlphttp "grepr" { client { endpoint = "" headers = { "x-grepr-token" = "" } } } otelcol.receiver.otlp "default" { http {} grpc {} output { logs = [otelcol.exporter.otlphttp.grepr.input] } } ``` Replace `` with the full ingestion URL provided by the Grepr UI, and `` with your Grepr token. To configure dual shipping, create two exporters: ```shell otelcol.exporter.otlphttp "grepr" { client { endpoint = "" headers = { "x-grepr-token" = "" } } } otelcol.exporter.otlphttp "grafana" { client { endpoint = "" headers = { "Authorization" = "Bearer " } } } otelcol.receiver.otlp "default" { http {} grpc {} output { logs = [ otelcol.exporter.otlphttp.grepr.input, otelcol.exporter.otlphttp.grafana.input ] } } ``` Replace `` with your Grafana Cloud OTLP endpoint and `` with your Grafana Cloud access token. To learn more about Grafana Alloy configuration, see the [Grafana Alloy documentation](https://grafana.com/docs/alloy/latest/). The OpenTelemetry Collector can send logs to Grepr using the `otlphttp` exporter. To configure the OpenTelemetry Collector to send logs to Grepr's ingestion endpoint, update your collector configuration (`collector.yaml`): ```yaml exporters: otlphttp: endpoint: headers: x-grepr-token: service: pipelines: logs: receivers: [otlp] processors: [batch] exporters: [otlphttp] ``` Replace `` with the full ingestion URL provided by the Grepr UI, and `` with your Grepr token. To configure dual shipping: ```yaml exporters: otlphttp/grepr: endpoint: headers: x-grepr-token: otlphttp/grafana: endpoint: headers: Authorization: Bearer service: pipelines: logs: receivers: [otlp] processors: [batch] exporters: [otlphttp/grepr, otlphttp/grafana] ``` Replace `` with your Grafana Cloud OTLP endpoint and `` with your Grafana Cloud access token. To learn more about OpenTelemetry Collector configuration, see the [OpenTelemetry Collector documentation](https://opentelemetry.io/docs/collector/). > Grafana Agent is end-of-life as of November 1, 2025. Grepr recommends migrating to Grafana Alloy for new and existing deployments. To configure Grafana Agent to send logs to Grepr, use the OTLP exporter in your agent configuration. Configuration (`agent.yaml`): ```yaml logs: configs: - name: default clients: - url: headers: x-grepr-token: ``` Replace `` with the full ingestion URL provided by the Grepr UI, and `` with your Grepr token. > Grafana Agent's static log client supports fewer options than Alloy's OTLP exporter. If your agent version cannot set a request header, migrate to Grafana Alloy. ## Advanced configuration ### Custom headers If your Grafana Cloud setup requires additional headers other than the Authorization header, you can add them in the Grepr UI when creating your OpenTelemetry integration: * Non-secret headers: Add in the **HTTP Headers** section. * Secret headers: Add in the **HTTP Headers** section and select the **Make header secret** checkbox. ### Endpoint overrides For advanced use cases, you can use the **Advanced** mode in the Grepr UI to specify separate endpoints for logs and traces: * **Logs Endpoint Override**: Specify a custom logs endpoint (if different from base endpoint + `/v1/logs`). * **Traces Endpoint Override**: Specify a custom traces endpoint (if different from base endpoint + `/v1/traces`). ## Frequently Asked Questions ### How do I connect Grepr to Grafana Cloud? Create an OpenTelemetry integration in Grepr with your Grafana Cloud OTLP endpoint and configure an Authorization header with your Grafana Cloud Access Policy token. The ingestion URL format is https\://\-\.ingest.grepr.ai/otlp. Configure your collector to send logs to this URL with your Grepr token in the x-grepr-token header. ### What is required to set up Grafana Cloud integration with Grepr? You need a Grafana Cloud Access Policy token with write access to logs and your Grafana Cloud OTLP endpoint URL. The token is used for authentication between Grepr and Grafana Cloud. You can create access policies in Grafana Cloud under Home > Administration > Users and access > Cloud access policies. ### How do I configure Grafana Alloy to send logs to Grepr? Grafana Alloy is the recommended collector for Grafana Cloud. Configure the otelcol.exporter.otlphttp component with your Grepr ingestion endpoint. For dual-shipping, add a second exporter pointing to your Grafana Cloud OTLP endpoint with the Authorization header containing your Grafana access token. ### Can I use OpenTelemetry Collector with Grafana Cloud and Grepr? Yes, the OpenTelemetry Collector can be used with Grafana Cloud. Configure the otlphttp exporter with your Grepr ingestion endpoint. For dual-shipping to both Grepr and Grafana Cloud, add multiple exporters to your logs pipeline with appropriate endpoint URLs and headers. ### What is Grafana Agent and why is it end-of-life? Grafana Agent is an older collector that has reached end-of-life as of November 1, 2025. Grepr recommends migrating to Grafana Alloy, which provides enhanced performance, better feature support, and ongoing maintenance. Grafana Alloy is the successor and recommended collector for new deployments. ### How do I migrate from Grafana Agent to Grafana Alloy with Grepr? Update your collector configuration to use Grafana Alloy and configure the otelcol.exporter.otlphttp component to point to your Grepr ingestion endpoint. Grafana Alloy uses the same OTLP protocol as the OpenTelemetry Collector, making migration straightforward. ### What custom headers can I add to my Grafana Cloud OpenTelemetry integration? You can add non-secret headers in the HTTP Headers section and secret headers (like API keys or authentication tokens) in the HTTP Headers section with the Make header secret checkbox selected. Secret headers are stored securely and masked in the UI. ### Can I use different endpoints for logs and traces with Grafana Cloud? Yes, for advanced use cases, you can use Advanced mode in the Grepr UI to specify separate Logs Endpoint Override and Traces Endpoint Override if your Grafana Cloud setup requires different endpoints for different signal types. ### How do I reduce Grafana Cloud storage costs with Grepr? Configure your Grepr pipeline with a Grafana Cloud source and sink. Use Grepr's transformation and log reducer features to filter, enrich, and aggregate logs before sending them back to Grafana Cloud. This reduces the volume of data stored in Grafana Cloud. ### What is the advantage of using Grepr with Grafana Cloud? Grepr enables advanced log processing, filtering, and aggregation using its log reducer and transformation features. By processing logs through Grepr before storing in Grafana Cloud, you can reduce storage costs, improve log quality, and gain deeper insights into your logs without additional Grafana expense.