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.
I usually avoid workshops. The pace of more than 3 people is hard to sync: I always feel rushed in some bits, slowed down in others. Luca fixed that with his code-centric approach [...] Here I was able to fully use the time and the knowledge of the trainer!
Additional Information
Duration & location
The workshop takes place over two days:
This allows participants to use the mornings to exercise or keep up with work. The workshop is run completely online and remote.Number of participants
To ensure the highest quality, we accept up to 15 participants.
For who?
This workshop is intended for developers who have some experience with Rust already.
Prerequisites
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.
Workshop overview
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).
Error handling
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?).
Panic handling
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.
Metrics
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.
