Actions9
- Prompt Actions
- Monitoring Actions
- Dataset Actions
Overview
This node interacts with the Basalt API to log output data related to prompts for monitoring purposes. It is useful for tracking and analyzing prompt executions by sending detailed log information such as prompt slug, output, input, version, timing, token usage, cost, and additional metadata. Practical applications include monitoring AI prompt performance, debugging prompt outputs, and collecting usage statistics for optimization.
Use Case Examples
- Logging the output of an AI prompt execution with associated metadata for performance tracking.
- Sending detailed prompt execution logs including input, ideal output, and timing information for monitoring and analysis.
Properties
| Name | Meaning |
|---|---|
| Prompt Slug | The slug identifier of the prompt to log. |
| Output | The output data of the prompt to be logged, in JSON format. |
| Log Options | Additional optional details about the prompt execution such as name, version, tag, input, ideal output, start and end times, token counts, cost, and metadata. |
| Request Options | Settings to control request behavior such as batching, SSL certificate validation, proxy usage, and timeout duration. |
Output
JSON
slug- The slug identifier of the prompt logged.output- The output data of the prompt logged.name- The name of the trace or log entry, if provided.version- The version of the prompt, if provided.tag- The tag associated with the prompt, if provided.input- The input data to the prompt, if provided.idealOutput- The ideal or expected output of the prompt, if provided.startTime- The start time of the prompt execution, if provided.endTime- The end time of the prompt execution, if provided.inputTokens- The number of input tokens processed, if provided.outputTokens- The number of output tokens generated, if provided.cost- The cost associated with the prompt execution, if provided.metadata- Additional metadata related to the prompt execution, if provided.
Dependencies
- Basalt API
Troubleshooting
- Ensure the Basalt API credentials are correctly configured to avoid authentication errors.
- Verify that the prompt slug is correctly specified to prevent logging failures.
- Check network connectivity and proxy settings if requests fail or time out.
- If SSL certificate validation errors occur, consider enabling the option to ignore SSL issues, but be aware of security risks.