Support OpenTelemetry for the ToolHive Operator
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
We have OpenTelemetry support inside of ToolHive that allows you to get traces and metrics information regarding usage of the underlying Proxy and the MCP server, but we do not have OpenTelemetry support for the Operator itself.
This ticket covers that support and ensuring that when configured, the Operator emits metrics about itself and any underlying MCP servers that it manages to an OTel collector.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing OpenTelemetry support for ToolHive's Proxy and MCP server, then trace how the Operator manages underlying MCP servers and accepts configuration. Done means the configured Operator emits its own metrics and metrics for managed MCP servers to an OpenTelemetry collector.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100