Recursos · 82
Relatórios fiáveis: fusos horários, fechos e eventos tardios
Evitar dias deslocados, contagens duplicadas e comparações incoerentes entre exportações e painéis.
Atualizado · 7 min
O que este guia ajuda a alcançar
- Distinguir instantes e dias de negócio
- Definir limites
- Tratar chegadas tardias
- Comparar âmbitos equivalentes
- Testar reconstrução
Verificação rápida
- Converter tudo para UTC basta?
- Porque muda o total após exportar?
- Um evento tardio é duplicado?
Método passo a passo
- 1
Distinguir instantes e dias de negócio
Separar evento, receção, alteração e data de atividade. UTC não define sozinho o dia comercial de uma loja. PostgreSQL converte timestamp with time zone para UTC sem guardar o nome do fuso original; conservá-lo separadamente quando necessário.
Resultado: dicionário de datas e fusos.
- 2
Definir limites
Usar início incluído e fim excluído. Calcular limites no fuso de negócio antes de converter. Testar horário de verão, fim do mês e datas sem hora; um dia local nem sempre tem vinte e quatro horas.
Resultado: casos de atribuição a períodos.
- 3
Tratar chegadas tardias
Definir que relatórios podem mudar e até quando. Guardar receção e identificadores para distinguir atraso de duplicado. Uma versão distribuída exige revisão datada ou correção explícita.
Resultado: política de revisão.
- 4
Comparar âmbitos equivalentes
Alinhar períodos, estados de negócio e fechos. Separar encomendas criadas, pagas, canceladas e reembolsadas. Examinar registos próximos dos limites antes de concluir que a recolha perdeu dados.
Resultado: reconciliação de discrepâncias por registo.
- 5
Testar reconstrução
Repetir um intervalo com mudança de hora e eventos tardios. Explicar diferenças num fecho igual. Mostrar fuso, atualização e estado provisório ou fechado junto dos resultados.
Resultado: teste reproduzível e legenda.
Caso de aceitação reproduzível
Exemplo fictício: estes dados não descrevem clientes nem resultados observados.
Ver dados do caso
{
"event_time": "2026-10-08T23:30:00Z",
"report_zone": "UTC+02:00",
"local_time": "2026-10-09T01:30:00+02:00"
}Decisão esperada
O evento pertence a 9 de outubro no fuso indicado; conserve também o instante UTC.
Procedimento de verificação
- Fixe fuso do relatório e instante.
- Reproduza evento próximo da meia-noite.
- Conserve UTC, data local e fecho. Inclua uma hora local ambígua numa mudança de hora; preserve desvio e zona em vez de deduzir um instante.
Planilha reutilizável
Preencha com suas observações autorizadas. Estes campos são um modelo de trabalho, não resultados observados.
| Campo | Informações a serem registradas |
|---|---|
| Calendário | Fuso, início da semana e limites |
| Tempos | Evento, receção, alteração e precisão |
| Fecho | Snapshot, revisão e tratamento dos atrasos |
| Reconciliação | Estados, identificadores e diferenças explicadas |
Exemplo prático fictício
Situação ilustrativa
Exemplo fictício: duas equipas comparam vendas de segunda-feira usando UTC e Europe/Paris.
Decisão e evidências esperadas
A reconciliação identifica encomendas no limite do dia e fixa um período de negócio e um fecho comuns.
Distinguir os mecanismos
| Mecanismo | Finalidade | Verificação ou limitação |
|---|---|---|
| Data de negócio | Atribui atividade a um calendário | Não é um instante sem convenção |
| Hora do evento | Indica quando ocorreu a atividade | Pode chegar tarde |
| Hora de receção | Mostra atualização da pipeline | Não é necessariamente a data da atividade |
Indicadores de gestão
| Indicador | O que mede | Primeira ação |
|---|---|---|
| Atraso de receção | Tempo até à disponibilidade | Definir janela provisória |
| Revisões | Variações entre versões comparáveis | Separar atrasos de correções |
| Diferenças nos limites | Registos atribuídos a dias distintos | Corrigir a convenção temporal |
Erros comuns
- Não é um instante sem convenção
- Pode chegar tarde
- Não é necessariamente a data da atividade
Perguntas frequentes
Converter tudo para UTC basta?
Não. Dias, semanas e fechos continuam a exigir calendário e fuso de negócio.
Porque muda o total após exportar?
Podem entrar eventos, correções ou novos estados. Verificar fecho e política de revisão.
Um evento tardio é duplicado?
Não. Comparar identificador e conteúdo; o atraso não demonstra repetição.
Cronologias: UTC e fusos horários
As notas detalhadas desta edição estão disponíveis em inglês.
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
| Information | What it provides | What it does not establish |
|---|---|---|
| Original text | Received representation, precision and any supplied offset. | Clock accuracy or event identity. |
| UTC instant | A comparable position on the time axis. | The business calendar or original zone. |
| Named zone and version | Civil-time rules applied to a local time. | Device synchronization. |
| Observation time | When the collector saw the line according to its own clock. | When the event actually occurred. |
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 02026-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 02026-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 02026-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 02026-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 02026-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
| Europe/Paris date | Inclusive UTC start | Exclusive UTC end | Elapsed duration |
|---|---|---|---|
| 2026-03-29 | 2026-03-28T23:00:00Z | 2026-03-29T22:00:00Z | 23 h |
| 2026-10-22 | 2026-10-21T22:00:00Z | 2026-10-22T22:00:00Z | 24 h |
| 2026-10-25 | 2026-10-24T22:00:00Z | 2026-10-25T23:00:00Z | 25 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.
| Delivery / event | Event instant UTC | Observation UTC | Role in the exercise |
|---|---|---|---|
| R01 / E01 | 2026-10-25T00:50:00Z | 2026-10-25T00:51:00Z | Initial observation · 2026-10-25T02:50:00+02:00 |
| R02 / E02 | 2026-10-25T01:10:00Z | 2026-10-25T01:11:00Z | Initial observation · 2026-10-25T02:10:00+01:00 |
| R03 / E03 | 2026-10-25T01:30:00Z | 2026-10-25T02:20:00Z | Late arrival · 2026-10-25T02:30:00+01:00 |
| R04 / E04 | 2026-10-25T02:00:00Z | 2026-10-25T02:01:00Z | Exclusive end boundary · 2026-10-25T03:00:00+01:00 |
| R05 / E02 | 2026-10-25T01:10:00Z | 2026-10-25T02:10:00Z | Identical E02 redelivery · 2026-10-25T02:10:00+01:00 |
| R06 / E01 | 2026-10-25T00:55:00Z | 2026-10-25T02:30:00Z | Conflicting 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
| State / UTC cutoff | Included events | Count | Explanation |
|---|---|---|---|
| S1 · 2026-10-25T02:00:00Z | E01, E02 | 2 | S1: E01 and E02 are known and inside the window. E03 has not yet been observed. |
| S2 · 2026-10-25T02:25:00Z | E01, E02, E03 | 3 | S2: 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:00Z | E02, E03 | 2 | S3: 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
Referências oficiais
As referências apoiam o método. Adapte as verificações ao seu contexto; elas não são uma certificação. Os títulos das referências originais e os documentos de origem podem estar em outro idioma.
Referências consultadas em .
