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

Add timestamp to logs

Abierto
  • ¿Algo no está bien?
#3,708 4 comentarios 1 reacción 2 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@JerryNixon ya está trabajando en esto.

Desde el 8/7/2026.

  • #3709 de @copilot-swe-agent — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

cli cri telemetry

tl;dr Add date / time logging to entries output. Use UTC for consistency and optionally make this a flag.

Currently when running DAB, especially in development, I get logs like this:

info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Request starting HTTP/1.1 GET http://localhost:5000/graphql/service-worker.js - - -
dbugdbug: Azure.DataApiBuilder.Core.AuthenticationHelpers.ClientRoleHeaderAuthenticationMiddleware[0]
bfa3a6ee-7f10-41ba-8899-2e0990428aa0 AuthN state: Anonymous. Role: Anonymous. Scheme: UnauthenticatedAuthentication
: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[3]
The request path does not match the path filter
dbug: Microsoft.AspNetCore.Routing.Matching.DfaMatcher[1001]
2 candidate(s) found for the request path '/graphql/service-worker.js'
dbug: Microsoft.AspNetCore.Routing.Matching.DfaMatcher[1005]
Endpoint 'Hot Chocolate GraphQL Pipeline' with route pattern '/graphql/{**slug}' is valid for the request path '/graphql/service-worker.js'

This is a fraction of what is logged for a request. However, trying to determine which new entries have occurred is hard and slow, even with AI LLM help. It would be nice to mark each of these with a timestamp, as mocked here.

2026/07/07 08:01:01.344 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Request starting HTTP/1.1 GET http://localhost:5000/graphql/service-worker.js - - -
2026/07/07 08:01:01.345 dbugdbug: Azure.DataApiBuilder.Core.AuthenticationHelpers.ClientRoleHeaderAuthenticationMiddleware[0]
bfa3a6ee-7f10-41ba-8899-2e0990428aa0 AuthN state: Anonymous. Role: Anonymous. Scheme: UnauthenticatedAuthentication
: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[3]
The request path does not match the path filter
2026/07/07 08:01:01.347 dbug: Microsoft.AspNetCore.Routing.Matching.DfaMatcher[1001]
2 candidate(s) found for the request path '/graphql/service-worker.js'
2026/07/07 08:01:01.348 dbug: Microsoft.AspNetCore.Routing.Matching.DfaMatcher[1005]
Endpoint 'Hot Chocolate GraphQL Pipeline' with route pattern '/graphql/{**slug}' is valid for the request path '/graphql/service-worker.js'

Lenguaje dominante
C#
Estrellas
1.5k
Forks
371
Merge medio
9 d 2 h
PR fusionados (30 d)
10

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 Azure/data-api-builder

Todos los issues de Azure/data-api-builder

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.