Skip to content

Feature: Dashboard panel — log hit table with configurable metadata columns #289

Description

@SemoTech

Summary

Add a custom dashboard panel type that shows individual log rows (not aggregations) with user-configurable metadata columns, so teams can pin an operational “hit list” on a dashboard (e.g. WAN access: host, source IP, HTTP status, GeoIP city/country).

Motivation

Today’s custom dashboard panels are either aggregations or a minimal live stream:

Panel Limitation
Time series / single stat / Top-N Counts / rates only — no per-hit rows
Live log stream Rows exist, but only time / level / service / message — no metadata columns
Log Search (Explore) Supports custom metadata columns (http_host, client_ip, geo.city, …) but cannot be embedded on a dashboard

For access-log / edge use cases (Caddy, nginx, API gateways), operators want a dashboard table like:

Time Host Client IP Status Location
19:17:42 rmm.example.com 174.x.x.x 200 Las Vegas, NV, US

That data is already in log metadata (and after GeoIP pipelines, under geo.*). Search already knows how to render it; dashboards do not.

Proposed panel: log_table (name flexible)

Config (suggested):

  • title
  • projectId (or inherit dashboard project)
  • service filter (optional)
  • levels[] (optional)
  • timeRange / refresh (e.g. 1h / 24h / live)
  • maxRows (e.g. 25–100)
  • columns: string[] — metadata keys with the same semantics as Log Search custom columns (exact key first, then dot-path, e.g. http_host, client_ip, http_status, geo.city, geo.subdivision, geo.countryCode)
  • Optional: include built-in columns (time, level, service, message) toggles

Behavior:

  • One row per log event (newest first)
  • Cells resolve via the same resolveMetadataPath rules as Log Search
  • Click-through to log Details / Context (nice-to-have)
  • Respect project / org tenancy like other panels

Alternatives considered

  • Using Live log stream — insufficient (no metadata columns)
  • Using Top-N — wrong shape (counts by service/error only)
  • Asking users to leave the dashboard for Explore — works, but breaks “one screen” ops dashboards

Related

Environment note

Self-hosted; Caddy WAN logs already enrich metadata with http_host, client_ip, http_status, and pipeline geo — only the dashboard surface is missing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions