#service-state #web-server #service-health #task #service-server

service-probe

Probe for querying service state through a minimal HTTP service

6 releases

Uses new Rust 2024

0.3.0 Nov 7, 2025
0.2.1 Jan 31, 2025
0.2.0 Dec 11, 2024
0.1.2 Nov 28, 2024

#354 in HTTP server

Download history 1741/week @ 2025-08-16 1581/week @ 2025-08-23 1711/week @ 2025-08-30 1367/week @ 2025-09-06 1483/week @ 2025-09-13 1564/week @ 2025-09-20 1723/week @ 2025-09-27 1014/week @ 2025-10-04 1284/week @ 2025-10-11 1481/week @ 2025-10-18 1711/week @ 2025-10-25 3163/week @ 2025-11-01 1589/week @ 2025-11-08 1896/week @ 2025-11-15 1277/week @ 2025-11-22 2345/week @ 2025-11-29

7,575 downloads per month

MIT/Apache

12KB
181 lines

Service probe

This crate provides an easy way to start a HTTP server that can be used for making the status of a service transparent to observers. The main use case is to communicate information about the health status of a service in containerized environments.

Tasks and synchronization throughout this crate uses tokio functionality, so the runtime must be present and running when the functions of this crate are called.

To start the service probe, add the following code to your service:

use service_probe::{start_probe, ServiceState, set_service_state};

// The probe server is started in the background. Up signals that the services is starting.
start_probe([0u8, 0, 0, 0], 11333, ServiceState::Up).await.unwrap();

// If everything is ready, we set the state to ready.
set_service_state(ServiceState::Ready);

Dependencies

~4–16MB
~158K SLoC