@grepr/cli 1.11.5-1e100fc → 1.11.5-23cef4b

package/build/dist/docs-index/0a335c0d-2f3c-4c8c-ad48-d833f08f44a9.txt

@@ -1,47 +0,0 @@
-# Datadog
-
-The payload containing integration data.
-
-**Type**: `object`
-
-## Properties
-
-- name: additionalTags (required)
-  type: array of string
-  description: Tags to add when writing data to Datadog
-
-- name: apiKey (optional)
-  type: string
-  description: Masked API key for Datadog
-
-- name: apiKeys (optional)
-  type: array of `IngestKeyView`
-  description: The API keys configured for this integration (masked).
-
-- name: appKey (optional)
-  type: string
-  description: Masked App key for Datadog
-
-- name: clientToken (optional)
-  type: string
-  description: Client token for Datadog
-
-- name: exceptions (optional)
-  type: object
-  description: The imported exceptions from Datadog. This is a map from the vendor resource Id to the exception.
-
-- name: filterQuery (required)
-  type: string
-  description: Filter to apply when reading any data from the Datadog API
-
-- name: sendKeyId (optional)
-  type: string
-  description: Identifier of the API key used to send data back to Datadog. Defaults to the only key when unset.
-
-- name: site (required)
-  type: string
-  description: Datadog site URL
-
-- name: validateKeysOnSave (optional)
-  type: boolean
-  description: Indicates whether to validate the API and App keys when saving the keys.

package/build/dist/docs-index/0abbc9a3-0977-4a26-918a-f6baaf64b9fb.txt

@@ -1,143 +0,0 @@
-A reference for the permission types in the Grepr platform, and which permissions are assigned to different roles.
-
-# Permissions in the Grepr platform
-
-This page is a reference to the permissions available in the Grepr platform. These permissions are assigned to users based on the user's role:
-
-* Organization-level roles: Admin, Member, and Reader
-* Team-level roles: Leader and Member
-
-A user can be assigned both an organization-level role and a team-level role. For example, an organization Member can also be a team Leader, giving them view access organization-wide and edit access to their team's resources.
-
-You can also create custom roles with a specific subset of Grepr platform permissions. To learn more about roles, including custom roles, see [Manage users in the Grepr platform](/admin/manage-users).
-
-At both the organization and team levels, there are three types of permissions:
-
-* View: Grants read-only access to specified resources.
-* Edit: Grants edit permissions over specified resources, including creating, editing, and deleting those resources.
-* Write: Grants permission to send data through an integration when the integration is used as a sink in a job, such as a backfill job that writes data to a vendor integration. Edit permission on an integration controls the integration's configuration. Write permission on an integration controls whether you can send data through it.
-
-Resources in the Grepr platform include your organization, vendor, and storage integrations, datasets, templates, users, teams, and jobs.
-
-The following sections provide more details on permissions in the Grepr platform and the permissions for each role type.
-
-## Available permissions in the Grepr platform
-
-This table lists all available permissions for organization and team-level roles:
-
-| Permission | Resource | Scope |
-| --- | --- | --- |
-| Edit | Organization settings | Organization |
-| View | Organization settings | Organization or Team |
-| Edit | Integrations | Organization or Team |
-| View | Integrations | Organization or Team |
-| Write | Integrations | Organization or Team |
-| Edit | Jobs | Organization or Team |
-| View | Jobs | Organization or Team |
-| Edit | Users | Organization |
-| View | Users | Organization or Team |
-| Edit | Teams | Organization or Team |
-| View | Teams | Organization or Team |
-| Edit | Templates | Organization or Team |
-| View | Templates | Organization or Team |
-| Edit | Datasets | Organization or Team |
-| View | Datasets | Organization or Team |
-
-## Permissions by role
-
-The following are the permissions granted to each role type in the Grepr platform:
-
-* Organization Admins have full control over all resources in the organization, including all team-scoped resources, and can write to any vendor integration.
-* Organization Members have view-only permissions to all resources in the organization, and have write permission on all vendor integrations so they can run backfill jobs.
-* Organization Readers have view-only permissions to all resources in the organization. Readers can query logs, but cannot create or edit any resources and cannot run backfill jobs that send data to a vendor integration.
-* Team Leaders have edit permissions for all resources scoped to their specific team or teams. This includes permissions to create and edit jobs, integrations, templates, and datasets assigned to the team, and to write to integrations assigned to the team. Team Leaders can also view all organization resources but only edit resources scoped to their team or teams.
-* Team Members have view-only permissions to resources scoped to their specific team or teams, plus write permission on integrations assigned to the team so they can run backfill jobs. A team Member can view resources assigned to the team and query logs, but does not have permission to create or edit resources, such as jobs, integrations, templates, or datasets, assigned to the team.
-* Teams can be granted access to resources, such as integrations, datasets, or templates, scoped at the organization level. When a team is granted access to a resource, team Leaders have edit permissions on the resource, and team Members have view-only permissions. However, to create or edit a job, such as a pipeline, a team Leader must have view permissions on all the integrations and datasets used by the job, and write permission on every vendor integration the job uses as a sink. For example, if a job is assigned to the `DevOps` team, but the team hasn't been granted access to an integration used in the job, a `DevOps` team Leader cannot edit or run the job.
-* To create a dataset, you must have edit permission on the integration the dataset belongs to.
-
-For each resource in the Grepr platform, this table shows the specific permissions granted to each role type at both the organization and team levels:
-
-| Permission | Resource | Access Scope | Organization Admin | Organization Member | Organization Reader | Team Leader | Team Member |
-| --- | --- | --- | --- | --- | --- | --- | --- |
-| View | Organization Settings | Organization | ✅ | ✅ | ✅ | ✅ | ✅ |
-| Edit | Organization Settings | Organization | ✅ | ❌ | ❌ | ❌ | ❌ |
-| View | Users | Organization | ✅ | ✅ | ✅ | ✅ | ❌ |
-| Edit | Users | Organization | ✅ | ❌ | ❌ | ❌ | ❌ |
-| View | Teams | Organization | ✅ | ✅ | ✅ | ✅ | ❌ |
-| Edit | Teams | Organization | ✅ | ❌ | ❌ | ❌ | ❌ |
-| View | Integrations | Organization | ✅ | ✅ | ✅ | ❌ | ❌ |
-| Edit | Integrations | Organization | ✅ | ❌ | ❌ | ❌ | ❌ |
-| Write | Integrations | Organization | ✅ | ✅ | ❌ | ❌ | ❌ |
-| View | Datasets | Organization | ✅ | ✅ | ✅ | ❌ | ❌ |
-| Edit | Datasets | Organization | ✅ | ❌ | ❌ | ❌ | ❌ |
-| View | Jobs | Organization | ✅ | ✅ | ✅ | ❌ | ❌ |
-| Edit | Jobs | Organization | ✅ | ❌ | ❌ | ❌ | ❌ |
-| View | Templates | Organization | ✅ | ✅ | ✅ | ✅ | ❌ |
-| Edit | Templates | Organization | ✅ | ❌ | ❌ | ❌ | ❌ |
-| View | Teams | Team | ✅ | ✅ | ✅ | ✅ | ✅ |
-| Edit | Teams | Team | ✅ | ❌ | ❌ | ✅ | ❌ |
-| View | Integrations | Team | ✅ | ✅ | ✅ | ✅ | ✅ |
-| Edit | Integrations | Team | ✅ | ❌ | ❌ | ✅ | ❌ |
-| Write | Integrations | Team | ✅ | ✅ | ❌ | ✅ | ✅ |
-| View | Datasets | Team | ✅ | ✅ | ✅ | ✅ | ✅ |
-| Edit | Datasets | Team | ✅ | ❌ | ❌ | ✅ | ❌ |
-| View | Jobs | Team | ✅ | ✅ | ✅ | ✅ | ✅ |
-| Edit | Jobs | Team | ✅ | ❌ | ❌ | ✅ | ❌ |
-| View | Templates | Team | ✅ | ✅ | ✅ | ✅ | ✅ |
-| Edit | Templates | Team | ✅ | ❌ | ❌ | ✅ | ❌ |
-
-## Organization roles vs. team roles
-
-This table describes the difference between organization-level and team-level roles. Users can have both types of roles:
-
-\| | Organization roles | Team roles | | :-------- | :----------------------------------------------------- | :------------------------------------------ | | Scope | Entire organization | A specific team | | Types | Admin, Member, Reader, or Custom Roles | Leader or Member | | Examples | - Admin: Full access to all resources and settings.\
-\- Member: View organization resources and run backfill jobs.\
-\- Reader: View organization resources and query logs only; no backfills to vendor integrations.\
-\- Custom role, such as "Developer": Specific permissions like "view all jobs, edit templates". | - Leader: Manage team members, create team-scoped integrations.\
-\- Member: View team resources and run backfill jobs to team integrations. |
-
-## Frequently Asked Questions
-
-### What are the main permission types in Grepr?
-
-The main permission types are View (grants read-only access to specified resources), Edit (grants permissions to create, edit, and delete specified resources), and Write (grants permission to send data through an integration when the integration is used as a sink in a job, such as a backfill). These permissions are assigned based on user roles at both organization and team levels.
-
-### What are organization-level roles?
-
-Organization-level roles control access across the entire organization. The standard roles are Admin (full control over all resources), Member (view access plus permission to run backfill jobs), and Reader (view-only access; no backfills to vendor integrations). You can also create custom roles with specific subsets of permissions tailored to your organization's needs.
-
-### What are team-level roles?
-
-Team-level roles control access to resources within a specific team. There are two team roles: Leader (edit permissions for team-scoped resources and view permissions for organization resources) and Member (view-only permissions for team resources). A user can be assigned to multiple teams with different roles.
-
-### Can a user have both organization and team roles?
-
-Yes, users can have both organization-level and team-level roles simultaneously. For example, a user can be an organization Member for organization-wide access while also being a Team Leader for a specific team, granting them edit access to that team's resources.
-
-### What resources can be controlled with Grepr permissions?
-
-Grepr permissions can control access to: organization settings, integrations (observability and storage), jobs, users, teams, templates, and datasets. Each resource can have view or edit permissions assigned at organization or team scope.
-
-### What permissions does an Organization Admin have?
-
-Organization Admins have full control over all resources in the organization, including all team-scoped resources. They can create, edit, and delete any resource, manage users, configure organization settings, and manage all integrations and datasets.
-
-### What permissions does an Organization Member have?
-
-Organization Members have view permissions to all resources in the organization, plus write permission on integrations so they can run backfill jobs. They can view integrations, datasets, jobs, users, and teams and write data through any vendor integration, but cannot create, edit, or delete any resources at the organization level.
-
-### What permissions does an Organization Reader have?
-
-Organization Readers have view-only permissions to all resources in the organization and can query logs. Readers cannot create, edit, or delete any resources, and cannot run backfill jobs that send data to a vendor integration. Use the Reader role for users who need to investigate data without incurring vendor write costs.
-
-### What permissions does a Team Leader have?
-
-Team Leaders have edit permissions for all resources scoped to their specific team(s), including creating and editing jobs, integrations, templates, and datasets. They can also view all organization resources but can only edit resources scoped to their team. Team Leaders can also manage team members.
-
-### What permissions does a Team Member have?
-
-Team Members have view permissions to resources scoped to their team, plus write permission on integrations assigned to the team so they can run backfill jobs. They can view jobs, integrations, templates, and datasets assigned to the team, query logs, and run backfills to team integrations, but cannot create or edit any resources.
-
-### What is a custom role in Grepr?
-
-Custom roles allow you to create roles with a specific subset of Grepr platform permissions tailored to your organization's needs. Instead of using standard roles, you can create custom roles like 'Developer' with permissions such as 'view all jobs' and 'edit templates' to match your team's responsibilities and access requirements.

package/build/dist/docs-index/20dd25d1-784b-45a7-a614-00cb1b82e6e5.txt

@@ -1,17 +0,0 @@
-# CreateVendorEstimationRunRequest
-
-**Type**: `object`
-
-## Properties
-
-- name: scopeQuery (optional)
-  type: string
-  description: Vendor query limiting the estimate to part of the customer's traffic. Applied to both the matched count and the total. Leave empty for all logs.
-
-- name: windowEnd (required)
-  type: string
-  description: Absolute end of the window to count over; must be after the start
-
-- name: windowStart (required)
-  type: string
-  description: Absolute start of the window to count over

package/build/dist/docs-index/29f58821-4c61-4ae0-a7d5-08d49e4f013c.txt

@@ -1,44 +0,0 @@
-# Start a vendor estimation run
-
-**POST** `/v1/integrations/{integrationId}/exceptions/vendor-estimation-runs`
-
-**Operation ID**: `createVendorEstimationRun`
-**Summary**: Start a vendor estimation run
-Creates a run over the given scope and window covering every exception the integration has imported, with one result row per distinct predicate, and queues its first slice. One non-terminal run per organization: starting a second returns 409 while the first is still in flight.
-
-## Tags
-- Integration Exceptions
-## Parameters
-
-- **integrationId** (required) - path
-  - Integration id
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `CreateVendorEstimationRunRequest`
-
-## Responses
-
-### 201
-
-Run created
-
-- **Content-Type**: `application/json` / `VendorEstimationRun`
-### 400
-
-Bad Request - Window is inverted or scope is invalid.
-
-### 401
-
-Unauthorized
-
-### 404
-
-Not Found - Integration not found.
-
-### 409
-
-Conflict - The organization already has a run that has not finished.

package/build/dist/docs-index/3a532df9-14cd-469a-b255-e984dac52e9b.txt

@@ -1,21 +0,0 @@
-# VendorEstimationRunPreview
-
-**Type**: `object`
-
-## Properties
-
-- name: distinctQueries (required)
-  type: integer
-  description: Distinct countable predicates among those exceptions, and so the number of vendor calls the run would make. Smaller than the exception count wherever several exceptions carry the same query.
-
-- name: exceptions (required)
-  type: integer
-  description: Exceptions the run would cover: every one the integration has imported
-
-- name: queuedAhead (optional)
-  type: integer
-  description: Runs that would start before this one if it were created now. Absent when a slot is free.
-
-- name: unparseable (required)
-  type: array of `UnparseableException`
-  description: Exceptions whose query could not be parsed at import and so cannot be counted, each with the parse error

package/build/dist/docs-index/3a707b85-8679-4d92-8000-8441ff19d901.txt

@@ -1,244 +0,0 @@
-Configure the Grepr log reducer to reduce the volume of logs forwarded to your observability vendor while preserving access to your raw logs.
-
-# Configure the log reducer in a Grepr pipeline
-
-This page describes the transformations the log reducer applies to incoming log messages and how to configure them to meet your requirements. When you create log reduction pipelines, Grepr adds a log reducer with default settings that control how log messages are aggregated, grouped, tokenized, and summarized. These settings are suitable for many log-processing workloads, but you can modify these settings to meet your requirements through the Grepr UI, the REST API, or the Grepr CLI. This page describes each setting and how to configure the setting in the UI. For the API documentation, see the [LogReducer API specification](/apis/api-spec#schema/LogReducer). For the CLI, see [The Grepr CLI](/cli).
-
-The log reducer transforms logs into summarized events through a multi-step process. The reducer divides the incoming log stream into consecutive *aggregation windows* and produces summaries for each window separately. An aggregation window is a fixed-duration, tumbling window over which the reducer counts and aggregates the messages that match each pattern. Tumbling windows are contiguous and non-overlapping, so each log belongs to exactly one window. The aggregation window is two minutes by default.
-
-> To change the aggregation window duration, you must use the Grepr REST API. You cannot use the Grepr UI to change the window duration. Before changing this value, Grepr recommends contacting <support@grepr.ai> for guidance.
-
-The following describes the core steps in this process and includes links with details on changing the default behavior for each step:
-
-* Masking replaces dynamic values such as timestamps, IDs, and IP addresses with specific tokens. By normalizing values that represent the same entity but might differ slightly in format or content, masking prevents them from being split incorrectly in the next step. See [Enable grouping of dynamic fields by assigning common tokens](#mask-configuration).
-* Tokenizing breaks log messages into tokens based on configurable delimiters, creating a structured representation optimized for grouping. See [Configure delimiters used to split log messages](#delimiter-configuration).
-* Grouping uses similarity metrics to group messages into patterns. A configurable similarity threshold determines how closely messages must match to be considered part of the same pattern. You can use grouping to retain the values of important fields by excluding them from aggregation. See [Configure how messages are grouped](#grouping-configuration).
-* Sampling sends a configurable number of raw sample messages per pattern. This number is referred to as the *deduplication threshold* throughout this documentation. After this threshold is reached, you can configure the reducer to stop forwarding that pattern until the end of the aggregation window, or use logarithmic sampling. See [Configure a sampling strategy](#sampling-configuration).
-* Summarizing generates, at the end of each aggregation window, concise summaries of aggregated messages that matched an identified pattern. For details on the fields included in the summarized output events, see [Summary message metadata](/transforms/reducer#summary-metadata).
-
-To modify the configuration settings in the UI, on the overview page for your pipeline, click **Reducer** in the left-hand navigation menu to open the **Edit Reducer** dialog. The dialog contains a form to configure **Grouping Configuration**, **Aggregation Configuration**, **Sampling Configuration**, **Mask Configuration**, **Delimiter Configuration**, and **Attribute Configuration** values. The following sections describe these settings.
-
-## Configure how messages are grouped \[#grouping-configuration]
-
-Grouping controls how incoming messages are partitioned into independent groups before pattern detection, and the level of similarity messages must meet to be considered part of the same pattern.
-
-### Group messages by a field \[#group-by-configuration]
-
-Messages are aggregated separately for each unique combination of values across the fields you group on, so patterns from different services, hosts, or other dimensions are never merged. Grouping on `service`, `host`, and the `http.url.path` attribute aggregates messages independently for each unique combination of those three values.
-
-To group on a field, on the pipeline's **Reducer** step, click **Edit** on the **Fields** card, find the field, and set its behavior to **Match or split**. A field with this behavior is kept out of aggregation, so messages whose values for it differ are never merged into one pattern.
-
-Attribute paths are written with an `@` prefix and dot notation for nested attributes, such as `@http.url.path`. Tag keys are written as the key name alone.
-
-Use grouping to retain the values of important fields by excluding them from aggregation, such as high-cardinality identifiers like user IDs. To keep a field that is currently inside the message, parse it into an attribute or a tag with the **JSON Parser** or **Grok Parser** step earlier in the pipeline, then group on that field. See [Transform JSON strings into JSON objects](/transforms/json-parsing) and [Parse log messages to enrich log events with the Grok parser](/transforms/grok).
-
-Grouping also decides how a summary can be routed, because a summary carries the tag values of the fields it was grouped on. To use grouping to send each group's logs to a different destination, see [_](/solution-guides/route-logs-to-several-accounts).
-
-### Similarity threshold (%)
-
-The similarity threshold controls how close a set of tokens must be to an existing pattern for the reducer to consider the message a match for that pattern. To set this threshold, enter a whole number from 20 to 100. This value represents the percentage of tokens that must match between the incoming message and the pattern.
-
-* A higher value requires a closer match to group messages into the same pattern. Higher values produce more distinct patterns, each containing fewer of the tokens defined by [regular expression masks](#mask-configuration), and reduce volume less aggressively.
-* A lower value allows grouping messages with more variation into the same pattern. Lower values lead to greater reduction, but the resulting summary messages contain more mask-defined tokens.
-
-## Configure how messages are aggregated \[#aggregation-configuration]
-
-The **Aggregation Configuration** section controls how many raw messages are forwarded before aggregation begins for a pattern and how summary messages are formatted.
-
-### Minimum number of samples
-
-To set a *deduplication threshold* for messages, in the **Minimum number of samples** field, enter a whole number of two or greater. This value is the minimum count of messages matching a pattern that the reducer forwards as raw messages inside a single aggregation window before it begins aggregating additional matches into a summary message. Until this threshold is reached, unaggregated messages are forwarded to your sinks.
-
-Use a lower value to begin aggregation sooner and maximize volume reduction. Use a higher value when a pattern has a higher threshold for the number of duplicate messages to forward before beginning aggregation.
-
-### Add repeat count prefix to summary messages
-
-To have the reducer prepend a prefix to each summary message that indicates the number of raw messages aggregated and the duration of the aggregation period, select **Add repeat count prefix to summary messages**.
-
-Clear **Add repeat count prefix to summary messages** if your downstream system needs to parse the summary message body without changes. For example, if summary messages use JSON formatting, the leading prefix would cause a syntax error.
-
-## Configure a sampling strategy \[#sampling-configuration]
-
-The **Sampling Configuration** section controls whether and how additional raw messages are forwarded for a pattern after the minimum number of samples is reached in the current aggregation window. To configure the sampling strategy for a reducer, in the **Sampling strategy** menu, select one of the following options:
-
-### No Additional Sampling
-
-During each aggregation window, Grepr passes through a configurable number of sample messages for each pattern before beginning aggregation. After the deduplication threshold is reached for a specific pattern, Grepr stops sending messages for that pattern until the end of the aggregation window, at which point a summary is emitted. This ensures that a minimum number of raw messages always pass through unmodified. Low-frequency messages that usually contain important troubleshooting information pass through unmodified.
-
-While this default behavior maximizes reduction, the actual count of messages seen at the vendor is independent of the number of original raw messages. Instead, the count is based on the messages summarized in each aggregation window. Features in external log aggregators that depend on message counts by pattern, such as Datadog's "top patterns" capability, might not work as expected. To address this, select the following logarithmic sampling option.
-
-### Window-Based Logarithmic
-
-With logarithmic sampling, high-volume patterns that occur in the aggregation window are sampled more heavily than low-volume patterns.
-
-When you select this option, to configure the rate of additional sampling, enter a whole number of two or greater in the **Logarithm Base** field. The reducer process uses this base value to increase the sample size logarithmically. For example, if the base is set to two and the deduplication threshold is set to four, Grepr sends one additional sample message when the number of messages in the aggregation window first exceeds two raised to the power of the deduplication threshold + 1 (`2^5 or 32`). Additional samples are then sent at the 64th, 128th, 256th, and subsequent messages. This ensures that an unexpectedly large increase in messages matching a pattern still appears as an increase in message count at the vendor, but with a logarithmically smaller magnitude.
-
-## Enable grouping of dynamic fields by assigning common tokens \[#mask-configuration]
-
-The **Mask Configuration** section defines the regular expression masks that the reducer uses to replace variable parts of a log message, such as timestamps, IDs, or IP addresses, with specific tokens before the message is tokenized and grouped. Masking normalizes variable content so that messages that differ only in these values are grouped into the same pattern.
-
-The reducer ships with the following default masks. Each appears as a row in the **Mask Configuration** section and can be enabled, disabled, edited, or reset to its original pattern:
-
-| Mask | Default state | Description |
-| --- | --- | --- |
-| `timestamp` | Enabled | Matches many timestamp formats, such as `2024-04-26T15:30:45.123Z`, `26/04/2024 15:30:45`, or `15:30:45`. |
-| `ipport` | Enabled | Matches IPv4 addresses and optional ports, such as `192.168.0.1` or `192.168.0.1:8080`. |
-| `number` | Enabled | Matches integers and decimal numbers up to 100 digits. |
-| `uuid` | Enabled | Matches UUIDs, such as `123e4567-e89b-12d3-a456-426614174000`. |
-| `awsarn` | Disabled | Matches AWS ARNs. |
-| `awstoken` | Disabled | Matches AWS session tokens. |
-
-For each mask row, you can:
-
-* Select or clear the checkbox on the left to enable or disable the mask. Only enabled masks are applied to incoming messages.
-* Click **Edit** to display the regular expression for the mask and modify the pattern. The pattern field cannot be empty.
-* For default masks, click the restore icon to reset the pattern to its original value.
-* For custom masks, click the delete icon to remove the mask.
-
-### Enable grouping of non-default formats by assigning custom tokens
-
-To ensure the correct grouping of fields with formats that aren't handled by the default masks, you can create custom masks. For example, you might have a field with values that include delimiter characters, and you need to prevent the reducer from splitting the single field on those delimiters.
-
-When you add a custom mask, you must enter a name for the mask that:
-
-* Contains only lowercase alphabetic characters. Spaces, digits, and symbols are not allowed.
-* Is no more than 50 characters long.
-* Is unique across all masks in this reducer.
-
-Enter the mask in the **Regular Expression Pattern** text box. A custom mask pattern supports the following common regular expression constructs:
-
-* Literal characters and character classes, such as `[a-z]`, along with predefined classes such as `\d`, `\w`, and `\s`.
-* Quantifiers, such as `*`, `+`, `?`, and `{n,m}`.
-* Alternation with `|` and grouping with `(` and `)`.
-* Anchors and word boundaries, such as `^`, `$`, and `\b`.
-
-> Custom mask patterns do not support lookahead or lookbehind assertions or backreferences. A pattern that uses one of these constructs passes the validation in the form but prevents the reducer from processing messages. To confirm that a custom mask matches the values you expect, test the pattern against sample messages.
-
-## Configure delimiters used to split log messages \[#delimiter-configuration]
-
-The **Delimiter Configuration** section defines the characters that the reducer uses to split a log message into tokens during clustering. After masking, the reducer splits each message into tokens using these characters and then calculates similarity against known patterns. Characters that are not in the delimiter list are treated as part of a token.
-
-The default delimiter set contains common punctuation and whitespace characters: `:`, `#`, `[`, `]`, `(`, `)`, `{`, `}`, `|`, `,`, `;`, `"`, `'`, space, `\t`, `\n`, and `\r`.
-
-> The default set intentionally omits `@` and `.` so that email addresses and dotted identifiers, such as fully qualified class names, are not split across tokens.
-
-To modify the delimiter list:
-
-* To remove a delimiter, hover over its chip in the delimiter list and click the delete icon that appears.
-* To add a delimiter, enter the character in the **Add delimiter** field and click **Add** or press **Enter**. For control characters, enter the escape sequence: `\t` for tab, `\n` for newline, `\r` for carriage return, `\b` for backspace, `\f` for form feed, `\v` for vertical tab, or `\0` for null. Duplicate delimiters are rejected.
-* To restore the default delimiter set, click **Reset to Defaults**.
-
-## Configure how attributes are merged \[#attribute-configuration]
-
-To group log messages, the log reducer uses only the text in the `message` field. However, because of the possible variability of the attribute values associated with the grouped messages, the reducer provides multiple strategies to merge them.
-
-To control how the reducer combines attributes, you use the **Attribute Configuration** section to specify merge strategies for individual attribute paths and configure a default strategy that applies to any attribute path without an explicit configuration.
-
-The reducer supports the following merge strategy types:
-
-| Strategy | Behavior |
-| --- | --- |
-| **Exact Match** | If all aggregated messages have the same value for the attribute, the summary preserves that value. If they differ, the summary stores a wildcard, `*`. |
-| **Sample** | Collects up to a configured **Sample Limit** of values from the aggregated messages. When the limit is reached, additional values are dropped. |
-| **Preserve All** | Collects every distinct or repeated value from the aggregated messages, up to a configured **Preserve Limit**. When the incoming data exceeds the limit, the reducer emits the current summary and starts a new one, rather than dropping values. |
-| **Sum** | Sums numeric values across aggregated messages and stores the result as a scalar number. Non-numeric values are ignored. Collections of numbers are summed element by element. |
-| **Min** | Keeps the minimum numeric value across aggregated messages. Non-numeric values are ignored. |
-| **Max** | Keeps the maximum numeric value across aggregated messages. Non-numeric values are ignored. |
-| **Average** | Computes the arithmetic mean of numeric values across aggregated messages. Non-numeric values are ignored. |
-
-To see examples and learn more about the merge strategies, see [Merge strategy examples](/transforms/reducer/configuration/merge-strategy-examples).
-
-### Configure merge strategies
-
-To add a merge strategy, in the **Attribute merging strategies** section, click the plus (+) icon. Select a strategy from the **Strategy** menu and enter the target attribute path. If any part of the target path uses dot notation, enter the target path using dot notation, such as `http.response.bytes`, or a JSON array, such as `["http", "response", "bytes"]`. Each entry must have a non-empty path, and each path must be unique within the list.
-
-When you select **Sample** or **Preserve All**, you can configure the following settings:
-
-* **Sample Limit** or **Preserve Limit**: A whole number that's one or greater. These values cap the size of the collected values. **Sample** defaults to 10 and **Preserve All** defaults to 1000.
-* **Keep unique values only**: When selected, the reducer stores the collected values as a set and discards duplicates. When cleared, the reducer stores the values as a list and preserves duplicates.
-
-When you configure more than one strategy for the same attribute path, the reducer writes a separate attribute in the summary for each strategy, using a suffix such as `_sum`, `_avg`, or `_min`. The first strategy in the list also writes to the base attribute name. For example, configuring **Sum** and then **Average** for `bytes_sent` produces `bytes_sent_sum`, which is also written to `bytes_sent`, and `bytes_sent_avg`. To change the order in which strategies are applied, drag them in the list.
-
-> Adding multiple strategies, whether to a specific path or the default, adds additional attributes to the summary and requires more processing per message. Use multiple strategies only when your analytics or dashboards need more than one aggregated form of the same attribute.
-
-Each strategy type can be used only once per attribute path.
-
-### Configure the default strategy
-
-The **Default Strategy** section defines the strategies that apply to every attribute path that is not configured under **Attribute merging strategies**. You must configure at least one default strategy. **Exact Match** is the default.
-
-As with path-specific strategies, you can add multiple default strategies. When you add multiple default strategies, each strategy produces a suffixed attribute in the summary, and the first strategy also writes to the base attribute name.
-
-## Frequently Asked Questions
-
-### What is the aggregation window?
-
-The aggregation window is a fixed-duration, tumbling window over which the reducer counts and aggregates the messages that match each pattern. The reducer divides the incoming log stream into consecutive windows and produces a summary separately for each window. The window is two minutes by default. You cannot change the window duration in the Grepr UI; you must use the REST API, and Grepr recommends contacting support for guidance before changing it.
-
-### How do I prevent messages from different services being aggregated together?
-
-Add the tag key that identifies each service, such as service or env, to the Group-by values field. The reducer aggregates messages independently for each unique combination of group-by values, so patterns from different services are never merged.
-
-### What does the similarity threshold control?
-
-The similarity threshold is the percentage of tokens that must match between an incoming message and an existing pattern for the message to be considered part of that pattern. Higher values produce more distinct patterns and less aggressive reduction. Lower values produce broader patterns and more aggressive reduction, at the cost of more mask-defined tokens in each summary.
-
-### Why should I raise the minimum number of samples?
-
-The minimum number of samples is how many raw matching messages are forwarded for a pattern in an aggregation window before aggregation begins. Raise it when you want more raw samples of each pattern to be sent to your observability backend. Lower it to begin aggregation sooner and reduce more volume.
-
-### When should I disable the repeat count prefix?
-
-Disable the repeat count prefix when downstream systems parse the summary message body directly, such as when summary messages contain JSON. The prefix would otherwise prepend non-JSON text and break parsing.
-
-### What's the difference between the two sampling strategies?
-
-No Additional Sampling stops forwarding raw messages for a pattern as soon as the minimum number of samples has been reached in an aggregation window. Window-Based Logarithmic continues to forward additional raw samples at a logarithmically decreasing rate, preserving more visibility into high-volume patterns.
-
-### How does the logarithm base affect sampling?
-
-With Window-Based Logarithmic sampling, a larger logarithm base forwards fewer additional samples as message volume grows, and a smaller base forwards more. The base must be at least two.
-
-### What are masks and why does the reducer apply them?
-
-Masks are regular expressions that identify variable parts of a log message, such as timestamps, IDs, or IP addresses, and replace them with specific tokens before clustering. This normalizes messages that differ only in those values so they can be grouped into the same pattern.
-
-### Can I add my own masks?
-
-Yes. Click Add Custom Mask in the Mask Configuration section. The mask name must contain only lowercase letters, be no more than 50 characters long, and be unique across all masks in the reducer. Then enter the regular expression pattern to apply.
-
-### Which regular expression features can I use in a custom mask?
-
-A custom mask pattern supports common regular expression constructs, including literal characters and character classes such as \[a-z], \d, \w, and \s; quantifiers such as \*, +, ?, and {n,m}; alternation and grouping; and anchors and word boundaries such as ^, $, and \b. Lookahead and lookbehind assertions and backreferences are not supported. A pattern that uses an unsupported construct passes the form's validation but prevents the reducer from processing messages, so test a custom pattern against sample messages.
-
-### What are delimiters and when should I change them?
-
-Delimiters are the characters the reducer uses to split messages into tokens during clustering. The defaults cover common punctuation and whitespace but omit @ and . so email addresses and dotted identifiers are not split. Change the list when your log format uses other separators, such as a custom field delimiter.
-
-### How do I add a tab, newline, or carriage return delimiter?
-
-Enter the escape sequence in the Add delimiter field: \t for tab, \n for newline, or \r for carriage return. Additional control-character escape sequences, including \b, \f, \v, and \0, are also supported.
-
-### What does each attribute merge strategy do?
-
-Exact Match keeps a single value if all messages agree and stores a wildcard otherwise. Sample collects up to a limit of values and drops overflow. Preserve All collects every value up to a limit and emits the current summary when the limit would be exceeded. Sum, Min, Max, and Average compute the corresponding aggregation over numeric values, ignoring non-numeric values.
-
-### What is the difference between Sample and Preserve All?
-
-Sample stops collecting once its limit is reached and discards any further values in the same summary. Preserve All emits the current summary and starts a new one when adding more values would exceed its limit, so no value is discarded. Sample has a lower default limit; Preserve All has a higher default limit.
-
-### When does the 'Keep unique values only' checkbox matter?
-
-For Sample and Preserve All strategies, it controls how collected values are stored. When selected, values are stored as a set and duplicates are discarded. When cleared, values are stored as a list, and duplicates are preserved.
-
-### How do I target a specific attribute with its own strategy?
-
-Add an entry under Attribute merging strategies, enter the attribute path using dot notation or a JSON array, and configure one or more strategies. Paths must be unique within the list, and each entry must have a non-empty path.
-
-### What happens when I select multiple strategies for the same attribute?
-
-The reducer produces a separate attribute in the summary for each strategy, suffixed with the strategy name, such as _sum or _avg. The first strategy in the list also writes to the base attribute name. Each strategy type can be used only once per attribute path.
-
-### What does the default strategy apply to?
-
-The default strategy applies to every attribute path that does not have an explicit entry in Attribute merging strategies. Exact Match is the default, but you can configure one or more other strategies. As with path-specific strategies, additional default strategies produce suffixed attributes and require more processing.