@grepr/cli 1.2.0 → 1.3.0-94fe60c

package/build/dist/docs-index/0f9188a0-998b-4f88-81b1-52add9033f20.json

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

package/build/dist/docs-index/0f9188a0-998b-4f88-81b1-52add9033f20.txt

@@ -1,13 +0,0 @@
-# WindowBasedLogarithmicSampling
-
-**Type**: `object`
-
-## Properties
-
-- name: logarithmBase (optional)
-  type: integer
-  description: Logarithm base used by sampling algorithm
-
-- name: type (required)
-  type: enum: `window-based-logarithmic-sampling`
-  description: A logarithmic sampler that reduces the log volume per reduction window

package/build/dist/docs-index/0fb49b0f-3786-4491-b40a-30483e1aa88a.json

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

package/build/dist/docs-index/0fb49b0f-3786-4491-b40a-30483e1aa88a.txt

@@ -1,17 +0,0 @@
-# ExternalSourceTrigger
-
-**Type**: `object`
-
-## Properties
-
-- 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: type (required)
-  type: enum: `event-predicate`
-  description: This trigger is activated by an external source, for eg: an API call from an observability tool.

package/build/dist/docs-index/10cc7fe5-b150-46f6-975f-c8a44e7d1f98.json

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

package/build/dist/docs-index/10cc7fe5-b150-46f6-975f-c8a44e7d1f98.txt

@@ -1,34 +0,0 @@
-# Create a S3 Data Warehouse integration
-
-**POST** `/v1/integrations/s3-data-warehouse`
-
-**Operation ID**: `create_2`
-**Summary**: Create a S3 Data Warehouse integration
-Creates an external S3 Data Warehouse integration
-
-## Tags
-- External S3 Data Warehouse Integration
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteS3DataWarehouse`
-
-## Responses
-
-### 201
-
-S3 Data Warehouse integration created successfully
-
-- **Content-Type**: `application/json` / `ReadS3DataWarehouse`
-### 400
-
-Bucket is not accessible or the role is invalid
-
-### 401
-
-Unauthorized
-
-### 409
-
-S3 Data Warehouse integration already exists

package/build/dist/docs-index/120a110a-1a64-4eb8-8a10-48fe2cd4a083.json

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

package/build/dist/docs-index/120a110a-1a64-4eb8-8a10-48fe2cd4a083.txt

@@ -1,8 +0,0 @@
-# ParseQueryRequest
-
-**Type**: `object`
-
-## Properties
-
-- name: query (optional)
-  type: `EventPredicate`

package/build/dist/docs-index/120ae49d-fe82-4018-859d-ef4e71a94345.json

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

package/build/dist/docs-index/120ae49d-fe82-4018-859d-ef4e71a94345.txt

@@ -1,8 +0,0 @@
-# Manifest
-
-**Type**: `object`
-
-## Properties
-
-- name: auth (required)
-  type: `AuthConfig`

package/build/dist/docs-index/12152940-6000-4c37-9d3e-e11633376d22.json

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

package/build/dist/docs-index/12152940-6000-4c37-9d3e-e11633376d22.txt

@@ -1,16 +0,0 @@
-# IntegrationExceptionConfig
-
-**Type**: `object`
-
-## Properties
-
-- name: ids (optional)
-  type: array of string
-
-- name: integrationId (required)
-  type: string
-  description: The ID of the integration associated with this exception configuration.
-
-- name: autoSync (optional)
-  type: boolean
-  description: When enabled, the exceptions list will be updated automatically based on the integration's exceptions.

package/build/dist/docs-index/1361dd23-7c16-44ff-8fbe-3b9c58ac7753.json

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

package/build/dist/docs-index/1361dd23-7c16-44ff-8fbe-3b9c58ac7753.txt

@@ -1,11 +0,0 @@
-# MatrixResult
-
-**Type**: `object`
-
-## Properties
-
-- name: metric (optional)
-  type: object
-
-- name: values (optional)
-  type: array of array of object

package/build/dist/docs-index/13d87950-2ea3-400e-a442-c861a0bcfc09.json

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

package/build/dist/docs-index/13d87950-2ea3-400e-a442-c861a0bcfc09.txt

@@ -1,24 +0,0 @@
-# Delete a S3 Data Warehouse integration
-
-**DELETE** `/v1/integrations/s3-data-warehouse/{id}`
-
-**Operation ID**: `delete_2`
-**Summary**: Delete a S3 Data Warehouse integration
-Deletes an external S3 Data Warehouse integration if it exists. No-op otherwise.
-
-## Tags
-- External S3 Data Warehouse Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-S3 Data Warehouse integration deleted successfully
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/15ea3bf2-f1da-40d3-9daf-d6caacbe2bcf.json

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

package/build/dist/docs-index/15ea3bf2-f1da-40d3-9daf-d6caacbe2bcf.txt

@@ -1,10 +0,0 @@
-# ParsedQueryTree
-
-The parsed query tree
-
-**Type**: `object`
-
-## Properties
-
-- name: root (optional)
-  type: `ParsedQueryNode`

package/build/dist/docs-index/1607fdb9-7e77-4026-99ec-8f25c025dd15.json

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

package/build/dist/docs-index/1607fdb9-7e77-4026-99ec-8f25c025dd15.txt

@@ -1,25 +0,0 @@
-# TagAction
-
-**Type**: `object`
-
-## Properties
-
-- name: order (optional)
-  type: integer
-  description: Action order. Lower is applied first.
-
-- name: modification (required)
-  type: enum: `ADD`, `REMOVE`, `SET`, `DELETE`
-  description: Modification actions on tag values.
-
-- name: tagKey (required)
-  type: string
-  description: The key of the tag to add.
-
-- name: values (required)
-  type: array of string
-  description: The values of the tag to modify.
-
-- name: type (required)
-  type: enum: `tag-action`
-  description: Modifies event tag values.

package/build/dist/docs-index/16c5f096-5095-44ee-96aa-c3dc9f04e157.json

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

package/build/dist/docs-index/16c5f096-5095-44ee-96aa-c3dc9f04e157.txt

@@ -1,5 +0,0 @@
-# LatestReadingStrategy
-
-Strategy to read files created after the current job start time
-
-**Type**: `object`

package/build/dist/docs-index/17260be3-a406-43f0-bb5a-6ca2c6832ca0.json

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

package/build/dist/docs-index/17260be3-a406-43f0-bb5a-6ca2c6832ca0.txt

@@ -1,66 +0,0 @@
----
-description: Step-by-step tutorials for building data pipelines, configuring integrations, and implementing transforms in Grepr
----
-
-import { HiddenFAQ } from '@/components/HiddenFAQ'
-
-# Learn how to use Grepr
-
-These tutorials provide hands-on guidance for building and configuring Grepr data pipelines. Each tutorial walks through specific tasks with practical examples, from basic pipeline creation to advanced data processing scenarios.
-
-## Build your first pipeline
-
-This tutorial covers the fundamentals of creating a Grepr pipeline. You'll learn how to configure a source, add transforms to process data, and set up a sink to output results. By the end, you'll understand the basic pipeline structure and workflow.
-
-See [Building your first pipeline](/tutorials/first-pipeline).
-
-## Troubleshoot incidents with Grepr-processed data
-
-Learn how to use Grepr to enhance your incident response workflows. This tutorial demonstrates how to use Grepr-processed data in an observability platform to quickly identify and troubleshoot issues.
-
-See [Troubleshoot incidents with Grepr-processed data and your observability tool](/tutorials/troubleshooting-example).
-
-## See how data flows through your pipelines and test changes
-
-Learn how to use the live edit feature in the Grepr pipelines UI to see in real-time how data flows through your pipelines. This tutorial also shows you how to use live edit to safely test changes to your pipeline processing.
-
-See [View pipeline data flows and test changes with live edit](/tutorials/live-edit).
-
-<HiddenFAQ faqs={[
-  {
-    q: "What is the best way to get started with Grepr?",
-    a: "Start with the 'Build your first pipeline' tutorial, which covers fundamentals including configuring a source, adding transforms to process data, and setting up a sink for outputs. This provides foundational knowledge about Grepr's pipeline structure and workflow before moving to more advanced scenarios."
-  },
-  {
-    q: "Where do I find the available tutorials?",
-    a: "Tutorials are organized in the learning section and cover key topics: building your first pipeline, troubleshooting incidents with Grepr-processed data, and viewing pipeline data flows with live edit. Each tutorial is self-contained and focuses on specific tasks with practical examples."
-  },
-  {
-    q: "What will I learn in the first pipeline tutorial?",
-    a: "The 'Build your first pipeline' tutorial teaches you how to configure a source to ingest data, add transforms to process and modify that data, and set up a sink to output results to external systems. You'll understand the basic pipeline structure, how data flows through operations, and the fundamental Grepr workflow."
-  },
-  {
-    q: "How can I use Grepr to improve incident response?",
-    a: "The 'Troubleshoot incidents with Grepr-processed data' tutorial demonstrates how to enhance incident response workflows using Grepr-enriched data in your observability platform. It shows practical techniques for quickly identifying and troubleshooting issues using processed data."
-  },
-  {
-    q: "What is live edit and when should I use it?",
-    a: "Live edit is a feature in the Grepr pipelines UI that lets you see in real-time how data flows through your pipelines and safely test changes without deploying. The 'View pipeline data flows and test changes with live edit' tutorial shows how to use this for development, testing, and debugging pipeline logic."
-  },
-  {
-    q: "Do I need coding experience to use these tutorials?",
-    a: "The basic tutorials focus on configuration and UI usage, requiring no coding experience. However, advanced features like templates use JavaScript. Tutorials provide examples and step-by-step instructions that work for both beginners and experienced users. Start with basic tutorials and advance based on your needs."
-  },
-  {
-    q: "What prerequisites do I need before starting tutorials?",
-    a: "You should have access to a Grepr instance with appropriate permissions to create pipelines. Most tutorials assume basic familiarity with log data and observability concepts. Some advanced tutorials may require JavaScript knowledge or experience with your specific observability platform."
-  },
-  {
-    q: "Can I apply tutorial patterns to my own data?",
-    a: "Yes, tutorials provide generalizable patterns and best practices that you can adapt to your specific use cases. Each tutorial includes configurable examples and explains the underlying concepts so you can apply those patterns to your data sources, transforms, and sinks."
-  },
-  {
-    q: "How do I move from tutorials to production pipelines?",
-    a: "After completing tutorials, you can build on those foundations by creating more complex pipelines, using templates for reusability, implementing custom transforms, and integrating with your specific data sources and destinations. The REST API and CLI provide additional programmatic capabilities beyond the UI."
-  }
-]} />

package/build/dist/docs-index/17876c18-e486-4496-a799-5ed9bdd19e67.json

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

package/build/dist/docs-index/17876c18-e486-4496-a799-5ed9bdd19e67.txt

@@ -1,124 +0,0 @@
----
-description: Learn how to create and manage Grepr teams, assign users to teams, and use teams to control access to Grepr features.
----
-
-import { Callout } from 'nextra/components'
-import { HiddenFAQ } from '@/components/HiddenFAQ'
-
-# Manage teams in the Grepr platform
-
-Teams allow you to organize users and resources in your organization. Team members can be assigned the Leader or Member roles. You can also use teams to control access to jobs, integrations, templates, and datasets.
-
-Team roles are separate from organization-level roles. A user can be a team Leader without being an organization-level administrator.
-
-You can manage teams in the Grepr UI or the REST API. This page describes how to manage teams in the UI. To use the API, see the [Teams specification](/apis/api-spec#tag/Teams).
-
-<Callout>
-  You must have the `view:users` permission to access the user management UI. This permission is granted to organization Admins and team Leaders.
-</Callout>
-
-## Team roles in the Grepr platform
-
-A user is assigned to a team with one of the following roles:
-
-- The Leader role has elevated permissions in the team and can manage team membership and team-scoped resources. These permissions include creating and editing jobs, integrations, templates, and datasets assigned to the team. Team Leaders can also view all organization resources, but only edit resources scoped to their team or teams.
-- A Member can view resources assigned to the team, run backfill jobs, and query logs, but does not have permissions to create or edit resources such as jobs, integrations, templates, or datasets assigned to the team.
-
-For details on the permissions for these roles, see [Permissions in the Grepr platform](/grepr-platform/permissions).
-
-## Grant team access to resources
-
-You can grant access to a team when you create or edit a resource, such as an integration, dataset, template, or job. When you grant a team access to a resource, team Leaders have edit permissions on the resource, and team Members have view permissions. To learn how to add team access when you create a resource, see the documentation for that resource. For example, to add teams to a Datadog integration, see [Configure Datadog connections for integration with Grepr](/integrations/datadog).
-
-To edit and use a job, such as a pipeline, a user must have access to all resources assigned to the job. Because of this requirement, if a job is assigned to a team, and the team Leader has edit permissions on the integration used as a source and sink in the job, but not on the dataset used in the job, the team Leader cannot edit or use the job.
-
-## Access team management features in the UI
-
-To manage teams in the Grepr UI:
-
-1. Sign in to the Grepr UI and click your profile icon in the top bar.
-1. In the menu, select **User Management**.
-1. On the **User Management** page, click **Teams** in the left pane.
-
-The **Teams** pane displays each team in your organization on a card. Each card includes the team name, number of team members, and options to manage or delete the team.
-
-Click **Manage** on any team card to view and manage team members.
-
-## Create a team
-
-To create a team:
-
-1. In the **Teams** pane, click **Create New Team**.
-1. In the **Create New Team** dialog, enter a name for the team.
-1. Click **Create**.
-
-## Add members to a team
-
-To add members to a team:
-
-1. In the **Teams** pane, click **Manage Team** in the team card.
-1. Click **Add Users**.
-1. Select one or more users to add as Leaders or Members.
-1. Click **Add Users**.
-
-## Remove members from a team
-
-1. In the **Teams** pane, find the member in the Team Members table.
-1. Click the trash icon next to their name.
-1. Click **Remove**.
-
-Removing a user from a team revokes their access to team-scoped resources.
-
-## Delete a team
-
-1. In the **Teams** pane, click the trash can icon in the team card.
-1. In the **Confirm Delete** dialog, click **Delete**.
-
-<Callout>
-  You can delete a team even if it has members. Before deleting a team, ensure the team doesn't have any dependencies on resources, such as integrations or jobs, assigned to it.
-</Callout>
-
-<HiddenFAQ
-  faqs={[
-    {
-      q: "What is a team in Grepr and how does it differ from organization-level roles?",
-      a: "Teams are groups of users that allow you to organize and scope access to resources like jobs, integrations, templates, and datasets. Team roles (Leader/Member) are separate from organization-level roles (Admin/Member), allowing for more granular access control within teams."
-    },
-    {
-      q: "What permissions do team Leaders have compared to team Members?",
-      a: "Team Leaders have elevated permissions including creating and editing jobs, integrations, templates, and datasets assigned to the team. Team Members can only view resources assigned to the team, run backfill jobs, and query logs, but cannot create or edit team resources."
-    },
-    {
-      q: "Can a team Leader edit organization-level resources?",
-      a: "Team Leaders can view all organization resources, but can only edit resources that are scoped to their team. To edit organization-wide resources, they need organization-level Admin permissions."
-    },
-    {
-      q: "How do I grant a team access to resources like integrations or jobs?",
-      a: "When creating or editing a resource, you can assign it to one or more teams. Once assigned, Team Leaders have edit permissions and Team Members have view permissions on that resource."
-    },
-    {
-      q: "What happens if I try to use a job with multiple team dependencies?",
-      a: "A user must have access to all resources assigned to a job. If a job uses an integration and dataset from different teams, the user must be a member of both teams with appropriate permissions to use the job."
-    },
-    {
-      q: "Can I delete a team with active members?",
-      a: "Yes, you can delete a team even if it has members. However, you should first ensure the team has no dependencies on resources like integrations or jobs assigned to it."
-    },
-    {
-      q: "What happens to a user's access when I remove them from a team?",
-      a: "Removing a user from a team revokes their access to all team-scoped resources. They retain access to organization-level resources and resources assigned to other teams they are members of."
-    },
-    {
-      q: "Can a team be assigned to multiple jobs or integrations?",
-      a: "Yes, a single team can have access to multiple resources. When you grant a team access to a resource, that team can manage or view that resource depending on the team member's role (Leader or Member)."
-    },
-    {
-      q: "How do I change a user's role within a team from Member to Leader?",
-      a: "In the Teams pane, click 'Manage Team' on the team card, find the user in the Team Members table, and use the role management interface to update their role from Member to Leader."
-    },
-    {
-      q: "What is the recommended way to organize users into teams?",
-      a: "Organize teams based on functional areas, projects, or business units. This allows you to scope resources and permissions to specific groups, following the principle of least privilege and making access management simpler at scale."
-    }
-  ]}
-/>

package/build/dist/docs-index/1795e087-6344-4b45-a9dd-2cdd1a23d55f.json

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

package/build/dist/docs-index/1795e087-6344-4b45-a9dd-2cdd1a23d55f.txt

@@ -1,39 +0,0 @@
-# Update a Splunk integration.
-
-**PUT** `/v1/integrations/splunk/{id}`
-
-**Operation ID**: `update_5`
-**Summary**: Update a Splunk integration.
-Updates an integration to connect to Splunk. The version should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.
-
-## Tags
-- Splunk Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteSplunk`
-
-## Responses
-
-### 200
-
-Integration updated successfully
-
-- **Content-Type**: `application/json` / `ReadSplunk`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.
-
-### 409
-
-Integration was modified or deleted concurrently.

package/build/dist/docs-index/17b45af1-0874-45ec-8cda-b71eab23e999.json

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

package/build/dist/docs-index/17b45af1-0874-45ec-8cda-b71eab23e999.txt

@@ -1,24 +0,0 @@
-# WriteSumo
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-  description: Name of the integration.
-
-- name: version (required)
-  type: integer
-  description: Version of the integration. Should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.
-
-- name: payload (required)
-  type: `Sumo`
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this integration is associated with.
-
-- name: type (required)
-  type: enum: `sumo`
-  description: The type of the integration. This is used to determine the payload type.

package/build/dist/docs-index/180700f4-2d4f-471f-9803-7d3a310c7df0.json

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

package/build/dist/docs-index/180700f4-2d4f-471f-9803-7d3a310c7df0.txt

@@ -1,126 +0,0 @@
----
-description: Learn how to optimize your Google Cloud observability with Grepr and the Google Pub/Sub to Datadog feature.
----
-
-import { Callout } from 'nextra/components'
-import { HiddenFAQ } from '@/components/HiddenFAQ'
-
-# Google Cloud Platform observability with Grepr
-
-To enhance your Google Cloud Platform (GCP) observability, you can stream GCP logs to Grepr, process and transform the logs using Grepr's powerful features, then forward the processed logs to any Grepr-supported observability platform or tool, such as Datadog, Splunk, or New Relic. The Grepr integration with GCP uses Google's `Pub/Sub to Datadog` Dataflow template with a configured Grepr Datadog integration, and requires only minimal configuration changes to route logs through a Grepr pipeline. To learn more about the `Pub/Sub to Datadog` feature, see [Pub/Sub to Datadog template](https://cloud.google.com/dataflow/docs/guides/templates/provided/pubsub-to-datadog).
-
-## Requirements
-
-<Callout type="info">
-  The integration with GCP requires a Datadog integration configured in Grepr, including a valid Datadog API key. However, when you configure a Grepr pipeline using this integration, you can use any Grepr-supported sink. For example, a pipeline that sources GCP logs with a Datadog integration can use a Splunk integration as a sink.
-</Callout>
-
-To integrate Grepr with GCP and Datadog, you must have:
-
-- A Datadog API key for your account. You use the same API key in your Grepr integration and the GCP component configurations.
-- A Datadog integration configured in Grepr. See the [Configure Datadog connections for integration with Grepr](/integrations/datadog).
-- A Grepr ingestion URL. This URL is available when you create a Grepr pipeline using the Datadog integration. To learn how to create a Grepr pipeline, see the [Build your first Grepr pipeline](/tutorials/first-pipeline) tutorial.
-- Completed the configuration of the GCP to Datadog infrastructure. See [Stream logs from Google Cloud to Datadog](https://cloud.google.com/architecture/partners/stream-cloud-logs-to-datadog). Make sure you have:
-  - A Pub/Sub topic and subscription for collecting logs and sending them to Grepr.
-  - A GCP Cloud Logging sink configured to route logs to your Pub/Sub topic.
-  - Correct GCP IAM permissions.
-
-## Configure the GCP and Datadog integration with Grepr
-
-To configure the integration, you modify the Google `Pub/Sub to Datadog` Dataflow template to send logs to Grepr instead of directly to Datadog:
-
-1. In the GCP Console, go to **Dataflow > Jobs > Create Job From Template**.
-1. Select **Pub/Sub to Datadog** from the available templates.
-1. In **Required Parameters**, enter the following value:
-   - `Datadog Logs API URL: <your-grepr-ingestion-url>`
-1. In **Optional Parameters**, enter the following value:
-   - `Logs API key: <your-datadog-api-key>`
-
-<Callout type="warning">
-  The `Logs API key` parameter in your Dataflow job must exactly match the Datadog API key configured in your Grepr Datadog integration. Mismatched API keys will cause authentication failures and prevent log delivery.
-</Callout>
-
-### Example configuration
-
-```yaml
-# Standard Datadog configuration:
-url: https://http-intake.logs.datadoghq.com/api/v2/logs
-apiKey: <datadog-api-key>
-
-# Modified for Grepr:
-url: https://<integration-id>-<org-id>.ingest.grepr.ai
-apiKey: <same-datadog-api-key>
-```
-
-To get the Grepr ingestion URL, go to your pipeline's source configuration page in the Grepr UI and click **Copy ingest URL**.
-
-![Accessing the ingestion URL in the Grepr pipeline UI.](/images/integrations/ingestion-url-datadog.png)
-
-## Verifying the integration
-
-After deploying your Dataflow job:
-
-1. **Check Dataflow Status**: Verify the job is running without errors in the GCP Console.
-2. **Monitor Grepr Pipeline**: In the Grepr UI, confirm your pipeline shows active log ingestion and processing metrics.
-3. **Verify Datadog Delivery**: Check that processed logs are arriving in Datadog with tags applied by Grepr. For example, `processor:grepr`.
-
-## Troubleshooting
-
-### Common issues
-
-- **Authentication Errors**: Verify the Datadog API key matches between the Grepr integration and the Dataflow job.
-- **Connection Failures**: Ensure Dataflow workers can reach the Grepr ingestion endpoint.
-- **Missing Logs**: Verify the Cloud Logging sink is properly routing logs to your Pub/Sub topic.
-
-### Monitoring
-
-Monitor the health of the integration with:
-- GCP Dataflow job metrics and logs.
-- Grepr pipeline throughput and processing metrics.
-- Datadog log intake monitoring.
-- Pub/Sub subscription metrics for backlog monitoring.
-
-<HiddenFAQ
-  faqs={[
-    {
-      q: "How do I stream logs from Google Cloud Platform to Grepr?",
-      a: "Use the Google Pub/Sub to Datadog Dataflow template configured with Grepr. Set up a Cloud Logging sink to route logs to a Pub/Sub topic. Then create a Dataflow job using the Pub/Sub to Datadog template, but configure it to send logs to your Grepr ingestion URL instead of directly to Datadog."
-    },
-    {
-      q: "What authentication is required for GCP integration with Grepr?",
-      a: "You need a Datadog API key that is configured in both your Grepr Datadog integration and your GCP Dataflow job. The API key must be identical in both places. Additionally, you need appropriate GCP IAM permissions to create Dataflow jobs and access Pub/Sub topics."
-    },
-    {
-      q: "What is the Pub/Sub to Datadog Dataflow template?",
-      a: "It is a Google-provided template that processes logs from a Pub/Sub topic and forwards them to Datadog. Grepr uses this template by configuring it to send logs to Grepr's ingestion endpoint instead, allowing you to process GCP logs through Grepr before final delivery."
-    },
-    {
-      q: "Do I need to use Datadog as my sink when using GCP integration with Grepr?",
-      a: "You must configure a Datadog integration in Grepr to use the GCP integration, but you can use any Grepr-supported sink for processed logs. For example, you can ingest GCP logs via Datadog integration and send processed logs to Splunk, New Relic, or other platforms."
-    },
-    {
-      q: "How do I configure the Pub/Sub to Datadog Dataflow job for Grepr?",
-      a: "In GCP Console, create a Dataflow job from the Pub/Sub to Datadog template. Set the Datadog Logs API URL to your Grepr ingestion URL (format: https://<integration-id>-<org-id>.ingest.grepr.ai) and the Logs API key to your Datadog API key. Ensure the key matches your Grepr Datadog integration."
-    },
-    {
-      q: "What happens if the Datadog API key doesn't match between Grepr and Dataflow?",
-      a: "If the API keys don't match, authentication will fail and logs will not be delivered. The mismatch prevents the Dataflow job from authenticating with Grepr, causing the integration to break. Always verify that the API key is identical in both your Grepr integration and your Dataflow job configuration."
-    },
-    {
-      q: "How do I set up the GCP infrastructure required for this integration?",
-      a: "You need to set up a Pub/Sub topic and subscription for log collection, configure a Cloud Logging sink to route logs to the Pub/Sub topic, and ensure your GCP IAM permissions allow creating and managing Dataflow jobs. See Google's documentation on streaming logs to Datadog for detailed infrastructure setup."
-    },
-    {
-      q: "How can I reduce costs using GCP logs with Grepr?",
-      a: "Process logs through Grepr pipelines to filter, aggregate, and reduce log volume before final storage. Use Grepr's Log Reducer to identify and exclude redundant messages. This reduces the volume of data stored in your final observability platform, lowering your overall observability costs."
-    },
-    {
-      q: "Can I transform GCP logs in Grepr before sending to Datadog?",
-      a: "Yes, that is the main benefit of the integration. Logs flow from GCP Cloud Logging through Pub/Sub to Grepr via Dataflow. In Grepr, you can apply transformations, filtering, log reduction, and other processing before sending to Datadog or other sinks."
-    },
-    {
-      q: "How do I monitor the GCP to Grepr integration?",
-      a: "Monitor the Dataflow job status in GCP Console for errors and processing metrics. In Grepr, check your pipeline's ingestion metrics to verify logs are arriving. Check your Dataflow job logs for any authentication or processing errors. Verify processed logs are appearing in your final sink platform."
-    }
-  ]}
-/>

package/build/dist/docs-index/181cdf78-0f6c-4775-994a-0f463618f4e4.json

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

package/build/dist/docs-index/181cdf78-0f6c-4775-994a-0f463618f4e4.txt

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

package/build/dist/docs-index/1913bd37-ff5d-4fd3-8e6b-3e8f2dfbb208.json

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