@grepr/cli 1.2.0 → 1.3.0-94fe60c

package/build/dist/docs-index/3feedaba-03c4-4c35-9f94-a3c61af35320.txt

@@ -1,114 +0,0 @@
----
-description: Learn how Grepr integrates with Datadog, Splunk, New Relic, and other platforms to reduce observability costs and provide real-time log processing and analysis.
----
-
-import { Cards } from 'nextra/components'
-import { HiddenFAQ } from '@/components/HiddenFAQ'
-
-# What is Grepr?
-
-Grepr is an enterprise-grade data storage, processing, and analytics platform for your observability data. Grepr collects, transforms, and analyzes your log data and then sends the processed logs to your observability platform.
-
-Before sending log data to the destination platform, Grepr uses machine learning to analyze and intelligently aggregate the data. During normal operations, Grepr reduces your observability costs by reducing the volume of data sent to your observability tools, while retaining all of your raw data in low-cost cloud storage. If an incident or anomaly occurs, Grepr increases the granularity of the forwarded data to ensure that sufficient data is available for troubleshooting. Grepr also uses the raw data to backfill any historical data relevant to the incident.
-
- Grepr supports popular observability platforms, including Datadog, Splunk, New Relic, Sumo Logic, Grafana Cloud, and OpenTelemetry-compatible platforms.
-
-If you're just getting started with Grepr, follow the **Get started** guides below. If you're already using Grepr and need information on creating pipelines to process logs or to query raw logs stored in Grepr, see the guides under **Process and explore your logs**. If you need to automate your Grepr tasks or implement clients that use Grepr features, or use JavaScript to code reusable components for your pipelines, see the **Developers** documentation.
-
-<div style={{
-  display: 'grid',
-  gridTemplateColumns: '1fr 1fr 1fr',
-  gap: '2rem',
-  marginTop: '2rem'
-}}>
-  <div>
-    <h2 style={{ textAlign: 'center', fontWeight: 'bold' }}>Get started</h2>
-    <Cards>
-      <Cards.Card
-        title="Create your first pipeline"
-        href="/tutorials/first-pipeline"
-      />
-      <Cards.Card
-        title="Learn about the platform"
-        href="/grepr-platform"
-      />
-    </Cards>
-  </div>
-  <div>
-    <h2 style={{ textAlign: 'center', fontWeight: 'bold' }}>Process and explore your logs</h2>
-    <Cards>
-      <Cards.Card
-        title="Connect to external tools"
-        href="/integrations"
-      />
-      <Cards.Card
-        title="Process and transform data"
-        href="/transforms"
-      />
-      <Cards.Card
-        title="Query logs in the data lake"
-        href="/queries"
-      />
-    </Cards>
-  </div>
-  <div>
-    <h2 style={{ textAlign: 'center', fontWeight: 'bold' }}>Developers</h2>
-    <Cards>
-      <Cards.Card
-        title="Use the Grepr Rest API"
-        href="/apis"
-      />
-      <Cards.Card
-        title="Use the Grepr CLI"
-        href="/cli"
-      />
-      <Cards.Card
-        title="Custom pipeline components"
-        href="/templates"
-      />
-    </Cards>
-  </div>
-</div>
-
-<HiddenFAQ faqs={[
-  {
-    q: "What is Grepr?",
-    a: "Grepr is an enterprise-grade data storage, processing, and analytics platform for observability data. It collects, transforms, and analyzes log data, then sends processed logs to your observability platform while retaining raw data in low-cost cloud storage."
-  },
-  {
-    q: "How does Grepr reduce observability costs?",
-    a: "Grepr uses machine learning to intelligently aggregate and reduce the volume of log data sent to your observability tools during normal operations, while automatically increasing data granularity during incidents. This significantly reduces costs while maintaining full raw data access."
-  },
-  {
-    q: "What observability platforms does Grepr integrate with?",
-    a: "Grepr supports popular platforms including Datadog, Splunk, New Relic, Sumo Logic, Grafana Cloud, and OpenTelemetry-compatible platforms."
-  },
-  {
-    q: "What is the Grepr data lake?",
-    a: "The Grepr data lake is a secure cloud storage layer built on Apache Iceberg and S3 that stores your raw log data. It provides efficient querying capabilities and serves as the foundation for historical analysis and incident backfills."
-  },
-  {
-    q: "Can I query raw logs in Grepr?",
-    a: "Yes, you can query raw logs stored in the Grepr data lake using the query interface or REST API. The data lake supports powerful queries with tags, time ranges, and custom filters to analyze historical log data."
-  },
-  {
-    q: "How do I create a Grepr pipeline?",
-    a: "You can create pipelines using the Grepr UI, REST API, or CLI. Pipelines consist of data sources, transformations (like log reduction and parsing), and destinations. Follow the 'Create your first pipeline' guide to get started."
-  },
-  {
-    q: "What happens to my data during an incident?",
-    a: "During incidents or anomalies, Grepr automatically increases the granularity of forwarded data to ensure sufficient detail for troubleshooting. It also backtransfers historical raw logs relevant to the incident from the data lake."
-  },
-  {
-    q: "Is my data secure in Grepr?",
-    a: "Yes, Grepr maintains SOC 2 Type II certification and implements enterprise security controls including encryption in transit (TLS 1.2+) and at rest, role-based access controls, and secure identity management with Auth0."
-  },
-  {
-    q: "Can I use Grepr with my existing observability tools?",
-    a: "Yes, Grepr is designed to integrate seamlessly with existing observability platforms. You continue using your current tools while Grepr handles data reduction and optimization in the background."
-  },
-  {
-    q: "How can I automate Grepr tasks?",
-    a: "You can automate tasks using the Grepr REST APIs, CLI, or custom JavaScript components in pipelines. The CLI supports job creation, queries, integration management, and dataset operations."
-  }
-]} />

package/build/dist/docs-index/40b588dd-f618-4329-ad91-43efd9a32b28.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/40b588dd-f618-4329-ad91-43efd9a32b28.txt

@@ -1,29 +0,0 @@
-# Get a Datadog integration
-
-**GET** `/v1/integrations/datadog/{id}`
-
-**Operation ID**: `get`
-**Summary**: Get a Datadog integration
-Get an integration to connect to Datadog.
-
-## Tags
-- Datadog Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-Integration retrieved successfully
-
-- **Content-Type**: `application/json` / `ReadDatadog`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/415ab0e3-9b6f-45ea-97c9-fac80df14881.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/415ab0e3-9b6f-45ea-97c9-fac80df14881.txt

@@ -1,8 +0,0 @@
-# ItemsCollectionReadDatadog
-
-**Type**: `object`
-
-## Properties
-
-- name: items (optional)
-  type: array of `ReadDatadog`

package/build/dist/docs-index/424c273a-355e-45f9-8a27-b2f46217af68.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/424c273a-355e-45f9-8a27-b2f46217af68.txt

@@ -1,16 +0,0 @@
-# EventActionRule
-
-**Type**: `object`
-
-## Properties
-
-- name: actionPredicate (required)
-  type: `EventPredicate`
-
-- name: actions (required)
-  type: array of `EventAction`
-  description: Actions to take on a matching event.
-
-- name: type (required)
-  type: enum: `event-rule`
-  description: This takes event actions on events that match the actionPredicate when this rule is triggered.

package/build/dist/docs-index/429fea8e-fac4-45d3-870b-3bc59a01e9a5.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/429fea8e-fac4-45d3-870b-3bc59a01e9a5.txt

@@ -1,32 +0,0 @@
-# Create a Datadog integration
-
-**POST** `/v1/integrations/datadog`
-
-**Operation ID**: `create`
-**Summary**: Create a Datadog integration
-Creates an integration to connect to Datadog.
-
-## Tags
-- Datadog Integration
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteDatadog`
-
-## Responses
-
-### 200
-
-Integration created successfully
-
-- **Content-Type**: `application/json` / `ReadDatadog`
-### 401
-
-Unauthorized
-
-### 409
-
-Integration already exists.
-
-- **Content-Type**: `application/json` / `ReadDatadog`

package/build/dist/docs-index/42a56d79-79eb-4c40-8406-0698212019f8.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/42a56d79-79eb-4c40-8406-0698212019f8.txt

@@ -1,42 +0,0 @@
-# VendorImportedException
-
-Exception that was imported from a vendor integration like Datadog, Splunk etc.
-
-**Type**: `object`
-
-## Properties
-
-- name: vendorResourceId (required)
-  type: string
-
-- name: vendorResourceName (optional)
-  type: string
-
-- name: integrationId (required)
-  type: string
-
-- name: sourceUri (optional)
-  type: string
-
-- name: eventPredicate (required)
-  type: `EventPredicate`
-
-- name: exceptionType (optional)
-  type: enum: `DATADOG_MONITOR`, `DATADOG_DASHBOARD`, `DATADOG_LOG_BASED_METRICS`, `SPLUNK_MONITOR`, `NEW_RELIC_MONITOR`, `NEW_RELIC_DASHBOARD`
-
-- name: parseResult (optional)
-  type: `ParseResult`
-
-- name: impactPercentage (optional)
-  type: number
-  description: The percent of events impacted by this exception
-
-- name: impactLastUpdated (optional)
-  type: string
-  description: Timestamp when the impact percentage was last updated
-
-- name: createdAt (optional)
-  type: string
-
-- name: updatedAt (optional)
-  type: string

package/build/dist/docs-index/43a5ba9d-c6c4-406d-857e-8d1465520860.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/43a5ba9d-c6c4-406d-857e-8d1465520860.txt

@@ -1,12 +0,0 @@
-# DatasetUpdate
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this dataset is associated with.

package/build/dist/docs-index/445439e2-fb53-4cd9-b9f1-4c17e40ed310.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/445439e2-fb53-4cd9-b9f1-4c17e40ed310.txt

@@ -1,46 +0,0 @@
-# MetricsIcebergTableSource
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-
-- name: start (required)
-  type: string
-  description: Start of time interval to query data for.
-
-- name: end (required)
-  type: string
-  description: End of time interval to query data for.
-
-- name: query (required)
-  type: `query`
-
-- name: variables (optional)
-  type: object
-  description: Variables that can be used to modify the query while parsed
-
-- name: offset (optional)
-  type: integer
-  description: Offset on the number of rows to process
-
-- name: limit (optional)
-  type: integer
-  description: The maximum number of rows to process
-
-- name: sortOrder (optional)
-  type: enum: `ASCENDING`, `DESCENDING`, `UNSORTED`
-  description: The order in which the rows should be sorted by
-
-- name: datasetId (required)
-  type: string
-  description: The ID of the dataset to read data from.
-
-- name: aggSpec (required)
-  type: `MetricAggSpec`
-
-- name: type (required)
-  type: enum: `metrics-iceberg-table-source`
-  description: Reads metrics out of an Iceberg Table for processing.

package/build/dist/docs-index/44d59b10-5b0b-4ed3-9ab6-7c45577fa58c.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/44d59b10-5b0b-4ed3-9ab6-7c45577fa58c.txt

@@ -1,13 +0,0 @@
-# PhraseNode
-
-**Type**: `object`
-
-## Properties
-
-- name: terms (required)
-  type: array of string
-  description: The terms in a phrase to match 
-
-- name: type (required)
-  type: enum: `phrase-node`
-  description: A node that represents a phrase match in a parsed query.

package/build/dist/docs-index/46499192-a0e2-4e94-a38b-e495a8ae34af.json

@@ -1 +0,0 @@
-{"docType":"doc"}

package/build/dist/docs-index/46499192-a0e2-4e94-a38b-e495a8ae34af.txt

@@ -1,292 +0,0 @@
----
-description: Connect Grepr to observability vendors for standardized telemetry data collection and forwarding using the OpenTelemetry Protocol (OTLP).
----
-
-import { Callout } from 'nextra/components'
-import AddTeamAccess from '@/app/shared/add-team-access-to-resource.mdx'
-import IngestUrlConfig from '@/app/shared/configure-ingest-url.mdx'
-import IntegrationsInterchangeability from '@/app/shared/integrations-interchangeability.mdx'
-import { Tabs } from 'nextra/components'
-import { HiddenFAQ } from '@/components/HiddenFAQ'
-
-# Configure connections to OpenTelemetry compatible platforms
-
-The Grepr OpenTelemetry integration enables you to ingest logs into Grepr using a Grepr source, process them with a Grepr pipeline, and then send the processed logs to any observability vendor that accepts the OpenTelemetry Protocol HTTP source (OTLP/HTTP).
-
-To send logs to a Grepr pipeline before forwarding the logs to an OTLP/HTTP source, you change your collector configuration to send the logs to a Grepr endpoint URL instead of a OTLP/HTTP endpoint. The Grepr OpenTelemetry integration supports several OpenTelemetry-compatible collectors, including the OpenTelemetry Collector, Datadog collectors, and Sumo Logic collectors.
-
-The Grepr endpoint URL requires a Grepr-generated token for authentication. When you create an OpenTelemetry integration, Grepr automatically generates this token for you. In the UI, the token is displayed in a dialog after you create the integration. You must copy this token and include it in your collector configuration. When you use the REST API to create the integration, the token is included in the response.
-
-You can use the Grepr UI or REST API to add an OpenTelemetry integration. 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-opentelemetry-integration).
-
-To use the REST API, see the [OpenTelemetry Integration specification](/apis/api-spec#tag/OpenTelemetry-Integration).
-
-<Callout>
-  <IntegrationsInterchangeability />
-</Callout>
-
-## Requirements
-
-Creating and configuring an OpenTelemetry integration requires the following:
-
-- The URL for the HTTP/HTTPS endpoint where your observability vendor accepts OpenTelemetry data.
-
-## Use an OpenTelemetry integration in a Grepr pipeline [#use-opentelemetry-integration]
-
-Use the following steps to create an OpenTelemetry integration in the Grepr UI and use it in a pipeline to source and sink data.
-
-### Step 1: Create an OpenTelemetry integration
-
-To create an OpenTelemetry integration in the Grepr UI:
-
-1. Go to the **Integrations** page in the Grepr UI and click **Add new** next to **Observability Vendors**.
-
-   ![The Integrations page in the Grepr UI.](/images/tutorials/first-pipeline/integrations-page.png)
-
-1. In the **Add Observability Vendor** dialog:
-   - In the **Type** menu, select **OpenTelemetry**.
-   - In the **Name** field, enter a name for the integration.
-   - In the **Endpoint** field, enter the URL for the HTTP/HTTPS endpoint.
-   - (Optional) In the **HTTP Headers** section, add any required headers, such as authentication headers. For example, `Authorization: Bearer <token>` or `X-API-Key: <api-key>`. You can optionally select **Make headers secret** to store the headers securely and mask them in the UI. Use this option for sensitive headers, such as API keys or tokens.
-1. Click **Create**.
-1. After clicking **Create**, the **Grepr Token** dialog appears with a Grepr-generated token. Click the **Copy to Clipboard** icon to copy the token. This token is required when you configure your collector to send logs to Grepr.
-1. Click **Confirm** to close the dialog.
-
-   #### (Optional) Grant team access to the integration
-
-   <AddTeamAccess resource_type='integration' />
-
-### 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 overview page for an existing pipeline or create a new pipeline from the homepage.
-1. In the left-hand navigation menu on the pipeline overview page, click **Sources**.
-1. In the **Add source** dialog, select the OpenTelemetry integration in the **Source** menu.
-1. Click **Submit**.
-
-### Step 3: Configure log forwarding to Grepr
-
-<IngestUrlConfig image_url='/images/integrations/ingestion-url-otel.png' url='https://<integration-id>-<org-id>.ingest.grepr.ai/otlp/<grepr-token>' />
-
-Replace `<grepr-token>` with the token generated when you created the OpenTelemetry integration in Step 1.
-
-For an observability vendor not included in this section, you can use the OpenTelemetry integration with these general steps:
-
-1. Check your vendor's documentation for their OTLP/HTTP endpoint URL.
-
-2. Identify any required headers—for example, authentication headers, such as API keys or tokens.
-
-3. Configure the integration:
-   - **Endpoint URL**: Your vendor's OTLP HTTP endpoint.
-   - **Headers**: Any non-sensitive headers required by your vendor.
-   - **Secret Headers**: Sensitive authentication headers like API keys.
-
-4. Configure your OpenTelemetry Collector: Use the `otlphttp` exporter to send logs to Grepr's ingestion endpoint. See the OpenTelemetry Collector configuration examples below.
-
-To see more information and configuration examples, select the tab for your preferred log collector:
-
-<Tabs items={['OpenTelemetry Collector', 'Datadog', 'Sumo Logic']}>
-  <Tabs.Tab>
-
-    The OpenTelemetry Collector can send logs to Grepr using the `otlphttp` exporter. In the OpenTelemetry collector configuration (`collector.yaml`), set the endpoint to the ingestion URL from your OpenTelemetry integration:
-
-    ```yaml
-    exporters:
-      otlphttp:
-        endpoint: <ingestion-url>
-
-    service:
-      pipelines:
-        logs:
-          receivers: [otlp]
-          processors: [batch]
-          exporters: [otlphttp]
-    ```
-
-    Replace:
-    - `<ingestion-url>` with the ingestion URL from your OpenTelemetry integration.
-
-    For dual shipping, you need to create two exporters: one to send logs to Grepr, and another to send logs directly to your vendor's platform. Your exporter for Grepr should only include Grepr's ingestion endpoint, with any needed headers configured in the UI. Your exporter, configured directly to the vendor's platform, should include the endpoint for that platform and the necessary headers.
-
-    ```yaml
-    exporters:
-      otlphttp/grepr:
-        endpoint: <ingestion-url>
-
-      otlphttp/vendor:
-        endpoint: <vendor-otlp-endpoint>
-        headers:
-          authorization: "Bearer <vendor-token>"
-
-    service:
-      pipelines:
-        logs:
-          receivers: [otlp]
-          processors: [batch]
-          exporters: [otlphttp/grepr, otlphttp/vendor]
-    ```
-
-    Replace:
-    - `<ingestion-url>` with the ingestion URL from your OpenTelemetry integration.
-    - `<vendor-otlp-endpoint>` with your vendor's OTLP/HTTP endpoint URL.
-    - `<vendor-token>` with your vendor's authentication token.
-
-    To learn more about configuration settings for the OpenTelemetry Collector, see the [OTLP/HTTP Exporter documentation](https://github.com/open-telemetry/opentelemetry-collector#readme).
-
-  </Tabs.Tab>
-
-  <Tabs.Tab>
-
-    To send OpenTelemetry data to Datadog from Grepr, configure your integration with Datadog's OTLP endpoint and required headers.
-
-    **Integration Configuration:**
-    - **Endpoint URL**: `https://http-intake.logs.datadoghq.com/api/v2/logs`
-    - **Headers**:
-      - `dd-protocol`: `otlp`
-    - **Secret Headers**:
-      - `dd-api-key`: `<dd-api-key>`
-
-    In the collector configuration (`collector.yaml`), set the endpoint to the ingestion URL from your OpenTelemetry integration:
-
-    ```yaml
-    exporters:
-      otlphttp:
-        endpoint: <ingestion-url>
-
-    service:
-      pipelines:
-        logs:
-          receivers: [otlp]
-          processors: [batch]
-          exporters: [otlphttp]
-    ```
-
-    Replace:
-    - `<ingestion-url>` with the ingestion URL from your OpenTelemetry integration.
-    - `<dd-api-key>` with your Datadog API key.
-
-    To learn more, see [Datadog OTLP Logs Intake Endpoint](https://docs.datadoghq.com/opentelemetry/setup/intake_endpoint/otlp_logs/).
-
-  </Tabs.Tab>
-
-  <Tabs.Tab>
-
-    To send OpenTelemetry data to Sumo Logic from Grepr, configure your integration with Sumo Logic's OTLP/HTTP source endpoint.
-
-    **Integration Configuration:**
-    - **Endpoint URL**: Your Sumo Logic OTLP HTTP source URL. For example, `https://collectors.sumologic.com/receiver/v1/otlp/<sumo-unique-id>`.
-
-    <Callout>
-      Append `/v1/logs` to this endpoint when setting it in the Grepr UI. For example, `https://collectors.sumologic.com/receiver/v1/otlp/<sumo-unique-id>/v1/logs`. This is required because Sumo Logic's OTLP/HTTP source expects the logs endpoint path to be explicitly specified, unlike other vendors that handle this automatically.
-    </Callout>
-
-    In the collector configuration (`collector.yaml`), set the endpoint to the ingestion URL from your OpenTelemetry integration:
-
-    ```yaml
-    exporters:
-      otlphttp:
-        endpoint: <ingestion-url>
-
-    service:
-      pipelines:
-        logs:
-          receivers: [otlp]
-          processors: [batch]
-          exporters: [otlphttp]
-    ```
-
-    Replace:
-    - `<ingestion-url>` with the ingestion URL from your OpenTelemetry integration.
-    - `<sumo-unique-id>` with your Sumo Logic OTLP source unique identifier.
-
-    To learn more, see [Sumo Logic's OTLP documentation](https://help.sumologic.com/docs/send-data/hosted-collectors/http-source/otlp/).
-
-  </Tabs.Tab>
-</Tabs>
-
-## Grafana Cloud
-
-To connect with Grafana Cloud via Grepr, configure your OpenTelemetry integration with Grafana Cloud's OTLP endpoint and required authentication headers.
-
-**Integration Configuration:**
-- **Endpoint URL**: Your Grafana Cloud OTLP endpoint (e.g., `https://otlp-gateway-prod-us-west-0.grafana.net/otlp`).
-- **Secret Headers**:
-  - `Authorization`: `Bearer <grafana-access-token>`
-
-Your access token should be generated from a Cloud Access Policy with write access to logs. Navigate to **Home > Administration > Users and access > Cloud access policies** in Grafana Cloud.
-
-In the collector configuration (`collector.yaml`), set the endpoint to the ingestion URL from your OpenTelemetry integration:
-
-```yaml
-exporters:
-  otlphttp:
-    endpoint: <ingestion-url>
-
-service:
-  pipelines:
-    logs:
-      receivers: [otlp]
-      processors: [batch]
-      exporters: [otlphttp]
-```
-
-Replace:
-- `<ingestion-url>` with the ingestion URL from your OpenTelemetry integration.
-- `<grafana-access-token>` with your Grafana Cloud access token.
-
-For more information, see [Configure connections to Grafana Cloud with Grepr integrations](/integrations/grafana) for detailed setup instructions including configuration examples for Grafana Alloy, OpenTelemetry Collector, and Grafana Agent.
-
-## Security Considerations
-
-When configuring OpenTelemetry integrations:
-
-- **Use secret headers**: Always use secret headers for sensitive information like API keys, tokens, or passwords.
-- **Validate endpoints**: Ensure endpoint URLs use HTTPS for secure data transmission.
-- **Header validation**: Grepr validates all headers for security issues, including CRLF injection, control characters, and other potential attacks.
-- **Avoid reserved headers**: Some HTTP headers are reserved and cannot be set by users for security reasons.
-
-<HiddenFAQ
-  faqs={[
-    {
-      q: "How do I create an OpenTelemetry integration with Grepr?",
-      a: "In the Grepr UI, go to Integrations and click Add new. Select OpenTelemetry, enter a name, and provide the URL for your vendor's OTLP/HTTP endpoint. Optionally add HTTP headers for authentication. After creation, Grepr generates a token that you must include in your collector configuration at the ingestion endpoint."
-    },
-    {
-      q: "What is the purpose of the Grepr token in OpenTelemetry integrations?",
-      a: "The Grepr token is automatically generated during OpenTelemetry integration creation and is required for authentication. It ensures that only authorized collectors can send logs to your Grepr pipeline. The token must be appended to the ingestion URL in the format: https://<integration-id>-<org-id>.ingest.grepr.ai/otlp/<grepr-token>"
-    },
-    {
-      q: "Can I use OpenTelemetry integration with any observability vendor?",
-      a: "Yes, the OpenTelemetry integration works with any vendor that accepts the OpenTelemetry Protocol (OTLP) over HTTP. This includes Grafana Cloud, Sumo Logic with OTLP source, Datadog, and many others. Check your vendor's documentation for their OTLP/HTTP endpoint URL."
-    },
-    {
-      q: "How do I configure the OpenTelemetry Collector to send logs to Grepr?",
-      a: "Configure the otlphttp exporter in your collector.yaml with the Grepr ingestion endpoint. Set the endpoint to https://<integration-id>-<org-id>.ingest.grepr.ai/otlp/<grepr-token>. Add the exporter to your logs pipeline along with your receivers and processors."
-    },
-    {
-      q: "How do I set up dual-shipping with OpenTelemetry integration?",
-      a: "Create two exporters in your OpenTelemetry Collector configuration: one otlphttp/grepr pointing to your Grepr ingestion endpoint, and another otlphttp/vendor pointing to your vendor's OTLP endpoint with appropriate headers. Include both in your logs pipeline to send logs to both destinations."
-    },
-    {
-      q: "What headers do I need for OpenTelemetry integration with Datadog?",
-      a: "For Datadog, configure the integration with endpoint https://http-intake.logs.datadoghq.com/api/v2/logs and add headers: dd-protocol: otlp (non-secret) and dd-api-key: <your-api-key> (secret). Make sure to select Make header secret for the API key."
-    },
-    {
-      q: "How do I send logs to Sumo Logic via OpenTelemetry integration?",
-      a: "Configure the integration with your Sumo Logic OTLP/HTTP source endpoint. Important: Append /v1/logs to the endpoint URL when setting it in Grepr (e.g., https://collectors.sumologic.com/receiver/v1/otlp/<sumo-unique-id>/v1/logs) because Sumo Logic requires the logs endpoint path to be explicitly specified."
-    },
-    {
-      q: "How do I protect sensitive headers in OpenTelemetry integrations?",
-      a: "Always select the Make header secret checkbox for sensitive headers containing API keys, tokens, or passwords. Secret headers are stored securely in Grepr and masked in the UI. Do not include sensitive information in non-secret headers."
-    },
-    {
-      q: "What OpenTelemetry collectors are supported with Grepr?",
-      a: "Grepr supports the OpenTelemetry Collector, Datadog collectors, Sumo Logic collectors, and Grafana Alloy. Any collector that supports the otlphttp exporter and can send to OTLP/HTTP endpoints is compatible with Grepr's OpenTelemetry integration."
-    },
-    {
-      q: "How can I reduce costs using OpenTelemetry integration with Grepr?",
-      a: "Send logs through Grepr for processing and aggregation before storing in your observability platform. Use Grepr's transformation and Log Reducer features to filter redundant logs and enrich data, reducing storage volume in your vendor's platform while maintaining visibility into important events."
-    }
-  ]}
-/>

package/build/dist/docs-index/4699de94-2eb2-41e2-ae03-a1b1246dd1e5.json

@@ -1 +0,0 @@
-{"docType":"schema"}