ores.telemetry.core
Table of Contents
2. Summary
ores.telemetry.core is the observability library for ORE Studio. It provides
structured logging via Boost.Log with trace and span ID correlation (aligned
with OpenTelemetry semantics), the messaging types the service exchanges, and
domain types for log records and resource identity (host, service, version).
All other components link against this library to emit structured, correlated
logs, and the sink the host installs decides where a record goes: the database
sink writes it through ores.telemetry.database.
3. Inputs
- Log events emitted by other components via the Boost.Log sink interface.
- Configuration for the log level, the service identity and the record's source.
4. Outputs
- Structured
log_recordobjects handed to the sink the host installs. - The message and payload types the six
telemetry.v1.>subjects carry, generated from the three operation models.
5. Entry points
include/ores.telemetry.core/log/— Boost.Log initialisation, the lifecycle manager and the sinks.include/ores.telemetry.core/generators/— trace/span ID generators.include/ores.telemetry.core/domain/— log_record, trace_id, span_id, resource.include/ores.telemetry.core/messaging/— the generated protocol headers.include/ores.telemetry.core/exporting/— logging configuration and options.
6. Dependencies
- Boost.Log — structured logging sink infrastructure.
7. See also
- ores.telemetry.service — NATS service that receives and persists log records.
- ores.telemetry.database — persistence layer for telemetry records.
- ores.telemetry Messaging Reference — NATS protocol for log forwarding.
