You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Exporting runtime telemetry (OpenTelemetry / ClickHouse) from the hub
#1760
we know you from YouTube and the vlog series, much appreciated. A friend and I are building an observability platform and have been exploring how observability carries over to industry and shop floors, which is how we ended up reading through control, qitech_framework and qitech_lib. We like how much telemetry the runtime already produces: RuntimeReport carries cycle timings, log records, runtime events, measurement snapshots and the config/state property journals, and the EtherCAT HAL keeps AL transition reports.
Today all of that stays on the machine (fmt logs to journald, the report feeds the UI). We would like to understand whether an optional export path fits your roadmap:
A hub listener (via HubConfiguration::listener) that maps RuntimeReport to OTLP off the realtime thread: LogRecord to logs, TimingsReport to a cycle-time histogram and overrun counter, measurements to gauges, property journals and commands to events.
tracing-opentelemetry on the hub, so a UI request can be followed into the runtime request queue.
Or, if you prefer, finishing the ClickHouse module in the hub instead of OTLP.
Questions:
Is this something you would accept upstream as an opt-in crate or feature, or would you rather keep it out of tree?
Is the ClickHouse work in qitech_framework_hub/legacy paused on purpose, and is there a target design?
Are there constraints on the realtime side we should know about beyond keeping allocations and locks off the loop thread?
Side note: TimingsReport::duration_avg in qitech_framework_core/src/report/mod.rs divides duration_peak by cycle_count; it looks like it should be duration_total. Happy to send a PR.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi QiTech team,
we know you from YouTube and the vlog series, much appreciated. A friend and I are building an observability platform and have been exploring how observability carries over to industry and shop floors, which is how we ended up reading through control, qitech_framework and qitech_lib. We like how much telemetry the runtime already produces:
RuntimeReportcarries cycle timings, log records, runtime events, measurement snapshots and the config/state property journals, and the EtherCAT HAL keeps AL transition reports.Today all of that stays on the machine (fmt logs to journald, the report feeds the UI). We would like to understand whether an optional export path fits your roadmap:
HubConfiguration::listener) that mapsRuntimeReportto OTLP off the realtime thread:LogRecordto logs,TimingsReportto a cycle-time histogram and overrun counter, measurements to gauges, property journals and commands to events.tracing-opentelemetryon the hub, so a UI request can be followed into the runtime request queue.Questions:
qitech_framework_hub/legacypaused on purpose, and is there a target design?Side note:
TimingsReport::duration_avginqitech_framework_core/src/report/mod.rsdividesduration_peakbycycle_count; it looks like it should beduration_total. Happy to send a PR.All reactions