@grepr/cli 1.13.0-2632478 → 1.14.3-a181b29

package/build/dist/docs-index/75fdbf84-1c38-4cde-b082-93afecd1f726.json

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

package/build/dist/docs-index/75fdbf84-1c38-4cde-b082-93afecd1f726.txt

@@ -1,34 +0,0 @@
-# Import an integration's parsed queries now
-
-**POST** `/v1/integrations/{integrationId}/parsed-queries/import`
-
-**Operation ID**: `importParsedQueries`
-**Summary**: Import an integration's parsed queries now
-Reads the integration's alert, monitor and dashboard queries from its vendor without waiting for the hourly import. One fetch is shared by every integration in the organization using the same vendor account, so this updates all of them. If an import is already under way this joins it rather than starting another. The import runs in the background; its result appears in the integration's activity log.
-
-## Tags
-- Integrations
-## Parameters
-
-- **integrationId** (required) - path
-  - Integration id
-  - Type: string
-
-## Responses
-
-### 200
-
-Import started, or already under way
-
-- **Content-Type**: `application/json` / `ParsedQueryImportStatus`
-### 401
-
-Unauthorized
-
-### 404
-
-Not Found - Integration not found.
-
-### 409
-
-Conflict - This vendor has no parsed queries to import, or the integration has no application key saved.

package/build/dist/docs-index/76372eeb-fa21-44a2-a52d-98944adf2487.json

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

package/build/dist/docs-index/76372eeb-fa21-44a2-a52d-98944adf2487.txt

@@ -1,33 +0,0 @@
-# Get integration exception impacts for a pipeline
-
-**GET** `/v1/pipelines/{pipelineId}/exceptions/integrations/{integrationId}/impacts`
-
-**Operation ID**: `getIntegrationExceptionImpacts`
-**Summary**: Get integration exception impacts for a pipeline
-Returns the per-exception impact percentages the runtime auto-sync threshold filter would compare against for this pipeline/integration pair, each with the time that estimate was measured. The pipeline's sink dataset scopes the lookup; exceptions without an estimation row are absent from the response rather than reported as zero.
-
-## Tags
-- Pipeline Exceptions
-## Parameters
-
-- **pipelineId** (required) - path
-  - Pipeline ID providing the dataset scope
-  - Type: string
-- **integrationId** (required) - path
-  - Integration whose exceptions to look up impacts for
-  - Type: string
-
-## Responses
-
-### 200
-
-Impact percentages retrieved
-
-- **Content-Type**: `application/json` / object
-### 401
-
-Unauthorized
-
-### 404
-
-Not Found - Pipeline not found.

package/build/dist/docs-index/76b6f514-6b4e-4029-b3d2-ab9dd19fbb80.json

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

package/build/dist/docs-index/76b6f514-6b4e-4029-b3d2-ab9dd19fbb80.txt

@@ -1,29 +0,0 @@
-# AgentAnalyticsDashboardSummary
-
-**Type**: `object`
-
-## Properties
-
-- name: dataQuality (optional)
-  type: `DataQuality`
-
-- name: emitters (optional)
-  type: array of `Breakdown`
-
-- name: intentToolMatrix (optional)
-  type: array of `MatrixCell`
-
-- name: intentUsage (optional)
-  type: array of `Breakdown`
-
-- name: models (optional)
-  type: array of `Breakdown`
-
-- name: topIntents (optional)
-  type: array of `Intent`
-
-- name: topTools (optional)
-  type: array of `Tool`
-
-- name: totals (optional)
-  type: `Totals`

package/build/dist/docs-index/7744aa61-4414-47d2-87c3-f18e3515461f.json

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

package/build/dist/docs-index/7744aa61-4414-47d2-87c3-f18e3515461f.txt

@@ -1,40 +0,0 @@
-# Get Datadog integration exceptions
-
-**GET** `/v1/integrations/datadog/{id}/exceptions`
-
-**Operation ID**: `getDatadogIntegrationExceptions`
-**Summary**: Get Datadog integration exceptions
-Returns a paginated list of vendor imported exceptions for the specified Datadog integration
-
-## Tags
-- Datadog Integration
-## Parameters
-
-- **id** (required) - path
-  - Integration ID
-  - Type: string
-- **pageSize** (optional) - query
-  - Page size (100-2000, default: 100)
-  - Type: integer
-- **page** (optional) - query
-  - Page number (0-based, default: 0)
-  - Type: integer
-
-## Responses
-
-### 200
-
-Successfully retrieved integration exceptions
-
-- **Content-Type**: `application/json` / `IntegrationExceptionsList`
-### 401
-
-Unauthorized
-
-### 403
-
-Access denied
-
-### 404
-
-Integration not found

package/build/dist/docs-index/77823eb8-522f-4432-86ac-0c8e1ff97345.json

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

package/build/dist/docs-index/77823eb8-522f-4432-86ac-0c8e1ff97345.txt

@@ -1,18 +0,0 @@
-# Resource
-
-Resource information describing the entity that produced the telemetry data.
-
-**Type**: `object`
-
-## Properties
-
-- name: attributes (optional)
-  type: `Variant`
-
-- name: droppedAttributesCount (optional)
-  type: integer
-  description: Number of attributes that were dropped due to limits.
-
-- name: entityRefs (optional)
-  type: array of `EntityRef`
-  description: Set of entities that participate in this Resource.

package/build/dist/docs-index/778fd9a1-7b7b-4e0e-8098-f3283ad1eda5.json

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

package/build/dist/docs-index/778fd9a1-7b7b-4e0e-8098-f3283ad1eda5.txt

@@ -1,15 +0,0 @@
-# IssueEventsPage
-
-A page of an issue's history, newest first.
-
-**Type**: `object`
-
-## Properties
-
-- name: items (optional)
-  type: array of `IssueEvent`
-  description: The entries on this page.
-
-- name: nextCursor (optional)
-  type: string
-  description: Pass back as `cursor` for the next, older page; null on the last page.

package/build/dist/docs-index/77e1112a-2bde-4aed-bef7-e4d5ccd6e0c9.json

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

package/build/dist/docs-index/77e1112a-2bde-4aed-bef7-e4d5ccd6e0c9.txt

@@ -1,16 +0,0 @@
-# Transforms
-
-Per-stage tree-shape chains applied during log processing.
-
-**Type**: `object`
-
-## Properties
-
-- name: preExceptions (optional)
-  type: `ChainNode`
-
-- name: preParser (optional)
-  type: `ChainNode`
-
-- name: preWarehouse (optional)
-  type: `ChainNode`

package/build/dist/docs-index/782db012-0a26-4e04-87f4-c0351193a110.json

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

package/build/dist/docs-index/782db012-0a26-4e04-87f4-c0351193a110.txt

@@ -1,20 +0,0 @@
-# DatadogLogCloudSource
-
-**Type**: `object`
-
-## Properties
-
-- name: filterQuery (optional)
-  type: string
-  description: The Datadog query filter to use when reading logs from Datadog. This is concatenated with the one from the integration.
-
-- name: integrationId (required)
-  type: string
-  description: The Datadog integration id.
-
-- name: name (required)
-  type: string
-
-- name: type (required)
-  type: enum: `datadog-log-cloud-source`
-  description: Pulls log events from the Datadog cloud service for processing using a specified query.

package/build/dist/docs-index/7838ea7d-722c-4fd8-998b-aa1a3e99b9a8.json

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

package/build/dist/docs-index/7838ea7d-722c-4fd8-998b-aa1a3e99b9a8.txt

@@ -1,11 +0,0 @@
-# GrokRuleErrors
-
-**Type**: `object`
-
-## Properties
-
-- name: rule (optional)
-  type: string
-
-- name: ruleErrors (optional)
-  type: array of `GrokRuleError`

package/build/dist/docs-index/783efcc1-d137-42e9-9a37-0bf2113ed01b.json

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

package/build/dist/docs-index/783efcc1-d137-42e9-9a37-0bf2113ed01b.txt

@@ -1,23 +0,0 @@
-# Invite multiple people
-
-**POST** `/v1/invitations`
-
-**Operation ID**: `invite`
-**Summary**: Invite multiple people
-## Tags
-- Invitations
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `Invitee`
-
-## Responses
-
-### 200
-
-Invitations created successfully
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/78621572-dfd8-427b-935d-a8250dcf2b77.json

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

package/build/dist/docs-index/78621572-dfd8-427b-935d-a8250dcf2b77.txt

@@ -1,30 +0,0 @@
-# Create an agent
-
-**POST** `/v1/agents`
-
-**Operation ID**: `create_2`
-**Summary**: Create an agent
-Creates an agent with the given model configuration, tools and prompt.
-
-## Tags
-- Agents
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `AgentConfigCreate`
-
-## Responses
-
-### 200
-
-Agent created successfully
-
-- **Content-Type**: `application/json` / `AgentConfig`
-### 400
-
-A referenced model or MCP integration does not exist
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/789933c4-3439-4fd5-9da5-e82b32d38f77.json

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

package/build/dist/docs-index/789933c4-3439-4fd5-9da5-e82b32d38f77.txt

@@ -1,15 +0,0 @@
-# IssueLinkRef
-
-A linked object to find issues by, such as a pipeline or an investigation.
-
-**Type**: `object`
-
-## Properties
-
-- name: kind (required)
-  type: enum: `PIPELINE`, `INVESTIGATION`, `MEMORY`, `AGENT_SUGGESTION`, `EXTERNAL`, `ISSUE`
-  description: What the object is.
-
-- name: target (required)
-  type: string
-  description: Its id, or the URL for an external link.

package/build/dist/docs-index/78a80089-0135-4a45-ae5e-0dd739666810.json

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

package/build/dist/docs-index/78a80089-0135-4a45-ae5e-0dd739666810.txt

@@ -1,25 +0,0 @@
-# TraceReducerTemplateInput
-
-Schema for the trace reducer job graph.
-
-**Type**: `object`
-
-## Properties
-
-- name: datasetId (optional)
-  type: string
-  description: The unique identifier for the dataset persisted by the trace reducer. When absent, no raw spans will be stored and no dedup sinks will be wired. At least one of `datasetId` or `sinks` must be provided for non-draft pipelines.
-
-- name: reducer (optional)
-  type: `TraceReducer`
-
-- name: sinks (optional)
-  type: array of `TemplateTraceSink`
-  description: A list of template trace sinks, each wrapping a vendor sink operation. When absent, reduced spans will not be forwarded to any vendor. At least one of `sinks` or `datasetId` must be provided for non-draft pipelines.
-
-- name: sources (required)
-  type: array of `Operation`
-  description: A list of trace sources, each conforming to one of the defined source types.
-
-- name: sqlOperations (optional)
-  type: `TraceSqlOperations`

package/build/dist/docs-index/78d17484-de82-4beb-b3ef-91a1d4e3694f.json

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

package/build/dist/docs-index/78d17484-de82-4beb-b3ef-91a1d4e3694f.txt

@@ -1,14 +0,0 @@
-# FilterPrimitive
-
-Combined metric-name + attribute-value filter.
-
-**Type**: `object`
-
-## Properties
-
-- name: attributeFilters (optional)
-  type: object
-  description: Level-prefixed attribute key → glob pattern. All entries must match.
-
-- name: metricName (optional)
-  type: `MetricNameFilter`

package/build/dist/docs-index/791f3e5f-f61b-4aed-b413-be5775631917.json

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

package/build/dist/docs-index/791f3e5f-f61b-4aed-b413-be5775631917.txt

@@ -1,10 +0,0 @@
-# TemplateTraceSink
-
-Template trace sink configuration
-
-**Type**: `object`
-
-## Properties
-
-- name: sink (optional)
-  type: `Operation`

package/build/dist/docs-index/7982acc2-8c21-4adb-b191-df57c4bc4706.json

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

package/build/dist/docs-index/7982acc2-8c21-4adb-b191-df57c4bc4706.txt

@@ -1,17 +0,0 @@
-# MessageLengthNode
-
-**Type**: `object`
-
-## Properties
-
-- name: maxLength (optional)
-  type: integer
-  description: Inclusive maximum message length in characters. Null means no upper bound.
-
-- name: minLength (optional)
-  type: integer
-  description: Inclusive minimum message length in characters. Null means no lower bound.
-
-- name: type (required)
-  type: enum: `message-length-node`
-  description: A node representing a message-length filter in a parsed query.

package/build/dist/docs-index/7a261d0a-1677-48e8-a527-2b535e78dbf8.json

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

package/build/dist/docs-index/7a261d0a-1677-48e8-a527-2b535e78dbf8.txt

@@ -1,19 +0,0 @@
-# MaskingResult
-
-The masked results, aligned by position with the request's samples.
-
-**Type**: `object`
-
-## Properties
-
-- name: maskedAttributes (required)
-  type: object
-  description: The sample attributes after masking, unchanged when no mask matched.
-
-- name: maskedCount (optional)
-  type: integer
-  description: The number of substrings replaced across the message and attributes; zero when nothing matched.
-
-- name: maskedMessage (optional)
-  type: string
-  description: The sample message after masking, unchanged when no mask matched.

package/build/dist/docs-index/7a3a611e-4c53-4595-acd2-998499b75acf.json

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

package/build/dist/docs-index/7a3a611e-4c53-4595-acd2-998499b75acf.txt

@@ -1,19 +0,0 @@
-# PreviewAppKeyScopesRequest
-
-Unsaved changes to check Datadog authorization scopes against
-
-**Type**: `object`
-
-## Properties
-
-- name: apiKey (optional)
-  type: string
-  description: API key to probe with instead of the stored one
-
-- name: appKey (optional)
-  type: string
-  description: Application key to check instead of the stored one
-
-- name: site (optional)
-  type: string
-  description: Site to probe instead of the stored one

package/build/dist/docs-index/7a676bf4-2b44-420c-9d1b-f6be6d4ed135.json

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

package/build/dist/docs-index/7a676bf4-2b44-420c-9d1b-f6be6d4ed135.txt

@@ -1,145 +0,0 @@
-Learn how to ensure specific messages are forwarded unchanged to observability platforms by configuring them as exceptions to the reducer step.
-
-# Bypass aggregation of important messages with exceptions
-
-This page describes how to use *exceptions* to specify messages that should bypass the reducer and get forwarded directly to your observability platform without summarization. Examples of why you might want to forward raw, unsummarized messages include:
-
-* You need to track activity across messages, requiring samples of all messages associated with specific identifiers.
-* You want to provide unsummarized messages for a period before and after an anomalous event occurs or in response to an external event.
-* Dashboards, alerts, or monitors in your observability platform depend on receiving full, unsummarized messages to function correctly.
-
-This page explains how to configure the different exception types in the Grepr UI. You can also use the REST API to configure exceptions. With the API, you configure exceptions as part of the [LogReducer transform](/apis/api-spec#schema/LogReducer), and then include them as vertices in the job graph defining a log pipeline.
-
-## Configure exceptions in the Grepr UI
-
-You configure exceptions on the overview page when you create or edit a pipeline. To add an exception, in the left-hand navigation menu, click **Exceptions** to open the exceptions list, click **Add**, and then select the exception type to configure. The following sections describe the different exception types and their configuration options.
-
-To write queries for exception configurations, you use the same syntaxes you use for queries in the filtering or transformation steps of your pipeline. To learn more about supported query syntaxes, see [Query log data in the Grepr data lake](/queries).
-
-To edit an existing exception, click the exception's row in the list to open the **Edit Exception** dialog. To remove an exception, click the delete icon in the exception row.
-
-## Prevent aggregation of messages used in your observability platform \[#vendor-exceptions]
-
-Some Grepr integrations, such as Datadog and New Relic, support parsing queries used by monitors, dashboards, or alerts in your observability platform. To ensure the correct functioning of your observability platform assets, Grepr can use the parsing results to configure queries that should automatically bypass reduction. You can choose to apply exceptions for any or all of the parsed queries. To configure parsed queries to use as exceptions, select **Do not aggregate logs used in existing observability alerts** to display the **Imported Queries** table. Use the links in the **Name** column to go to the alert's source in your observability vendor's UI.
-
-The **Imported Queries** table also includes the **Passthrough %** column, which is an estimate of the percentage of events over a configurable time window that would bypass aggregation. You configure passthrough estimation as part of the integration configuration. See [Identify log events that should bypass aggregation](/integrations#passthrough-estimation).
-
-You can also enable **Auto-sync exceptions** to automatically add and remove exceptions as you add and remove alerts or dashboards in your observability vendor. When you enable auto-sync and no queries are selected in the **Imported Queries** table, all queries are selected automatically as exceptions. If at least one query is already selected, that selection is retained, and you must manually select any other queries to include. In both cases, Grepr automatically adds exceptions for any new queries parsed after enabling auto-sync.
-
-When you enable auto-sync, changes such as new alerts or dashboards in your observability platform might cause an unexpectedly large increase in the log events that bypass reduction. To mitigate this risk, you can set a threshold for auto-sync exceptions. The threshold setting prevents auto-sync from adding a new exception when the estimated percentage of log events excluded from reduction for that exception exceeds the threshold. To set this threshold, enter the value in the **Max %** text box.
-
-> If you rewrite alert or dashboard queries to use summarized messages, add `processor:grepr` to the new queries so that they do not match logs that did not go through Grepr. This tag is automatically added to all log messages that Grepr sends to external vendors and never matches any raw messages. It tells Grepr that a query for an alert or dashboard has already been rewritten.
-
-## Always forward messages matching a query \[#pattern-exceptions]
-
-To ensure that certain messages always bypass the reducer and are forwarded without aggregation, for example, when processing in your observability platform has a dependency on those messages, you can define a query to identify those messages. The reducer evaluates every incoming log message and forwards every matching message unmodified. This exception type doesn't trigger a backfill or affect the aggregation of other messages.
-
-## Forward samples of full logs based on trace identifiers \[#trace-sampler-exceptions]
-
-You can ensure you have samples of full logs for events that share a trace identifier. For this exception type, a trace refers to one or more values used to group related events, and not specifically an application performance monitoring trace. For example, a trace ID could be a request ID, a user ID, or a session ID.
-
-Based on the configured trace ID for each log message, Grepr samples a configurable percentage of trace IDs and forwards every log message that belongs to a sampled trace unmodified. Use this exception type to keep a representative sample of complete, end-to-end traces in your observability backend.
-
-Grepr uses the trace samplers in the order they are specified. After a message matches for trace sampling, it is not evaluated against any remaining trace samplers.
-
-Configure the following settings:
-
-* An optional query that scopes the sampling to messages that match the query. Only messages that match the query participate in trace sampling. Leave the query empty to apply sampling to all messages that pass through the reducer.
-* Attribute paths or tag keys to use as trace identifiers. To add the paths or keys, click the plus (+) icons. To enter attribute paths, use dot notation, such as `trace.id`, or a JSON array, such as `["trace", "id"]`. Use a JSON array if any segment of the path contains a literal dot. To remove a path or key, click the delete icon next to the entry.
-* A sample percentage of distinct trace IDs to sample, from 0 to 100. You can specify up to two decimal places, such as `1.50`. Grepr forwards every log message whose trace ID falls within the sampled percentage. The default is `1.00`.
-
-> You must specify at least one **Trace ID Attribute Path** or **Trace ID Tag Key**. The form does not allow you to save the exception when both lists are empty.
-
-## Pause aggregation and backfill logs for events matching a query \[#dynamic-exceptions]
-
-You can create an exception that automatically pauses aggregation of specific messages and optionally forwards full messages for a configured period when incoming events match a query. Use this exception type to forward full logs when specific events occur, such as production incidents or other anomalous events. For example, you can configure the query `status:error` to ensure you have full logs if an event arrives from a host with an error status.
-
-In addition to the query that triggers this exception, you also configure:
-
-* An optional list of attribute paths or tag keys that scope the backfill and the paused aggregation to the values found in the triggering message. For example, if you add `service`, only messages with the same `service` value as the triggering message are backfilled and excluded from aggregation.
-* The duration of historical data to backfill from the data lake when the exception is triggered. You can also choose to skip the backfill step and only pause aggregation.
-* The duration to pause aggregation of matching messages after the exception is triggered. You can also choose to continue aggregating matching messages and only run the backfill.
-
-## Pause aggregation and backfill logs in response to an external event \[#callback-exceptions]
-
-In addition to triggering exceptions based on incoming log messages, you can configure exceptions to be triggered by external events. This exception type is activated when an external system, such as an observability monitor or alert, calls the [External Triggers endpoint](/apis/api-spec#tag/External-Triggers).
-
-Configure the following settings:
-
-* An optional list of attribute paths or tag keys that scope the backfill and the paused aggregation to the values passed in the call to the external triggers endpoint. To add an attribute, type `@` and then select from the suggested values.
-* The duration of historical data to backfill from the data lake when the exception is triggered. You can also choose to skip the backfill step and only pause aggregation.
-* The duration to pause aggregation of matching messages after the exception is triggered. You can also choose to continue aggregating matching messages and only run the backfill.
-
-The attributes and keys you define are included as key-value pairs in the `variables` object in the body of the request to the external triggers endpoint. After you save the exception, click the terminal icon in the exception's **Actions** column to display a sample `curl` command to call the external triggers endpoint for that exception. After updating the placeholders for values in the `variables` object, you can use this command for testing and as a reference when configuring calls to the trigger from an external system.
-
-## Rewrite queries \[#rewrite-queries]
-
-When you first deploy Grepr's log reduction, you typically add exceptions for all existing alerts and dashboards to minimize disruptions to existing workflows. However, over time, you might find that some of these alerts and dashboards use queries that count the occurrence of a pattern that appears with high frequency. For example, you might have a dashboard that uses a count of HTTP requests with the status code 200. Because 200 is the standard success status code, most HTTP log messages include it. Adding an exception for this dashboard results in forwarding a large number of events that would normally be aggregated.
-
-To address this, you can rewrite the query to use the [grepr.repeatCount](/transforms/reducer#summary-metadata) attribute. This attribute appears in both summary and sample messages, enabling the derivation of metrics. See your vendor's documentation for specifics on creating a metric from a log attribute.
-
-## Frequently Asked Questions
-
-### What is an exception in a Grepr pipeline?
-
-An exception is a rule that you configure on a pipeline to identify log messages that should bypass aggregation by the reducer. Messages that match an exception are forwarded to your sinks unmodified. Some exception types also trigger a backfill from the data lake and temporarily pause aggregation for related messages.
-
-### What types of exceptions can I configure?
-
-You can configure five types of exceptions: a pattern exception that always forwards messages matching a query, a query trigger exception that backfills and pauses aggregation when a query matches, an integration exception that excludes queries used by alerts in your observability tool, a trace sampler exception that forwards a representative sample of full traces, and an external trigger exception that backfills and pauses aggregation in response to a call to the Grepr External Triggers API.
-
-### How do I add an exception to a pipeline?
-
-Open the pipeline in the Grepr UI, click Exceptions in the left-hand navigation menu, and click the add button. In the Add Exception dialog, select the type of exception, complete the configuration fields, and click Add.
-
-### What query languages can I use in an exception?
-
-You write exception queries using the same query syntaxes available for the filtering and transformation steps in your pipeline. Queries are used on pattern exceptions, query trigger exceptions, and as the optional scoping query on trace sampler exceptions.
-
-### What are scoping keys on an exception?
-
-Scoping keys are the attribute paths and tag keys you configure on a query trigger exception or external trigger exception. They limit the backfill and the paused aggregation to messages whose values for those keys match the values from the triggering event.
-
-### What does Auto-sync exceptions do on an integration exception?
-
-When Auto-sync exceptions is enabled, Grepr automatically adds new queries discovered in the integration as exceptions, instead of using only the queries you initially selected. You can clear specific queries to exclude them from auto-sync, and you can use the Max % field to prevent any single exception from excluding more than a specified percentage of incoming logs.
-
-### How do I prevent an auto-synced exception from forwarding too many logs?
-
-On an integration exception with Auto-sync exceptions enabled, set the Max % field to the maximum percentage of incoming logs that any single exception is allowed to exclude from reduction. If the estimated percentage of logs excluded by an auto-synced exception exceeds this threshold, Grepr does not activate the exception.
-
-### How does trace sampling work in Grepr?
-
-Based on the configured trace ID for each log message, Grepr samples a configurable percentage of trace IDs and forwards every log message that belongs to a sampled trace unmodified. The trace ID does not have to be an APM trace; anything that groups logs together, such as a request ID, user ID, or session ID, can be used.
-
-### What's the difference between Trace ID Attribute Paths and Trace ID Tag Keys on a trace sampler exception?
-
-Trace ID Attribute Paths are paths inside the structured attributes of a log message that contain the trace ID, expressed in dot notation or as a JSON array. Trace ID Tag Keys are top-level tag keys that contain the trace ID. You must specify at least one path or one tag key.
-
-### How does the Sample Percentage on a trace sampler exception work?
-
-The Sample Percentage is the percentage of distinct trace IDs that Grepr samples. Grepr forwards every log message that belongs to a sampled trace, so a sample percentage of 1% forwards complete logs for approximately 1% of the traces seen by the reducer.
-
-### In what order does Grepr apply trace samplers?
-
-Grepr applies trace samplers in the order they are listed. After a message matches a trace sampler, Grepr does not evaluate it against any of the remaining trace samplers.
-
-### Can Grepr import exceptions from my observability platform's monitors and dashboards?
-
-Yes. Some Grepr integrations, such as the Datadog and New Relic integrations, parse the queries used by your monitors, dashboards, and alerts and suggest them as exceptions you can apply. Each suggested exception includes a link back to the source of the alert in your observability vendor's UI.
-
-### How does an external trigger exception get activated?
-
-An external trigger exception is activated by a call to the Grepr External Triggers API. After you save the exception, the row for the exception in the Exceptions list provides a sample curl command that you can use to call the API. Scoping keys configured on the exception take their values from the API call.
-
-### How does the query trigger exception work?
-
-A query trigger exception activates when an incoming log message matches the configured query. When it activates, Grepr backfills matching messages from the data lake for a configured duration and pauses aggregation of matching messages for a configured duration. You can also choose to skip the backfill and only pause aggregation, or to keep aggregating and only run the backfill. You can use scoping keys to limit the backfill and paused aggregation to messages that share the triggering message's values.
-
-### Why might I need to rewrite alert or dashboard queries after adding exceptions?
-
-When you first deploy log reduction, you typically add exceptions for existing alerts and dashboards to minimize disruption. Some of those alerts and dashboards are powered by counts of high-volume events, such as HTTP requests with status 200, which limits how much volume the reducer can reduce. Rewriting those queries lets the reducer aggregate the underlying messages while keeping the dashboards accurate.
-
-### Can I rewrite my dashboards to use reduced logs?
-
-Yes, you can rewrite dashboard and alert queries to use grepr.repeatCount for accurate metrics on aggregated data. Add the processor:grepr tag to queries to ensure they only match processed logs, enabling cost-effective metrics on sampled data.

package/build/dist/docs-index/7b2ad36f-761c-4b57-a940-fb892eeb30d9.json

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