Monitor Sherlock consumption and events on CloudFerro Cloud

After trying models or changing project resources, you may want to see which models processed tokens and which actions were recorded. Sherlock provides usage views in Overview and Consumption, and an activity list in Events history.

Select your project using the project guide before following these checks. The figures show example records; your values depend on the activity and period selected.

Compare model usage in Overview

  1. Open Overview → Project overview.

  2. Find Model usage ranking and set Period to the dates you want to inspect.

  3. Select Input tokens or Output tokens to compare that category across models.

Model usage ranking with Input tokens and Output tokens tabs

The ranking groups token usage by model for the selected period.

The ranking measures usage. A model with more tokens is not necessarily more accurate or more suitable for your task.

Inspect Consumption

  1. Open Consumption in the left menu.

  2. Set Period on the Tokens consumption panel.

  3. Read the chart together with the table beneath it. The table separates Model name, Input tokens, and Output tokens.

Tokens consumption chart and per-model token table

The chart shows activity over time; the table reports input and output tokens for each listed model.

If the period does not cover your request, widen the date range. Check the selected project as well when the expected model is absent. These screens display token counts; they do not by themselves evaluate answer quality.

Find and export project events

  1. Open Events history.

  2. Set Period to include the action you want to inspect.

  3. Read Date, Event, Principal, and Event description to identify the recorded action and who performed it.

  4. Select Export CSV when you need a CSV copy of the event records.

Events history with a service-key creation record and Export CSV

The example records an API-key creation event. The principal identifies the actor for the recorded action.

A resource event confirms the recorded action. For example, key creation does not demonstrate that an application has successfully made an API request; check the application’s response separately.

What to do next

Still need help?
If this article doesn’t answer all of your questions, our support team will do their best to help you.
Contact support