@grepr/cli 1.13.0-2632478 → 1.14.3-a181b29

package/build/dist/docs-index/5966c46d-59aa-424b-939c-09cc3632d8fd.json

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

package/build/dist/docs-index/5966c46d-59aa-424b-939c-09cc3632d8fd.txt

@@ -1,147 +0,0 @@
-Create a Grepr AI agent, write its instructions, choose its model, set the limits that bound what it spends, and edit or delete it later.
-
-# Create an AI agent
-
-You create an agent once and it runs from then on, so the settings you choose decide both what the agent is good at and what it costs. This page covers the settings that define the agent itself. Its capabilities, its memory, and its subscriptions each have their own page, and the wizard links to the same settings.
-
-## Requirements
-
-Before you create an agent, you need:
-
-* An LLM integration for the model the agent reasons with. See [_](/integrations/llm).
-* A Grepr service account for the agent to act as. See [_](/admin/service-accounts).
-
-## Create an agent \[#create]
-
-On the **Agents** page, click **Create agent**. The **Create agent** wizard collects the agent's settings in five steps, and you can move between steps with **Back** and **Continue** or by clicking a step in the stepper. The agent is created when you click **Create agent** on the last step, so you can revise any step before then.
-
-### Step 1: Name the agent and write its instructions \[#step1-instructions]
-
-Enter a **Name** that says what the agent is for, such as `prod-log-triage`. The name identifies the agent everywhere you subscribe it to a source or read its investigations, and you can change it later.
-
-In the **System prompt** field, write the instructions that frame every investigation this agent runs. To start from a working example rather than an empty field, click **Use a starter prompt** and edit what it gives you.
-
-### Step 2: Choose a model \[#step2-model]
-
-1. In the **Provider** menu, select the provider of the LLM integration you want the agent to use.
-2. In the **LLM integration** menu, select the integration that provides the credentials for that provider. If the menu is empty, create the integration first. See [_](/integrations/llm).
-3. In the **Model name** field, enter the model the agent reasons with. Grepr suggests the models your integration reports, but the field accepts any model identifier the provider serves, so a model missing from the list is still valid.
-4. Set the agent's limits under **Advanced configuration**. See [Set an agent's limits](#limits).
-
-Investigations are long-running and tool-heavy, so the model you choose changes how well the agent reasons across many turns, not just how fast it answers. Prefer a model that handles extended tool use.
-
-### Step 3: Grant capabilities \[#step3-capabilities]
-
-The **Capabilities** step is where you choose the service account the agent acts as, the tools and skills it can use, the MCP servers it can call, and whether the pipeline changes it proposes need your approval. To learn more, see [_](/ai-agents/capabilities).
-
-The step ends with the **Memory and issues** section, which is collapsed. Every new agent records memories and works on issues, so open the section to turn off **Remember past investigations** or **Works on issues**, to set the store for searching memories by meaning, or to choose **Allow Ready** so the agent can file issues in Ready and move issues there. Every agent can search and read memories and issues, whichever switches are on. After the agent exists, these settings are on its **Memories** and **Issues** steps. To learn more about memory, see [_](/ai-agents/memory). To learn more about how agents work on issues and pick up Ready issues, see [_](/ai-agents/issue-board).
-
-### Step 4: Subscribe to signal sources \[#step4-subscriptions]
-
-The **Subscriptions** step is where you connect the agent to the pipelines and Grepr Agent integrations whose signals it investigates. You can leave it empty and subscribe later from the agent's page. To learn more, see [_](/ai-agents/subscriptions).
-
-### Step 5: Review and create \[#step5-review]
-
-The **Review** step lists every setting you chose. Check the system prompt, the model, the abilities and tools, what the agent does with memories and issues, and the subscriptions, then click **Create agent**.
-
-An agent with subscriptions starts investigating as soon as its sources produce signals. To review its behavior before it runs on live signals, create it without subscriptions, start an investigation manually, read the transcript, then subscribe it. See [_](/ai-agents/investigations#start-manual).
-
-## Set an agent's limits \[#limits]
-
-An agent's limits are under **Advanced configuration** on the **Model** step, and on the **Behavior** step after the agent exists. They are what bound the work and the cost of a single investigation and of the agent as a whole.
-
-### Limit a single investigation \[#run-limits]
-
-| Setting | What it does |
-| --- | --- |
-| **Max output tokens** | The largest response Grepr accepts from the model in one call. |
-| **Max turns per investigation** | How many turns an investigation can take before it ends. A turn is one model call and the tool calls that follow it. |
-| **Max tokens per investigation** | The total tokens one investigation can consume. The default is 3,000,000. |
-
-An investigation that reaches its turn or token limit ends where it is, keeping the transcript and the summary it had reached.
-
-### Limit the agent as a whole \[#window-limits]
-
-**Agent max tokens per window** caps the tokens this agent can consume across all its investigations in each budget window. Leave it empty to bound the agent only by the budget on its LLM integration.
-
-Grepr reserves an investigation's tokens before it starts and requires room in two budgets: this agent's window budget, and the budget on the LLM integration the agent shares with any other agent using it. When either is exhausted, new investigations stop starting, and the agent's page reports which budget blocked them and when the window resets. Raising this agent's limit does not help when the shared integration is the one that is full. To set the integration's budget, see [_](/integrations/llm#max-tokens).
-
-The two kinds of invocations, manual and signal triggered, end differently when a budget is exhausted. An investigation you start manually is discarded immediately, so you learn straight away. One triggered by a signal stays queued and runs when capacity returns, unless it waits longer than the maximum queue wait.
-
-### Control concurrency and queueing \[#concurrency]
-
-| Setting | What it does |
-| --- | --- |
-| **Max concurrent investigations** | How many of this agent's investigations run at the same time. The default is 3. |
-| **When at the limit** | Whether an additional signal waits or is dropped. **Queue** holds it until a slot frees. **Discard** drops it. |
-| **Max queue wait (minutes)** | How long a queued investigation waits before Grepr discards it. Leave empty for no limit. |
-
-The maximum queue wait applies only to investigations triggered by a signal, not to the ones you start manually. Set it when a stale signal is not worth investigating, such as a pattern that stopped occurring an hour ago. Leave it empty when you want every signal investigated eventually.
-
-An agent subscribed to a busy pipeline can produce more signals than it can investigate. **Discard** keeps the agent current at the cost of skipping signals, and **Queue** with a maximum wait keeps a bounded backlog. To reduce the signals instead of dropping them, narrow what the source emits. See [_](/ai-agents/subscriptions).
-
-## Write a system prompt \[#system-prompt]
-
-The system prompt is read at the start of every investigation this agent runs, so it should describe the agent's standing job rather than any one incident. A prompt that works well:
-
-* States what the agent is responsible for and what it should leave alone.
-* Names the systems and services it covers, using the same names that appear in your logs, so the agent can match a signal to a service.
-* Says what a finished investigation looks like, such as whether the agent should attempt a remediation or only diagnose.
-* Says when the agent should change a pipeline and when it should not.
-
-Keep behavior that only applies sometimes out of the prompt and put it in a skill, which the agent loads when it is relevant. This keeps the prompt short and lets several agents share the same guidance. See [_](/ai-agents/skills).
-
-You can revise the prompt at any time on the agent's **Behavior** step. A revised prompt applies to investigations that start afterwards, and running investigations keep the prompt they started with.
-
-## Monitor an agent \[#monitor]
-
-The agent's **Overview** step reports how the agent is doing over the time range you select, with its model, its last investigation, the share of its runs that failed, its run times, and how much of its token budget it has used. Three charts break down the investigations it started, how they ended, and the tokens they consumed.
-
-Read the failure rate together with the outcomes chart. Failures concentrated in time usually point at the model or a tool that became unavailable, while a failure rate that is steady across the range usually points at the agent's instructions or its limits.
-
-When a token budget is exhausted, new investigations stop starting and resume when the window resets. The agent's page shows which of the two budgets blocked them.
-
-## Edit an agent \[#edit]
-
-An agent's settings are spread across the steps on its page, which hold the same fields as the wizard:
-
-* **Behavior** holds the name, the system prompt, the model, and the limits.
-* **Capabilities** holds the service account, the tools, the skills, the MCP integrations, and the change approval mode.
-* **Memories** holds the memory settings and, below them, the memories the agent recorded.
-* **Issues** holds whether the agent works on issues, whether it can put issues in **Ready**, and which **Ready** issues it picks up. See [_](/ai-agents/issue-board).
-
-Changes to the settings on these four steps are held until you click **Save Changes**, so you can revise several steps in one pass. To abandon them, click **Discard Changes**. Subscriptions are not part of this and apply as soon as you make them. Neither are changes to individual memories on the **Memories** step: an edit, a verdict, or a delete applies as soon as you confirm it, and **Discard Changes** does not undo it.
-
-An investigation reads the agent's instructions, model, and limits when it starts, so correcting those mid-incident leaves the current run on the settings it began with and applies to the next one.
-
-The change approval mode is the exception. Grepr checks it when the agent submits a pipeline change, not when the investigation started, so switching an agent to **Auto-apply** lets an investigation that is already running apply its own changes.
-
-## Delete an agent \[#delete]
-
-To delete an agent, on its page, open the three-dot menu and select **Delete agent**. You can also delete it from the three-dot menu on its card on the **Agents** page.
-
-Grepr refuses to delete an agent while a pipeline is subscribed to it or a Grepr Agent integration names it, so detach it from both on its **Subscriptions** step first. A pipeline that names the agent directly in its agent signal sink is not covered by that check, so open the sink in each such pipeline and clear the agent from the **Agents** field yourself. A sink keeps at least one agent, so where the agent you are deleting is the only one named, either select another agent in its place or remove the sink along with the routes that feed it. A signal that arrives for a deleted agent is discarded. Investigations already running finish, and no new ones start.
-
-Deleting an agent does not delete its investigations or the memories it recorded, which stay readable and searchable by your other agents.
-
-## Frequently Asked Questions
-
-### What do I need before creating a Grepr AI agent?
-
-You need an LLM integration for the model, a Grepr service account for the agent to act as, and the Edit permission on integrations at the organization or team level.
-
-### How many investigations does a Grepr AI agent run at once?
-
-You set the maximum number of concurrent investigations, which defaults to 3, and choose whether an additional signal queues or is discarded at that limit. A queued investigation can also be given a maximum wait, after which Grepr discards it.
-
-### What happens when an agent reaches its token budget?
-
-New investigations stop starting, and the agent's page reports whether the agent's own window budget or the shared LLM integration's budget blocked them, and when the window resets. An investigation started manually is discarded immediately, while one triggered by a signal stays queued until capacity returns or its maximum queue wait elapses.
-
-### Do changes to an agent affect investigations that are already running?
-
-Mostly no. An investigation reads the instructions, model, and limits it started with, so changes to those apply to the next run. The change approval mode is the exception: Grepr checks it when the agent submits a pipeline change, so switching to Auto-apply lets an investigation that is already running apply its own changes.
-
-### Why can't I delete my Grepr AI agent?
-
-Grepr refuses to delete an agent while a pipeline is subscribed to it or a Grepr Agent integration names it. Detach it from both on its Subscriptions step, then delete it. Investigations already running finish, and its recorded memories remain searchable by your other agents.

package/build/dist/docs-index/59b759a8-d5d2-4dbe-8ba4-79c6e579e2cc.json

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

package/build/dist/docs-index/59b759a8-d5d2-4dbe-8ba4-79c6e579e2cc.txt

@@ -1,34 +0,0 @@
-# Creates or updates a Datadog integration api key
-
-**PUT** `/v1/integrations/datadog/{id}/api-key`
-
-**Operation ID**: `upsertDatadogApiKey`
-**Summary**: Creates or updates a Datadog integration api key
-Creates an API key for a Datadog integration if it doesn't exist and updates it otherwise.  If the key is updated while the integration is being used by a pipeline, the  new key will be picked at pipeline restart, rescaling or an update.  Ingestion supports the previous and the updated key for up to 24 hours of  a key update. Make sure to change the key used by the agents to send data within  24 hours of an update for a seamless transition
-
-## Tags
-- Datadog Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `SecretApi`
-
-## Responses
-
-### 204
-
-Api key upserted successfully.
-
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/59f338b8-08eb-4559-bf53-4844431f47c2.json

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

package/build/dist/docs-index/59f338b8-08eb-4559-bf53-4844431f47c2.txt

@@ -1,3 +0,0 @@
-# TimePartitionTransform
-
-**Type**: `object`

package/build/dist/docs-index/5a2ed7a5-0521-43b0-bab6-5142c6e3ef20.json

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

package/build/dist/docs-index/5a2ed7a5-0521-43b0-bab6-5142c6e3ef20.txt

@@ -1,5 +0,0 @@
-# TemplateIntegrationException
-
-Integration exception for template inputs with type field
-
-**Type**: `object`

package/build/dist/docs-index/5a341b8a-68f2-48bb-bb94-25983ca76b52.json

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

package/build/dist/docs-index/5a341b8a-68f2-48bb-bb94-25983ca76b52.txt

@@ -1,15 +0,0 @@
-# AnalyticsOrderBy
-
-Ordering applied to the analytical results.
-
-**Type**: `object`
-
-## Properties
-
-- name: direction (optional)
-  type: enum: `ASC`, `DESC`
-  description: Sort direction.
-
-- name: expression (required)
-  type: string
-  description: Grepr SQL expression or projection alias to order by. The expression may reference projection aliases.

package/build/dist/docs-index/5a8bc1e0-2c75-4d51-9740-381fbf4faa5d.json

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

package/build/dist/docs-index/5a8bc1e0-2c75-4d51-9740-381fbf4faa5d.txt

@@ -1,43 +0,0 @@
-# ActivityLogsSearch
-
-Activity logs search criteria
-
-**Type**: `object`
-
-## Properties
-
-- name: endTime (optional)
-  type: string
-  description: End of time range filter. Must be a valid ISO timestamp in UTC.
-
-- name: limit (optional)
-  type: integer
-  description: Maximum number of results to return
-
-- name: logTypes (optional)
-  type: array of enum: `INTEGRATION_IMPORT`, `INTEGRATION_STATISTICS`, `JOB_EXECUTION`, `USER_ACTIVITY`, `SECURITY_EVENT`
-  description: Optional filter by log types. If null or empty, matches all log types.
-
-- name: offset (optional)
-  type: integer
-  description: Number of results to skip for pagination
-
-- name: resourceFilters (optional)
-  type: array of `ResourceFilter`
-  description: Optional resource filters. Multiple filters use OR logic. If null or empty, matches all resources the user has access to (requires system logs permission if no filters specified).
-
-- name: searchQuery (optional)
-  type: string
-  description: Optional full-text search query for message content. Uses PostgreSQL's text search capabilities.
-
-- name: startTime (optional)
-  type: string
-  description: Start of time range filter. Must be a valid ISO timestamp in UTC.
-
-- name: statuses (optional)
-  type: array of enum: `INFO`, `WARNING`, `ERROR`
-  description: Optional filter by log statuses. If null or empty, matches all log statuses.
-
-- name: userIds (optional)
-  type: array of string
-  description: Optional filter by user IDs who triggered the activity. If null or empty, matches all users.

package/build/dist/docs-index/5a9b01fe-d17d-41b8-9dcc-1cd022e3fd27.json

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

package/build/dist/docs-index/5a9b01fe-d17d-41b8-9dcc-1cd022e3fd27.txt

@@ -1,24 +0,0 @@
-# WriteNewRelic
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-  description: Name of the integration.
-
-- name: payload (required)
-  type: `NewRelic`
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this integration is associated with.
-
-- name: type (required)
-  type: enum: `newrelic`
-  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/5acbd195-d5e0-40c4-975e-00aeb0609389.json

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

package/build/dist/docs-index/5acbd195-d5e0-40c4-975e-00aeb0609389.txt

@@ -1,14 +0,0 @@
-# AgentPipelineSubscription
-
-**Type**: `object`
-
-## Properties
-
-- name: jobId (required)
-  type: string
-
-- name: pausedAt (optional)
-  type: string
-
-- name: subscribedAt (required)
-  type: string

package/build/dist/docs-index/5b424dbf-4861-4830-a20c-59fa6d5f6452.json

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

package/build/dist/docs-index/5b424dbf-4861-4830-a20c-59fa6d5f6452.txt

@@ -1,16 +0,0 @@
-# EventActionRule
-
-**Type**: `object`
-
-## Properties
-
-- name: actionPredicate (required)
-  type: `EventPredicate`
-
-- name: actions (required)
-  type: array of `EventAction`
-  description: Actions to take on a matching event.
-
-- name: type (required)
-  type: enum: `event-rule`
-  description: This takes event actions on events that match the actionPredicate when this rule is triggered.

package/build/dist/docs-index/5c20dc23-bf73-411b-bf06-0fb1512bfb93.json

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

package/build/dist/docs-index/5c20dc23-bf73-411b-bf06-0fb1512bfb93.txt

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

package/build/dist/docs-index/5c23643a-1482-4123-910b-07d1f02f6995.json

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

package/build/dist/docs-index/5c23643a-1482-4123-910b-07d1f02f6995.txt

@@ -1,12 +0,0 @@
-# SpansSynchronousSink
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-
-- name: type (required)
-  type: enum: `spans-sync-sink`
-  description: Sink for returning results to the caller.

package/build/dist/docs-index/5c4e457f-c655-42d9-8d59-e3222a38beaa.json

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

package/build/dist/docs-index/5c4e457f-c655-42d9-8d59-e3222a38beaa.txt

@@ -1,17 +0,0 @@
-# SeverityNode
-
-**Type**: `object`
-
-## Properties
-
-- 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: severity (required)
-  type: integer
-  description: The severity level to match. This is an integer that is matched against the severity.
-
-- name: type (required)
-  type: enum: `severity-node`
-  description: A node that represents a severity in a parsed query.

package/build/dist/docs-index/5c7db210-8b98-4d01-bf7c-7acdad706d62.json

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

package/build/dist/docs-index/5c7db210-8b98-4d01-bf7c-7acdad706d62.txt

@@ -1,64 +0,0 @@
-Learn how AI agents work on issues on the issue board, how to hand an issue to an agent, and how agents pick up Ready issues.
-
-# Work on issues with AI agents
-
-An agent with **Works on issues** turned on files issues, works on them, and records what it found on the issue board. An agent works on an issue in an investigation started on that issue, called a *run* on the issue. A run starts on an issue in one of two ways: you hand the issue to the agent, or the agent picks the issue up from the **Ready** column.
-
-An agent's issue settings are on its **Issues** step: **Works on issues**, whether it can put issues in **Ready**, and which **Ready** issues it picks up. When you create an agent, they're in the wizard's **Memory and issues** section.
-
-## How an agent finds issues \[#finding-issues]
-
-Before an agent acts on a problem or files an issue, it searches the board for the problem and reads what it finds, including guidance comments. The search also finds issues people closed as **Ignored** or **Not a problem**, so an agent doesn't redo work a person ruled out. The issue page shows which runs each guidance comment was given to.
-
-An issue's entities, such as `entity:service=checkout`, say what the problem is. When an agent files an issue from an alert, it names at least one entity from the alert.
-
-## How an agent works on an issue \[#how-it-works]
-
-When a run on an issue starts, the agent joins the issue as an assignee, and an issue in **Ready** moves to **In progress**. The issue page lists the issue's runs with their status and a link to each one, and the issue's card shows an agent whose run is waiting to start.
-
-When the run ends:
-
-* The agent's assignment is finished.
-* The agent posts a comment on the issue that says how the run ended, with a link to the run. The comment includes the run's summary unless the agent already commented on the issue or the run failed.
-* If the issue is still **In progress**, with no one assigned and no other run on it, the issue moves to **Triage**, where a person decides what happens next. To keep an issue **In progress**, add yourself to it with **Add me**.
-
-An agent can close an issue it's assigned to, or move it to **Monitoring**: the move finishes the agent's own assignment. Another assignee's active assignment prevents the move, unless a person closes the issue.
-
-The same rules apply to an agent that joins an issue during another investigation, such as one started by an alert.
-
-## Hand an issue to an agent \[#hand-off]
-
-To hand an issue to an agent:
-
-1. On the issue page, click **Hand to an agent**.
-2. Choose the agent, and optionally add a note for it.
-3. To start the run ahead of the agent's other queued runs, select **Work on this next**. The run never stops a run that's already running.
-4. Click **Hand off**.
-
-You can hand an agent an open issue that the agent's service account can view and edit. The agent's page shows whose issues it works on. An agent that still has a run on the issue can't be handed it again: comment on the issue to steer the run, or cancel the run first.
-
-If the agent's run never starts, because it was discarded while waiting, failed to start, or was cancelled, the issue's history says so, with a link to the run.
-
-When you continue an investigation that was on an open issue, the new investigation works on that issue too, as if you handed the issue to the agent. If the issue is closed, the new investigation isn't on an issue.
-
-## Let an agent pick up Ready issues \[#pickup]
-
-To let an agent pick up issues on its own, open the agent's **Issues** step, turn on **Pick up Ready issues**, and choose which issues it takes: a priority, labels, entities, and teams. An issue must match every filter you set. Labels are the dependable way to route issues to an agent.
-
-The agent picks up issues in **Ready** that no one is assigned to and no run is on, most urgent first, then the one that has been in **Ready** the longest. It follows these rules:
-
-* It starts runs only in free run slots, and starts none while it has as many runs on issues as **Runs on issues at once**. Keep slots free for alerts and the issues people hand it.
-* It picks up only issues its service account can view and edit.
-* It doesn't pick up an issue again during the same stay in **Ready**.
-* Agents pick up an issue at most two times before a person acts on it again, by moving, changing, commenting on, or handing off the issue.
-* After three runs on issues in a row fail or never start, the agent picks up nothing for 30 minutes.
-
-Pausing an agent discards its runs on issues that are waiting to start, so that other agents can pick those issues up.
-
-## Let an agent put issues in Ready \[#allow-ready]
-
-By default, an agent files issues in **Triage** for a person to review, and can't move an issue to **Ready**. To let an agent file issues in **Ready** and move issues there, choose **Allow Ready** on the agent's **Issues** step. Agents whose pickup filters match an issue in **Ready** pick it up, and every agent can see the other agents' pickup filters, so an agent can label an issue for the agent that handles it.
-
-## Remove an agent from an issue \[#remove]
-
-To take an agent off an issue, remove it from the issue's assignees. Its assignment ends and its runs on the issue are cancelled. Until someone hands it the issue again or unlocks the issue's assignees, the agent can only comment on the issue. If no one else is working on an issue that is **In progress**, the issue moves to **Triage**.

package/build/dist/docs-index/5cce4fd2-8659-4c61-b662-6983afc40649.json

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

package/build/dist/docs-index/5cce4fd2-8659-4c61-b662-6983afc40649.txt

@@ -1,34 +0,0 @@
-# SqlOperation
-
-Processes data through a sequence of SQL statements executed in order. Supports VIEW statements that create temporary tables, OUTPUT statements that produce DataStream results, and IO statements that perform side effects.
-
-**Type**: `object`
-
-## Properties
-
-- name: availableDatasets (optional)
-  type: array of string
-  description: IDs of datasets whose tables can be referenced in SQL statements. These will be registered as queryable tables in the SQL environment. The tables from each dataset will appear in a separate namespace based on the dataset name.
-
-- name: globalStateTtl (optional)
-  type: string
-  description: Global time-to-live for operation state. When calculating aggregations or joins in streaming mode, Grepr pipelines will keep track of some state (such as the count and sum of values for an averaging aggregation). To prevent the size of the state from growing indefinitely, Grepr will set a default time-to-live value for any state. If state does not receive updates after this TTL, it will be considered idle and the state will be cleared. Aggregations for will be reset for the idle group for example.
-
-- name: inputs (optional)
-  type: object
-  description: Input table names that can be referenced in SQL statements. Each input table corresponds to an input stream that is connected to this operation in the job graph. All connected input types must be compatible with the SQL operations. Each type specifies what the schema of the resulting table that is available for the SQL statements looks like. For `COMPLETE_SPAN`, the table schema uses SQL row field names, which differ from the REST JSON property names in the `CompleteSpan` schema.
-
-- name: name (required)
-  type: string
-
-- name: statements (required)
-  type: array of `SqlExecutable`
-  description: List of SQL statements to execute in order. Each statement can reference tables created by previous statements, the input tables, and any tables from the available datasets.
-
-- name: type (required)
-  type: enum: `sql-operation`
-  description: Processes data through a sequence of SQL statements.
-
-- name: watermarkDelay (optional)
-  type: string
-  description: Delay for watermark generation. Default is 5 seconds. Watermarks are used to track event time progress in streaming jobs. The watermark is usually the maximum event time seen by a processing task minus this delay. Watermarks are used to trigger time-based operations like windowing. This delay defines how far behind the system can be in processing events before it considers the event time to be 'late'. Late events would not be included in windowing operations that might have already been closed (ie where the data is already sent). This also means that the results of windowing operations will be delayed by this delay, as the system waits for the watermark to catch up. For more information, see the Flink documentation on watermarks.

package/build/dist/docs-index/5d9750b4-d4c9-4411-8a9e-2bab9faeffa8.json

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

package/build/dist/docs-index/5d9750b4-d4c9-4411-8a9e-2bab9faeffa8.txt

@@ -1,8 +0,0 @@
-# GrokParseBatchResponse
-
-**Type**: `object`
-
-## Properties
-
-- name: results (optional)
-  type: array of `GrokParseResponse`

package/build/dist/docs-index/5da4f5db-b854-467b-ad6e-0e6f54608e2b.json

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

package/build/dist/docs-index/5da4f5db-b854-467b-ad6e-0e6f54608e2b.txt

@@ -1,21 +0,0 @@
-# create
-
-**POST** `/v1/agent-session-analytics/jobs`
-
-**Operation ID**: `create`
-**Summary**: No summary provided.
-## Tags
-- Agent Session Analytics
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `CreateAgentSessionAnalyticsJob`
-
-## Responses
-
-### 200
-
-Analytics run created
-
-- **Content-Type**: `application/json` / `AgentSessionAnalyticsJob`

package/build/dist/docs-index/5dcefaa8-a460-4933-8609-bbebdaa03961.json

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

package/build/dist/docs-index/5dcefaa8-a460-4933-8609-bbebdaa03961.txt

@@ -1,17 +0,0 @@
-# TagNode
-
-**Type**: `object`
-
-## Properties
-
-- name: tagKey (required)
-  type: string
-  description: The tag key 
-
-- name: tagValue (required)
-  type: string
-  description: This is a string that is matched against the tag value.
-
-- name: type (required)
-  type: enum: `tag-node`
-  description: A node that represents a tag key and value in a parsed query.

package/build/dist/docs-index/5e53e121-f03d-4f2a-b244-fe242539dd51.json

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

package/build/dist/docs-index/5e53e121-f03d-4f2a-b244-fe242539dd51.txt

@@ -1,3 +0,0 @@
-# StringData
-
-**Type**: `object`

package/build/dist/docs-index/5f16205d-02a4-4355-9d33-eaecb88f5ba8.json

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

package/build/dist/docs-index/5f16205d-02a4-4355-9d33-eaecb88f5ba8.txt

@@ -1,3 +0,0 @@
-# Any
-
-A value that can be a primitive (String or number), a list, or a map.

package/build/dist/docs-index/5f379af6-2b7e-4d98-babf-3ed29dc319ef.json

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

package/build/dist/docs-index/5f379af6-2b7e-4d98-babf-3ed29dc319ef.txt

@@ -1,13 +0,0 @@
-# DatadogQueryPredicate
-
-**Type**: `object`
-
-## Properties
-
-- name: query (required)
-  type: string
-  description: The datadog query used by the predicate. See https://docs.datadoghq.com/tracing/trace_explorer/query_syntax
-
-- name: type (required)
-  type: enum: `datadog-query`
-  description: A predicate that checks if an event matches a datadog query.

package/build/dist/docs-index/5f37f734-3404-4538-8044-cb28fca99584.json

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

package/build/dist/docs-index/5f37f734-3404-4538-8044-cb28fca99584.txt

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

package/build/dist/docs-index/5f394045-3f04-4ee2-8b0e-57cc021bbaf2.json

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