Logs Explorer

Search production logs by service, level, request, environment, and time while keeping latency and error context close. The screen connects Live tail and Search so platform and engineering teams can find the “Run search” action while checking events/min and errors.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as api-gateway · 42% and worker · 24%, rather than an empty visual shell.

Logs Explorer
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Run search

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Platform and engineering teams need a clear “Run search” action without losing sight of events/min, errors and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Run search is clearly available where the task happens.
  • Main view: Live tail keeps the starting point obvious.
  • Connected view: Search supplies nearby context.
  • Metric: Events/min is visible with a meaningful value.
  • Another signal: Errors helps people judge what to do next.
  • Representative record: api-gateway · 42% makes the example specific.
  • Second record: worker · 24% shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading live tail without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for search; clarify who can continue.
  • Success after choosing Run search; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Live tail → Search → Run search → Review outcome

Patterns used

Analytics, Live tail, Search, Saved, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare api-gateway · 42% with worker · 24%. Make events/min clear, then use errors to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Run search” action. The happy path alone is not enough.

Related UI examples: Deployment Console, Feature Flags, API Dashboard.

Start from this in Figr

Design a logs explorer screen for our existing software product. Use our real design-system tokens, components and product language. Show Live tail and Search, include believable records such as api-gateway · 42%, and make run search easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr