draft

Author: Andrei Bratu

index.ts

@@ -47,6 +47,8 @@ export interface CreateEvaluatorLogRequest {
     source?: string;
     /** Any additional metadata to record. */
     metadata?: Record<string, unknown>;
+    /** Status of a Log. Set to `incomplete` if you intend to update the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If not provided, observability will pick up the Log as soon as possible; switching from specified to unspecified is undefined behavior. */
+    logStatus?: Humanloop.LogStatus;
     /** Identifier of the evaluated Log. The newly created Log will have this one set as parent. */
     parentId: string;
     /** Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair. */

src/api/resources/evaluators/client/requests/CreateEvaluatorLogRequest.ts

@@ -75,6 +75,8 @@ export interface FlowLogRequest {
     source?: string;
     /** Any additional metadata to record. */
     metadata?: Record<string, unknown>;
+    /** Status of the Trace. When a Log is updated from `incomplete` to `complete`, it becomes available to Monitoring Evaluators. Flow Logs cannot have an unspecified status: they must start as `incomplete` to allow children to be added. Provide `complete` if you don't intend to add children to the trace. */
+    logStatus?: Humanloop.LogStatus;
     /** Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair. */
     sourceDatapointId?: string;
     /** The ID of the parent Log to nest this Log under in a Trace. */
@@ -89,6 +91,4 @@ export interface FlowLogRequest {
     logId?: string;
     /** Flow used to generate the Trace. */
     flow?: Humanloop.FlowKernelRequest;
-    /** Status of the Trace. When a Log is updated from `incomplete` to `complete`, it becomes available to Monitoring Evaluators. Flow Logs cannot have an unspecified status: they must start as `incomplete` to allow children to be added. Provide `complete` if you don't intend to add children to the trace. */
-    logStatus?: Humanloop.LogStatus;
 }

src/api/resources/flows/client/requests/FlowLogRequest.ts

@@ -497,6 +497,7 @@ export class Prompts {
             abortSignal: requestOptions?.abortSignal,
         });
         if (_response.ok) {
+            console.log("CALL RESPONSE",  JSON.stringify(_response.body, null, 2)); 
             return serializers.PromptCallResponse.parseOrThrow(_response.body, {
                 unrecognizedObjectKeys: "passthrough",
                 allowUnrecognizedUnionMembers: true,

src/api/resources/prompts/client/Client.ts

@@ -73,6 +73,8 @@ export interface ToolLogRequest {
     source?: string;
     /** Any additional metadata to record. */
     metadata?: Record<string, unknown>;
+    /** Status of a Log. Set to `incomplete` if you intend to update the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If not provided, observability will pick up the Log as soon as possible; switching from specified to unspecified is undefined behavior. */
+    logStatus?: Humanloop.LogStatus;
     /** Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair. */
     sourceDatapointId?: string;
     /** The ID of the parent Log to nest this Log under in a Trace. */

src/api/resources/tools/client/requests/ToolLogRequest.ts

@@ -2,6 +2,8 @@
  * This file was auto-generated by Fern from our API Definition.
  */
 
+import * as Humanloop from "../../../../index";
+
 /**
  * @example
  *     {}
@@ -31,4 +33,6 @@ export interface ToolLogUpdateRequest {
     startTime?: Date;
     /** When the logged event ended. */
     endTime?: Date;
+    /** Status of a Log. Set to `incomplete` if you intend to update the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If not provided, observability will pick up the Log as soon as possible; switching from specified to unspecified is undefined behavior. */
+    logStatus?: Humanloop.LogStatus;
 }

src/api/resources/tools/client/requests/ToolLogUpdateRequest.ts

@@ -32,6 +32,8 @@ export interface EvaluatorLogResponse {
     source?: string;
     /** Any additional metadata to record. */
     metadata?: Record<string, unknown>;
+    /** Status of a Log. Set to `incomplete` if you intend to update the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If not provided, observability will pick up the Log as soon as possible; switching from specified to unspecified is undefined behavior. */
+    logStatus?: Humanloop.LogStatus;
     /** Identifier of the evaluated Log. The newly created Log will have this one set as parent. */
     parentId?: string;
     /** Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair. */

src/api/types/EvaluatorLogResponse.ts

@@ -36,6 +36,8 @@ export interface FlowLogResponse {
     source?: string;
     /** Any additional metadata to record. */
     metadata?: Record<string, unknown>;
+    /** Status of a Log. Set to `incomplete` if you intend to update the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If not provided, observability will pick up the Log as soon as possible; switching from specified to unspecified is undefined behavior. */
+    logStatus?: Humanloop.LogStatus;
     /** Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair. */
     sourceDatapointId?: string;
     /** The ID of the parent Log to nest this Log under in a Trace. */
@@ -62,6 +64,4 @@ export interface FlowLogResponse {
     traceChildren?: Humanloop.LogResponse[];
     /** Flow used to generate the Log. */
     flow: Humanloop.FlowResponse;
-    /** Status of the Trace. When a Trace is marked as `complete`, no more Logs can be added to it. Monitoring Evaluators will only run on completed Traces. */
-    logStatus?: Humanloop.LogStatus;
 }

src/api/types/FlowLogResponse.ts

@@ -58,6 +58,8 @@ export interface PromptLogResponse {
     source?: string;
     /** Any additional metadata to record. */
     metadata?: Record<string, unknown>;
+    /** Status of a Log. Set to `incomplete` if you intend to update the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If not provided, observability will pick up the Log as soon as possible; switching from specified to unspecified is undefined behavior. */
+    logStatus?: Humanloop.LogStatus;
     /** Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair. */
     sourceDatapointId?: string;
     /** The ID of the parent Log to nest this Log under in a Trace. */

src/api/types/PromptLogResponse.ts

@@ -32,6 +32,8 @@ export interface ToolLogResponse {
     source?: string;
     /** Any additional metadata to record. */
     metadata?: Record<string, unknown>;
+    /** Status of a Log. Set to `incomplete` if you intend to update the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If not provided, observability will pick up the Log as soon as possible; switching from specified to unspecified is undefined behavior. */
+    logStatus?: Humanloop.LogStatus;
     /** Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair. */
     sourceDatapointId?: string;
     /** The ID of the parent Log to nest this Log under in a Trace. */