Add to dashboard action for the trace search RED charts

Abierto
#3,177 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
65/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
clickhouse, react, typescript

Línea de trabajo

Start by examining the existing RED tile components and the 'add to dashboard' action pattern in the codebase, likely in packages/app/src/components/Search/traceRedMetrics.ts. Understand how chart configs are built and serialized. Check the heatmap view for similar functionality. The goal is to add an action button that captures the current filter and config to create a dashboard tile.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Context

PR #2826 adds RED metrics (Throughput, Errors, Duration) to the trace search results view. Each tile is a chart card built from the same base config the search histogram uses, so the aggregations already honor the active WHERE filter and the selected time range.

Dashboard tiles elsewhere in the app offer an action to save a chart to a dashboard. The trace search RED tiles do not, so a user who spots something in one of these charts has to rebuild the same aggregation by hand in a dashboard or in the chart explorer.

Proposal

Offer an "add to dashboard" action on each RED tile that carries the tile's config (select, display type, number format, granularity) plus the active search filter, so the saved tile matches what the user was looking at.

The configs are already pure builders in packages/app/src/components/Search/traceRedMetrics.ts, which is what a save action would serialize.

Notes

Worth checking what the heatmap view should do here as well, since it is the same switch on the same area.

Lenguaje dominante
TypeScript
Estrellas
10.1k
Forks
527
Merge medio
1 d 20 h
PR fusionados (30 d)
186

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ClickHouse/ClickStack

Todos los issues de ClickHouse/ClickStack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.