Monitoring & Logging Tools
Observing system health and capturing logs for debugging and alerting.
Partly. Hosts sign observations and keep hash-chained journals; `dh logs app` tails a replica over the mesh; the console shows the age of every value. There is no metrics history, alerting or telemetry export (a self-hosted metrics export is planned).
Monitoring vs. logging, and why both matter
Monitoring answers "is the system healthy right now" via numeric time-series (CPU%, request latency, error rate) that tools like Prometheus scrape and Grafana visualize, usually with alerting rules that page someone when a threshold is crossed. Logging answers "what exactly happened" -- discrete, timestamped events (a request came in, an exception was thrown) that you search after the fact to debug a specific incident. A mature setup has both: monitoring tells you something's wrong, logs tell you why.
Observing system health and capturing logs for debugging and alerting. Partly. Hosts sign observations and keep hash-chained journals; `dh logs app` tails a replica over the mesh; the console shows the age of every value. There is no metrics history, alerting or telemetry export (a self-hosted metrics export is planned).