@grepr/cli 1.2.0 → 1.3.0-4e666db

package/build/dist/docs-index/5d99505f-9136-4520-9199-c317661f1c80.json

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

package/build/dist/docs-index/5d99505f-9136-4520-9199-c317661f1c80.txt

@@ -1,10 +0,0 @@
-# ImmutableSetListString
-
-Map from tag key to an ordered set of attribute paths to search for values. All paths will be tried, and all found values will be added. If no value is found, the tag will not be changed. The attribute paths are are a list of paths. This does not remove existing tag values.
-
-**Type**: `array`
-
-## Properties
-
-- name: empty (optional)
-  type: boolean

package/build/dist/docs-index/5dbb3bd1-cb55-4b54-a032-9459b49301da.json

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

package/build/dist/docs-index/5dbb3bd1-cb55-4b54-a032-9459b49301da.txt

@@ -1,24 +0,0 @@
-# DatadogLogSink
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-
-- name: integrationId (required)
-  type: string
-  description: The Datadog integration id.
-
-- name: additionalTags (optional)
-  type: array of string
-  description: Additional tags to add to the logs when writing to Datadog. Gets combined with the integration's additionalTags.
-
-- name: browserLogGroupByAttributes (optional)
-  type: array of string
-  description: Group by attributes to use when writing logs to Datadog browser intake.Defaults to ["http.useragent", "network.client.ip"].
-
-- name: type (required)
-  type: enum: `datadog-log-sink`
-  description: Writes processed events to Datadog.

package/build/dist/docs-index/5e78694f-28bc-40f0-bb77-bc3e9ad04b12.json

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

package/build/dist/docs-index/5e78694f-28bc-40f0-bb77-bc3e9ad04b12.txt

@@ -1,20 +0,0 @@
-# List all NewRelic integrations
-
-**GET** `/v1/integrations/newrelic`
-
-**Operation ID**: `list_3`
-**Summary**: List all NewRelic integrations
-Get all NewRelic integrations.
-
-## Tags
-- New Relic Integration
-## Responses
-
-### 200
-
-Integrations retrieved successfully
-
-- **Content-Type**: `application/json` / `ItemsCollectionReadNewRelic`
-### 401
-
-Unauthorized

package/build/dist/docs-index/5f3b925f-235f-47dd-b602-75f7180b2a04.json

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

package/build/dist/docs-index/5f3b925f-235f-47dd-b602-75f7180b2a04.txt

@@ -1,24 +0,0 @@
-# EventPredicateTrigger
-
-**Type**: `object`
-
-## Properties
-
-- name: predicate (required)
-  type: `EventPredicate`
-
-- name: conditionIds (required)
-  type: array of string
-  description: The ids for the conditions that are activated by this trigger.
-
-- name: duration (required)
-  type: string
-  description: The duration for which the associated conditions will be active.
-
-- name: variables (required)
-  type: object
-  description: Map from variable names to paths for variables to extract from a matching event. If starting with '@', the path indicates an attribute. Otherwise, it's a tag. The variable names must start with '__' and be unique. Note that __timestamp (and __severity for logs) variable is automatically extracted from the respective top level fields of the matching event.
-
-- name: type (required)
-  type: enum: `event-predicate`
-  description: This is triggered by an event matching the given predicate.

package/build/dist/docs-index/5f87228e-8227-4ed6-983d-b7e2177db0c7.json

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

package/build/dist/docs-index/5f87228e-8227-4ed6-983d-b7e2177db0c7.txt

@@ -1,5 +0,0 @@
-# TraceIdLogsBackfillAction
-
-Action that triggers logs backfill for matching traces. Accumulates trace IDs in time-based windows and calls the logs backfill API with the collected trace IDs.
-
-**Type**: `object`

package/build/dist/docs-index/5fb1467a-1997-456c-b2cb-d531f403fe65.json

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

package/build/dist/docs-index/5fb1467a-1997-456c-b2cb-d531f403fe65.txt

@@ -1,30 +0,0 @@
-# Update access configuration for the organization
-
-**PUT** `/v1/organization/access-config`
-
-**Operation ID**: `updateAccessConfig`
-**Summary**: Update access configuration for the organization
-Updates the access configuration for the organization.
-
-## Tags
-- Access Configuration
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `AccessConfig`
-
-## Responses
-
-### 200
-
-Access configuration updated successfully
-
-- **Content-Type**: `application/json` / `AccessConfig`
-### 401
-
-Unauthorized
-
-### 403
-
-Unauthorized

package/build/dist/docs-index/606d1f9a-8054-44c0-bc39-1655fe6ea909.json

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

package/build/dist/docs-index/606d1f9a-8054-44c0-bc39-1655fe6ea909.txt

@@ -1,19 +0,0 @@
-# List templates
-
-**GET** `/v1/templates`
-
-**Operation ID**: `listTemplates`
-**Summary**: List templates
-Lists templates a user has access to. Only returns the latest versions of each.
-
-## Tags
-- Templates
-## Responses
-
-### 200
-
-Results returned successfully
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/6148c6b4-5621-400d-9f3f-b942ff22715c.json

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

package/build/dist/docs-index/6148c6b4-5621-400d-9f3f-b942ff22715c.txt

@@ -1,9 +0,0 @@
-# IgnoreAttributesMergeStrategy
-
-**Type**: `object`
-
-## Properties
-
-- name: type (required)
-  type: enum: `ignore`
-  description: IgnoreAttributesMergeStrategy: Does nothing during merge - leaves the current value unchanged. Used internally for suffixed keys managed by CompositeAttributesMergeStrategy.

package/build/dist/docs-index/624a0463-fe2b-4cc5-bd31-5e0d6e529438.json

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

package/build/dist/docs-index/624a0463-fe2b-4cc5-bd31-5e0d6e529438.txt

@@ -1,17 +0,0 @@
-# TemplateSqlOperation
-
-SQL operation with template-specific sqlMode for graph construction.
-
-**Type**: `object`
-
-## Properties
-
-- name: sqlOperation (required)
-  type: `SqlOperation`
-
-- name: sqlMode (optional)
-  type: enum: `else`, `also`
-  description: SQL processing mode that determines how this SQL operation connects to filter operations. 'else' mode processes data that does NOT match the associated filter predicate. 'also' mode processes ALL data in addition to the normal filter flow.
-
-- name: sqlFilterPredicate (optional)
-  type: `EventPredicate`

package/build/dist/docs-index/62760b70-fb2e-4a7d-85e2-fcef9d00e062.json

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

package/build/dist/docs-index/62760b70-fb2e-4a7d-85e2-fcef9d00e062.txt

@@ -1,351 +0,0 @@
----
-description: Learn how to create and use a Datadog integration to ingest logs to a Grepr pipeline for processing and send the processed logs to your Datadog instance.
----
-
-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 Datadog connections for integration with Grepr
-
-The Grepr Datadog 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 Datadog using a Grepr sink.
-
-To send logs to a Grepr pipeline before forwarding the logs to Datadog, change your collector configuration to send the logs to a Grepr endpoint URL instead of a Datadog endpoint. The Grepr Datadog integration supports several Datadog-compatible collectors, including the Datadog Agent, Fluent Bit, Fluentd, and the OpenTelemetry Collector. This page includes example configurations for the supported collectors.
-
-You can use the Grepr UI or REST API to add a Datadog integration. To learn how to create a Datadog integration in the Grepr UI and configure collectors to send logs to Grepr, see [Use a Datadog integration in a Grepr pipeline](#use-datadog-integration).
-
-To use the REST API, see the [Datadog Integration specification](/apis/api-spec#tag/Datadog-Integration).
-
-<Callout>
-  - Although the Grepr Datadog integration supports all Datadog sites, when you use the Datadog `US1` site in the `us-east-1` region, the Grepr SaaS offering uses an AWS PrivateLink connection to Datadog.
-  - <IntegrationsInterchangeability />
-</Callout>
-
-## Requirements
-
-Creating and configuring a Datadog integration requires the following:
-
-- A Datadog API key for your account. You must use the same API key in both your Grepr integration and collector configuration.
-- (Optional) A Datadog application key for your account. An application key is required only to enable Grepr's automatic exception parsing feature. See [Enable selective reduction with a Datadog integration](#enable-selective-reduction). An application key also allows you to use the Datadog integration as a [cloud source](/integrations/support-matrix/#supported-observability-integrations).
-
-If you configure an application key, it must have the following authorization scopes:
-
-- `dashboards_read`
-- `logs_read_config`
-- `logs_read_data`
-- `monitors_read`
-
-To learn more about Datadog keys and scopes, see [API and Application Keys](https://docs.datadoghq.com/account_management/api-app-keys/) and [Authorization Scopes](https://docs.datadoghq.com/api/latest/scopes/).
-
-## Enable selective reduction with a Datadog integration [#enable-selective-reduction]
-
-When you include a Datadog application key in your integration configuration, Grepr automatically tracks all log monitors configured in your Datadog account. By parsing queries used in these monitors and making them available as exceptions to Grepr's Log Reducer, Grepr can determine which messages should not be processed by the reducer.
-
-The application key must have the required authorization scopes. See [Requirements](#requirements).
-
-To see a complete list of exceptions when this feature is enabled, in the **Observability vendors** section of the **Integrations** page in the Grepr UI, click on the cloud sync icon under **Actions**.
-
-![List of Datadog parsed alerts](/images/integrations/datadog-parsed-alerts.png)
-
-To learn more about Grepr log reduction, see [Optimizing logs with Grepr's intelligent aggregation](/grepr-platform/reduction).
-
-## Use a Datadog integration in a Grepr pipeline [#use-datadog-integration]
-
-Use the following steps to create a Datadog integration in the Grepr UI and use it in a pipeline to source and sink data.
-
-### Step 1: Create a Datadog integration
-
-To create a Datadog 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 **Datadog**.
-   - In the **Name** field, enter a name for the integration.
-   - In the **Site** menu, select the parameter matching your Datadog site.
-   - In the **API Key** field, enter your Datadog API key.
-   - (Optional) In the **Application Key** field, enter your Datadog Application key. The application key is required only to import exceptions from Datadog or to use the integration as a cloud source.
-1. Click **Create**.
-
-   ![Add a Datadog integration in the Grepr UI.](/images/integrations/add-datadog-integration-modal.png)
-
-   #### (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 Datadog 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 Datadog integration in the **Source** menu.
-1. (Optional) In the **Name** field, to override the Grepr-generated name, enter a new name for the source.
-1. Click **Submit**.
-
-### Step 3: Configure log forwarding to Grepr [#configure-forwarding-to-grepr]
-
-<IngestUrlConfig image_url='/images/integrations/ingestion-url-datadog.png' url='https://<integration-id>-<org-id>.ingest.grepr.ai' />
-
-To see more information and configuration examples, select the tab for your preferred log collector:
-
-<Tabs items={['Datadog Agent', 'Fluent Bit', 'Fluentd', 'OpenTelemetry Collector', 'Datadog Forwarder']}>
-  <Tabs.Tab>
-
-    Forwarding logs to Grepr from Datadog agents requires adding or updating settings in the agent configuration. How you configure these settings depends on how your agents are deployed:
-
-    - **Standalone agent**: Update the `datadog.yaml` file with the following settings:
-      - Set `api_key` to your Datadog API key.
-      - Set `logs_enabled` to `true`.
-      - Set `logs_config.logs_dd_url` to the ingestion URL.
-      - Set `logs_config.force_use_http` to `true`.
-
-    The following example is a snippet from the `datadog.yaml` configuration file for a standalone agent:
-
-    ```yaml copy
-    ## @param api_key - string - required
-    api_key: <dd-api-key>
-
-    ## @param logs_enabled - boolean - optional - default: false
-    logs_enabled: true
-
-    ## @param logs_config - custom object - optional
-    logs_config:
-        ## @param logs_dd_url - string - optional
-        logs_dd_url: <ingestion-url>
-
-        ## @param force_use_http - boolean - optional - default: false
-        force_use_http: true
-    ```
-
-    - **Docker agent**: Set or pass the following environment variables:
-      - Set `DD_LOGS_CONFIG_LOGS_DD_URL` to the ingestion URL
-      - Set `DD_LOGS_CONFIG_USE_HTTP` to `true`.
-      - Set `DD_LOGS_ENABLED` to `true`.
-      - Set `DD_API_KEY` to your Datadog API key.
-      - (Optional) Set `DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL` to `true` to collect logs from all containers.
-      - (Optional) Change the `DD_SITE` argument to match your Datadog site if you're not using `datadoghq.com`.
-      - (Optional) To assign a custom name to the agent container, set the name using the `--name` argument.
-
-    The following is an example command line to run a Datadog Docker agent configured to send logs to Grepr:
-
-    ```bash copy
-    docker run -d --rm --name <datadog-agent-name> \
-    -e DD_API_KEY=<dd-api-key> \
-    -e DD_SITE="datadoghq.com" \
-    -e DD_LOGS_ENABLED=true \
-    -e DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL=true \
-    -v /var/run/docker.sock:/var/run/docker.sock:ro \
-    -v /proc/:/host/proc/:ro \
-    -v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro \
-    -e DD_LOGS_CONFIG_LOGS_DD_URL=<ingestion-url> \
-    -e DD_LOGS_CONFIG_USE_HTTP="true" \
-    gcr.io/datadoghq/agent:latest
-    ```
-
-    <Callout>
-      The Grepr platform supports only HTTP and HTTPS. TCP is not supported. Setting the `logs_config.force_use_http` and `DD_LOGS_CONFIG_USE_HTTP` settings to `true` enforces HTTP/HTTPS transport for Datadog agents.
-
-      To learn more about Datadog support and configuration for agent transport, see [Agent Transport for Logs](https://docs.datadoghq.com/agent/logs/log_transport/?tab=https)
-    </Callout>
-
-    To learn more about standalone agent configuration, see [Host Agent Log collection](https://docs.datadoghq.com/agent/logs/).
-
-    To learn more about configuring Docker and other container agents, see [Container Monitoring](https://docs.datadoghq.com/containers/).
-
-  </Tabs.Tab>
-
-  <Tabs.Tab>
-
-    Fluent Bit can forward logs using the Datadog output plugin. To configure the plugin, set the `Host` value using the ingestion URL from the integration and set the `apikey` value to your Datadog API key. The following is an example `OUTPUT` section from a Fluent Bit configuration file (`fluent-bit.conf`):
-
-    ```fluent copy
-    [OUTPUT]
-      Name        datadog
-      Match       *
-      Host        <ingestion-url>
-      TLS         On
-      apikey      <dd-api-key>
-      # Optional: Specify service, source, tags, host
-      # dd_service
-      # dd_source
-      # dd_tags
-      # dd_hostname
-    ```
-
-    To learn more about configuration settings for Fluent Bit, see the documentation for the [Fluent Bit Datadog output plugin](https://docs.fluentbit.io/manual/pipeline/outputs/datadog).
-
-  </Tabs.Tab>
-
-  <Tabs.Tab>
-
-    FluentD can forward logs to Grepr using the `fluent-plugin-datadog` output plugin. To configure the plugin, add a `match` directive to the FluentD configuration. The following is an example `match` directive from a Fluentd configuration file (`fluentd.conf`):
-
-    ```fluent copy
-    <match your_tag.**> # Adjust your match pattern as needed
-      @type datadog
-      api_key <dd-api-key>
-      host    <ingestion-url>
-
-      # Optional: Specify service, source, or tags
-      # service
-      # source
-      # tags
-
-      # Buffer configuration is recommended for production
-      <buffer>
-        @type memory # Or file for persistence
-        flush_interval # Adjust as needed
-        chunk_limit_size # Adjust as needed
-        # Add other buffer parameters as needed
-      </buffer>
-    </match>
-    ```
-
-    Replace:
-    - `your_tag.**` with the tag of the logs you want to forward to Grepr or use `**` to match all tags.
-    - `<dd-api-key>` with your Datadog API key.
-    - `<ingestion-url>` with the ingestion URL from your Datadog integration.
-
-    To learn more about configuration settings for Fluentd, see the documentation for the [Fluentd Datadog output plugin](https://docs.datadoghq.com/integrations/fluentd/?tab=host).
-
-  </Tabs.Tab>
-
-  <Tabs.Tab>
-
-    The OpenTelemetry Collector can forward logs to Grepr using the Datadog exporter. In the OpenTelemetry collector configuration (`collector.yaml`), set `<ingestion-url>` to the ingestion URL from your Datadog integration and `<dd-api-key>` to your Datadog API key:
-
-
-    ```yaml
-    exporters: copy
-      datadog/exporter:
-        api:
-          key: <dd-api-key>
-          fail_on_invalid_key: false
-        logs:
-          endpoint: <ingestion-url>
-
-    service:
-      pipelines:
-    logs:
-      receivers: [otlp] # Replace with your actual receiver(s)
-      processors: [batch] # Replace/add your actual processor(s)
-      exporters: [datadog/exporter]
-    ```
-
-    See [Install and Configure the OpenTelemetry Collector](https://docs.datadoghq.com/opentelemetry/setup/collector_exporter/).
-
-  </Tabs.Tab>
-
-  <Tabs.Tab>
-
-    The Datadog Forwarder is an AWS Lambda function that forwards logs from AWS services to Datadog. You can instead forward logs to Grepr for processing by modifying the Lambda Forwarder's configuration. These instructions detail how to use AWS CloudFormation, recommended by Datadog, to configure and deploy the forwarder. See [Datadog Forwarder](https://docs.datadoghq.com/logs/guide/forwarder).
-
-    <Callout type="warning">
-      Grepr requires the Datadog Forwarder version 5.0.0 or later.
-    </Callout>
-
-    To deploy the Datadog Forwarder using CloudFormation, follow the [Datadog Forwarder installation instructions](https://docs.datadoghq.com/logs/guide/forwarder/?tab=cloudformation#installation). Before creating the CloudFormation stack, configure the following parameters to send logs to Grepr:
-
-    | CloudFormation Parameter  | Lambda Environment Variable  | Value               | Description                                                   |
-    |---------------------------|------------------------------|---------------------|---------------------------------------------------------------|
-    | `ddUrl`                   | `DD_URL`                     | `<ingestion-url>`   | The Grepr ingestion URL without the `https://` prefix.        |
-    | `ddPort`                  | `DD_PORT`                    | `443`               | Port for HTTPS connections to Grepr. Set this value to `443`. |
-    | `ddApiKey`                | `DD_API_KEY`                 | `<dd-api-key>`      | Your Datadog API key.                                         |
-    | `ddLogLevel`              | `DD_LOG_LEVEL`               | `DEBUG` (optional)  | Set to `DEBUG` to enable detailed logging.                    |
-
-    <Callout type="warning">
-      - The `ddUrl` parameter must not include the `https://` prefix. Use only the hostname portion of your ingestion URL.
-      - The `<dd-api-key>` value must be must be the same Datadog API key you configured in your Grepr Datadog integration. Alternatively, configure `DdApiKeySecretArn` if the key is stored in AWS Secrets Manager or `DdApiKeySsmParameterName` if the key is in AWS Systems Manager Parameter Store.
-      - Parameter names use camelCase when configuring the CloudFormation stack and UPPERCASE_UNDERSCORE when viewing or editing the Lambda function's environment variables in the AWS Console.
-    </Callout>
-
-    To send logs through the Datadog Forwarder after deployment, you set up triggers on your AWS services to run the forwarder whenever a new batch of log events is available. See [Send AWS Services Logs With The Datadog Lambda Function](https://docs.datadoghq.com/logs/guide/send-aws-services-logs-with-the-datadog-lambda-function/?tab=awsconsole).
-
-    If you already have a Datadog Forwarder sending logs to Datadog and want to also send logs to Grepr without modifying your existing configuration, you can enable dual-shipping of logs by deploying a second Grepr-configured forwarder. You then use the `DD_ADDITIONAL_TARGET_LAMBDAS` environment variable on the existing forwarder to invoke the Grepr forwarder. This approach allows you to:
-
-    - Keep your existing Datadog forwarder configuration unchanged.
-    - Send logs to both Datadog and Grepr simultaneously.
-    - Avoid reconfiguring triggers on your existing forwarder.
-
-    To configure dual-shipping with the Datadog Forwarder:
-
-    1. Deploy a new Lambda Forwarder following the steps above, configured to send logs to Grepr (with `ddUrl`, `ddPort`, and `ddApiKey` set for Grepr).
-    1. On your existing forwarder that sends logs to Datadog, add the `DD_ADDITIONAL_TARGET_LAMBDAS` environment variable set to the ARN of your new Grepr-configured forwarder.
-    1. Your existing forwarder will now invoke the new Grepr forwarder for each log batch, effectively dual-shipping logs to both Datadog and Grepr.
-
-    Example:
-    ```
-    DD_ADDITIONAL_TARGET_LAMBDAS=arn:aws:lambda:us-east-1:123456789012:function:datadog-forwarder-grepr
-    ```
-
-    <Callout type="info">
-      To specify multiple additional forwarders, separate ARNs with commas.
-    </Callout>
-
-    If logs are not appearing in Grepr, the following are suggested troubleshooting steps:
-
-    - Check the Lambda function's CloudWatch Logs for errors.
-    - Set `ddLogLevel`/`DD_LOG_LEVEL` to `DEBUG` for more detailed logging.
-    - Verify the ingestion URL does not include the `https://` prefix.
-    - Confirm the API key matches the one in your Grepr Datadog integration.
-    - Ensure you are using Datadog Forwarder version 5.0.0 or later.
-
-  </Tabs.Tab>
-</Tabs>
-
-## Forward events from an Azure event hub to Grepr
-
-If you have an existing integration that sends events from an Azure event hub to Datadog, you can modify it to forward events to Grepr for processing before sending them to Datadog. An example use of this event hub-to-Datadog integration is when the event hub is used to queue log events from other Azure services. These log events are then forwarded to a Datadog endpoint for processing.
-
-You can include Grepr in this integration by changing the destination URL from the Datadog endpoint to a Grepr ingestion URL, allowing you to use Grepr's log processing features, such as log reduction, parsing, and enrichment, on the events before they reach Datadog.
-
-Adding Grepr to an event hub-to-Datadog integration requires:
-
-- An existing Azure Event Hubs-to-Datadog integration. The integration must be implemented to send events to a Datadog HTTP endpoint. Grepr does not support TCP.
-- A Datadog API key for your account. When sending events to Grepr, you must use the same API key that's used for the direct Datadog integration.
-
-### Configure event forwarding to Grepr
-
-To integrate Grepr into your Event Hubs-to-Datadog integration:
-
-1. Create a Grepr Datadog integration, add the integration to a Grepr pipeline, and create a source. For step-by-step instructions, see [Use a Datadog integration in a Grepr pipeline](#use-datadog-integration).
-1. Get the ingestion URL for the Grepr integration by following the instructions in [Step 3: Configure log forwarding to Grepr](#configure-forwarding-to-grepr), then skip the instructions for configuring collectors.
-1. In the Azure component that forwards events to Datadog, such as an Azure Function, replace the Datadog endpoint URL with the Grepr ingestion URL and include the path from the Datadog URL. For example, replace:
-
-   ```cs
-   var eventsEndpoint = "https://http-intake.logs.datadoghq.com/api/v2/logs";
-   ```
-
-    with:
-
-    ```cs
-    var eventsEndpoint = "https://1234567890123-yourorg.ingest.grepr.ai/api/v2/logs";
-    ```
-
-1. Ensure the existing Datadog API key is also included in the request sent to Grepr.
-
-After you make this configuration change, you can use your existing Grepr pipelines or create new pipelines to process the events before they are forwarded to Datadog.
-
-## Limitations
-
-- The Datadog integration supports only HTTP/HTTPS connections. TCP connections are not supported.
-- The Datadog integration does not support the use of [Datadog log pipelines](https://docs.datadoghq.com/logs/processing/pipelines/). Grepr processes and routes all logs before sending them to Datadog.
-
-<HiddenFAQ faqs={[
-  { q: "How do I send Datadog logs to Grepr?", a: "Configure your log collector (Datadog Agent, Fluent Bit, Fluentd, or OpenTelemetry Collector) to forward logs to your Grepr ingest endpoint URL." },
-  { q: "What is the Grepr Datadog ingestion endpoint format?", a: "The endpoint format is https://<integration-id>-<org-id>.ingest.grepr.ai" },
-  { q: "How do I reduce Datadog logging costs with Grepr?", a: "Use Grepr's log reduction and filtering to lower log volume before sending to Datadog." },
-  { q: "Can I use Grepr with the Datadog Agent?", a: "Yes, configure logs_config.logs_dd_url to your Grepr endpoint and set force_use_http to true." },
-  { q: "How do I configure Fluent Bit to send logs to Grepr instead of Datadog?", a: "In the Fluent Bit OUTPUT section, set the Host to your Grepr ingestion URL and include your Datadog API key." },
-  { q: "Does Grepr support the OpenTelemetry Collector with Datadog?", a: "Yes, configure the Datadog exporter with your Grepr endpoint in the logs.endpoint setting." },
-  { q: "What is selective reduction with Datadog?", a: "When you provide a Datadog application key, Grepr automatically tracks your Datadog log monitors and excludes matching logs from reduction." },
-  { q: "Can I forward Azure Event Hub logs through Grepr to Datadog?", a: "Yes, replace the Datadog endpoint URL in your Azure function with your Grepr ingestion URL." },
-  { q: "Does Grepr support the Datadog Forwarder Lambda?", a: "Yes, Grepr supports Datadog Forwarder version 5.0.0 or later. Set DD_URL to your Grepr ingestion hostname." },
-  { q: "What protocols does the Grepr Datadog integration support?", a: "Only HTTP and HTTPS. TCP connections are not supported." }
-]} />

package/build/dist/docs-index/62cc03e2-aa6e-4e2c-aa24-1a2f07fbf5d9.json

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

package/build/dist/docs-index/62cc03e2-aa6e-4e2c-aa24-1a2f07fbf5d9.txt

@@ -1,17 +0,0 @@
-# AuthConfig
-
-**Type**: `object`
-
-## Properties
-
-- name: provider (required)
-  type: string
-
-- name: authServerUrl (required)
-  type: string
-
-- name: appClientId (required)
-  type: string
-
-- name: signupClientId (optional)
-  type: string

package/build/dist/docs-index/62e88fe6-e8d9-47c5-81f2-e3da98cb2b34.json

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

package/build/dist/docs-index/62e88fe6-e8d9-47c5-81f2-e3da98cb2b34.txt

@@ -1,14 +0,0 @@
-# AttributesMergeStrategyEntry
-
-List of attribute paths and their corresponding merge strategies. If no strategy is defined for a path, the terminal merge strategy will be used.
-
-**Type**: `object`
-
-## Properties
-
-- name: attributePath (required)
-  type: array of string
-  description: The attribute path, represented as an array of strings (e.g., ["user", "id"]).
-
-- name: strategy (required)
-  type: `AttributesMergeStrategy`

package/build/dist/docs-index/64164aec-6442-4219-84b5-4344381176f0.json

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

package/build/dist/docs-index/64164aec-6442-4219-84b5-4344381176f0.txt

@@ -1,19 +0,0 @@
-# QuantileSamplingTier
-
-List of quantile sampling tiers for performance-based sampling. Each tier defines a percentile threshold, sampling rate, and label. Traces ABOVE each quantile get the corresponding sampling rate and are labeled with the tier's label. Always include a 0.0 quantile tier for baseline rate. Evaluated in descending quantile order.
-
-**Type**: `object`
-
-## Properties
-
-- name: quantile (required)
-  type: number
-  description: The percentile threshold for this tier (0.0 = 0th percentile, 0.5 = 50th percentile, 0.99 = 99th percentile). Traces with duration ABOVE this percentile will be evaluated for this sampling rate.
-
-- name: samplingRate (required)
-  type: number
-  description: The sampling rate to apply for traces that exceed this quantile threshold. 0.0 = 0% (no sampling), 1.0 = 100% (always sample).
-
-- name: label (required)
-  type: string
-  description: Human-readable label for this tier, used as the percentile bucket value in the enriched span data. This allows you to categorize traces into named buckets for querying and analysis.

package/build/dist/docs-index/644393d4-9ebe-4d3d-af93-9f6e55097817.json

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