Side view of the BMW iX3 Neue Klasse with illuminated door handles

Measure first. Then save.

Grafana at the November Hackathon in Munich

No V8 in the Neue Klasse. The sound was nostalgia.

7:10Munich

iX3 Neue Klasse

-2°

Cabin

Monday, 7:10 am.
Munich, minus 2 degrees.

One tap on Preheat. What happens behind it?

1Tap in the app

3API requests

2Backend services

4Database queries

37Log lines

Example values, not measured. Traces show how many it is for you.

The heater runs.
So does the bill.

While the car heats, the app polls its status. Every poll costs requests, CPU, log lines and traffic.

Weights picked freely, just for playing. Real numbers come from your data.

App polls status every30 s

Log lines per request10

Payload per response50 KB

Heat index, reference = 100

100

Where we can help

Tap a card to jump to its slide.

What the jury wants to see comes from measurements

Teams bring

Cost per requestMetrics and traces per service in one dashboard

Cost per log statementLog volume per service and level, priced

Before and afterTime comparison in a dashboard, flame graph diff, k6 runs

Adoption planDashboards and alerts as code keep the gain alive

Judging criteria: tap one

Let's talk.

Your stack

Grafana Cloud with all features is ready. We show you where to start.

Starter kit

Dashboards for cost per request, cost per log and before/after.

On-site mentoring

A contact per challenge area. The focus is measuring.

Jury

On request, with an eye on impact and demo quality.

Where do you look first when a request is slow?