@grepr/cli 1.12.7 → 1.14.3-5fb972a

package/build/dist/docs-index/2cb0388c-7667-4fa7-a2b2-ea2294e8c824.txt

@@ -1,44 +0,0 @@
-# InvestigationSummary
-
-**Type**: `object`
-
-## Properties
-
-- name: actions (optional)
-  type: array of `InvestigationAction`
-
-- name: agentId (optional)
-  type: string
-
-- name: createdAt (optional)
-  type: string
-
-- name: endedAt (optional)
-  type: string
-
-- name: inputTokens (optional)
-  type: integer
-
-- name: investigationId (optional)
-  type: string
-
-- name: live (optional)
-  type: boolean
-
-- name: outputTokens (optional)
-  type: integer
-
-- name: resumable (optional)
-  type: boolean
-
-- name: startedAt (optional)
-  type: string
-
-- name: status (optional)
-  type: enum: `QUEUED`, `RUNNING`, `STOPPING`, `CANCELLING`, `STOPPED`, `COMPLETED`, `FAILED`, `CANCELLED`, `DISCARDED`
-
-- name: summary (optional)
-  type: string
-
-- name: triggerSignals (optional)
-  type: array of `TriggerSignal`

package/build/dist/docs-index/2e3ffd39-6eaf-42a9-8319-93c4cee90b49.json

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

package/build/dist/docs-index/2e3ffd39-6eaf-42a9-8319-93c4cee90b49.txt

@@ -1,29 +0,0 @@
-# Get a Splunk integration with exceptions
-
-**GET** `/v1/integrations/splunk/{id}/with-exceptions`
-
-**Operation ID**: `getSplunkIntegrationWithExceptions`
-**Summary**: Get a Splunk integration with exceptions
-Get an integration to connect to Splunk with vendor imported exceptions populated.
-
-## Tags
-- Splunk Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-Integration retrieved successfully with exceptions
-
-- **Content-Type**: `application/json` / `ReadSplunk`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/2e7a8da5-8389-4c18-a744-721e5efc4be8.json

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

package/build/dist/docs-index/2e7a8da5-8389-4c18-a744-721e5efc4be8.txt

@@ -1,19 +0,0 @@
-# IssueGuidanceReads
-
-The investigations a guidance comment was delivered to.
-
-**Type**: `object`
-
-## Properties
-
-- name: commentId (optional)
-  type: string
-  description: The guidance comment.
-
-- name: latest (optional)
-  type: array of `IssueGuidanceRead`
-  description: The latest deliveries, newest first, at most 3.
-
-- name: readCount (optional)
-  type: integer
-  description: How many investigations it was delivered to.

package/build/dist/docs-index/2e8e58a8-68ee-4ec0-a290-93f14f0eac19.json

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

package/build/dist/docs-index/2e8e58a8-68ee-4ec0-a290-93f14f0eac19.txt

@@ -1,115 +0,0 @@
-# LogAttributesRemapper
-
-**Type**: `object`
-
-## Properties
-
-- name: attributeRemappingRules (optional)
-  type: array of `AttributeRemappingRule`
-  description: List of attribute-to-attribute remapping rules. Each rule moves the value from a source attribute path to a target attribute path, removing the source unless the rule's preserveSource flag is set. An optional predicate filter controls when each rule is applied.
-
-- name: hostPreserveSource (optional)
-  type: boolean
-  description: When true, preserves the source host attribute after remapping instead of removing it. Defaults to true (source is preserved).
-
-- name: hostReservedAttributePaths (optional)
-  type: array of array of string
-  description: Paths to search for host values
-
-- name: hostReservedAttributes (optional)
-  type: array of string
-  description: Attributes to search for host values
-
-- name: messagePreserveSource (optional)
-  type: boolean
-  description: When true, preserves the source message attribute after remapping instead of removing it. Defaults to false (source is removed after remapping).
-
-- name: messageReservedAttributePaths (optional)
-  type: array of array of string
-  description: Paths to search for message values
-
-- name: messageReservedAttributes (optional)
-  type: array of string
-  description: Attributes to search for message values. The used attribute will be removed once remapped.
-
-- name: name (required)
-  type: string
-
-- name: servicePreserveSource (optional)
-  type: boolean
-  description: When true, preserves the source service attribute after remapping instead of removing it. Defaults to true (source is preserved).
-
-- name: serviceReservedAttributePaths (optional)
-  type: array of array of string
-  description: Paths to search for service values
-
-- name: serviceReservedAttributes (optional)
-  type: array of string
-  description: Attributes to search for service values
-
-- name: statusMapping (optional)
-  type: `StatusMapping`
-
-- name: statusPreserveSource (optional)
-  type: boolean
-  description: When true, preserves the source status attribute after remapping instead of removing it. Defaults to true (source is preserved).
-
-- name: statusReservedAttributePaths (optional)
-  type: array of array of string
-  description: Attributes to search for status values
-
-- name: statusReservedAttributes (optional)
-  type: array of string
-  description: Attributes to search for status values
-
-- name: tagMappingPaths (optional)
-  type: object
-  description: Map from tag key to an ordered list of attribute paths to search for values. All paths will be tried, and all found values will be added. If no value is found, the tag will not be changed. The attribute paths are a list of paths. This does not remove existing tag values.
-
-- name: tagMappings (optional)
-  type: object
-  description: Map from tag key to an ordered list of attribute paths to search for values. All paths will be tried, and all found values will be added. If no value is found, the tag will not be changed. The attribute paths are dot-separated. This does not remove existing tag values.
-
-- name: tagMappingsLocationPaths (optional)
-  type: array of array of string
-  description: Possible locations of a map of string to string or to collection of strings that has tags. Added to tags, without replacement.
-
-- name: tagMappingsLocationPreserveSource (optional)
-  type: boolean
-  description: When true, preserves the source tag map location attributes after remapping instead of removing them. Defaults to false (source is removed after remapping).
-
-- name: tagMappingsLocations (optional)
-  type: array of string
-  description: Possible locations of a map of string to string or to collection of strings that has tags. Added to tags, without replacement.
-
-- name: tagMappingsPreserveSource (optional)
-  type: boolean
-  description: When true, preserves the source tag mappings attributes after remapping instead of removing them. Defaults to false (source is removed).
-
-- name: timestampPreserveSource (optional)
-  type: boolean
-  description: When true, preserves the source timestamp attribute after remapping instead of removing it. Defaults to true (source is preserved).
-
-- name: timestampReservedAttributePaths (optional)
-  type: array of array of string
-  description: Paths to search for timestamp values
-
-- name: timestampReservedAttributes (optional)
-  type: array of string
-  description: Attributes to search for timestamp values
-
-- name: traceIdPreserveSource (optional)
-  type: boolean
-  description: When true, preserves the source traceId attribute after remapping instead of removing it. Defaults to true (source is preserved).
-
-- name: traceIdReservedAttributePaths (optional)
-  type: array of array of string
-  description: Paths to search for traceId values
-
-- name: traceIdReservedAttributes (optional)
-  type: array of string
-  description: Attributes to search for traceId values
-
-- name: type (required)
-  type: enum: `log-attributes-remapper`
-  description: Maps attributes to top-level fields and tags.

package/build/dist/docs-index/2f00d84f-7352-4d99-8604-aee39b8a31c2.json

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

package/build/dist/docs-index/2f00d84f-7352-4d99-8604-aee39b8a31c2.txt

@@ -1,39 +0,0 @@
-# TraceSampler
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-
-- name: sampleDurationMillis (optional)
-  type: integer
-  description: How long (in milliseconds) a sampled trace ID remains marked for as sampled without new messages before being declared expired. After this duration with no more events for trace, subsequent events for the same trace will be re-evaluated for sampling if seen again.
-
-- name: sampleRate (required)
-  type: number
-  description: The probability (0.0 to 1.0) of sampling a newly seen trace ID.
-
-- name: selector (optional)
-  type: `EventPredicate`
-
-- name: traceIdAttributePaths (optional)
-  type: array of array of string
-  description: List of attribute paths (each path is a list of segments) to extract trace IDs from. The first non-null value found will be used as the trace ID.
-
-- name: traceIdTagKeys (optional)
-  type: array of string
-  description: List of tag keys to extract trace IDs from. The first non-null value found will be used as the trace ID (checked after attribute paths).
-
-- name: traceSamplerTagKey (optional)
-  type: string
-  description: The key for the tag added to events of sampled traces to signal downstream operations differentiated processing.
-
-- name: traceSamplerTagValue (optional)
-  type: string
-  description: The value for the tag added to events of sampled traces to signal downstream operations differentiated processing.
-
-- name: type (required)
-  type: enum: `trace-sampler`
-  description: Samples traces based on their ID and marks associated events that are part of the selected traces. This can be used to bypass downstream processing such as message reduction, ensuring complete unmodified logs for those selected traces. This operation can add some overhead since it might require an additional shuffle in the pipeline. Messages that have trace IDs will be output on the "traced" output, while messages that do not have any trace IDs be output on the "untraced" output.

package/build/dist/docs-index/2f01b2e5-bb56-427c-9ea9-80b21fb7afa1.json

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

package/build/dist/docs-index/2f01b2e5-bb56-427c-9ea9-80b21fb7afa1.txt

@@ -1,78 +0,0 @@
-Two ways to send logs to several vendor accounts, by creating a pipeline for each group or by grouping the reducer and filtering each sink.
-
-# Route logs to several vendor accounts
-
-Your logs do not all belong in the same place. Separate teams, environments, or business units each own an account in your observability platform, and a log has to reach the account that owns it. Each account you send to is its own Grepr integration.
-
-A Grepr pipeline is a free-form processing graph rather than a fixed shape, so you can arrange this in more than one way. Here are two examples, and you can combine them.
-
-## Create a pipeline for each group \[#pipeline-per-group]
-
-Create one pipeline for each group of logs that belongs together, filter its source to that group, and give it the sink for that group's account.
-
-Each pipeline summarizes only its own logs, so you can tune each one on its own. Choose this when the groups need different configurations, or when you want them isolated from each other.
-
-To create a pipeline, see [_](/tutorials/first-pipeline). To limit what one ingests, see [_](/transforms/filter-events).
-
-## Group the reducer and filter each sink \[#grouped-sinks]
-
-Run a single pipeline, add a sink for each account, and filter each sink to that account's logs. Choose this when the groups have the same configuration, and you would rather manage one pipeline than several.
-
-Routing rests on a *routing key*, which is a field whose value names the account a log belongs to, such as `account` or `team`. Two settings act on it: the reducer groups on the key, and each sink filters on it.
-
-Grouping is what makes the filtering correct. A summary carries the values of the fields it was grouped on, so grouping on the routing key gives every summary exactly one account, and each sink's filter then matches its own account and no other.
-
-> Configure the grouping before you add the sinks, because leaving it out fails quietly. Without the routing key in the group-by, logs bound for different accounts aggregate together. A tag then carries every value the merged messages had, so every account receives the same summary, reporting counts that include the other accounts' logs. An attribute is merged instead, and the default merge strategy replaces values that differ with a wildcard, so no filter matches and the summary reaches no account.
-
-### Step 1: Put the routing key on every log \[#step1-routing-key]
-
-The routing key has to be on each log before the reducer sees it, holding one value per account. If your collectors already tag logs with the owning team or environment, use that tag. If the value is inside the message, parse it into an attribute or a tag first with the Grok parser or the JSON parser. See [_](/transforms/grok) and [_](/transforms/json-parsing).
-
-A tag and an attribute both work as the routing key. Choose one whose values are few and stable, because each value aggregates separately. Decide what happens to logs carrying no value for the key, which match no filter and so reach no account: give them a default value when you parse, or add a sink that catches them.
-
-### Step 2: Group the reducer on the routing key \[#step2-group]
-
-1. On the pipeline's **Reducer** step, click **Edit** on the **Fields** card.
-2. If the routing key is listed, set its **Behaviour** to **Match or split**.
-3. If it is not listed, enter it in the **Add field** row, set the **Behaviour** to **Match or split**, and click **Add**.
-4. Click **Save**.
-
-The **Match or split** behavior keeps a field out of aggregation, so messages whose values differ are never merged into one pattern. Enter tag keys plainly, and prefix attribute paths with `@`. An attribute is merged as well as grouped, and the default merge strategy keeps the value that every message in the group agrees on. If you set a different merge strategy for the routing attribute, check that it preserves that value rather than combining or discarding it. See [_](/transforms/reducer/configuration#attribute-configuration).
-
-### Step 3: Create a Grepr integration for each account \[#step3-integrations]
-
-Create one Grepr integration for each account you send to. An integration authenticates to a single account, so its credential is what decides where its logs land. Name each integration after its account, because that name is what you select when you add the sink. See [_](/integrations).
-
-### Step 4: Add a filtered sink for each account \[#step4-sinks]
-
-Repeat for each account:
-
-1. On the pipeline's **Sinks** step, click **Add sink**.
-2. In the **Sink** menu, select the integration for the account. Grepr fills in a **Name**, which you can change.
-3. In the **Query language** menu, select the syntax you want to write the filter in.
-4. In the **Filter Query** field, enter a query that matches only that account's logs, such as `team:platform`.
-5. Click **Add**, then save the pipeline.
-
-A sink with an empty filter forwards everything, so give each sink a filter query that matches it to one account. A sink's card reports its filter and shows **All messages** when it has none, which is how you spot one you missed. The filter runs on everything the reducer emits, so summaries, samples, passthrough messages, and exceptions all follow the same routing. To learn about the filter syntax, see [_](/queries/datadog) and [_](/queries/new-relic).
-
-## Frequently Asked Questions
-
-### Can one Grepr pipeline send logs to several accounts of the same vendor?
-
-Yes. Add one sink for each account, each pointing at that account's integration, and give each sink a filter that matches only that account's logs. Group the reducer on the same routing key the filters use, so that each summary belongs to exactly one account.
-
-### Why does the reducer need to group on the routing key?
-
-Without it, logs for different accounts aggregate together and the summary no longer identifies one account. If the key is a tag, the summary carries every value the merged messages had, so each account's filter matches it and every account receives counts that include the other accounts' logs. If the key is an attribute, the default merge strategy replaces the differing values with a wildcard, so no filter matches and the summary reaches no account.
-
-### Should I create a pipeline for each account or filter the sinks of one pipeline?
-
-Create a pipeline for each group when the groups need different reduction settings or different exceptions, or when you want them isolated. Filter the sinks of one pipeline when the groups share one reduction policy and you would rather keep a single pipeline to change.
-
-### What happens to logs that have no value for the routing key?
-
-They match no sink's filter and reach no vendor account. Give them a default value when you parse the routing key, or add a sink whose filter matches them so they land somewhere you can see.
-
-### Does a sink filter apply to summarized logs as well as raw ones?
-
-Yes. The filter runs on everything the reducer emits, so summaries, samples, passthrough messages, and exceptions all follow the same routing.

package/build/dist/docs-index/2f0b1157-a4b0-460b-9dad-6876b1aaaa96.json

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

package/build/dist/docs-index/2f0b1157-a4b0-460b-9dad-6876b1aaaa96.txt

@@ -1 +0,0 @@
-Although this page describes using an integration to create a pipeline for sourcing and sending data with a single observability platform, your pipelines can use multiple integrations to source and sink data for different platforms. For example, you can create a pipeline with a Datadog integration that's used to source data from Datadog agents, and a Splunk integration and sink that sends the pipeline output to Splunk.

package/build/dist/docs-index/2f0fe928-28ab-45ca-a876-44fb3902693c.json

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

package/build/dist/docs-index/2f0fe928-28ab-45ca-a876-44fb3902693c.txt

@@ -1,10 +0,0 @@
-# LogEventMapper
-
-Selects the mapper used to decode raw file records into LogEvents.
-
-**Type**: `object`
-
-## Properties
-
-- name: type (required)
-  type: string

package/build/dist/docs-index/301876a2-7163-4f94-aad8-87abaf2bcd7a.json

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

package/build/dist/docs-index/301876a2-7163-4f94-aad8-87abaf2bcd7a.txt

@@ -1,26 +0,0 @@
-# EventAction
-
-Base class of all Event Actions
-
-**Type**: `object`
-
-## One Of
-
-This schema accepts one of the following types:
-
-### Option 1
-`TagAction`
-
-### Option 2
-`RemoveKeyAttributeAction`
-
-### Option 3
-`MergeMapAttributeAction`
-
-### Option 4
-`AddToListAttributeAction`
-
-## Properties
-
-- name: order (optional)
-  type: integer

package/build/dist/docs-index/304a7dc7-c804-4ce8-8f0d-213f38b8a9c3.json

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

package/build/dist/docs-index/304a7dc7-c804-4ce8-8f0d-213f38b8a9c3.txt

@@ -1,18 +0,0 @@
-# AggregationDecl
-
-One aggregation function declaration.
-
-**Type**: `object`
-
-## Properties
-
-- name: args (optional)
-  type: array of object
-  description: Function arguments. Heterogeneous; validated at pipeline construction. PERCENTILE accepts [rank], [rank, relativeAccuracy], or [rank, relativeAccuracy, maxNumBins].
-
-- name: as (optional)
-  type: string
-  description: Output suffix. Omitted = preserve source metric name; in rule conditions the output is addressed as `<alias>.val` (at most one as-less aggregation per block).
-
-- name: fn (required)
-  type: `AggType`

package/build/dist/docs-index/30714459-f5fb-4b2a-a0d7-f436a2dfd57d.json

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

package/build/dist/docs-index/30714459-f5fb-4b2a-a0d7-f436a2dfd57d.txt

@@ -1,26 +0,0 @@
-# VendorEstimate
-
-What a run says about one exception. The type field selects the variant.
-
-**Type**: `object`
-
-## One Of
-
-This schema accepts one of the following types:
-
-### Option 1
-`VendorEstimateCounted`
-
-### Option 2
-`VendorEstimatePending`
-
-### Option 3
-`VendorEstimateUnparseable`
-
-### Option 4
-`VendorEstimateError`
-
-## Properties
-
-- name: type (required)
-  type: string

package/build/dist/docs-index/3085a757-4a92-454d-8575-bb27172b7de1.json

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

package/build/dist/docs-index/3085a757-4a92-454d-8575-bb27172b7de1.txt

@@ -1,24 +0,0 @@
-# WriteLiteLlm
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-  description: Name of the integration.
-
-- name: payload (required)
-  type: `LiteLlm`
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this integration is associated with.
-
-- name: type (required)
-  type: enum: `litellm`
-  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/30eb2764-738f-453a-8f8b-4ff1bb64c6af.json

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

package/build/dist/docs-index/30eb2764-738f-453a-8f8b-4ff1bb64c6af.txt

@@ -1,38 +0,0 @@
-# IssueDetail
-
-An issue with what a person or agent needs to act on it.
-
-**Type**: `object`
-
-## Properties
-
-- name: assignments (optional)
-  type: array of `IssueAssignment`
-  description: Its assignees.
-
-- name: guidance (optional)
-  type: array of `IssueComment`
-  description: Its newest guidance comments, oldest first: at most 20, and 32768 bytes of their bodies, though the newest is always there.
-
-- name: guidanceOmitted (optional)
-  type: integer
-  description: How many older guidance comments that bound left out; `GET /v1/issues/{id}/comments` pages every comment.
-
-- name: guidanceReads (optional)
-  type: array of `IssueGuidanceReads`
-  description: For each current guidance comment that agents were given, the investigations it was delivered to; a comment no longer guidance is not listed.
-
-- name: issue (optional)
-  type: `Issue`
-
-- name: recentComments (optional)
-  type: array of `IssueComment`
-  description: Its latest comments, newest first, at most 20.
-
-- name: recentEvents (optional)
-  type: array of `IssueEvent`
-  description: Its latest history entries, newest first, at most 20; `GET /v1/issues/{id}/events` pages older ones.
-
-- name: runs (optional)
-  type: array of `IssueRun`
-  description: Its runs that haven't ended, oldest first: queued or working on it, handed, picked up or watching.

package/build/dist/docs-index/30f188fa-34c5-4135-996e-ab60583443ff.json

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

package/build/dist/docs-index/30f188fa-34c5-4135-996e-ab60583443ff.txt

@@ -1,19 +0,0 @@
-# SlackMcp
-
-The payload containing integration data.
-
-**Type**: `object`
-
-## Properties
-
-- name: apiKey (optional)
-  type: string
-  description: Masked API key for the MCP server.
-
-- name: serverUrl (required)
-  type: string
-  description: MCP server endpoint URL.
-
-- name: validateKeysOnSave (optional)
-  type: boolean
-  description: Indicates whether to validate the API key when saving.

package/build/dist/docs-index/310720fa-71c6-4434-81d6-38e69e9a587d.json

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

package/build/dist/docs-index/310720fa-71c6-4434-81d6-38e69e9a587d.txt

@@ -1,21 +0,0 @@
-# AttributeWithComparatorNode
-
-**Type**: `object`
-
-## Properties
-
-- name: attribute (required)
-  type: string
-  description: The attribute name
-
-- name: comparator (required)
-  type: enum: `GREATER_THAN`, `GREATER_THAN_OR_EQUAL`, `LESS_THAN`, `LESS_THAN_OR_EQUAL`, `EQUAL`, `NOT_EQUAL`
-  description: The comparator to use for the match.
-
-- 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-comparator-node`
-  description: A node that matches an attribute in a parsed query.

package/build/dist/docs-index/314e8d7a-eb90-4147-8134-ddf1b7aca1f8.json

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

package/build/dist/docs-index/314e8d7a-eb90-4147-8134-ddf1b7aca1f8.txt

@@ -1,24 +0,0 @@
-# WriteGreprPipe
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-  description: Name of the integration.
-
-- name: payload (required)
-  type: `GreprPipe`
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this integration is associated with.
-
-- name: type (required)
-  type: enum: `grepr-pipe`
-  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/31808628-f4db-4bb9-b75d-56dc31d4462e.json

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

package/build/dist/docs-index/31808628-f4db-4bb9-b75d-56dc31d4462e.txt

@@ -1,28 +0,0 @@
-# Delete an SSO claim mapping
-
-**DELETE** `/v1/sso-claim-mapping/{id}`
-
-**Operation ID**: `deleteClaimMapping`
-**Summary**: Delete an SSO claim mapping
-Deletes an existing SSO claim mapping
-
-## Tags
-- SSO Claim Mappings
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 204
-
-Claim mapping deleted successfully
-
-### 403
-
-Insufficient permissions
-
-### 404
-
-Claim mapping not found

package/build/dist/docs-index/31fff878-88bc-49b1-975d-8a5ab669c7cb.json

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