Risorse · 82

Report affidabili: fusi orari, chiusure ed eventi tardivi

Evitare giorni spostati, doppi conteggi e confronti incoerenti fra esportazioni e dashboard.

Aggiornato · 7 min

Stazione di comunicazioni satellitari senza personale al crepuscolo Illustrazione editoriale generata con IA

Obiettivi di questa guida

  • Distinguere istanti e giorni aziendali
  • Fissare i confini
  • Gestire gli arrivi tardivi
  • Confrontare perimetri uguali
  • Provare la ricostruzione

Verifica rapida

  • Basta convertire tutto in UTC?
  • Perché il totale cambia dopo l’export?
  • Un evento tardivo è un duplicato?

Metodo passo passo

  1. 1

    Distinguere istanti e giorni aziendali

    Separare evento, ricezione, modifica e data di attività. UTC non definisce da solo il giorno di un negozio. PostgreSQL converte timestamp with time zone in UTC senza conservare il nome del fuso originario: registrarlo separatamente quando necessario.

    Risultato: dizionario delle date e dei fusi.

  2. 2

    Fissare i confini

    Usare inizio incluso e fine esclusa. Calcolare i limiti nel fuso aziendale prima della conversione. Testare ora legale, fine mese e date prive di orario; un giorno locale non dura sempre ventiquattro ore.

    Risultato: casi di assegnazione ai periodi.

  3. 3

    Gestire gli arrivi tardivi

    Definire quali report possono cambiare e fino a quando. Conservare ricezione e identificatori per distinguere ritardo e duplicato. Una versione già distribuita richiede una revisione datata o una correzione esplicita.

    Risultato: politica delle revisioni.

  4. 4

    Confrontare perimetri uguali

    Allineare periodi, stati aziendali e chiusure. Separare ordini creati, pagati, annullati e rimborsati. Esaminare i record vicini al confine del giorno prima di concludere che la raccolta ha perso dati.

    Risultato: riconciliazione dei record discordanti.

  5. 5

    Provare la ricostruzione

    Ripetere un intervallo con cambio d’ora ed eventi tardivi. Spiegare ogni differenza a parità di chiusura. Mostrare fuso, aggiornamento e stato provvisorio o chiuso accanto ai risultati.

    Risultato: test riproducibile e legenda.

Caso di accettazione riproducibile

Esempio fittizio: questi dati non descrivono clienti o risultati osservati.

Vedi dati del caso
{
    "event_time": "2026-10-08T23:30:00Z",
    "report_zone": "UTC+02:00",
    "local_time": "2026-10-09T01:30:00+02:00"
}

Decisione attesa

L’evento appartiene al 9 ottobre nel fuso indicato; conserva anche l’istante UTC.

Procedura di verifica

  1. Fissa fuso del rapporto e istante.
  2. Riproduci evento vicino alla mezzanotte.
  3. Conserva UTC, data locale e chiusura. Includere un’ora locale ambigua al cambio d’ora; conservare offset e zona invece di dedurre un istante.

PostgreSQL — Date/time types

Foglio di lavoro riutilizzabile

Completare con le proprie osservazioni autorizzate. Questi campi costituiscono un modello di lavoro, non risultati osservati.

CampoInformazioni da registrare
CalendarioFuso, inizio settimana e limiti
OrariEvento, ricezione, modifica e precisione
ChiusuraSnapshot, finestra di revisione e ritardi
ConfrontoStati, identificatori e differenze spiegate

Esempio pratico fittizio

Situazione illustrativa

Esempio fittizio: due team confrontano vendite del lunedì usando UTC e Europe/Paris.

Decisione e prove attese

La verifica individua ordini al confine del giorno e adotta periodo aziendale e chiusura comuni.

Distinguere i meccanismi

MeccanismoScopoVerifica o limitazione
Data aziendaleAssegna attività a un calendarioNon è un istante senza convenzione
Ora dell’eventoMisura quando avviene l’attivitàPuò arrivare in ritardo
Ora di ricezioneDescrive freschezza della pipelineNon coincide necessariamente con l’attività

Indicatori di gestione

IndicatoreCosa misuraPrima azione
Ritardo di ricezioneTempo fino alla disponibilitàDefinire la finestra provvisoria
RevisioniVariazioni fra versioni confrontabiliSeparare ritardi e correzioni
Scarti al confineRecord assegnati a giorni diversiCorreggere la convenzione

Errori comuni

  • Non è un istante senza convenzione
  • Può arrivare in ritardo
  • Non coincide necessariamente con l’attività

Domande frequenti

Basta convertire tutto in UTC?

No. Giorni, settimane e chiusure richiedono comunque calendario e fuso aziendale.

Perché il totale cambia dopo l’export?

Possono arrivare eventi, correzioni o nuovi stati. Verificare chiusura e politica di revisione.

Un evento tardivo è un duplicato?

No. Confrontare identificatore e contenuto; il ritardo non dimostra ripetizione.

Cronologie: UTC e fusi orari

Le note dettagliate di questa edizione sono disponibili in inglese.

Reliable timelines separate wall time, instants and receipt

In cyber logs, OSINT collection or dashboards, two lines displaying 02:30 can represent different instants. Receipt order can also differ from event order. Preserving both axes avoids inventing a causal sequence from a simple string sort.

Fictional offline exercise for Europe/Paris, using IANA 2026e rules supplied by tzdata 2026.5. March and October 2026 clock changes are acceptance cases. The times and six deliveries describe no real incident. A correct conversion establishes neither source-clock accuracy nor log authenticity.

Four pieces of information that do not replace each other

Four pieces of information that do not replace each other
InformationWhat it providesWhat it does not establish
Original textReceived representation, precision and any supplied offset.Clock accuracy or event identity.
UTC instantA comparable position on the time axis.The business calendar or original zone.
Named zone and versionCivil-time rules applied to a local time.Device synchronization.
Observation timeWhen the collector saw the line according to its own clock.When the event actually occurred.
The same 02:30, two instants 60 minutes apart
The same 02:30, two instants 60 minutes apart On 25 October 2026 in Europe/Paris, 02:30 with +02:00 corresponds to 00:30 UTC and fold 0; 02:30 with +01:00 corresponds to 01:30 UTC and fold 1. The instants are 60 minutes apart. Europe/Paris · 2026-10-25 · 02:30:00 First occurrence · fold 0 02:30:00 +02:00 00:30:00 UTC 2026-10-25 Second occurrence · fold 1 02:30:00 +01:00 01:30:00 UTC 2026-10-25 60 min Compare UTC instants, beyond displayed wall times.

An ambiguous local time remains undecidable without more information. The profile expects an explicit fold choice or an offset consistent with the claimed zone. The diagram shows two instants, not a duplicate to delete. Computation uses UTC for elapsed durations and comparisons across the fold.

12 inputs and their normalization decisions

Two contracts are tested: local time plus a named zone, or an offset timestamp plus the zone it claims to represent. The teaching profile requires YYYY-MM-DDTHH:MM:SS, with Z or ±HH:MM in the second contract. Fractions, leap seconds, lowercase variants and -00:00 are outside this profile; that does not declare them all invalid under RFC 3339.

T01 · Repeated time without a choice
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Selected instant : No instant selected

Clarify: two possible instants

Two UTC candidates exist. Neither is selected by default: the record needs clarification rather than an invented instant.

T02 · First occurrence selected
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
0

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Selected instant : 2026-10-25T00:30:00Z

Temporal interpretation resolved

fold 0 selects the first 02:30 occurrence: +02:00 and 00:30 UTC. This choice must come from producer information, beyond a collector’s hidden preference.

T03 · Second occurrence selected
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
1

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Selected instant : 2026-10-25T01:30:00Z

Temporal interpretation resolved

fold 1 selects the second occurrence: +01:00 and 01:30 UTC. Its wall display matches T02, but the instant is one hour later.

T04 · Missing spring local time
Received text
2026-03-29T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

No valid local candidate

Selected instant : No instant selected

Reject: missing local time

On 29 March 2026, 02:30 does not exist in this zone. A round trip through UTC returns no candidate to that local time. Merely attaching tzinfo does not validate it.

T05 · Unambiguous local time
Received text
2026-10-22T10:00:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

  • 2026-10-22T08:00:00Z · 2026-10-22T10:00:00+02:00 · fold 0

Selected instant : 2026-10-22T08:00:00Z

Temporal interpretation resolved

These rules yield one UTC position. Acceptance covers temporal interpretation. Device-clock accuracy remains unverified.

T06 · Unknown zone
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Pariss
Fold choice
Not supplied

Valid UTC candidates

Check not performed

Selected instant : No instant selected

Reject: unknown zone

Europe/Pariss is unavailable in the supplied rules. The profile rejects it instead of silently substituting the server zone.

T07 · Fold value outside the contract
Received text
2026-10-25T02:30:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
2

Valid UTC candidates

Check not performed

Selected instant : No instant selected

Reject: invalid fold choice

The profile accepts only 0, 1 or no fold choice. It rejects 2 before selection.

T08 · Impossible calendar date
Received text
2026-02-30T10:00:00
Contract
Local time + zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

Check not performed

Selected instant : No instant selected

Reject: impossible date or time

30 February 2026 is not a calendar date. A correctly shaped string is insufficient to produce an instant.

T09 · Consistent +02:00 offset
Received text
2026-10-25T02:30:00+02:00
Contract
Offset timestamp + claimed zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Instant carried by the offset : 2026-10-25T00:30:00Z

Conversion back to the claimed zone : 2026-10-25T02:30:00+02:00

Selected instant : 2026-10-25T00:30:00Z

Temporal interpretation resolved

+02:00 matches the first occurrence of this Paris wall time. It yields the same instant as T02.

T10 · Consistent +01:00 offset
Received text
2026-10-25T02:30:00+01:00
Contract
Offset timestamp + claimed zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

  • 2026-10-25T00:30:00Z · 2026-10-25T02:30:00+02:00 · fold 0
  • 2026-10-25T01:30:00Z · 2026-10-25T02:30:00+01:00 · fold 1

Instant carried by the offset : 2026-10-25T01:30:00Z

Conversion back to the claimed zone : 2026-10-25T02:30:00+01:00

Selected instant : 2026-10-25T01:30:00Z

Temporal interpretation resolved

+01:00 matches the second occurrence. It yields T03’s instant, which differs from T09.

T11 · Offset inconsistent with the zone
Received text
2026-03-29T02:30:00+01:00
Contract
Offset timestamp + claimed zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

No valid local candidate

Instant carried by the offset : 2026-03-29T01:30:00Z

Conversion back to the claimed zone : 2026-03-29T03:30:00+02:00

Selected instant : No instant selected

Reject: time and zone disagree

The +01:00 string denotes a calculable instant, but conversion to Europe/Paris displays 03:30 with +02:00. It contradicts a claim of Paris local time 02:30. Rejection applies to this zone claim; the timestamp can still have meaning in another context.

T12 · Missing offset in the second contract
Received text
2026-10-25T02:30:00
Contract
Offset timestamp + claimed zone
Claimed zone
Europe/Paris
Fold choice
Not supplied

Valid UTC candidates

Check not performed

Selected instant : No instant selected

Reject under the format contract

Offset mode requires an explicit offset. The same text can belong to T01’s local contract, but switching contracts must be explicit.

Three civil days, three UTC durations

Three civil days, three UTC durations
Europe/Paris dateInclusive UTC startExclusive UTC endElapsed duration
2026-03-292026-03-28T23:00:00Z2026-03-29T22:00:00Z23 h
2026-10-222026-10-21T22:00:00Z2026-10-22T22:00:00Z24 h
2026-10-252026-10-24T22:00:00Z2026-10-25T23:00:00Z25 h

Boundaries are consecutive local midnights converted separately to UTC. A civil day and a duration of 24 hours serve different needs. This table changes no organizational cutoff rule.

Six fictional deliveries, four event identifiers

Studied window: 25 October 2026, from 00:00 UTC inclusive to 02:00 UTC exclusive. Clocks are assumed accurate only for the exercise. Each snapshot uses deliveries observed strictly before its cutoff. Receipt does not change an event’s time-window assignment.

Six fictional deliveries, four event identifiers
Delivery / eventEvent instant UTCObservation UTCRole in the exercise
R01 / E012026-10-25T00:50:00Z2026-10-25T00:51:00ZInitial observation · 2026-10-25T02:50:00+02:00
R02 / E022026-10-25T01:10:00Z2026-10-25T01:11:00ZInitial observation · 2026-10-25T02:10:00+01:00
R03 / E032026-10-25T01:30:00Z2026-10-25T02:20:00ZLate arrival · 2026-10-25T02:30:00+01:00
R04 / E042026-10-25T02:00:00Z2026-10-25T02:01:00ZExclusive end boundary · 2026-10-25T03:00:00+01:00
R05 / E022026-10-25T01:10:00Z2026-10-25T02:10:00ZIdentical E02 redelivery · 2026-10-25T02:10:00+01:00
R06 / E012026-10-25T00:55:00Z2026-10-25T02:30:00ZConflicting E01 version · 2026-10-25T02:55:00+02:00

R01 displays 02:50 with +02:00 and R02 displays 02:10 with +01:00. String sorting puts R02 before R01; instant sorting puts E01 at 00:50 UTC before E02 at 01:10 UTC. Computed chronological order still establishes no causal relationship.

Three dated states: explain 2 → 3 → 2

Three dated states: explain 2 → 3 → 2
State / UTC cutoffIncluded eventsCountExplanation
S1 · 2026-10-25T02:00:00ZE01, E022S1: E01 and E02 are known and inside the window. E03 has not yet been observed.
S2 · 2026-10-25T02:25:00ZE01, E02, E033S2: E03 explains the increase from 2 to 3. R05 identically redelivers E02, counted once; E04 remains at the exclusive end.
S3 · 2026-10-25T02:40:00ZE02, E032S3: R06 reveals two different temporal contents for E01. The local policy sends both versions to review and removes E01 from the included count, now 2. This quarantine policy belongs to the exercise; other workflows may choose differently.

An event identifier deduplicates here only when UTC instant and kind match. The same identifier with changed content triggers review. The exercise preserves the conflict instead of overwriting a version or deleting it without a trace. Earlier snapshots retain their dates. These are fictional exercise counts, with no measurement of real activity.

Six records to reconstruct the timeline

  • Original text and received precision, retained with a protected source reference.
  • Normalized instant, claimed zone, rule version and ambiguous/missing-time decision.
  • Observation time and the component whose clock produced it, separately from event time.
  • Stable identifiers and the rule separating identical redelivery from conflicting versions.
  • Inclusive/exclusive boundaries, cutoff and included records for every published snapshot.
  • Unverified clock limits: synchronization, drift, precision or causal order.

Conversions use the Europe/Paris file bundled with tzdata 2026.5, IANA 2026e. Clarification, format and quarantine decisions are a local editorial method. OpenTelemetry distinguishes source and observation time; this page claims neither a conforming OTLP record nor verification of real clocks.

Python 3.12.14 · tzdata 2026.5 · IANA 2026e

Primary sources and rule version

  • IETF · RFC 3339 · Standards Track · July 2002
    §4.2 Numeric offsets · §5.1 Ordering · §5.6 Internet timestamp format
  • Python · PEP 495 · Final · Python 3.6+ · checked 2026-10-22
    Fold and gap · constructors do not validate missing times · temporal arithmetic
  • Python 3.12 · zoneinfo · Python 3.12 documentation · checked 2026-10-22
    fold · data sources · ZoneInfo.from_file
  • IANA · Time Zone Database 2026e · Release 2026e · 2026-09-29
    Versioned time-zone database · scope of the exercise
  • IANA · 2026e Europe rules · tzdb 2026e · source file
    Rule EU: March/October last Sunday at 01:00 UTC · Zone Europe/Paris
  • OpenTelemetry · Logs Data Model · Stable model · living documentation · checked 2026-10-22
    Timestamp: source clock · ObservedTimestamp: collection-system clock

Sources reviewed on

Riferimenti ufficiali

I riferimenti supportano il metodo. Adattare i controlli al proprio contesto; non costituiscono una certificazione. I titoli dei riferimenti originali e i documenti di origine potrebbero essere in un'altra lingua.

Riferimenti consultati il .