Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tool usage page: fix time range claims and add utility

Open Beginner friendly
  • Is something wrong?
#1,185 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Edit docs/connector-gateway/tool-usage.mdx, starting with the listed lines and the current page structure. Update the time-range and UI wording, explain the admin questions the page helps answer, add the specified usage-detail links, and move troubleshooting into its own section. Include the metering prerequisite once #1179 confirms it; done when the recommendations are reflected accurately in the page.

Written by the indexing model from the issue text.

Description

bug documentation needs-triage

Part of #1175. Page: docs/connector-gateway/tool-usage.mdx

Problems

  1. The time range claim is misleading (lines 12-13). The page implies the time range controls everything on the screen. The options are Last 24h, Last 7d, and Last 30d, with 24h the default. They drive the tiles and the tables, but the Tool calls trend chart always shows Last 3 months, whatever range is selected.
  2. The page doesn't help the reader answer anything. It lists what's on screen, but not what an admin can learn from it, such as which connectors are unused, where adoption is growing, or which tools are called most. It doesn't mention drill-down either. Connector names in the tables aren't links, and per-user detail is only on each connector's Activity tab.
  3. Troubleshooting is mixed into the body (lines 20-22), and it leaves out the most likely cause of an empty screen: the metering prerequisite tracked in #1179.
  4. Minor:
    • The console title is Tool Usage (title case). Match it when bolding the UI label.
    • Line 15 says "integrations". Use "connectors".

Recommendations

  • List the time range options and the default, and state that the chart's window is fixed at 3 months
  • Document the tiles (Tool calls, Active connectors, Top connector) and the table columns (By connector: Connector, Calls, Share; By tool: Tool, Connector, Calls, Share)
  • Frame the page around two or three admin questions it answers
  • Link to the connector Activity tab for per-user and per-call detail
  • Mention that users see their own usage on the Usage tab in the User experience
  • Move lines 20-22 into a Troubleshooting section, and add the metering prerequisite once #1179 confirms it
Dominant language
TypeScript
Stars
4
Forks
3
Avg merge
22h
Merged PRs (30d)
37

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 stacklok/docs-website

All issues in stacklok/docs-website

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.