@grepr/cli 1.9.3-34505b9 → 1.9.3-5829052

package/build/dist/docs-index/{cda41860-5a0e-47ab-928d-792ce2dc0fc4.txt → 2006977c-05cf-4cd5-acd2-61e081fae866.txt}

@@ -172,7 +172,7 @@ To have Grepr recompute impact percentages during the next impact estimation cyc
 
 ## Limitations
 
-Grepr might split log events over 1MB, causing them to lose their original structured format. Each split event includes a common `grepr.splitOriginId` attribute if you need to reconstruct the original message.
+Grepr might split log events over 900KB, causing them to lose their original structured format. Each split event includes a common `grepr.splitOriginId` attribute if you need to reconstruct the original message.
 
 ## Frequently Asked Questions
 
@@ -212,6 +212,6 @@ The Grepr data lake uses Amazon S3 to store raw log data. You can configure eith
 
 Grepr might drop incoming data from external integration sources with timestamps older than 48 hours. This limitation helps optimize storage and processing while allowing you to retain raw logs in the data lake for longer-term analysis.
 
-### What happens when a log event is larger than 1MB?
+### What happens when a log event is larger than 900KB?
 
-If a log event exceeds 1MB, Grepr might split it into smaller events, which can cause them to lose their original structured format. Each split event includes a common 'grepr.splitOriginId' attribute that you can use to reconstruct the original message from its component parts.
+If a log event exceeds 900KB, Grepr might split it into smaller events, which can cause them to lose their original structured format. Each split event includes a common 'grepr.splitOriginId' attribute that you can use to reconstruct the original message from its component parts.

package/build/dist/docs-index/ba17e8b0-7526-4b79-af3a-85ea95280c1f.txt

@@ -0,0 +1,15 @@
+# AgentSessionsEndpoint
+
+An OTLP integration attached as an Agent Sessions source or sink.
+
+**Type**: `object`
+
+## Properties
+
+- name: integrationId (required)
+  type: string
+  description: OTLP integration carrying both agent event logs and execution spans.
+
+- name: name (required)
+  type: string
+  description: Base operation name; the generated logs and traces operations suffix it.