Logs

Review prompt activity logs, inspect request details, and check inputs and responses for individual runs

Prompt logs help you inspect how a prompt ran after you tested it or invoked it through runtime paths. Use the logs view to review individual runs, inspect request details, and check the inputs and response for a selected completion.

Accessing activity logs

Open the prompt in the editor.

Click Activity Logs in the header.

Fetch Hive opens the prompt-specific activity log view for that prompt.

The logs page includes a paginated table of runs on the left and a detail panel for the selected run on the right.

You can also use Refresh logs to reload the table or Editor to go back to the prompt editor.

What's tracked

The log table shows summary data for each run, including:

• Owner

• Completed time

• Provider

• Model

• Charge type

• Status

• Provider charge

• Total tokens

• Duration

When you select a run, the detail panel gives you additional views:

• Response for the generated output

• Request for model settings and usage details

• Inputs for the values passed into the prompt

If the selected run failed, the detail panel shows the error message. Some providers can also add provider-specific metadata. For example, Perplexity runs include a citations view.

Traces

The prompt activity log view focuses on run details such as Response, Request, and Inputs.

Start with Response, then check Request and Inputs to understand how the prompt ran.

Filtering and search

The prompt activity log view includes pagination, row selection, and Refresh logs.

This view does not include dedicated filter or search controls.

Notes

• The log detail view includes a share link action for the selected run.

• A selected run can also include a discussion thread so your team can comment on the run in context.

• Use the prompt editor for iteration and the logs view for after-the-fact inspection.

See also: Creating and Editing and Run with API