K6 Dashboard
You set up a k6 dashboard by turning on the built-in web view or sending test metrics to a charting tool. This setup shows live request rates, error counts, and response times in your browser. Many teams share one host or metric store for these test runs. Broad host roles or shared keys let anyone run heavy tests or read raw logs. How a k6 dashboard works The load test tool runs scripts that send fake traffic to your app. As the script runs, the engine tracks timing and failure numbers every
GitLab Security Dashboard: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You set up a k6 dashboard by turning on the built-in web view or sending test metrics to a charting tool. This setup shows live request rates, error counts, and response times in your browser. Many teams share one host or metric store for these test runs. Broad host roles or shared keys let anyone run heavy tests or read raw logs.
How a k6 dashboard works
The load test tool runs scripts that send fake traffic to your app. As the script runs, the engine tracks timing and failure numbers every second. You can view these numbers in two main ways.
First, the tool can start a local web server during the test run. This local server streams live charts to your browser over a local port. When the test ends, it can save a static HTML report file. Teams use this local view for quick checks on a single machine.
Second, the tool can push metric streams to an external time-series database. A charting app then reads that database to build a shared k6 dashboard. This path lets whole teams compare past runs and watch long tests together. The test runner needs a write key to send data to the store. Viewers need a read role in the charting app to see the panels.
How to set up metric storage and team roles
Start by picking where your test metrics will live after each run. For quick local checks, turn on the built-in web output before you start. The tool opens a port on your machine and renders the charts live. Save the output file if you want to share the results later.
For team views, set up a metric database and a charting app first. Create a scoped write key in the metric store just for test runners. Put that key in your test runner environment so it can push metrics. Next, create viewer roles in the charting app for your developers. Link the charting app to the metric store using a read-only database user. Build panels that show request rate, error rate, and tail latency side by side.
GitLab Security Dashboard: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native dashboard setups solve and where they fall short
A native k6 dashboard gives clear visibility into how your app handles stress. Teams spot slow endpoints fast and see exact failure spikes during a run. Role settings in the charting app also keep viewers from deleting shared panels. Scoped write keys stop test runners from reading old metrics in the database.
Still, dashboard roles only control who views charts after metrics leave the runner. They do not control who can start a test on a shared host. They also do not check what the test script sends in flight. Test scripts often use real API keys or query live databases during runs. If a script logs failed responses, raw emails or card numbers can leak. Standard login roles decide who starts a session, not what individual commands do.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
Can I view a k6 dashboard without an external database?
Yes, the tool includes a built-in web dashboard that runs on your machine. It streams live metrics to a local browser port and exports HTML reports.
What metrics should appear on a primary load test board?
Track requests per second, error rate percentage, and high-percentile response times first. These three numbers show when your app starts to slow down or fail.
Why do load test logs create data privacy risks?
Test scripts often print full response bodies when an HTTP request fails. Those responses can contain real emails, phone numbers, or card numbers from test databases.