Telemetry for Rust applications
Your Rust application has finally been deployed to production! Nice! But is it working?
This workshop will introduce you to a comprehensive toolkit to detect, troubleshoot and resolve issues in your Rust applications.
This workshop is designed for developers who are operating Rust services in production-like environments, or are preparing to do so.
Duration & location
The workshop takes place over two days:
Number of participants
To ensure the highest quality, we accept up to 15 participants.
This workshop is intended for developers who have some experience with Rust already.
We will send a detailed list of instructions for preparation, including the installation of tools, etc. Additionally, we will share a Github project with workshop materials. This information will be provided closer to the workshop date.
Structured logging (tracing)
An introduction to the tracing instrumentation library, covering both how to instrument your code (capturing fields, log levels, macros) and how to process the resulting telemetry data in your application (subscriber configuration, logging levels, log filtering).
We will cover Rust’s Error trait, with a focus on the information that can be retrieved and recorded in your logs; we will also spend some time on logging patterns (e.g. when should an error be logged?).
You should always manage to capture details about what went wrong, even if it’s due to an uncaught panic rather than an error. We will review panic hooks and integrate them in our tracing setup.
Structured logs are important, but they don’t tell the full story. We will look at how to capture metric data using the metrics library, as a tool for designing alarms as well troubleshooting faulty behaviour.