@grepr/cli 1.8.4-b895a9f → 1.8.6-7c73069

package/build/dist/commands/docs-get-command.d.ts

@@ -39,7 +39,7 @@ export declare class DocsGetCommand implements ICommand {
      * Executes the document retrieval command.
      *
      * This method:
-     * 1. Initializes the DocsSearch engine (loads embedding model and opens index)
+     * 1. Opens the bundled documentation index without loading the embedding model
      * 2. Retrieves the full document content by URI
      * 3. Outputs raw markdown to stdout (no formatting, perfect for piping)
      *

package/build/dist/commands/docs-get-command.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"docs-get-command.d.ts","sourceRoot":"","sources":["../../../src/main/typescript/commands/docs-get-command.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpC,OAAO,EAAE,QAAQ,EAAE,MAAM,4BAA4B,CAAC;AAEtD,OAAO,EAAE,kBAAkB,EAAwB,MAAM,aAAa,CAAC;AAEvE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,qBAAa,cAAe,YAAW,QAAQ;IAC7C,cAAc,IAAI,MAAM;IAIxB,qBAAqB,IAAI,MAAM;IAI/B,YAAY,CAAC,OAAO,EAAE,OAAO,EAAE,mBAAmB,EAAE,kBAAkB,GAAG,IAAI;IAgB7E;;;;;;;;;;;;OAYG;YACW,OAAO;CAOtB"}
+{"version":3,"file":"docs-get-command.d.ts","sourceRoot":"","sources":["../../../src/main/typescript/commands/docs-get-command.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpC,OAAO,EAAE,QAAQ,EAAE,MAAM,4BAA4B,CAAC;AAEtD,OAAO,EAAE,kBAAkB,EAAwB,MAAM,aAAa,CAAC;AAEvE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,qBAAa,cAAe,YAAW,QAAQ;IAC7C,cAAc,IAAI,MAAM;IAIxB,qBAAqB,IAAI,MAAM;IAI/B,YAAY,CAAC,OAAO,EAAE,OAAO,EAAE,mBAAmB,EAAE,kBAAkB,GAAG,IAAI;IAgB7E;;;;;;;;;;;;OAYG;YACW,OAAO;CAKtB"}

package/build/dist/commands/docs-get-command.js

@@ -56,7 +56,7 @@ export class DocsGetCommand {
      * Executes the document retrieval command.
      *
      * This method:
-     * 1. Initializes the DocsSearch engine (loads embedding model and opens index)
+     * 1. Opens the bundled documentation index without loading the embedding model
      * 2. Retrieves the full document content by URI
      * 3. Outputs raw markdown to stdout (no formatting, perfect for piping)
      *
@@ -67,7 +67,6 @@ export class DocsGetCommand {
      */
     async execute(uri) {
         const search = new DocsSearch();
-        await search.initialize();
         const content = await search.getDocument(uri);
         console.log(content);
     }

package/build/dist/commands/docs-get-command.js.map

@@ -1 +1 @@
-{"version":3,"file":"docs-get-command.js","sourceRoot":"","sources":["../../../src/main/typescript/commands/docs-get-command.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,UAAU,EAAE,MAAM,uBAAuB,CAAC;AAGnD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,MAAM,OAAO,cAAc;IACzB,cAAc;QACZ,OAAO,UAAU,CAAC;IACpB,CAAC;IAED,qBAAqB;QACnB,OAAO,wDAAwD,CAAC;IAClE,CAAC;IAED,YAAY,CAAC,OAAgB,EAAE,mBAAuC;QACpE,OAAO;aACJ,OAAO,CAAC,IAAI,CAAC,cAAc,EAAE,CAAC;aAC9B,WAAW,CAAC,IAAI,CAAC,qBAAqB,EAAE,CAAC;aACzC,QAAQ,CAAC,OAAO,EAAE,8DAA8D,CAAC;aACjF,MAAM,CAAC,KAAK,EAAE,GAAW,EAAE,QAA8B,EAAE,EAAE;YAC5D,IAAI,CAAC;gBACH,MAAM,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC;YAC1B,CAAC;YAAC,OAAO,KAAK,EAAE,CAAC;gBACf,MAAM,YAAY,GAAG,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,eAAe,CAAC;gBAC9E,OAAO,CAAC,KAAK,CAAC,mBAAmB,IAAI,CAAC,cAAc,EAAE,GAAG,EAAE,YAAY,CAAC,CAAC;gBACzE,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;YAClB,CAAC;QACH,CAAC,CAAC,CAAC;IACP,CAAC;IAED;;;;;;;;;;;;OAYG;IACK,KAAK,CAAC,OAAO,CAAC,GAAW;QAC/B,MAAM,MAAM,GAAG,IAAI,UAAU,EAAE,CAAC;QAChC,MAAM,MAAM,CAAC,UAAU,EAAE,CAAC;QAE1B,MAAM,OAAO,GAAG,MAAM,MAAM,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC;QAC9C,OAAO,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;IACvB,CAAC;CACF"}
+{"version":3,"file":"docs-get-command.js","sourceRoot":"","sources":["../../../src/main/typescript/commands/docs-get-command.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,UAAU,EAAE,MAAM,uBAAuB,CAAC;AAGnD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,MAAM,OAAO,cAAc;IACzB,cAAc;QACZ,OAAO,UAAU,CAAC;IACpB,CAAC;IAED,qBAAqB;QACnB,OAAO,wDAAwD,CAAC;IAClE,CAAC;IAED,YAAY,CAAC,OAAgB,EAAE,mBAAuC;QACpE,OAAO;aACJ,OAAO,CAAC,IAAI,CAAC,cAAc,EAAE,CAAC;aAC9B,WAAW,CAAC,IAAI,CAAC,qBAAqB,EAAE,CAAC;aACzC,QAAQ,CAAC,OAAO,EAAE,8DAA8D,CAAC;aACjF,MAAM,CAAC,KAAK,EAAE,GAAW,EAAE,QAA8B,EAAE,EAAE;YAC5D,IAAI,CAAC;gBACH,MAAM,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC;YAC1B,CAAC;YAAC,OAAO,KAAK,EAAE,CAAC;gBACf,MAAM,YAAY,GAAG,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,eAAe,CAAC;gBAC9E,OAAO,CAAC,KAAK,CAAC,mBAAmB,IAAI,CAAC,cAAc,EAAE,GAAG,EAAE,YAAY,CAAC,CAAC;gBACzE,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;YAClB,CAAC;QACH,CAAC,CAAC,CAAC;IACP,CAAC;IAED;;;;;;;;;;;;OAYG;IACK,KAAK,CAAC,OAAO,CAAC,GAAW;QAC/B,MAAM,MAAM,GAAG,IAAI,UAAU,EAAE,CAAC;QAChC,MAAM,OAAO,GAAG,MAAM,MAAM,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC;QAC9C,OAAO,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;IACvB,CAAC;CACF"}

package/build/dist/docs-index/0030585b-74b0-4a49-81b0-eca27a9a1de1.json

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

package/build/dist/docs-index/0030585b-74b0-4a49-81b0-eca27a9a1de1.txt

@@ -0,0 +1,20 @@
+# List all Datadog MCP integrations
+
+**GET** `/v1/integrations/datadog-mcp`
+
+**Operation ID**: `list_6`
+**Summary**: List all Datadog MCP integrations
+Get all Datadog MCP server integrations for your organization. This will contain masked API keys if present.
+
+## Tags
+- Datadog MCP Integration
+## Responses
+
+### 200
+
+Integrations retrieved successfully
+
+- **Content-Type**: `application/json` / `ItemsCollectionReadDatadogMcp`
+### 401
+
+Unauthorized

package/build/dist/docs-index/00d70d42-dc0d-44a8-af22-4493f7c0c622.json

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

package/build/dist/docs-index/00d70d42-dc0d-44a8-af22-4493f7c0c622.txt

@@ -0,0 +1,24 @@
+# WriteDatadog
+
+**Type**: `object`
+
+## Properties
+
+- name: name (required)
+  type: string
+  description: Name of the integration.
+
+- name: payload (required)
+  type: `Datadog`
+
+- name: teamIds (optional)
+  type: array of string
+  description: The team IDs that this integration is associated with.
+
+- name: type (required)
+  type: enum: `datadog`
+  description: The type of the integration. This is used to determine the payload type.
+
+- 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.

package/build/dist/docs-index/017a1a84-51e1-4d15-a89c-5f1727d604ad.json

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

package/build/dist/docs-index/017a1a84-51e1-4d15-a89c-5f1727d604ad.txt

@@ -0,0 +1,18 @@
+# MetricNameFilter
+
+Glob-pattern filter on metric names.
+
+**Type**: `object`
+
+## Properties
+
+- name: empty (optional)
+  type: boolean
+
+- name: excludes (optional)
+  type: array of string
+  description: Glob patterns to exclude. Precedence over includes.
+
+- name: includes (optional)
+  type: array of string
+  description: Glob patterns to include. Empty list matches all.

package/build/dist/docs-index/0221f11e-48cc-40c4-bf75-52def8ebe013.json

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

package/build/dist/docs-index/0221f11e-48cc-40c4-bf75-52def8ebe013.txt

@@ -0,0 +1,30 @@
+# Reset impact estimations for a pipeline
+
+**POST** `/v1/pipelines/{pipelineId}/exceptions/impact-estimation-reset`
+
+**Operation ID**: `resetImpactEstimation`
+**Summary**: Reset impact estimations for a pipeline
+Clears the cached impact percentage and last-updated timestamp on estimation rows in the pipeline's scope. The hourly impact-estimation cycle picks up the cleared rows on its next tick; fresh values appear on a later poll. Rows currently being processed by an active estimation job are skipped and retain their values until that job completes. Returns the number of rows cleared; zero indicates a no-op (no opted-in sink datasets, or no estimation-capable source integrations).
+
+## Tags
+- Pipeline Exceptions
+## Parameters
+
+- **pipelineId** (required) - path
+  - Pipeline ID to reset estimations for
+  - Type: string
+
+## Responses
+
+### 200
+
+Reset complete
+
+- **Content-Type**: `application/json` / `ResetImpactEstimationResponse`
+### 401
+
+Unauthorized
+
+### 404
+
+Not Found - Pipeline not found.

package/build/dist/docs-index/027b2c2e-673e-46d4-84a7-64fd9e804062.json

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

package/build/dist/docs-index/027b2c2e-673e-46d4-84a7-64fd9e804062.txt

@@ -0,0 +1,61 @@
+# LlmPrompt
+
+**Type**: `object`
+
+## Properties
+
+- name: availableRuleTypes (optional)
+  type: array of string
+  description: Rule types that the LLM can produce as output. When non-empty, the LLM output schema is augmented with a 'rules' field describing the available rule type schemas. Rules returned by the LLM are parsed and persisted to the LogRulesApplication operator for dynamic per-pattern rule application.
+
+- name: availableTools (optional)
+  type: array of `LlmToolConfig`
+  description: MCP tool integrations available for the LLM to invoke as terminal actions. Each entry references an integration that exposes MCP-compatible tools.
+
+- name: capacity (optional)
+  type: integer
+  description: Maximum number of concurrent LLM calls per operator instance. Note: Total concurrent calls = capacity × Flink parallelism. For example, with parallelism=4 and capacity=100, up to 400 concurrent calls may occur. Consider your LLM provider's rate limits when configuring this value.
+
+- name: integrationId (required)
+  type: string
+  description: The LLM integration ID (Gemini or OpenAI).
+
+- name: llmConfig (required)
+  type: `LlmConfig`
+
+- name: maxRetries (optional)
+  type: integer
+  description: Maximum number of retries for failed LLM calls.
+
+- name: name (required)
+  type: string
+
+- name: outputActions (optional)
+  type: array of enum: `FORWARD_TO_SINKS`
+  description: Controls where LLM-enriched events are routed after processing. Multiple actions can be combined.
+
+- name: outputSchema (optional)
+  type: string
+  description: JSON Schema defining the expected structure of the LLM output. When set, the LLM is instructed to return structured JSON matching this schema. The output will include an 'actionable' boolean and a 'user_result' object. Supports standard JSON Schema property keywords: type, description, and enum.
+
+- name: predicate (optional)
+  type: `EventPredicate`
+
+- name: promptInstruction (required)
+  type: string
+  description: The user's prompt instruction describing what the LLM should do. Context (event JSON, entity context, similar patterns) is assembled automatically by the system — do not include placeholders.
+
+- name: responseFormat (optional)
+  type: enum: `TEXT`, `JSON`
+  description: The format for the LLM response.
+
+- name: timeoutSeconds (optional)
+  type: integer
+  description: Timeout for LLM calls in seconds.
+
+- name: type (required)
+  type: enum: `llm-prompt`
+  description: Runs LLM prompts on new log patterns.
+
+- name: workflowConfig (optional)
+  type: `LlmWorkflowConfig`

package/build/dist/docs-index/02c37356-a84d-427a-9e20-5122222d1f19.json

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

package/build/dist/docs-index/02c37356-a84d-427a-9e20-5122222d1f19.txt

@@ -0,0 +1,14 @@
+# TranscriptToolCall
+
+**Type**: `object`
+
+## Properties
+
+- name: argumentsJson (optional)
+  type: string
+
+- name: id (optional)
+  type: string
+
+- name: name (optional)
+  type: string

package/build/dist/docs-index/0307fbe8-3baa-4c63-9fd4-8594470c677f.json

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

package/build/dist/docs-index/0307fbe8-3baa-4c63-9fd4-8594470c677f.txt

@@ -0,0 +1,72 @@
+# LogReducer
+
+**Type**: `object`
+
+## Properties
+
+- name: attributeMergeStrategyEntries (optional)
+  type: array of `AttributesMergeStrategyEntry`
+  description: List of attribute paths and their corresponding merge strategies. If no strategy is defined for a path, the terminal merge strategy will be used.
+
+- name: dedupThreshold (optional)
+  type: integer
+  description: Number of duplicates we send for a pattern before we start deduplication.
+
+- name: defaultAttributesMergeStrategy (optional)
+  type: `AttributesMergeStrategy`
+
+- name: delimiters (required)
+  type: array of string
+  description: Characters to use for splitting tokens. Default is missing '@' to avoid splitting email addresses. Also missing '.' to avoid splitting identifiers using it.
+
+- name: emitNewPatternSignals (optional)
+  type: boolean
+  description: Whether this operation emits LogPatternSignal events to the agent-service when new patterns are detected or replayed.
+
+- name: enabledMasks (required)
+  type: array of string
+  description: Masks that are enabled for tokenizing messages. These are specified as the names of the masks to use. The default enabled masks are: ipport, timestamp, uuid, number.
+
+- name: integrationExceptionConfigs (optional)
+  type: array of `IntegrationExceptionConfig`
+  description: Exception configs that define which exceptions to use from the ones imported from the observability vendor integrations.
+
+- name: logReducerExceptions (optional)
+  type: array of `EventPredicate`
+  description: Predicate for skipping events. Logs matching these predicates won't be aggregated.
+
+- name: masks (required)
+  type: array of array of string
+  description: Set of masks that can be applied to messages before tokenizing them. These masks are specified as pairs of (name, regex). The default masks are: ipport, timestamp, uuid, number, awsarn, awstoken.
+
+- name: name (required)
+  type: string
+
+- name: partitionByAttributePaths (optional)
+  type: array of array of string
+  description: Attribute paths as arrays of keys. Use for unambiguous nested vs flat attributes. Example: [["user", "id"]] for nested user.id, [["user.id"]] for flat attribute named 'user.id'
+
+- name: partitionByAttributes (optional)
+  type: array of string
+
+- name: partitionByTags (optional)
+  type: array of string
+
+- name: reductionTimeWindow (optional)
+  type: string
+  description: Time window in which logs are considered for deduplication. Should not be modified without explicit guidance.
+
+- name: repeatCountInSummaryMessageEnabled (optional)
+  type: boolean
+  description: Whether to include the repeat count prefix in the summary message. Grepr will add a prefix to the summary message with the number messages aggregated. However, this might break downstream parsing if the message is expected to be in a specific format. If you want to include the repeat count, set this to true.
+
+- name: samplingConfig (optional)
+  type: `SamplingConfig`
+
+- name: similarityThreshold (optional)
+  type: number
+  description: Controls how close a set of tokens are to a pattern before it is considered a match. Calculated as the percent of matching tokens between a pattern and a message.
+
+- name: type (required)
+  type: enum: `log-reducer`
+  description: Reduces logs by combining messages with similar patterns.

package/build/dist/docs-index/03305366-dd14-4d47-be2d-537501cb8943.json

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

package/build/dist/docs-index/03305366-dd14-4d47-be2d-537501cb8943.txt

@@ -0,0 +1,32 @@
+# Create an OpenAI integration
+
+**POST** `/v1/integrations/openai`
+
+**Operation ID**: `create_11`
+**Summary**: Create an OpenAI integration
+Creates an integration to connect to OpenAI.
+
+## Tags
+- OpenAI Integration
+## Request Body
+
+**Content-Type**: `application/json`
+
+**Schema**: `WriteOpenAi`
+
+## Responses
+
+### 200
+
+Integration created successfully
+
+- **Content-Type**: `application/json` / `ReadOpenAi`
+### 401
+
+Unauthorized
+
+### 409
+
+Integration already exists.
+
+- **Content-Type**: `application/json` / `ReadOpenAi`

package/build/dist/docs-index/035d13d6-c118-49d7-a2d2-cb30a5e9745d.json

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

package/build/dist/docs-index/035d13d6-c118-49d7-a2d2-cb30a5e9745d.txt

@@ -0,0 +1,17 @@
+# AttributeNode
+
+**Type**: `object`
+
+## Properties
+
+- name: attribute (required)
+  type: string
+  description: The attribute name
+
+- name: term (required)
+  type: string
+  description: The term to match. This is a string that is matched against the attribute.
+
+- name: type (required)
+  type: enum: `attribute-node`
+  description: A node that matches an attribute in a parsed query.

package/build/dist/docs-index/044a4e8b-7ab0-41a2-95be-69c9916961cd.json

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

package/build/dist/docs-index/044a4e8b-7ab0-41a2-95be-69c9916961cd.txt

@@ -0,0 +1,34 @@
+# Creates or updates a Datadog MCP integration application key
+
+**PUT** `/v1/integrations/datadog-mcp/{id}/app-key`
+
+**Operation ID**: `upsertAppKey_1`
+**Summary**: Creates or updates a Datadog MCP integration application key
+Creates the DD-APPLICATION-KEY for a Datadog MCP integration if it doesn't exist and updates it otherwise.
+
+## Tags
+- Datadog MCP Integration
+## Parameters
+
+- **id** (required) - path
+  - Type: string
+
+## Request Body
+
+**Content-Type**: `application/json`
+
+**Schema**: `SecretApi`
+
+## Responses
+
+### 204
+
+Application key upserted successfully.
+
+### 401
+
+Unauthorized
+
+### 404
+
+Integration not found.

package/build/dist/docs-index/04821f50-6f27-4509-b6bb-b55037c1474a.json

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

package/build/dist/docs-index/04821f50-6f27-4509-b6bb-b55037c1474a.txt

@@ -0,0 +1,13 @@
+# MessageRe2Node
+
+**Type**: `object`
+
+## Properties
+
+- name: regex (required)
+  type: string
+  description: The regex to match. This is a regex string that is matched against the message.
+
+- name: type (required)
+  type: enum: `message-re2-node`
+  description: A node that represents a message regex in a parsed query.

package/build/dist/docs-index/0488322b-ef30-40b7-8753-83632dd423a8.json

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

package/build/dist/docs-index/0488322b-ef30-40b7-8753-83632dd423a8.txt

@@ -0,0 +1,5 @@
+# PassthroughNode
+
+Terminal — forwards every event to the chain's downstream pipeline step. UI label is stage-derived (e.g. "Send to Reducer").
+
+**Type**: `object`

package/build/dist/docs-index/04d9d792-9abe-4b0f-a22d-92071a1ac3f6.json

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

package/build/dist/docs-index/04d9d792-9abe-4b0f-a22d-92071a1ac3f6.txt

@@ -0,0 +1,75 @@
+Learn how Grepr integrates with Datadog, Splunk, New Relic, and other platforms to reduce observability costs and provide real-time log processing and analysis.
+
+# 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.
+
+## Get started
+
+[Create your first pipeline](/tutorials/first-pipeline)
+
+[Learn about the platform](/grepr-platform)
+
+## Process and explore your logs
+
+[Connect to external tools](/integrations)
+
+[Process and transform data](/transforms)
+
+[Query logs in the data lake](/queries)
+
+## Developers
+
+[Use the Grepr Rest API](/apis)
+
+[Use the Grepr CLI](/cli)
+
+[Custom pipeline components](/templates)
+
+## Frequently Asked Questions
+
+### What is Grepr?
+
+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.
+
+### How does Grepr reduce observability costs?
+
+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.
+
+### What observability platforms does Grepr integrate with?
+
+Grepr supports popular platforms including Datadog, Splunk, New Relic, Sumo Logic, Grafana Cloud, and OpenTelemetry-compatible platforms.
+
+### What is the Grepr data lake?
+
+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.
+
+### Can I query raw logs in Grepr?
+
+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.
+
+### How do I create a Grepr pipeline?
+
+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.
+
+### What happens to my data during an incident?
+
+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.
+
+### Is my data secure in Grepr?
+
+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.
+
+### Can I use Grepr with my existing observability tools?
+
+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.
+
+### How can I automate Grepr tasks?
+
+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/0518c4de-01f3-47af-bc48-c44b85dccf4f.json

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

package/build/dist/docs-index/0518c4de-01f3-47af-bc48-c44b85dccf4f.txt

@@ -0,0 +1,34 @@
+# Creates or updates a Datadog MCP integration API key
+
+**PUT** `/v1/integrations/datadog-mcp/{id}/api-key`
+
+**Operation ID**: `upsertApiKey_3`
+**Summary**: Creates or updates a Datadog MCP integration API key
+Creates the DD-API-KEY for a Datadog MCP integration if it doesn't exist and updates it otherwise.
+
+## Tags
+- Datadog MCP Integration
+## Parameters
+
+- **id** (required) - path
+  - Type: string
+
+## Request Body
+
+**Content-Type**: `application/json`
+
+**Schema**: `SecretApi`
+
+## Responses
+
+### 204
+
+API key upserted successfully.
+
+### 401
+
+Unauthorized
+
+### 404
+
+Integration not found.

package/build/dist/docs-index/05c63753-5395-4735-9fce-2bb3d683f7f5.json

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

package/build/dist/docs-index/05c63753-5395-4735-9fce-2bb3d683f7f5.txt

@@ -0,0 +1,24 @@
+# Delete a Datadog integration
+
+**DELETE** `/v1/integrations/datadog/{id}`
+
+**Operation ID**: `delete_2`
+**Summary**: Delete a Datadog integration
+Deletes an integration to connect to Datadog. This will delete the associated keys as well. No-op if already deleted.
+
+## Tags
+- Datadog Integration
+## Parameters
+
+- **id** (required) - path
+  - Type: string
+
+## Responses
+
+### 204
+
+Integration deleted successfully
+
+### 401
+
+Unauthorized

package/build/dist/docs-index/05fce0c8-23c8-4add-865c-9c98c6b63e22.json

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