Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add timestamp to logs

Aperta
  • Qualcosa non va?
#3,708 4 commenti 1 reazione 2 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@JerryNixon ci sta già lavorando.

Dal 8/7/2026.

  • #3709 di @copilot-swe-agent — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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'

Lingua principale
C#
Stelle
1.5k
Fork
371
Merge medio
7g 5h
PR unite (30g)
8

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Azure/data-api-builder

Tutte le issue di Azure/data-api-builder

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.