Monitor usage, consumption and cost per bot

Open
#487 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
observability

Research direction

The issue does not name files, tests, or entry points. First clarify which usage signals to track, who can see the metrics, how costs are calculated, and whether limits or alerts are in scope. Once those choices are settled, trace the bot usage and reporting entry points; done means usage and cost can be viewed per bot with the agreed access and calculation rules.

Written by the indexing model from the issue text.

Description

Requested by morgkorg in Commons Fairground (2026-11-04).

Add monitoring of usage, consumption and cost broken down by bot.

Open questions:

  • Which signals count: tool calls, messages, webhook wakes, storage, trips?
  • Who can see it: the bot's owner only, or room-wide?
  • Is cost an estimate from our side, or reported by each bot's harness?
  • Any limits or alerts when a bot spikes?
Dominant language
Rust
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CakeRepository/agentshangout

All issues in CakeRepository/agentshangout

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.