getsentry / getsentry/sentry

Organization-wide API key usage & rate-Limit visibility dashboard

Open
#104,312 4 comments 0 reactions 0 assignees View on GitHub
API Platform Feature Product Area: APIs Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

A customer would like to request a feature that allows organizations to view all API activity broken down by API key or integration. In large organizations, multiple teams may create and use API keys, and there is no centralized visibility into how those keys are being used. Because the rate limiter groups requests by “caller identity,” it’s also unclear whether one team’s workload can cause another team’s key to be rate-limited. This lack of insight makes it difficult to debug issues or ensure responsible usage across teams. A dashboard showing request volume, errors, and rate-limit events per key would resolve this. It would also help identify leaked, misconfigured, or overused keys quickly. Overall, this feature would give organizations the transparency they need to manage API usage at scale.

ZD ticket for more context: https://sentry.zendesk.com/agent/tickets/167857

### Solution Brainstorm

_No response_

### Product Area

APIs

Contributor guide

Open the contributing guide

Research direction

Start with the API product area described in the issue and review the linked Zendesk ticket for additional context. Define the dashboard scope around request volume, errors, and rate-limit events per API key or integration, and clarify how caller identity affects shared rate limits; completion should provide that organization-wide visibility.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
analytics, api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.