Skip to main content
Version: 2.5.0

Data Model Overview

ChronoLog's data model organizes time-series log events from distributed HPC applications into a hierarchical structure. Events flow from client processes through a multi-tier distributed pipeline, ultimately reaching persistent storage. The model is designed to support high-throughput ingestion from many concurrent clients while preserving global event ordering.

Key Concepts

Client-oriented:

  • Chronicle — A named top-level container that groups related Stories. Identified by CityHash64(chronicleName).
  • Story — A time-series dataset within a Chronicle representing a logical event stream. Carries configurable attributes for indexing granularity, type, tiering policy, and access control.
  • Event — The atomic data unit, carrying a timestamp, client ID, event index, and an opaque payload. Globally ordered by EventSequence = (eventTime, clientId, eventIndex).

Internal:

  • StoryChunk — A time-windowed batch of Events [startTime, endTime). The unit of data movement through the distributed pipeline, merged from partial chunks produced by multiple ChronoKeepers. It is transparent to the users. It is only used in communications between ChronoKeeper and ChronoGrapher.
  • Archive — Historical storage associated with a Story, with user-defined metadata properties. It is another concept only visible to ChronoLog services. It is used to manage HDF5 files on the persistent storage.

For detailed definitions and configuration options, see Concepts.

Data Lifecycle

Events follow a well-defined path through the system. Client applications create Events and send them to ChronoKeeper processes running on compute nodes. ChronoKeepers batch these Events into StoryChunks during time-windowed acceptance periods. When the window closes, the StoryChunk is shipped to a ChronoGrapher process on a storage node, which merges partial chunks from different ChronoKeepers into a unified StoryPipeline. Finally, completed StoryChunks are extracted and persisted to the storage layer (HDF5 files). For a detailed walkthrough of this pipeline, see Distributed Story Pipeline.

Further Reading

TopicPage
Concept definitions and detailsConcepts
Distributed pipeline designDistributed Story Pipeline