Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[FAQ] Module 4 Homework Q3: How do I find the request metric, its log and its trace in Grafana?

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#419 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
75/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
prometheus
Área
documentation, observability

Línea de trabajo

Comienza con la estructura de FAQ existente del repositorio y coloca esta respuesta de Module 4 Homework Q3 en la entrada de FAQ correspondiente. Conserva los pasos de Grafana Explore, los ejemplos de nombres de Prometheus y las referencias a Grafana, OpenTelemetry y Explore. Se considera terminado cuando la pregunta explica cómo encontrar la métrica, el log y el trace, y la respuesta se publica con su checklist cumplida.

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

Descripción

faq-proposal
Course

ai-dev-tools-zoomcamp

Question

How do I find the request metric for a lookup in Grafana, and check that its log and trace also appear?

Answer

Use Grafana's Explore page (compass icon in the left menu). Choose a data source at the top: your metrics store (for example Prometheus), your logs store (for example Loki) or your traces store (for example Tempo). Set the time range to cover when you made the request.

1. Find the metric

Select the metrics data source and open the metrics browser. Search for part of the metric name, such as http_server, rather than the exact name from your app's console output. OpenTelemetry names are often translated when stored. In Prometheus, for example:

  • dots become underscores
  • the unit is added as a suffix (s becomes _seconds)
  • a histogram is split into _bucket, _count and _sum series

So http.server.request.duration is stored as http_server_request_duration_seconds_count. Attribute names change the same way, so http.response.status_code becomes http_response_status_code. Query the _count series and group it by route and status code to see your request.

2. Check the log

Select the logs data source, filter by your service name, and search for text from the request (for example part of its URL). Expand the log line. If your app adds trace context to its logs, you'll see a trace ID.

3. Check the trace

If the logs data source links to traces, click the link next to the trace ID. Otherwise, copy the trace ID into the traces data source's query, or search by service name. New traces can take a few seconds to become searchable, so re-run the search if it's empty at first.

If one of the three doesn't appear, check that your app exports that signal and that your telemetry pipeline routes it to the matching data source.

References:

Checklist
  • I have searched existing FAQs and this question is not already answered
  • The answer provides accurate, helpful information
  • I have included any relevant code examples or links
Lenguaje dominante
Python
Estrellas
7
Forks
19
Merge medio
9 d 22 h
PR fusionados (30 d)
10

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 DataTalksClub/faq

Todos los issues de DataTalksClub/faq

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.