Capturing Bugzooka Usage metrics

[Balatripura587]

Description:

Feature to add metrics collection from Bugzooka to understand its usage metrics across teams (Jira Issue Tracker ). As a part of this feature the following are implemented:

• Events are emitted to OpenSearch for every BugZooka command
• Each event would capture command name, team, user, success/failure, duration, token usage, retry counts, and command-specific metadata
• To achieve this , we use a background daemon thread with an in-memory queue which periodically fetches events from the queue and performs a bulk write to the ES server.

For each command the following is the json event structure emitted to the ES server:
{
"command": "auto_analyze",
"trigger_type": "automatic",
"channel_id": "C12345",
"user_id": "U12345",
"team": "OCP-PerfScale",
"timestamp": "2026-05-19T10:30:00+00:00",
"success": true,
"error_message": null,
"error_type": null,
"duration_ms": 12500,
"retry_count": 0
}

In addition to these common fields, each command emits command-specific metrics specific to its workflow — such as total_tokens and tool_calls_count for analyze_pr, failure_type and used_llm for auto_analyze, etc.

Testing

• Tested Locally and uploaded event to QE ES Server

[mohit-sheth]

lgtm