The setting
makes software for watching how computer systems are running. is its hosted platform for collecting, searching, displaying and alerting on metrics, logs, traces and profiles, so customers do not run their own tools.
A fresh entity catalog is moving the service an investigator is about to open.
Automatic discovery keeps the list current, while a stable selection keeps the investigation on its intended service.
Who you’d be doing this for
“I found the service, clicked, and landed somewhere else. Then I had to go back and check whether I'd misread the name.”
Samir Nejad · Site Reliability Engineer · a character in this brief
Uses the entity catalog to find services outside their usual area during an investigation.
What is at stake
Four of six engineers opened the wrong service when a catalog reordered. You have to preserve their place without hiding newly discovered services.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fresh ordering vs stable targets
- automatic updates vs explicit refresh
- visible change vs quiet keyboard navigation
- release scope vs interaction consistency
Why Grafana
Knowledge Graph turns automatically discovered services into an entry point for engineers who do not already know the system.
Written with these in mind
Not your kind of problem? 31 more at Grafana, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Grafana. They are listed as sources, not as openings.
- Senior Product Designer, Knowledge Graph | Germany | Remote (opens in a new tab)
- Senior Product Designer, Knowledge Graph | Sweden | Remote (opens in a new tab)
- Senior Product Designer, Knowledge Graph | Ireland | Remote (opens in a new tab)
- Senior Product Designer, Knowledge Graph | Spain | Remote (opens in a new tab)
- Senior Product Designer, Knowledge Graph | Canada | Remote (opens in a new tab)
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on moving faster inside a system others depend on.
Indexing success falls to 99.6% during scheduled node replacements, delaying up to 18,000 catalog updates.
You must weigh uninterrupted writes against the safeguards that keep the cluster safe to operate.
Only 46% of failed-run investigations now reach model context, down from 58%.
You have to weigh faster error scanning against enough lineage context to diagnose the right model.
The same setting, from another role
Each is set around Grafana’s Grafana Cloud, written for a different role. They’re separate briefs, not the same scenario.
SRE leaders are registering for events but taking follow-up meetings at uneven rates.
You must decide whether AI recommends the next test from linked evidence or leaves competing interpretations for strategist review.
Alerting customers are spending incident time reconstructing browser failures from disconnected evidence.
You must choose which browser-investigation story earns a scarce technical follow-up without overpromising the result.
Renewal-stage expansion acceptance fell from 18% to 9% after pricing conversations.
You must choose how directly the campaign addresses metered investigation costs without weakening the managed-service case.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make complicated, high-stakes systems feel simple to navigate without quietly removing the protections people depend on.
Cross-surface tasks take a median of 7.4 navigation actions, and support data ties the confusion to delayed production changes.
You have to decide how developers move between workflows, evaluations, connections and deployed agents before deep links and permissions migrate and set that path.
Admins stall at permission validation and destination selection, and many misread what happens when a connection is committed.
You have to settle the interaction model now, because changing it after rollout is costly.
In audit samples, interviewers saw context that some customers do not permit, and the migration runs one way.
You have to keep scorecards structured and auditable while narrowing what interviewers see.
