Developer Tools Dashboard Design

Developer tools dashboard design is the design of the usage and monitoring screens developers open to check whether their integration is healthy: request volume, error rates, latency, rate limits and spend. Gestures designs these dashboards so every chart leads to the requests behind it, and every number states its time range, time zone and the moment it was last updated.

Developer tools dashboard design with Gestures costs $2,250 per week, $4,000 for a two-week sprint or $7,500 per month for ongoing work across products and metered plans. Every plan covers strategy, design and review on a scope agreed before work starts.

Start with the four golden signals

Google's Site Reliability Engineering book names four golden signals for monitoring a user-facing system: latency, traffic, errors and saturation. A developer tools dashboard turns each signal into something a customer can act on in their own integration.

Golden signals mapped to a developer tools usage dashboard
SignalWhat the developer seesBreakdown that matters
TrafficWhat the developer seesRequests per minute or per dayBreakdown that mattersBy endpoint, API key and environment
ErrorsWhat the developer seesThe share of failed requestsBreakdown that mattersBy status code and error type, with client errors separated from server errors
LatencyWhat the developer seesResponse time percentilesBreakdown that mattersBy endpoint, with failed requests measured on their own
SaturationWhat the developer seesHow much of each rate limit and quota is in useBreakdown that mattersBy key and by limit, with the time each limit resets

Show latency as percentiles, not averages

An average hides the slow requests developers complain about. The SRE book describes a web service with an average latency of 100 ms at 1,000 requests per second where 1% of requests might easily take 5 seconds, so we design latency charts around percentiles and keep the average out of the headline.

  • p50, p95 and p99 on the same chart, each labelled at the end of its line.
  • A histogram for the selected window, showing how many requests fell into each duration range.
  • Latency of failed requests on its own line, because a slow failure costs more than a fast one.
  • The endpoint table sorted by p95, so the slowest routes rise to the top.

Every chart opens the requests behind it

A spike on a chart helps only when one click shows the requests that caused it. Gestures designs every chart point as a link into the request log, with the time window, endpoint and status already applied as filters.

From a developer dashboard chart to the cause
StartClickLands on
A spike in the error rateClickThe spikeLands onThe log for that minute, filtered to the failing status codes
A slow endpointClickThe endpoint rowLands onThe slowest requests for that endpoint, sorted by duration
A rate limit close to fullClickThe limit barLands onThe keys and endpoints using most of the limit
Spend above the forecastClickThe spend lineLands onUsage by key, project and metered product

Time ranges, time zones and freshness on every chart

Developers compare dashboard charts with their own logs, so each chart states its time zone, its aggregation interval and when its data last arrived.

  • One switch between UTC and local time that changes charts and logs together.
  • The bucket size shown beside the range, such as one-minute buckets for the last hour.
  • Deploys, incidents and API version changes marked on the time axis.
  • A URL that keeps the range and filters, ready to paste into an incident channel.
Dashboard components including input fields, buttons, menus and activity lists.
Inputs, menus and activity lists drawn for dense dashboards, a Gestures interface study on Dribbble.

Rate limits and spend before they turn into errors

A developer should learn about a limit from the dashboard, not from a failing request, so each usage state has its own dashboard response.

Usage states and the developer dashboard response for each
Usage stateDashboard response
Well within a limitDashboard responseA usage bar with the current amount, the limit and the reset time
Approaching a limitDashboard responseA notice on the dashboard and by email, at a level the developer sets
At a limitDashboard responseThe count of rejected requests, the endpoints affected and the change that raises the limit
Spend above budgetDashboard responseThe budget, the forecast to the end of the billing period and the keys driving it

Developer tools dashboard design scope and cost with Gestures

Developer tools dashboard design with Gestures costs $2,250 per week, $4,000 for a two-week sprint or $7,500 per month for ongoing work. The plan depends on how many monitoring views are in scope.

Developer tools dashboard design scopes and the plan that fits each
ScopeWhat it coversPlan
API usage overviewWhat it coversTraffic, errors and latency by endpoint, key and environmentPlanWeekly sprint, $2,250 per week
Limits, usage and spendWhat it coversRate limits, quotas, metered usage, budgets and noticesPlanWeekly sprint, $2,250 per week
Monitoring with drill-downWhat it coversCharts linked to the request log, time controls and event markersPlanTwo-week sprint, $4,000
A full developer analytics areaWhat it coversAll dashboards, shared charts and tables, and new products as they launchPlanMonthly partnership, $7,500 per month

For an overview of developer products, see our developer tools design page. API keys, webhooks, environments and versions are covered by developer tools product design. The request log behind these charts is a table with filters, which our dashboard UX audit covers.

Most chosen

Monthly partnership

$7,500$10,500USD / month

Studio $7,500 + Growth $3,000 / month

For a developer product that adds endpoints, regions and metered products. Set the current focus each month and review what needs attention next.

Strategy · Design · Review

Work starts within 1 day of payment.

Cancel anytime.

Start your project

Weekly sprint

$2,250$4,000USD / week / 2 weeks

+ $3,000 / month for Growth

For one dashboard, such as API usage, the latency view or rate limits and spend. Agree the metrics your platform records before starting.

Save $500 with two weeks: $4,000 instead of $4,500.

Strategy · Design · Review

Work starts within 1 day of payment.

Cancel anytime.

Start your project

Add Growth to a studio plan

SEO, content strategy and content production, alongside your design team. Growth is billed monthly. Cancel anytime.

+$3,000 / month

See Full Pricing

Compare all plans or book a call to agree the first dashboard.

Questions about developer tools dashboard design

How much does developer tools dashboard design cost?

Developer tools dashboard design with Gestures costs $2,250 per week, $4,000 for a two-week sprint or $7,500 per month. One usage overview fits a weekly sprint. See pricing for every plan.

Do you design with our charting library?

Yes. We design within the limits of the charting library your engineers use, and note any chart that needs a custom component before it is built.

Should the dashboard replace a tool such as Grafana?

No. A customer-facing dashboard shows each developer their own integration, while your internal monitoring tools serve your operations team. We design the customer-facing side.

How do you design for very high request volumes?

We design aggregated charts, sampled log views that say they are sampled and server-side filters, so the dashboard stays fast at any volume.

Can the dashboard show status and incidents?

Yes. Incidents from your status page can appear as markers on charts and as a notice on the dashboard, so developers know whether a problem is theirs or yours.

What do you need from our team to start?

A sandbox account with real traffic, the list of metrics your platform emits, any usage screens you have today and an engineer who knows the data pipeline.

Do you design the rest of the developer console?

Yes. Keys, webhooks, environments and destructive actions are covered on our developer tools product design page.

Send us the chart developers screenshot in support tickets

Share the dashboard view that appears most often in support conversations, and what developers ask about it. We will reply with the monitoring view we would redesign first and whether Gestures fits the work. The wider service is on our product design page.